Firmware backup error

[type-a1pha]

Code: Select all

Filesystem                Size      Used Available Use% Mounted on
/dev/sda9               825.5M    825.5M         0 100% /sda9


[fvdw]

thats odd I would have expected that it would be large enough

lets re-format it and try again

Code: Select all

umount /sda9
mke2fs-ext3 -j -m 0 /dev/sda9

when finished format

Code: Select all

mount /dev/sda9 /sda9

after that try again the dd command as I posted earlier

[type-a1pha]

Code: Select all

root@fvdw-sta-kirkwood:/ # umount /sda9
root@fvdw-sta-kirkwood:/ # mke2fs-ext3 -j -m 0 /dev/sda9
mke2fs 1.41.14 (22-Dec-2010)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=0 blocks, Stripe width=0 blocks
54768 inodes, 218877 blocks
0 blocks (0.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=226492416
7 block groups
32768 blocks per group, 32768 fragments per group
7824 inodes per group
Superblock backups stored on blocks:
        32768, 98304, 163840

Writing inode tables: done                           
Creating journal (4096 blocks): done
Writing superblocks and filesystem accounting information: done

This filesystem will be automatically checked every 31 mounts or
180 days, whichever comes first.  Use tune2fs -c or -i to override.
root@fvdw-sta-kirkwood:/ # mount /dev/sda9 /sda9
root@fvdw-sta-kirkwood:/ # dd if=/dev/sda8 of=/sda9/lacie-partition8.img
dd: writing '/sda9/lacie-partition8.img': No space left on device
1687249+0 records in
1687248+0 records out
863870976 bytes (823.9MB) copied, 91.275193 seconds, 9.0MB/s
root@fvdw-sta-kirkwood:/ # ls -al /sda9
total 844472
drwxr-xr-x    3 root     root          4096 Sep 28 20:37 .
drwxrwxrwt   13 root     root           360 Sep 28 19:57 ..
-rw-r--r--    1 root     root     863870976 Sep 28 20:39 lacie-partition8.img
drwx------    2 root     root         16384 Sep 28 20:37 lost+found
root@fvdw-sta-kirkwood:/ # df -h
Filesystem                Size      Used Available Use% Mounted on
/dev/sda9               825.5M    825.5M         0 100% /sda9
root@fvdw-sta-kirkwood:/ #


Maybe we could use sda2? At least to check how much space lacie-partition8.img is going to take? As I said my NAS is formatted so there's no data saved on it.

[fvdw]

yes you could use sda2 if it mounts, it should already be formatted in xfs
So try it mounts and then write the image to that partition ( I think I have added xfs support to the standalone kernel)

Code: Select all

mkdir sda2
mount /dev/sda2 /sda2

afterwards you can sent it to the pc running fvdw-sl console using

Code: Select all

tftp -l /sda2/lacie-partition8.img -r lacie-partition8.img -p ip-pc

NOTE: replace ip-pc in this command by the actual ip of your pc running the fvdw-sl console

[type-a1pha]

It worked and the result is:

Code: Select all

root@fvdw-sta-kirkwood:/ # mkdir sda2
root@fvdw-sta-kirkwood:/ # mount /dev/sda2 /sda2
root@fvdw-sta-kirkwood:/ # tftp -l /sda2/lacie-partition8.img -r lacie-partition8.img -p 192.168.0.2
lacie-partition8.img 100% |****************************************************************|   831M  0:00:00 ETA
root@fvdw-sta-kirkwood:/ # ls -al /sda2
total 851416
drwxr-xr-x    9 root     root           127 Sep 28 21:06 .
drwxrwxrwt   14 root     root           380 Sep 28 21:22 ..
drwxr-xr-x    2 root     root             6 Sep 27 15:44 afp_db
drwxr-xr-x    2 root     root             6 Sep 27 15:44 autoupdate
drwxr-xr-x    2 root     root             6 Sep 27 15:44 images
-rw-r--r--    1 root     root     871847424 Sep 28 21:07 lacie-partition8.img
drwxr-xr-x    4 root     root            22 Sep 27 15:44 shares
drwxr-xr-x    2 root     root             6 Sep 27 15:43 tmp
drwxr-xr-x    2 root     root             6 Sep 27 15:44 torrent_dir
drwxr-xr-x    6 root     root            68 Sep 27 15:44 var
root@fvdw-sta-kirkwood:/ # df -h
Filesystem                Size      Used Available Use% Mounted on
/dev/sda9               825.5M    825.5M         0 100% /sda9
/dev/sda2                 1.8T    863.7M      1.8T   0% /sda2
root@fvdw-sta-kirkwood:/ #


Thank you so much for the help.
I will now try to install the new firmware!

P.S.: What is the purpose of sda9 and sda10 in the standard NAS configuration?

[fvdw]

thanks for pointing us to this problem. I will adapt the script to use sda2. In the past the standalone kernel did not support xfs.

P.S.: What is the purpose of sda9 and sda10 in the standard NAS configuration?

sda9 is used for upgrades of the lacie firmware, sda10 may contain an upgrade of the kernel lacie is using

[lamosca01isa]

Hola! Me da el mismo error que el compañero al hacer un backup del firmware. Sigo los pasos descrito. Me podrían ayudar en lo que tendría que corregir para que pueda realizar el backup correctamente? Gracias y un saludo!

Upload the lacie-firmware-backup to the NAS by entering in telnet client window:

tftp -r lacie-firmware-backup.sh -l lacie-firmware-backup -g ip-of-your-pc

Replace ip-of-your-pc by the actual ip address of your PC, it is mentioned in the main fvdw-sl-console window.

The reason why the script is not included in the kernel is that is subject to change (optimization)
and can be changed in future without need to recompile the standalone kernel.

(9) Make the installer script executable
After the script is transferred to the nas make it executable by entering in the telnet client:

chmod 755 lacie-firmware-backup

(10) Start the installer by entering in the telnet client:

/lacie-firmware-backup ip-pc

(replace ip-pc by the actual ip address of your pc

[Jocko]

Hi lamosca01isa,

:scratch if you already installed fvdw-sl the Lacie partitions exist no longer :scratch

[lamosca01isa]

Hi lamosca01isa,

:scratch if you already installed fvdw-sl the Lacie partitions exist no longer :scratch

Hola! Gracias por responder. Ahora mismo tengo puesto el disco original del lacie network space 2 por lo que me dispongo a realizar un backup. Antes en otro instale el fvdw-sl que funciona bien, por cierto un gran trabajo!!! Ese firmware se instala en el disco duro o el la caja?

[Jocko]

Ese firmware se instala en el disco duro o el la caja?

As Lacie, our firmware is installed on the disk.
So when you install fvdw-sl, you destroy the lacie partitions. Then after installing fvdw-sl, you can not backup Lacie partitions as they exists no longer.