5big2 not booting

[Jocko]

I do not remember well but as on md4 you have a xfs filesystem you may need to load the mount.tar package and untar it.

So load the package mount.tar as you did with mdadm and run the command

Code: Select all

tar -xf mount.tar -C /

[peterihuman]

I do not remember well but as on md4 you have a xfs filesystem you may need to load the mount.tar package and untar it.

So load the package mount.tar as you did with mdadm and run the command

Code: Select all

tar -xf mount.tar -C /

Ah okay.

Thanks.

I have to do that tomorrow then, when I'm back at the box with the Windows applications.

Thank you :)

Peter

[peterihuman]

Data is now being transferred.

How dependent is the tftp connection? The FVDW console is running on a windows installation on my laptop, the Lacie box is sitting in my office and transferring to a Mac, same place.
But I have to take my laptop with me at some point :)



Thank you very much for the forum and all the help.

Sincerely
Peter

[Jocko]

Hi,

fvdw-sl console is a troubleshooting tool, or for configuring and it allows a special environment on the NAS : basic settings and max privileges.

So fvdw-sl console must be running on the same LAN of the NAS and vsftpd allows client connections only from LAN

[peterihuman]

Hi

One more disk decided to give trouble when copying data over the weekend.
So now I can't access the data.

I'm getting this:

Code: Select all

root@fvdw-sta-kirkwood:/ # mdadm --assemble /dev/md4 /dev/sd[abcd]2
mdadm: /dev/md4 assembled from 3 drives - not enough to start the array.
root@fvdw-sta-kirkwood:/ # mdadm --examine /dev/sd[abcde]2
/dev/sda2:
          Magic : a92b4efc
        Version : 0.90.00
           UUID : 8508cd4c:e50c8378:642ee5f7:16a31c22
  Creation Time : Thu Jan  1 00:01:07 1970
     Raid Level : raid5
  Used Dev Size : 1463127808 (1395.35 GiB 1498.24 GB)
     Array Size : 5852511232 (5581.39 GiB 5992.97 GB)
   Raid Devices : 5
  Total Devices : 4
Preferred Minor : 4

    Update Time : Wed Nov 23 11:43:27 2016
          State : clean
 Active Devices : 3
Working Devices : 3
 Failed Devices : 2
  Spare Devices : 0
       Checksum : 3d7ecf90 - correct
         Events : 3592

         Layout : left-symmetric
     Chunk Size : 64K

      Number   Major   Minor   RaidDevice State
this     0       8       34        0      active sync   /dev/sda2

   0     0       8       34        0      active sync   /dev/sda2
   1     1       8       18        1      active sync   /dev/sdb2
   2     2       8        2        2      active sync   /dev/sdc2
   3     3       0        0        3      faulty removed
   4     4       0        0        4      faulty removed
/dev/sdb2:
          Magic : a92b4efc
        Version : 0.90.00
           UUID : 8508cd4c:e50c8378:642ee5f7:16a31c22
  Creation Time : Thu Jan  1 00:01:07 1970
     Raid Level : raid5
  Used Dev Size : 1463127808 (1395.35 GiB 1498.24 GB)
     Array Size : 5852511232 (5581.39 GiB 5992.97 GB)
   Raid Devices : 5
  Total Devices : 4
Preferred Minor : 4

    Update Time : Wed Nov 23 11:43:27 2016
          State : clean
 Active Devices : 3
Working Devices : 3
 Failed Devices : 2
  Spare Devices : 0
       Checksum : 3d7ecf82 - correct
         Events : 3592

         Layout : left-symmetric
     Chunk Size : 64K

      Number   Major   Minor   RaidDevice State
this     1       8       18        1      active sync   /dev/sdb2

   0     0       8       34        0      active sync   /dev/sda2
   1     1       8       18        1      active sync   /dev/sdb2
   2     2       8        2        2      active sync   /dev/sdc2
   3     3       0        0        3      faulty removed
   4     4       0        0        4      faulty removed
/dev/sdc2:
          Magic : a92b4efc
        Version : 0.90.00
           UUID : 8508cd4c:e50c8378:642ee5f7:16a31c22
  Creation Time : Thu Jan  1 00:01:07 1970
     Raid Level : raid5
  Used Dev Size : 1463127808 (1395.35 GiB 1498.24 GB)
     Array Size : 5852511232 (5581.39 GiB 5992.97 GB)
   Raid Devices : 5
  Total Devices : 4
Preferred Minor : 4

    Update Time : Wed Nov 23 11:43:27 2016
          State : clean
 Active Devices : 3
Working Devices : 3
 Failed Devices : 2
  Spare Devices : 0
       Checksum : 3d7ecf74 - correct
         Events : 3592

         Layout : left-symmetric
     Chunk Size : 64K

      Number   Major   Minor   RaidDevice State
this     2       8        2        2      active sync   /dev/sdc2

   0     0       8       34        0      active sync   /dev/sda2
   1     1       8       18        1      active sync   /dev/sdb2
   2     2       8        2        2      active sync   /dev/sdc2
   3     3       0        0        3      faulty removed
   4     4       0        0        4      faulty removed
/dev/sdd2:
          Magic : a92b4efc
        Version : 0.90.00
           UUID : 8508cd4c:e50c8378:642ee5f7:16a31c22
  Creation Time : Thu Jan  1 00:01:07 1970
     Raid Level : raid5
  Used Dev Size : 1463127808 (1395.35 GiB 1498.24 GB)
     Array Size : 5852511232 (5581.39 GiB 5992.97 GB)
   Raid Devices : 5
  Total Devices : 4
Preferred Minor : 4

    Update Time : Wed Nov 23 11:42:57 2016
          State : clean
 Active Devices : 4
Working Devices : 4
 Failed Devices : 1
  Spare Devices : 0
       Checksum : 3d7ecf83 - correct
         Events : 3588

         Layout : left-symmetric
     Chunk Size : 64K

      Number   Major   Minor   RaidDevice State
this     3       8       66        3      active sync   /dev/sdd2

   0     0       8       34        0      active sync   /dev/sda2
   1     1       8       18        1      active sync   /dev/sdb2
   2     2       8        2        2      active sync   /dev/sdc2
   3     3       8       66        3      active sync   /dev/sdd2
   4     4       0        0        4      faulty removed
/dev/sde2:
          Magic : a92b4efc
        Version : 0.90.00
           UUID : 8508cd4c:e50c8378:642ee5f7:16a31c22
  Creation Time : Thu Jan  1 00:01:07 1970
     Raid Level : raid5
  Used Dev Size : 1463127808 (1395.35 GiB 1498.24 GB)
     Array Size : 5852511232 (5581.39 GiB 5992.97 GB)
   Raid Devices : 5
  Total Devices : 5
Preferred Minor : 4

    Update Time : Thu Nov 24 10:33:12 2016
          State : clean
 Active Devices : 5
Working Devices : 5
 Failed Devices : 0
  Spare Devices : 0
       Checksum : 3d7ff501 - correct
         Events : 26

         Layout : left-symmetric
     Chunk Size : 64K

      Number   Major   Minor   RaidDevice State
this     4       8       50        4      active sync   /dev/sde2

   0     0       8       34        0      active sync   /dev/sda2
   1     1       8       18        1      active sync   /dev/sdb2
   2     2       8        2        2      active sync   /dev/sdc2
   3     3       8       66        3      active sync   /dev/sdd2
   4     4       8       50        4      active sync   /dev/sde2


Best case scenario would be that I can mount tha raid with the faulty disk(s) and continue to copy out the data.
If it is just a matter of bad blocks, I can live with faulty files, if I can copy everything else out.

Thanks.

Sincerely. Peter.

[Jocko]

Hi

It is a very bad new your last post. Usually a raid 5 with 2 faulty disks, you can not recover your data :sob
It is why a raid can be never a safe backup way. Your case demonstrates it: as the disks have a similar use, if a disk gets a faulty status it is highly likely that soon a second disks becomes it also ...

So did you backup your data ?

if no, I need to find again the way (I found it in the past) how to assemble a raid5 with 2 faulty disks.

During this time do nothing with your NAS

[peterihuman]

It's for a guy I know.
Not my own box, and there is no backup. I only managed to copy out around 1,5TB of the total of 5TB.

I would very much like you to find a way.

I am thinking that the disks are there, and we need to somehow reattach the disks and then just ignore bad blocks?

Dmesg is actually finding all 5 disks.

Thank you very much :)

Peter

[Jocko]

As the trick consists in to overwrite the RAID array and there is no go back possible.

Can you try this safe command

Code: Select all

mdadm --assemble /dev/md4 /dev/sd[abcd]2 --force
cat /proc/mdstat

and if mdadm command is successful

Code: Select all

mdadm --detail /dev/md4

Please to note as sdd got a faulty status, the last written data are not synced and lost (parity not saved).

If this way is successful, you should backup quickly data and use the raid on a readonly mode :

Code: Select all

mount -o ro /dev/md4 /md4

[peterihuman]

Code: Select all

root@fvdw-sta-kirkwood:/ # mdadm --assemble /dev/md4 /dev/sd[abcd]2 --force
mdadm: /dev/sda2 is busy - skipping
mdadm: /dev/sdb2 is busy - skipping
mdadm: /dev/sdc2 is busy - skipping
mdadm: /dev/sdd2 is busy - skipping
root@fvdw-sta-kirkwood:/ # cat /proc/mdstat
Personalities : [linear] [raid0] [raid1] [raid10] [raid6] [raid5] [raid4]
md4 : inactive sda2[0](S) sdd2[3](S) sdc2[2](S) sdb2[1](S)
      5852511232 blocks
       
unused devices: <none>
root@fvdw-sta-kirkwood:/ # mdadm --detail /dev/md4
mdadm: md device /dev/md4 does not appear to be active.


Don't really know why it is busy as I have done nothing since booting except for already trying to assemble the raid.

Peter

[peterihuman]

Maybe the next thing to do is to turn over the device to a recovery service.
They will probably clone all the drives and then reassemble the raid from there, and extract data.

But if you have any other ideas let me know.

Peter