Lacie 5Big2 Failed After Firmware Update

[unlucky1]

tried to use

Code: Select all

kill -9 1003

(the pid)

but it won't kill.

I also tried to kill gzip first but no luck.

And unlink is not found. Can I try rm -f ?

[fvdw]

ctrl +c is not killing dd

Use the other telnet window to kill it
use command

Code: Select all

ps -ef

Take the number at the line where dd and gzip are mentioned (thi si the PID)
kill them

Code: Select all

kill -9 <number>

replace <number> by actual PID number of the process to be killed (dd and gzip)
after this delete the files in /mountpoint folder

yes you can use rm instead of unlink

[fvdw]

if killing isn't working probably this is because no ram left. Then reboot the 5big2 and load standalone kernel again. That will give you an empty RAM again

[unlucky1]

Okay, they are unkillable. I need to head to bed anyway as I have an early meeting tomorrow in the city. So I'll shut down the NAS now and continue the copying in the morning. Maybe tomorrow is the day we save the data! (Trying to be positive.)

Thanks again for another day of your help!! You're really a great person for helping me out in such a jam!

[fvdw]

ps

looking to the file size

Code: Select all

-rw-r--r--    1 root     root     495304704 Jul  9 20:51 sda2_end.gz
-rw-r--r--    1 root     root      10884716 Jul  9 20:44 sda2_start.gz

I think Mijzelf should check his proposal as you copied more then 495 MB of the last part of sda2 partition, as it is compressed the real size is much bigger.
The start of the partition isas expected a 10 MB file

[fvdw]

yes good night and see you tomorrow, indeed bedtime

[Mijzelf]

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?

[unlucky1]

Just got back. Hi! I am booting up the Lacie and will try to do the back-up again. I'm not really sure about the skip blocks and all that so I'll leave that expertise to you :/ Hope it works out right! Shall we talk next steps?

[unlucky1]

Trying again I'm having trouble mounting! I made /mountpoint but now I can't get it to mount:

Code: Select all

root@(none):/ # mkdir /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)
root@(none):/ # more /proc/partitions
major minor  #blocks  name

  31        0        500 mtdblock0
  31        1          4 mtdblock1
   8        0 2930266580 sea
   8        1 2930253824 sea1
   8       16  976762584 sdc
   8       18  974737408 sdc2
   8       32  976762584 sdb
   8       34  974737408 sdb2
   8       48  976762584 sda
   8       50  974737408 sda2
   8       64  976762584 sde
   8       66  974737408 sde2
   8       80  976762584 sdd
   8       82  974737408 sdd2
root@(none):/ # mount /dev/sea1 /mountpoint
mount: mounting /dev/sea1 on /mountpoint failed: No such file or directory
root@(none):/ # 974737408 sde2
-sh: 974737408: not found
root@(none):/ # mknod -m 666 /dev/sea1 b 8 81
root@(none):/ # mount /dev/sea1 /mountpoint
mount: mounting /dev/sea1 on /mountpoint failed: No such device or address
root@(none):/ # mknod -m 666 /dev/sea1 b 8 81
mknod: /dev/sea1: File exists
root@(none):/ # mount /dev/sea1 /mountpoint
mount: mounting /dev/sea1 on /mountpoint failed: No such device or address
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)
root@(none):/ # cd mountpoint/
root@(none):/mountpoint # ls
root@(none):/mountpoint # cd ..
root@(none):/ #

[Mijzelf]

8 1 2930253824 sea1

mknod -m 666 /dev/sea1 b 8 81

That should be 'b 8 1' in this case. It are the first two numbers in the /proc/partitions line.
So

Code: Select all

rm /dev/sea1
mknod -m 666 /dev/sea1 b 8 1

I'm not really sure about the skip blocks and all that so I'll leave that expertise to you

Well, it's no rocket science, just some simple math. But there must be an error, and I just don't see it.

Maybe first take the middle disk. The first one might have hardware problems, although I don't see how it could influence this process this way.