fvdw-sl-12-0 update failed?

[fvdw]

If you didn't do all that as mentioned in previous post I don't know why it refuse to complete boot.

There is a way to restore the firmware used when you did the first time install.
For this you need to take out the HDD and connect it to a PC running Linux.
When you have done that mount partition /dev/sdb7 (assuming sdb is the hard disk of the nwsp2 on your Linux PC). Go to the directory where you mounted this partition
You will see a directory with nam "lacie-boot" in the root file system of this partition. Delete it and put the HDD back in the nwsp2. Now it should boot with the first time install firmware you used. After that try the upgrade again. (This only works if you have set up the HDD according the instruction provide for first time install)

[hamcloak]

then its not completing boot procedure. :scratch
Did you modify yourself the main boot script (rcS) in /etc/init.d folder before doing the upgrade ?
Did you set the nwsp2 as specified in the how to guide with all the partions as mentioned (sda1,2,3,4,5,6,7,8) ?

Nope, I didn't modify the boot script, and as far as I know I made the partitions following the guide (not 100% sure but don't know why i shouldn't have).

[fvdw]

a last question, did you replace the mount binary ? To be able to run the upgrade installed via the web interface it will try to mount either sda1 or sda2 partition very early in the boot process, if that mount fails then the NAS will not boot

[hamcloak]

a last question, did you replace the mount binary ? To be able to run the upgrade installed via the web interface it will try to mount either sda1 or sda2 partition very early in the boot process, if that mount fails then the NAS will not boot

What do you mean by mount binary?
You helped me with the USB host settings, could that be the problem?
Maybe I remember something about adding an extra partition while setting it up, that was meant to serve my USB port (what didn't work afterwards).
I can't really remember how I made the partition, but i think this is the problem.

So I think the problem is caused by this extra (unused) partition. Now what do i have to do now?
To be sure, can I just install the fvdw-sl-11-0 without losing all my data?

[fvdw]

no this usb partition we made can not be the reason.

Follow the instruction I posted on taken out the disk and modifying partition /dev/sda7

As long as you don't change the partition table and do not touch /dev/sda8 your data will be fine and not lost. (All data you have put on the nwsp2 is stored on partition /dev/sda8)

--copy from previous post

There is a way to restore the firmware used when you did the first time install.
For this you need to take out the HDD and connect it to a PC running Linux.
When you have done that mount the partition /dev/sdb7 (assuming sdb is the hard disk of the nwsp2 on your Linux PC). Go to the directory where you mounted this partition
You will see a directory with name "lacie-boot" in the root directory of this partition. Delete it and put the HDD back in the nwsp2. Now it should boot with the first time install firmware you used. After that try the upgrade again. (This only works if you have set up the HDD according the instruction provide for first time install)

[hamcloak]

I fixed my NS2 yesterday by deleting the file in the 'lacie-boot' folder, super easy, thanks for that.

Still not managed to update it to fvdw-sl-12-0 though, there was one extra partition on '/dev/sdb9', I deleted this one and tried updating again, without success.
Do the blocks have to match exactly with the guide to successfully update the firmware?

[fvdw]

There should be no /dev/sdb9. It will not appear by itself so you must have created it in the past. But it doesn't matter if the nwsp2 boots when deleting the "lacie-boot" this partition is probably not the cause of your problem. There must be another reason. The block numbers not being exactly as in the how to guide also should be no problem But it makes me suspicious that you have set up the nwsp2 in a non standard way. Please post your partition table.

To make the nwsp2 boot after the upgrade it will try to mount either /dev/sda1 or /dev/sda2 on a folder /fvdw-chroot in the root file system of /dev/sda7. And boot the nas from the firmware present on sda1 or sda2 in a chrooted environment. If this mount fails then it won't boot. This can only happen if you modified the boot scripts or replaced the "mount" binary as present on /dev/sda7.

Anyhow to check if the mount fails you could try it yourself.
Boot the nas without the lacie-boot folder. Now it boots from sda7. Access the nwsp2 with putty and make a folder with name /test it using the command

Code: Select all

mkdir -p /test

Now mount /dev/sda1 on this folder using

Code: Select all

/bin/mount /dev/sda1 /test

If it fails it will give an error message. If no error is displayed then check if it is mounted by using the command

Code: Select all

mount

without anything behind it. It should list all mounted files system you should find /dev/sda mounted on /test in this list.
To check if the mount was succesfull type

Code: Select all

cd /test

and do a directory listing using command

Code: Select all

ls

.
You should see a fvdw-sl root file tree simailar as on sda7. In fact this is the root file system of /dev/sda1

If this works then the upgrade should work as well and the nas should boot unless you modified some file on sda7 such as the boot scripts. :tapfoot

[hamcloak]

There should be no /dev/sdb9. It will not appear by itself so you must have created it in the past. But it doesn't matter if the nwsp2 boots when deleting the "lacie-boot" this partition is probably not the cause of your problem. There must be another reason. The block numbers not being exactly as in the how to guide also should be no problem But it makes me suspicious that you have set up the nwsp2 in a non standard way. Please post your partition table.

To make the nwsp2 boot after the upgrade it will try to mount either /dev/sda1 or /dev/sda2 on a folder /fvdw-chroot in the root file system of /dev/sda7. And boot the nas from the firmware present on sda1 or sda2 in a chrooted environment. If this mount fails then it won't boot. This can only happen if you modified the boot scripts or replaced the "mount" binary as present on /dev/sda7.

Anyhow to check if the mount fails you could try it yourself.
Boot the nas without the lacie-boot folder. Now it boots from sda7. Access the nwsp2 with putty and make a folder with name /test it using the command

Code: Select all

mkdir -p /test

[...]

When I try to make this folder it gives me the message "No space left on device", even after a reboot.
How can I make this folder?

[fvdw]

aha then we found the cause of your problems

Apparently you stored something on the system partition filling all the free space. Then the new firmware will not be able to boot as it can not create a mountpoint to mount the system partition sda1 or sda2 and load the new firmware
Either you installed something, for instance an optware package (not recommended by the way), or you copied something to this partition. The system partition is only 200 MB it easy to fill up.

The solution, delete files you installed on sda7, be careful not to delete system files !
Or do a fresh install the firmware on sda7 using the image in the first time install package. Write again the disk image to sda7 and then upgrade to fvdw-sl-12-0