Lacie 5Big2 Failed After Firmware Update

[unlucky1]

Okay, thanks! It looks right now:

Code: Select all

root@(none):/ # mount
rootfs on / type rootfs (rw)
none on /proc type proc (rw,relatime)
none on /sys type sysfs (rw,relatime)
none on /dev/pts type devpts (rw,relatime,mode=600)
/dev/sea1 on /mountpoint type ext3 (rw,relatime,errors=continue,barrier=0,data=ordered)
root@(none):/ #

Just a question but should I try the back-up without gzip or won't that matter?

[Mijzelf]

Just a question but should I try the back-up without gzip or won't that matter?

It shouldn't matter, and there are two reasons for zipping it:
1) smaller output (not really important now)
2) data analytics. The files should be roughly equal in size. If not, the nature of the data is different for the different disks. Can be nice to know if we must skip a disk.


Oh, by the way, if the usb disk is '8 1' now, that means all other disks are shifted. So better reboot the box, and plugin the usb disk *after* booting.

[unlucky1]

Okay, I'll reboot and then put in USB. I'll start the back-up and get that going then. I'll let you know if I have any problems ;)

[unlucky1]

This look right to you?

Code: Select all

root@(none):/ # cat /proc/partitions
major minor  #blocks  name

  31        0        500 mtdblock0
  31        1          4 mtdblock1
   8        0  976762584 sdc
   8        2  974737408 sdc2
   8       16  976762584 sdb
   8       18  974737408 sdb2
   8       32  976762584 sda
   8       34  974737408 sda2
   8       48  976762584 sde
   8       50  974737408 sde2
   8       64  976762584 sdd
   8       66  974737408 sdd2
   8       80 2930266580 sef
   8       81 2930253824 sef1
root@(none):/ # mknod -m 666 /dev/sef1 b 8 81
root@(none):/ # mount /dev/sef1 /mountpoint
root@(none):/ # mount
rootfs on / type rootfs (rw)
none on /proc type proc (rw,relatime)
none on /sys type sysfs (rw,relatime)
none on /dev/pts type devpts (rw,relatime,mode=600)
/dev/sef1 on /mountpoint type ext3 (rw,relatime,errors=continue,barrier=0,data=ordered)
root@(none):/ #


Shall I start the back-up?

[unlucky1]

Ok, I did and it looks like it's going to the USB drive now:

Code: Select all

root@(none):/ # dd if=/dev/sda2 bs=1M count=64 | gzip >/mountpoint/sda2_start.gz
64+0 records in
64+0 records out
67108864 bytes (64.0MB) copied, 49.602967 seconds, 1.3MB/s

root@(none):/mountpoint # ls -al
total 11748
drwxr-xr-x    3 root     root          4096 Jul 10 13:45 .
drwxr-xr-x   13 root     root             0 Jul 10 13:33 ..
drwx------    2 root     root         16384 Jul  9 20:24 lost+found
-rw-r--r--    1 root     root      11990312 Jul 10 13:46 sda2_start.gz


I'll keep going.

[unlucky1]

I noticed the second (bigger) back-up stopped. Here's the error:

Code: Select all

root@(none):/ # dd if=/dev/sda2 bs=1M skip=951820 | gzip >/mountpoint/sda2_end.gz
gzip: short write


[Mijzelf]

"short write"?

As far as I know that error means that a write action didn't succeed to write all bytes. As gzip is only writing to a pipe, that means that either the pipe broke (but that would give (also) another message, I suppose) or the output of the pipe failed.
Your disk cannot possibly be full, can it?

Does 'dmesg' show alarming errors (I/O errors)?

[fvdw]

Good morning, sorry for suddenly being gone yesterday.

I don't really see where I made a mistake in 'skip' blocks, yesterday. According to /proc/partitions the data partition size is 974738119 'blocks', which is KiB. That equals about 974GB, so the value is sane.
Devided by 1024 it gives 951892.69 MiB. So when I want about the last 70 blocks of 1MiB, I should skip 951822 1M blocks. Right?

Where is the error?

:scratch I can not see an error, but if it copies only 60 MB how can it be that the file on disk becomes more then 490 MB....(it even is compressed data)
unless in dd 1M is not equal to 1024*1024 bytes (not likely)

[fvdw]

maybe better not to use gzip it only makes copying a lot longer.
If you want to compress the data it can be done later, the 3 TB disk should be big enough to contain 10 times 60 MB....
the command would then be

Code: Select all

dd if=/dev/sda2 of=/mountpoint/sda2_end.gz  bs=1M skip=951820


[unlucky1]

Okay, dmesg shows nothing alarming:

Code: Select all

[  185.517323] usb 1-1.1: new high speed USB device number 3 using orion-ehci
[  185.668794] usb 1-1.1: New USB device found, idVendor=0bc2, idProduct=a0a4
[  185.675640] usb 1-1.1: New USB device strings: Mfr=2, Product=3, SerialNumber=1
[  185.682928] usb 1-1.1: Product: Backup+ Desk
[  185.687212] usb 1-1.1: Manufacturer: Seagate
[  185.691458] usb 1-1.1: SerialNumber: NA5JLB0T
[  185.696683] scsi2 : usb-storage 1-1.1:1.0
[  186.698133] scsi 2:0:0:0: Direct-Access     Seagate  Backup+ Desk     0503 PQ: 0 ANSI: 6
[  186.707591] sd 2:0:0:0: [sef] 732566645 4096-byte logical blocks: (3.00 TB/2.72 TiB)
[  186.716644] sd 2:0:0:0: [sef] Write Protect is off
[  186.721474] sd 2:0:0:0: [sef] Mode Sense: 43 00 00 00
[  186.721486] sd 2:0:0:0: [sef] Assuming drive cache: write through
[  186.728570] sd 2:0:0:0: [sef] 732566645 4096-byte logical blocks: (3.00 TB/2.72 TiB)
[  186.736933] sd 2:0:0:0: [sef] Assuming drive cache: write through
[  186.754006]  sef: sef1
[  186.757821] sd 2:0:0:0: [sef] 732566645 4096-byte logical blocks: (3.00 TB/2.72 TiB)
[  186.766309] sd 2:0:0:0: [sef] Assuming drive cache: write through
[  186.772407] sd 2:0:0:0: [sef] Attached SCSI disk
[  781.359015] EXT3-fs: barriers not enabled
[  781.397217] kjournald starting.  Commit interval 5 seconds
[  781.410099] EXT3-fs (sef1): using internal journal
[  781.414871] EXT3-fs (sef1): recovery complete
[  781.419237] EXT3-fs (sef1): mounted filesystem with ordered data mode