loading kernel with fvwd-sl-console 5.5 is stuck at telnet

[arjanlugtenberg]

Yesterday I have decided to use the fvwd-sl-console program to fix my NAS (it was failing and since the latest Lacie firmware update it does not get an IP-adress from DHCP anymore)
At first attempt it was looking good, it was transferring the kernel image to a box fine.
after that it was rebooting and then the telnet client tried to connect to 192.168.0.252 (in my case)
That was timing out. I could not even ping that address.

After that I tried the process again and again but now the process is stuck during the U-boot process.
Also I have noticed that during a reboot of the NAS, the LED shortly is flashing red and blue.
This sounds to me there is a problem but I do not know what it is.

Can somebody here help me out what I can do next?

[fvdw]

When you selectected first install it has asked you to select a standalone kernel. Which one did you select? Could you see in the command window that the kernel was uploaded and the message that the kernel was started?

Ps a blue red flashing means that the bootloader can not find the disk. This can have various reasons, including a dective hdd.

[arjanlugtenberg]

I do not know exactly which image I selected. I am quite sure I selected the standalone image for kirkwood.

It could also be that I have used the image "UIMAGE-3142-NWSP2CL-2"

It now looks like I can not load another kernel from the fvwd-sl-console.
Looks like the ethernet port is not working anymore or is not holding the IP-adress 192.168.0.252 during booting.

Is there a way I can solve this with taking out the HDD and fixing it in ubuntu? Or did I damage something on the box itself?

[arjanlugtenberg]

I also have read you can connect to the box via a serial cable. Is that a possible solution for my situation?

[fvdw]

I do not know exactly which image I selected. I am quite sure I selected the standalone image for kirkwood.

It could also be that I have used the image "UIMAGE-3142-NWSP2CL-2"

It now looks like I can not load another kernel from the fvwd-sl-console.
Looks like the ethernet port is not working anymore or is not holding the IP-adress 192.168.0.252 during booting.

Is there a way I can solve this with taking out the HDD and fixing it in ubuntu? Or did I damage something on the box itself?

Then repeat the action on the vdws-sl console , but to test loading of a standalone kernel choose as action "load and start standalone kernel" and choose this kernel :
UIMAGE-3142-NWSP2CL-KIRKWOOD-24-standalone

Be sure that the tftp server and clunc may pass your firewall, or disable your firewall temporarily, if you do not do that then transfer of the kernel will fail

Please note this standalone kernel will run fully from RAM and even with a broken disk the kernel should load and start the telnet server. That will enable you to connect with the telnet client and investigate what is wrong with the disk ;)

[arjanlugtenberg]

I finally found out why it was failing...
My router UTP LAN ports are defect.

I am now directly connected with a UTP between laptop and NAS. Stupid I should have thought of this before as a network engineer... ;)

But now I am on the device and can investigate further...

This is was fdisk -l is telling me:

Code: Select all

root@fvdw-sta-kirkwood:/ # fdisk -l

Disk /dev/mtdblock0: 0 MB, 512000 bytes
255 heads, 63 sectors/track, 0 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Disk /dev/mtdblock0 doesn't contain a valid partition table

Disk /dev/mtdblock1: 0 MB, 4096 bytes
255 heads, 63 sectors/track, 0 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Disk /dev/mtdblock1 doesn't contain a valid partition table


Disk /dev/sda: 2000.3 GB, 2000398934016 bytes
255 heads, 63 sectors/track, 243201 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot      Start         End      Blocks  Id System
/dev/sda1               1      243202  1953514583+ ee EFI GPT

Last couple of lines of dmesg:

Code: Select all

[  890.891479] ata1: link is slow to respond, please be patient (ready=0)
[  895.391481] ata1: SRST failed (errno=-16)
[  895.395514] ata1: hard resetting link
[  900.941480] ata1: link is slow to respond, please be patient (ready=0)
[  905.441479] ata1: SRST failed (errno=-16)
[  905.445509] ata1: hard resetting link
[  910.991481] ata1: link is slow to respond, please be patient (ready=0)
[  940.451488] ata1: SRST failed (errno=-16)
[  940.455514] ata1: limiting SATA link speed to 1.5 Gbps
[  940.460658] ata1: hard resetting link
[  945.471488] ata1: SRST failed (errno=-16)
[  945.475517] ata1: reset failed, giving up
[  945.479539] ata1.00: disabled
[  945.482559] ata1.00: device reported invalid CHS sector 0
[  945.488009] ata1: EH complete
[  945.491044] sd 0:0:0:0: [sda] Unhandled error code
[  945.495852] sd 0:0:0:0: [sda] 
[  945.498999] Result: hostbyte=0x04 driverbyte=0x00
[  945.503704] sd 0:0:0:0: [sda] CDB:
[  945.507186] cdb[0]=0x28: 28 00 00 00 00 00 00 00 20 00
[  945.512529] end_request: I/O error, dev sda, sector 0
[  945.517567] Buffer I/O error on device sda, logical block 0
[  945.523150] Buffer I/O error on device sda, logical block 1
[  945.528713] Buffer I/O error on device sda, logical block 2
[  945.534297] Buffer I/O error on device sda, logical block 3
[  945.540075] sd 0:0:0:0: [sda] Unhandled error code
[  945.544887] sd 0:0:0:0: [sda] 
[  945.548028] Result: hostbyte=0x04 driverbyte=0x00
[  945.552734] sd 0:0:0:0: [sda] CDB:
[  945.556215] cdb[0]=0x28: 28 00 00 00 00 00 00 00 08 00
[  945.561552] end_request: I/O error, dev sda, sector 0
[  945.566589] Buffer I/O error on device sda, logical block 0

Will look myself also what i can do with this but if you/someone can help me with some steps that would be nice.

[fvdw]

I am afraid you drive is defective when seeing this output.
It has a GPT partion table so use the command gdisk to see the partition table

Code: Select all

gdisk -l /dev/sda

[arjanlugtenberg]

Code: Select all

root@fvdw-sta-kirkwood:/ # gdisk -l /dev/sda
GPT fdisk (gdisk) version 0.8.5

Warning! Read error 5; strange behavior now likely!
Warning! Read error 5; strange behavior now likely!
Partition table scan:
  MBR: not present
  BSD: not present
  APM: not present
  GPT: not present

Creating new GPT entries.
Disk /dev/sda: 3907029168 sectors, 1.8 TiB
Logical sector size: 512 bytes
Disk identifier (GUID): 00000000-0000-0000-0000-000000000000
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 3907029134
Partitions will be aligned on 2048-sector boundaries
Total free space is 3907029101 sectors (1.8 TiB)

Number  Start (sector)    End (sector)  Size       Code  Name

Is it worth a try to completely format the disk?
Or is my HDD too damaged for that?

[Jocko]

Hi arjanlugtenberg,

In my opinion, you should extract the disk and plug it on your laptop to make some SMART checks (with fvdw-sl console you can not do a SMART control)

I think your disk is dead or pre-failure

[arjanlugtenberg]

Oke thanks.
Yesterday it was behaving strangely in my PC with ubntu on it. So this HDD is not reliable anymore.

I am considering to buy a Seagate NAS HDD (ST2000VN000)
Anyone has experience with this internal HDD?