Cannot install fvdw-sl. Tried both GPT and DOS partition

[mlundemann]

It is also stuck when trying to start the older kernel:

Code: Select all

Marvell>> tftpboot 0x800000 UIMAGE-3142-NWSP2CL-8
tftpboot 0x800000 UIMAGE-3142-NWSP2CL-8
Using egiga0 device
TFTP from server 192.168.1.201; our IP address is 192.168.1.252
Filename 'UIMAGE-3142-NWSP2CL-8'.
Load address: 0x800000
Loading: #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         ##############
done
Bytes transferred = 4727472 (4822b0 hex)
Marvell>> bootm
bootm
## Booting image at 00800000 ...
   Image Name:   Linux-3.14.2
   Created:      2015-09-03  19:30:38 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    4727408 Bytes =  4.5 MB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
OK
bootargs from environment variables : console=ttyS0,115200 netconsole=6666@192.1
68.1.252/,6666@192.168.1.201/ root=/dev/sda7 cap=gpt,lba64

Starting kernel ...

I will probably be able to get my hands on another SATA disk tomorrow. Should I try loading the UIMAGE-3142-NWSP2CL-14 from the u-boot console, with that other disk in the cloudbox?

[fvdw]

with the other disk just repeat the installation procedure using the installer and if it is succesful reboot and see if the the firmware comes up.

If not we can start to rpeat the steps we did this evening.

If the older kernel also does n't run a corrupt file is pobably not the cause, also the installer checks the md5sum of the kernel before writing it to disk, if the md5sum is not correct the installer will abort

The standalone kernel differs not so much from the normal kernel, it only carries an root file system with it that is loaded in ram and that is is used as root file system. The normal kernel tries to load the root file system form disk, if that fails it hangs but I would have expected that netconsole would have given at least some output when using the u-boot console method

Anyhow lets see tomorrow evening if using another disk solve the problem

[mlundemann]

Re-extracting the rar-files with another unrar-tool did not change anything, so I think you are right, that a corrupt file is not causing the problem.

I will try the install on another disk tomorrow and keep you posted!

[mlundemann]

Hi fvdw,

I found another disk and re-did the installation with that, and now it works like a charm. I think you're right, that I might have a corrupt Seagate disk. Running the short tests in the SeaTools for Windows did not indicate any errors, however, running the "Fix All -> Long" reported a problem, probably caused by bad sectors. I am trying to erase everything using the SeaTools utility at the moment.

[fvdw]

ok thx for the update, glad to hear that we seem to have found your problem. It is a pity to loose a 2TB disk but I would never use a disk that is suspected or had problems. I would scrap it. of course it is different when the data on it has no value or little value.