Save original firmware for later restoration

[Jocko]

Hi matzi,

In which slot, the disk with the new rcS is plugged?
With the timestamp and no list.log file, I assume it is in the 2th slot. This disk must be plugged in the 1st slot.

[matzi]

How many times in my life I will run into the same trap... (forgot permissions)

list.log:

brw-rw---- 1 root 0 8, 0 Jan 3 2008 /dev/sda
brw-rw---- 1 root 0 8, 1 Nov 16 2011 /dev/sda1
brw-rw---- 1 root 0 8, 2 Jan 3 2008 /dev/sda2
brw-rw---- 1 root 0 8, 3 Nov 16 2011 /dev/sda3
brw-rw---- 1 root 0 8, 4 Jan 3 2008 /dev/sda4
brw-rw---- 1 root 0 8, 5 Jan 3 2008 /dev/sda5
brw-rw---- 1 root 0 8, 6 Nov 16 2011 /dev/sda6
brw-rw---- 1 root 0 8, 7 Jan 3 2008 /dev/sda7
brw-rw---- 1 root 0 8, 8 Nov 16 2011 /dev/sda8
brw-rw-r-- 1 root 0 8, 16 Jan 3 2008 /dev/sdb
brw-r--r-- 1 root 0 8, 17 Jan 3 2008 /dev/sdb1
brw-r--r-- 1 root 0 8, 18 Jan 3 2008 /dev/sdb2
brw-r--r-- 1 root 0 8, 19 Jan 3 2008 /dev/sdb3
brw-r--r-- 1 root 0 8, 20 Jan 3 2008 /dev/sdb4
brw-r--r-- 1 root 0 8, 21 Jan 3 2008 /dev/sdb5
brw-r--r-- 1 root 0 8, 22 Jan 3 2008 /dev/sdb6
brw-r--r-- 1 root 0 8, 23 Jan 3 2008 /dev/sdb7

[matzi]

list log was made with only one disc in slot1

[Jocko]

Well, I think that we found the explanation.

Look at your previous post viewtopic.php?f=26&t=1860&start=80#p15099, the device node are swapped after chrooted the file system.

At booting, the minor number (0) for the first disk (sda) is the value of the minor number of sdb after chroot... the value should be 16 for sda.

So you must upgrade the installed firmware version on sda7 for both disk

Note: I am no longer here for one hour now...

[matzi]

OK, is there an Image for sda7, we have to consider my partition sizes. May I can mount an image and just transfer the files?

[Jocko]

Currently the firmware image size is 256MB so there is no issue with a size ~500MB (I don't think that the next firmware images sizes can be 512MB)

So you can keep your partitions table.

I already posted the firmware image for partition 7, here : viewtopic.php?f=26&t=1860&start=90#p15121

and so to upgrade the firmware on partition 7 on the not boot disk

Code: Select all

dd if=/path..to/xfvdw-sl-15-2-5big2-30mar2014.img of=/dev/sdb7

Repeat this command by swapping the disks.

See you later

[matzi]

Transferring the image to the disc breaks after about 64180kB. On the disc is resides as "xfvdw-sl-15-2-5big2-30mar2014.img.filepart". Can the archive be corrupt? I tried two times.

[matzi]

One thing I still do not understand: I ran into the problem when installing a second disc.
1 Situation second disc had all correct but empty partitions the system did not boot
2 Situation second disc was installed with fvdw console with nwsp2 software and then updated to 5big two software. This time it ran but obviously with the other system partition on the boot disc. How that?

Finally: May I now delete sdx6 on the second disc? (Not sure if I should anyway, it does not give more space for the shares)

[Jocko]

Transferring the image to the disc breaks after about 64180kB. On the disc is resides as "xfvdw-sl-15-2-5big2-30mar2014.img.filepart". Can the archive be corrupt? I tried two times.

You can check if there is an issue with their md5sum

Code: Select all

dc9a4c547be5c4f5ccd061fe8af1b6b4  xfvdw-sl-15-2-5big2-30mar2014.img
6517842b5010bd4bf1f034f1a177a2a4  xfvdw-sl-15-2-5big2-30mar2014.part01.rar
0cd4dc0bcf7e881b64a931f82d302302  xfvdw-sl-15-2-5big2-30mar2014.part02.rar


I download the file from the server (but with a ftp access of the provider) and the rar file are not corrupted.

I go to download from the standard way.

[Jocko]

One thing I still do not understand: I ran into the problem when installing a second disc.
1 Situation second disc had all correct but empty partitions the system did not boot
2 Situation second disc was installed with fvdw console with nwsp2 software and then updated to 5big two software. This time it ran but obviously with the other system partition on the boot disc. How that?

Finally: May I now delete sdx6 on the second disc? (Not sure if I should anyway, it does not give more space for the shares)

Previously, I thought that the NAS booted from the 2th disk but it's wrong. It starts from the 1st disk but when it wants to chroot the file system it tries to mount the firmware image from sdb1. if sdb1 is empty the boot script fails.

Indeed you can remove the kernel from sdb6