All Shares Gone - Lacie 5Big Network 2

Re: All Shares Gone - Lacie 5Big Network 2

Postby matt-white » Tue Mar 21, 2017 2:56 pm

Jocko,

I have tried to reboot the drive. Looking in the dashboard, there are still no shares.

I rebooted back in to the console and started again with the swap space as you described.
It confirmed that it had been set up. (But is still not visible in top.)

I then tried xfs_repair, but it killed at the same point again.
I tried to mount md4 again, it succeeded on the second attempt and I could see the files.
I tried to unmount in order to run xfs_repair again, but the unmount command cannot be found.

As I can see the files in the telnet window, can I copy from there? (about 5.5TB)

Many thanks

Code: Select all
root@fvdw-sta-kirkwood:/ # tftp -l /sbin/mdadm -r mdadm -g 10.10.7.148
mdadm                100% |**********************************************************************|  1100k  0:00:00 ETA
root@fvdw-sta-kirkwood:/ # chmod 755 /sbin/mdadm
root@fvdw-sta-kirkwood:/ # mdadm --assemble /dev/md4 /dev/sd[abcde]2
mdadm: /dev/md4 has been started with 5 drives.
root@fvdw-sta-kirkwood:/ # tftp -l mount.tar -r mount.tar -g 10.10.7.148
mount.tar            100% |**********************************************************************|   199k  0:00:00 ETA
root@fvdw-sta-kirkwood:/ # tar -xvf mount.tar
usr/
usr/sbin/
usr/sbin/mount
usr/lib/
usr/lib/libblkid.so.1
usr/lib/libblkid.so.1.1.0
usr/lib/libblkid.so
root@fvdw-sta-kirkwood:/ # mdadm --assemble /dev/md3 /dev/sd[abcde]5
mdadm: /dev/md3 has been started with 5 drives.
root@fvdw-sta-kirkwood:/ # mkswap /dev/md3
Setting up swapspace version 1, size = 262074368 bytes
UUID=0357ce1b-ecdb-4c71-9f12-ec3ad61a7b87
root@fvdw-sta-kirkwood:/ # swapon /dev/md3
root@fvdw-sta-kirkwood:/ # tftp -l /sbin/xfs_repair -r xfs_repair -g 10.10.7.148
xfs_repair           100% |**********************************************************************|   622k  0:00:00 ETA
root@fvdw-sta-kirkwood:/ # chmod 755 /sbin/xfs_repair
root@fvdw-sta-kirkwood:/ # tftp -l glibc-mini-mkfs.xfs-25feb14.tar -r glibc-mini-mkfs.xfs-25feb14.tar -g 10.10.7.148
glibc-mini-mkfs.xfs- 100% |**********************************************************************|  2519k  0:00:00 ETA
root@fvdw-sta-kirkwood:/ # tar -xvf glibc-mini-mkfs.xfs-25feb14.tar -C /
./
./usr/
./usr/lib/
./usr/lib/libuuid.so
./usr/lib/libuuid.so.1.3.0
./usr/lib/libgcc_s.so.1
./usr/lib/libuuid.so.1
./bin/
./sbin/
./sbin/mkfs.xfs
./lib/
./lib/libutil.so.1
./lib/libc-2.17.so
./lib/librt.so.1
./lib/librt-2.17.so
./lib/libc.so.6
./lib/libm-2.17.so
./lib/libpthread.so.0
./lib/ld-linux.so.3
./lib/ld-2.17.so
./lib/libutil-2.17.so
./lib/libpthread-2.17.so
./lib/libm.so.6
root@fvdw-sta-kirkwood:/ # xfs_repair -n /dev/md4
Phase 1 - find and verify superblock...
Phase 2 - using internal log
        - scan filesystem freespace and inode maps...
        - found root inode chunk
Phase 3 - for each AG...
        - scan (but don't clear) agi unlinked lists...
        - process known inodes and perform inode discovery...
        - agno = 0
Killed
root@fvdw-sta-kirkwood:/ # mkdir /md4
root@fvdw-sta-kirkwood:/ # /usr/sbin/mount /dev/md4 /md4
mount: /dev/md4: can't read superblock
root@fvdw-sta-kirkwood:/ # cd md4/
root@fvdw-sta-kirkwood:/md4 # ls -l
total 0
root@fvdw-sta-kirkwood:/ # /usr/sbin/mount /dev/md4 /md4
mount: /dev/md4 already mounted or /md4 busy
mount: according to mtab, /dev/md4 is already mounted on /md4
root@fvdw-sta-kirkwood:/ # ls -l
total 2732
drwxr-xr-x    2 root     root          1820 Feb 25  2014 bin
drwxrwxr-x    6 root     root          4680 Mar 21 14:36 dev
drwxrwxrwx    4 root     root           200 Feb  3  2016 etc
-rwxr-xr-x    1 root     root           672 Feb  2  2016 fvdw-sl-programs
-rw-r--r--    1 root     root       2579456 Mar 21 14:38 glibc-mini-mkfs.xfs-25feb14.tar
-rwxr-xr-x    1 root     root          2125 Oct 26  2015 init
-rw-r--r--    1 root     root            12 Mar 21 14:35 ip.txt
drwxr-xr-x    3 root     root           300 Mar 21 14:38 lib
lrwxrwxrwx    1 root     root            12 Mar 21 14:35 linuxrc -> /bin/busybox
drwxr-xr-x   10 root     root           115 Mar 17 10:13 md4
drwxrwxrwx    3 root     root            60 Feb  3  2016 mnt
-rw-r--r--    1 root     root        204288 Mar 21 14:36 mount.tar
dr-xr-xr-x   70 root     root             0 Jan  1  1970 proc
drwxr-xr-x    2 root     root          1660 Mar 21 14:38 sbin
dr-xr-xr-x   12 root     root             0 Mar 21 14:35 sys
drwxr-xr-x    6 root     root           120 Feb 25  2014 usr
drwxr-xr-x    3 root     root            60 Feb  3  2016 var
root@fvdw-sta-kirkwood:/ # cd md4/
root@fvdw-sta-kirkwood:/md4 # ls -l
total 0
drwxr-xr-x    2 root     root             6 Mar 17 10:13 afp_db
drwxr-xr-x    3 root     root            25 Nov 15  2013 autoupdate
drwxr-xr-x    2 root     root             6 Nov 12  2013 images
drwxr-xr-x    2 root     root            45 Nov 12  2013 reserved
drwxr-xr-x    6 root     root            38 Mar 16 14:05 shares
drwxr-xr-x    2 root     root             6 Mar 17 10:13 tmp
drwxr-xr-x    2 root     root             6 Nov 12  2013 torrent_dir
drwxr-xr-x    3 root     root            18 Nov 12  2013 var
root@fvdw-sta-kirkwood:/md4 # cd shares/
root@fvdw-sta-kirkwood:/md4/shares # ls -l
total 16
drwxrwxrwx   26 root     root          4096 Mar 17 10:14 1
drwxrwxrwx   13 root     root          4096 Mar 17 11:29 3
drwxrwxrwx    8 root     root          4096 Mar 17 10:14 4
drwxrwxrwx   20 root     root          4096 Mar 17 10:14 5
root@fvdw-sta-kirkwood:/md4/shares # cd /
root@fvdw-sta-kirkwood:/ # unmount /md4
-sh: unmount: not found
root@fvdw-sta-kirkwood:/ # xfs_repair -n /dev/md4
xfs_repair: /dev/md4 contains a mounted and writable filesystem

fatal error -- couldn't initialize XFS library
root@fvdw-sta-kirkwood:/ #
matt-white
 
Posts: 7
Joined: Fri Mar 17, 2017 3:38 pm

Re: All Shares Gone - Lacie 5Big Network 2

Postby Jocko » Thu Mar 30, 2017 10:33 am

Hi matt-white,

Sorry for the delay but currently I need time for personal issues.

But if now you have a dashboard access and you can mount the data raid you should be able to restore your shares just by recreating them (use the same name as previously and same case) from the dashboard.
Jocko
Site Admin - expert
 
Posts: 11356
Joined: Tue Apr 12, 2011 4:48 pm
Location: Orleans, France

Re: All Shares Gone - Lacie 5Big Network 2

Postby matt-white » Thu Mar 30, 2017 11:04 am

Thanks for getting back to me Jocko.
I didn't have access to the dashboard as it didn't load the LaCie firmware anymore.
What I managed to do was mount another drive attached to the e-sata port and copy files off via the command line.
My only restrictions were that I had to format it FAT32, so max volume was 1TB, and largest file I could transfer was 4GB. But I managed to recover most of the data before I reset and reformatted the raid.
Many thanks for your assistance.
matt-white
 
Posts: 7
Joined: Fri Mar 17, 2017 3:38 pm

Re: All Shares Gone - Lacie 5Big Network 2

Postby Jocko » Thu Mar 30, 2017 12:13 pm

So I did not understand you:
matt-white wrote:I have tried to reboot the drive. Looking in the dashboard, there are still no shares.
I though you can load the dashboard.

Can you confirm this point.

If not we will need to check the other raids but as they are raid1 devices it should not have issues on them that would prevent us from loading the lacie firmware

Otherwise, md4 seems to be clean now as you posted
Code: Select all
root@fvdw-sta-kirkwood:/ # cd md4/
root@fvdw-sta-kirkwood:/md4 # ls -l
total 0
drwxr-xr-x    2 root     root             6 Mar 17 10:13 afp_db
drwxr-xr-x    3 root     root            25 Nov 15  2013 autoupdate
drwxr-xr-x    2 root     root             6 Nov 12  2013 images
drwxr-xr-x    2 root     root            45 Nov 12  2013 reserved
drwxr-xr-x    6 root     root            38 Mar 16 14:05 shares
drwxr-xr-x    2 root     root             6 Mar 17 10:13 tmp
drwxr-xr-x    2 root     root             6 Nov 12  2013 torrent_dir
drwxr-xr-x    3 root     root            18 Nov 12  2013 var
root@fvdw-sta-kirkwood:/md4 # cd shares/
root@fvdw-sta-kirkwood:/md4/shares # ls -l
total 16
drwxrwxrwx   26 root     root          4096 Mar 17 10:14 1
drwxrwxrwx   13 root     root          4096 Mar 17 11:29 3
drwxrwxrwx    8 root     root          4096 Mar 17 10:14 4
drwxrwxrwx   20 root     root          4096 Mar 17 10:14 5
So no need to run again xfs_repair (fs is ok)

Note: the unmount command is 'umount' and not 'unmount'
Jocko
Site Admin - expert
 
Posts: 11356
Joined: Tue Apr 12, 2011 4:48 pm
Location: Orleans, France

Re: All Shares Gone - Lacie 5Big Network 2

Postby Bourinos » Thu Oct 05, 2017 12:25 pm

Hello,
I have the same exact problem with my 5big network 2 as well...
I went for a lot of reading on this thread but the post concerning the mdadm files leads to a thread I am not allowed to read for some reason.
I've read there https://plugout.net/viewtopic.php?f=28&t=2727&p=25691&hilit=mdadm#p25691 that mdadm was included now, however, I don't see it in the folder and so I can't install them.
Of course, as it is clearly seen in my question, I'm a total noob when it comes to that sort of things.
Bourinos
 
Posts: 3
Joined: Thu Oct 05, 2017 9:59 am

Re: All Shares Gone - Lacie 5Big Network 2

Postby Jocko » Thu Oct 05, 2017 1:15 pm

Hi

Indeed with the last fvdw-sl console package, there is an undocumented change about these extra-tools (mdadm; mount; xfs_repair; ...).

So you need no longer to upload them manually one by one (via tftp command and chmod command) but use a new option with fvdw-programs menu :
* run on the telnet window the command: fvdw-sl-programs
(then a menu will appear)
* select "Upload and extract glibc mini and tools"

Which will install these additional commands
Jocko
Site Admin - expert
 
Posts: 11356
Joined: Tue Apr 12, 2011 4:48 pm
Location: Orleans, France

Re: All Shares Gone - Lacie 5Big Network 2

Postby Bourinos » Thu Oct 05, 2017 4:01 pm

Thanks a lot for that quick answer!
It's running as intended now...
Still, I got that while trying to run xfs_repair, did I do something wrong or this fatal error in the end means my NAS is bricked? I mean, drives seems to be fine (that's the first thing I checked with Lacie web browser) but something else is definitely wrong...
Thank you so much for your time!
Code: Select all
root@fvdw-sta-kirkwood:/ # mdadm --assemble /dev/md4 /dev/sd[abcde]2
mdadm: /dev/md4 has been started with 5 drives.
root@fvdw-sta-kirkwood:/ # mkdir /mountpoint
root@fvdw-sta-kirkwood:/ # mount -o ro /dev/md4 /mountpoint
mount: /dev/md4: can't read superblock
root@fvdw-sta-kirkwood:/ #  mdadm --detail /dev/md4
/dev/md4:
        Version : 1.0
  Creation Time : Fri Jul 12 10:58:56 2013
     Raid Level : raid5
     Array Size : 7805956096 (7444.34 GiB 7993.30 GB)
  Used Dev Size : 1951489024 (1861.09 GiB 1998.32 GB)
   Raid Devices : 5
  Total Devices : 5
    Persistence : Superblock is persistent

    Update Time : Thu Oct  5 15:40:18 2017
          State : clean
 Active Devices : 5
Working Devices : 5
 Failed Devices : 0
  Spare Devices : 0

         Layout : left-symmetric
     Chunk Size : 512K

           Name : (none):4
           UUID : 9ba6b120:3c2a4aef:0fb00f62:8b598696
         Events : 7017727

    Number   Major   Minor   RaidDevice State
       0       8       34        0      active sync   /dev/sda2
       1       8       18        1      active sync   /dev/sdb2
       2       8        2        2      active sync   /dev/sdc2
       3       8       66        3      active sync   /dev/sdd2
       4       8       50        4      active sync   /dev/sde2
root@fvdw-sta-kirkwood:/ # xfs_repair /dev/md4
Phase 1 - find and verify superblock...

fatal error -- couldn't allocate block map, size = 8388480
Bourinos
 
Posts: 3
Joined: Thu Oct 05, 2017 9:59 am

Re: All Shares Gone - Lacie 5Big Network 2

Postby Jocko » Thu Oct 05, 2017 5:43 pm

So your raid on data partition is clean and you have an issue "only" with the filesystem on it. It seems to be corrupted.

Your last issue is the expected behaviour as with a 5big2 you do not have enough RAM to run xfs_repair so you need to add some swap memory by plugging a memory stick. So your NAS is not bricked.

So you need a memory stick with at least 1GB size. After plugging it, do
Code: Select all
cat /proc/partitions | grep '/dev/se'
. Please to note the kernel name of your USB device. On a first login, it must be '/dev/sek'.

Now you need to create its partitions table
Code: Select all
fdisk /dev/sek
                                  Then do(delete the current partition, I assume there is only one)
d
1
                                  (create a new one)
n
p
1
1
1000

t
1
82
w
next is to create the swap system on sek1
Code: Select all
mkswap /dev/sek1
and bring up the new swap partition
Code: Select all
swapon /dev/sek1
Check if you get a not empty swap size with the command
Code: Select all
free
If yes, you can try again to run the xfs_repair command
Jocko
Site Admin - expert
 
Posts: 11356
Joined: Tue Apr 12, 2011 4:48 pm
Location: Orleans, France

Re: All Shares Gone - Lacie 5Big Network 2

Postby Bourinos » Thu Oct 05, 2017 8:55 pm

Thanks, I'm getting somewhere...
Code: Select all
root@fvdw-sta-kirkwood:/ # mount -o ro /dev/md4 /mountpoint
mount: /dev/md4: can't read superblock
root@fvdw-sta-kirkwood:/ #
root@fvdw-sta-kirkwood:/ # xfs_repair /dev/md4
Phase 1 - find and verify superblock...
Phase 2 - using internal log
        - zero log...
ERROR: The filesystem has valuable metadata changes in a log which needs to
be replayed.  Mount the filesystem to replay the log, and unmount it before
re-running xfs_repair.  If you are unable to mount the filesystem, then use
the -L option to destroy the log and attempt a repair.
Note that destroying the log may cause corruption -- please attempt a mount
of the filesystem before doing this.

I'm a little bit confused with this, in one hand it says "zero log" but in the other it tells me that the filesystem has valuable metadata changes in a log...
What should I do?
Bourinos
 
Posts: 3
Joined: Thu Oct 05, 2017 9:59 am

Re: All Shares Gone - Lacie 5Big Network 2

Postby Jocko » Thu Oct 05, 2017 10:42 pm

You should do what it says.
So try to mount again /dev/md4 (as now phase 1 is ok), then
if you succeed to mount it, you need to unmount it and run again xfs_repair to finish restoring
Code: Select all
umount /dev/md4
xfs_repair /dev/md4
and only if you still fail to mount it you need to run again xfs_repair with the option '-L'.
Code: Select all
xfs_repair -L /dev/md4
Jocko
Site Admin - expert
 
Posts: 11356
Joined: Tue Apr 12, 2011 4:48 pm
Location: Orleans, France

Previous

Return to Lacie 5big Network vs2

Who is online

Users browsing this forum: Google [Bot] and 1 guest