nwsp2 lite - stock Seagate AF HD 2TB not booting correctly

[frenbu]

The firmware image was corrupted, I downloaded and writed it again, the boot still hangs..... :laughat

here's the output of ext2ls:

Code: Select all

Marvell>> ext2ls ide 0:7 /etc/init.d
ext2ls ide 0:7 /etc/init.d
## Valid DOS partition found ##
<DIR>       4096 .
<DIR>       4096 ..
             700 rc.bootup2
           12172 rcS.copy
            5467 rc.bootup1
             700 rc.bootup2.copy
            3779 rc.banner
           12172 rcS
            3779 rc.banner.copy
            5467 rc.bootup1.copy


Notice the different size values of the files, could it be because you run a different version than mine (11.0)?

Also the corrupted firmware doesn't explain why my old WD boot (installation done in november 2012) hangs at the same point, this is driving me crazy... :shock:

[fvdw]

yes the size is different because it is a different version.

Are you sure that your kernel file is not corrupt as well ?
Indeed strange that the WD disk ran for a few weeks and now also refuses to boot. That could indicate a hardware problem

Are you sure that there is no trace of boot.log file in root directory (/) ?
if it is we could see were it halts. If it is not there then it halt before the file is created, meaning at the point were the kernel tries to mount /proc and /sysfs and need those to do anything else. No clue yet why it should be not able to mount those (or bad RAM ??)

To install a newer version you could download the xfvdw-sl-14-0 upgrade file for the nwsp2. The bin file is in fact a bz2 compressed archive
you can unpack it with tar -xjvf This will give you a bunch of files like the latest kernel and the disk image of fvdw-sl-14-0

Those you could use to write to the hdd and see if they will boot your nwsp2

[frenbu]

I've upgraded to fvdw-sl-14-0 the old WD HD but boot still fails... Kernel recognized, partitions ok, etc, etc, same "movie"
I also forgot to check latest boot.log written on partition 7 before upgrading :sob :sob :sob it should had been from the latest boot a week ago or so.

Seems that we are running out of ammo :corner and I think we are facing a sly hardware issue

If you wish i can send you by mail the nwsp2 to play around... with no HD ;)

[fvdw]

could be indeed a hardware issue.
If you wish I can prepare a kernel that is able to boot from memory (we will load it form usb) and that has a telnet daemon inside that would enable us to see if mounting of partitions and so is possible.

There is still something else, these lacie device have an eeprom that is used to influence power on and wake on lan features. It could be that this eeprom must be reset. I assume you didn't play with that.

If this all not work , yes then I would like to rweceive it and try to bring it back to live. Always in for a challenge.

[frenbu]

If you aren't tired we could try with the custom kernel and then with the eeprom reset - I have zero experience with this last operation :) but no problem about that.

Waiting for your istructions ;)

[fvdw]

pm sent with trial kernel

If you can get telnet access then we can start investigating
First command will be

Code: Select all

dmesg

to see kernel message stored during boot, this to judge if any component is not working
Next check if /proc and /sysfs are mounted
Easy to do by using

Code: Select all

cd /proc

and do a directory listing using

Code: Select all

ls

same for /sysfs, should list a lot of files, if no output is given then it is not mounted

if all this works and gives the normal output then try to mount sda7
create a mountpoint with

Code: Select all

mkdir sda

and mount it using

Code: Select all

mount /dev/sda7 /sda7

No check if we can read the rcS file

Code: Select all

cat/sda7/etc/init.d/rcS

To try to reset the eeprom you could use

Code: Select all

/sda7/sbin/sleepmode_config --disable-wol
/sda7/sbin/sleepmode_config --clear-sleepmode
/sda7/sbin/sleepmode_config --set-power-on

[/code]

[frenbu]

Bad news, the kernel loading via sdb6 hangs same as with the standard one.... :sob
And the usb start command hangs too, after issueing the command and waiting 10+ minutes:

Code: Select all

Marvell>> usb start
usb start
(Re)start USB...
USB:   scanning bus for devices...

:dontknow

Thanks for the help fvdw but i think this nwsp2 is hardware-fooling us ;)
Do you think eeprom reset is possible via u-boot?

[fvdw]

Maybe you didn't understand correctly the output in netconsole is the same but did you try to connect with telnet using the ip I specified ? This kernel will not load the firmware but just starts a telnet daemon from ram and has a version of busybox inside enabling us to give basic linux commands.

Last resort is using a kernel to produces also output when loaded via clunc. Will do some test this evening

The fact that the usb scan is not completed is a bad sign, does that also happens when no usb stick/disk is attached

[frenbu]

Don't worry i perfectly understood, i tried to connect via telnet to the ip you provided me, i connected my pc to a ethernet hub with the nas and assigned myself an address of the same network but there was no response and the usb scan fails also with no usb attached.

If you want to craft a kernel that produces output on the net console i'll try that also ;)

[fvdw]

the new kernel is in your pm box