Lacie 5Big2 Failed After Firmware Update

Re: Lacie 5Big2 Failed After Firmware Update

Postby Mijzelf » Thu Jul 11, 2013 7:56 am

Is there a benifit of using ftp instead of tftp
Yes. ftp is just more mature. For instance it supports directory listings, which means that the client can show directories on the other side.

A command to start an ftp server on the Lacie could be:
Code: Select all
tcpsvd -vE 0.0.0.0 21 ftpd -v /mp2
If this works you can use your favorite ftp client to browse the disk. (Even Windows Explorer can. Type ftp://<ip-of-nas> in the address bar)

Some random thoughts:

Ext3:
You can read that ext3 disk on a Windows machine, using tools like explore2fs. However, I think the disk has to be cleanly unmounted for that.

Data corruption:
As you had 3 damaged partition tables (at the beginning of the disks) and 2 corrupted raid headers (at the end of the disks), I can hardly imagine there is no corruption in between. (Yet is it possible. I just can't think what actually happened to your system)
Because the data is stored redundant, a corruption on a certain place can be covered by re-calcultating the value from the parity. Unfortunately raid5 contains redundancy, but no error correction. When a parity doesn't fit on it's 4 data chunks, there is no way to tell *which* block is corrupted. Only data analysis can tell. (The one possibility out of 5 which gives a nice photograph is the right one.)
So how can this help? When you have certain corrupted file, you can try to assemble a degraded array in 5 different ways (omitting each disk once) to see if you can extract the good file.
Unfortunately I know no easy way to automate this. Unless there is some pattern in the corruption I don't think it's possible either.

Do I have to somehow reset or reinitialize the USB drive again to get it stop making those errors?
Yes, you have to unmount and remount it:
Code: Select all
umount /mountpoint
mount /dev/sef1 /mountpoint
Mounting could fail, if a filesystem check is necessary.
Mijzelf
 
Posts: 255
Joined: Wed Nov 21, 2012 9:12 am

Re: Lacie 5Big2 Failed After Firmware Update

Postby unlucky1 » Thu Jul 11, 2013 8:24 am

I googled getting busybox ftpd running and tried some stuff but in the end, all advice online ends with "ask on the forums of the gadget developer".

This worked the best:

Code: Select all
tcpsvd -vE 0.0.0.0 10021 ftpd /mp2/shares/3


But failed to find ftpd

So no, I couldn't get ftpd working. I'll wait until you have time this evening then. Maybe I'll see what I can get off with tftp if the USB mounting fails.

Thanks!!
unlucky1
Donator VIP
Donator VIP
 
Posts: 184
Joined: Sun Jul 07, 2013 3:18 pm

Re: Lacie 5Big2 Failed After Firmware Update

Postby Mijzelf » Thu Jul 11, 2013 8:29 am

According to fvdw ftpd should be there. Maybe just a missing symlink?
Code: Select all
ln -s busybox /bin/ftpd


(You know, all those tools are actually just the single busybox. But busybox reacts different if it is called by a different name. Hence the name 'busybox')
Mijzelf
 
Posts: 255
Joined: Wed Nov 21, 2012 9:12 am

Re: Lacie 5Big2 Failed After Firmware Update

Postby unlucky1 » Thu Jul 11, 2013 8:52 am

It wouldn't let me re-mount it. I looked in the mounts and saw seg?

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
   9        0 3898947584 md0
   8       96 2930266580 seg
   8       97 2930253824 seg1
unlucky1
Donator VIP
Donator VIP
 
Posts: 184
Joined: Sun Jul 07, 2013 3:18 pm

Re: Lacie 5Big2 Failed After Firmware Update

Postby unlucky1 » Thu Jul 11, 2013 8:55 am

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/md0 on /mp2 type xfs (ro,relatime,delaylog,sunit=1024,swidth=4096,noquota)
root@(none):/ # mount /dev/sef1 /mountpoint
mount: mounting /dev/sef1 on /mountpoint failed: No such device or address
unlucky1
Donator VIP
Donator VIP
 
Posts: 184
Joined: Sun Jul 07, 2013 3:18 pm

Re: Lacie 5Big2 Failed After Firmware Update

Postby unlucky1 » Thu Jul 11, 2013 9:00 am

Okay, got it now. So I'm going to try to back up those 2 important directories!
unlucky1
Donator VIP
Donator VIP
 
Posts: 184
Joined: Sun Jul 07, 2013 3:18 pm

Re: Lacie 5Big2 Failed After Firmware Update

Postby unlucky1 » Thu Jul 11, 2013 9:08 am

Nope, not working. Getting the read-only file system error again and again.
unlucky1
Donator VIP
Donator VIP
 
Posts: 184
Joined: Sun Jul 07, 2013 3:18 pm

Re: Lacie 5Big2 Failed After Firmware Update

Postby fvdw » Thu Jul 11, 2013 9:36 am

8 96 2930266580 seg
8 97 2930253824 seg1


this means the usb disk is now seg (instead of sef) that happens if you disconnect and reconnect usb and the system has still sef in use
So try to mount it with using /dev/seg1
fvdw
Site Admin - expert
 
Posts: 13471
Joined: Tue Apr 12, 2011 2:30 pm
Location: Netherlands

Re: Lacie 5Big2 Failed After Firmware Update

Postby fvdw » Thu Jul 11, 2013 9:45 am

why not copy the important directories using tftp ?
fvdw
Site Admin - expert
 
Posts: 13471
Joined: Tue Apr 12, 2011 2:30 pm
Location: Netherlands

Re: Lacie 5Big2 Failed After Firmware Update

Postby unlucky1 » Thu Jul 11, 2013 9:54 am

In the end I disconnected the USB and reconnected it but still am getting the read-only errors. Strange. It could be having problems with some of the directory names:

Code: Select all
root@(none):/mp2/shares/3/CLEAN BACKUP/Pictures/2013 # cp -r * /mountpoint/backup/3/2013/* .
cp: '01 - January' and './01 - January' are the same file
cp: '02 - February' and './02 - February' are the same file
cp: '03 - March' and './03 - March' are the same file
cp: '04 - April' and './04 - April' are the same file
cp: '05 - May' and './05 - May' are the same file
cp: can't stat '/mountpoint/backup/3/2013/*': No such file or directory
root@(none):/mp2/shares/3/CLEAN BACKUP/Pictures/2013 # cp -r * /mountpoint/backup/3/2013/*
cp: can't create directory '/mountpoint/backup/3/2013/*/01 - January': No such file or directory
cp: can't create directory '/mountpoint/backup/3/2013/*/02 - February': No such file or directory
cp: can't create directory '/mountpoint/backup/3/2013/*/03 - March': No such file or directory
cp: can't create directory '/mountpoint/backup/3/2013/*/04 - April': No such file or directory
cp: can't create directory '/mountpoint/backup/3/2013/*/05 - May': No such file or directory


I tried with tftp but it didn't like the wildcard characters. So to copy the 2013 directory with all files and subdirectories, what would it look like in tftp? This is the directory I'm trying to copy:
/mp2/shares/3/CLEAN BACKUP/Pictures/2013/

and I want to put it on drive Q of my windows disk (it's an external disk).

thanks!
unlucky1
Donator VIP
Donator VIP
 
Posts: 184
Joined: Sun Jul 07, 2013 3:18 pm

PreviousNext

Return to Lacie 5big Network vs2

Who is online

Users browsing this forum: No registered users and 13 guests