not booting after power failure

[kuzanagi88]

still the same result. The disk with the original partitions also isn't recognized. Will that work when the nas is flashed?
i'll check on getting the original up again. I don't see another reason port 23 should be closed..

maybe i just bricked it somehow? will check another power adapter, has done wonders for me in the past.

[fvdw]

very strange

The u-boot in flash is ok otherwise it wouldn't give you the the marvell> prompt
also your network card is working otherwise you could connect to it with the u-boot console or upload a file via tftp.
So if something is broken it must be something else that is not loaded by u-boot bit is loaded by the kernel. It could also be a RAM issue or a defective sata port making the kernel hang.

probably the only way to find out is hooking up a serial connector and see via output on the serial port (http://lacie.nas-central.org/wiki/Seria ... space_2%29) what is happening when the kernel is loaded.
What we do with the fvdw-sl console is almost the same but it use the netconsole instead of serial port. The commands given instruct u-boot to switch to netconsole output instead of serial port. The kernel itself has netconsole enabled. However before you get output from the kernel via the netconsole the kernel needs to have loaded the netconsole driver. If it hangs before the netconsole driver is loaded then you do not get any output.

You could do some test with u-boot console to see if the sata port has a problem
Put in a disk, connect to it with the u-boot console of the fvdw-sl console and give on the marvel prompt the command

Code: Select all

ide reset

and then

Code: Select all

ide part

The last command should list the partition table, the first one will mention if it has found or not a sata port.

[fvdw]

also read this
viewtopic.php?f=11&t=1082

You could have damaged the board when sliding the disk backwards from the connector, some smd's on the baod are easy to rip of...I have seen this several times.

[kuzanagi88]

Hi FVDW,

I allready checked the board for damages, but will check again with a magnifier tonight.
I'll also check if i can see the partitions and otherwise I can check if i can r/w the serial port. I think I have an FTDI FT232RL at home. Even with the right plug.

[kuzanagi88]

well, upon inspection the board seems fine. My usb2serial only support 5V. I tried a 3.3V connection with resistors, but no luck so far.

my hard disk is dead though, the sata connection somehome broke off. I cant seem to find the missing parts too.. Maybe my 1 year old kid has something to do with that, he really seems to enjoy throwing stuff like that around the house :)

I'm trying to decide whether to:
1. Buy a new 3TB disk to replace the 1.5TB disk i had.
2. Buy a new 3TB nas.
3. Buy a new 3TB usb disk to hook up to my raspberry pi media center. (so i can configure that as a nas/mediacenter)

The big problem with option 3 is the noise. Harddrives make alot of noise which i why i'd rather avoid having them in my living room. I do like the freedom the pi gives me though.

I saw you also live in the netherlands, if you want i can send you the empty nas if i decide to ditch it. I'm from Amsterdam btw.

[fvdw]

Maybe my 1 year old kid has something to do with that, he really seems to enjoy throwing stuff like that around the house

:disapprove

yes I am always interested to receive it if you decide to ditch it, only to see what is causing this very peculiar problem and see if this nas can be brought back to functioning again.

very odd that the standalone kernel cannot connect with telnet, it should work even without a disk. The serial port output could disclose where the kernel hangs. If I can make it work I also can return it to you.

You can sent me a pm if you want to go that route