RN 316 - Raid 5 config, Data Volume Dead

You can always make another image of the 4 healthy drives, so backing up those images only saves you time in case you need to start over.

---

Sandshark wrote:

You can always make another image of the 4 healthy drives, so backing up those images only saves you time in case you need to start over.

---

FWIW, it's not clear how healthy they are, given that several failed the self test (per the logs).

That said, I agree that disk 5 is the most important one to backup up, so if there is enough storage on the PC for that image, halbertn could skip the others.

Though 2x20TB is a reasonable way to start over on the NAS, and halbertn likely will also need storage for offload the files.

StephenB wrote:

---

Sandshark wrote:

You can always make another image of the 4 healthy drives, so backing up those images only saves you time in case you need to start over.

---

FWIW, it's not clear how healthy they are, given that several failed the self test (per the logs).

 

That said, I agree that disk 5 is the most important one to backup up, so if there is enough storage on the PC for that image, halbertn could skip the others.

Since my plan is to use VirtualBox to run the ReadyNAS OS VM, I will need the extra hard drive storage so that I can covert each .img into the .vdi and store them. Unfortunately VirtualBox only supports .vdi

Though 2x20TB is a reasonable way to start over on the NAS, and halbertn likely will also need storage for offload the files.

 

---

Yes, I like this idea. I've already ordered my second drive. 

StephenB Sandshark 
I finished converting all my img to .vdi so that I could mount them using virtualbox. I assigned each drive as follows:

ReadyNasVM.vdk - SATA port 0
Disk1.vid - SATA port 1

Disk2.vdi - SATA port 2

Disk4.vid - SATA port 4

Disk5.vdi - SATA port 5
Disk6.vdi - SATA port 6

I intentionally skip SATA port3 as that should be the slot at which disk3 went in, but my disk3 clone was bad, so I'm ignoring that slot for now.

I boot up the VM in VirtualBox. However, my Raid5 volume is not recognized. I have an error stating "Remove inactive volumes to use the disk. Disk #1, 2, 4, 5, 6". I also have two data volumes, both which are inactive.

I'm including a screenshot below my post. I also have a zip of the latest logs, but I can't attach zips to this post. If you can point me to which log you'd like to review, I can include that in my next post.

Any ideas on what went wrong? Or am I missing a step to rebuild the raid array (I assumed it would ReadyNAS would to it automatically on boot). 

---

halbertn wrote:

I'm including a screenshot below my post. I also have a zip of the latest logs, but I can't attach zips to this post. If you can point me to which log you'd like to review, I can include that in my next post.

---

Likely the volume is out of sync.

The best approach is to get me the full log zip.  Do that in a private message (PM) using the envelope link in the upper right of the forum age.  Put the log zip into cloud storage, and include a link in the PM.  Make sure the permissions are set so anyone with the link can download.

StephenB sent you a DM with a link to the logs.zip. Tried to also include the message below, but I don't think it was formatted properly. Including it here in case you have trouble reading it:

If you look at systemd-journal.log beginning at line: 3390, you'll see below

Apr 06 19:24:02 nas-homezone kernel: md: bind<sdd3>
Apr 06 19:24:02 nas-homezone kernel: md: bind<sdf3>
Apr 06 19:24:02 nas-homezone kernel: md: bind<sde3>
Apr 06 19:24:02 nas-homezone kernel: md: bind<sdc3>
Apr 06 19:24:02 nas-homezone kernel: md: bind<sdb3>
Apr 06 19:24:02 nas-homezone kernel: md/raid:md127: device sdb3 operational as raid disk 0
Apr 06 19:24:02 nas-homezone kernel: md/raid:md127: device sde3 operational as raid disk 5
Apr 06 19:24:02 nas-homezone kernel: md/raid:md127: device sdf3 operational as raid disk 4
Apr 06 19:24:02 nas-homezone kernel: md/raid:md127: device sdd3 operational as raid disk 3
Apr 06 19:24:02 nas-homezone kernel: md/raid:md127: allocated 6474kB
Apr 06 19:24:02 nas-homezone start_raids[1295]: mdadm: failed to RUN_ARRAY /dev/md/data-0: Input/output error
Apr 06 19:24:02 nas-homezone start_raids[1295]: mdadm: Not enough devices to start the array.
Apr 06 19:24:02 nas-homezone systemd[1]: Started MD arrays.
Apr 06 19:24:02 nas-homezone systemd[1]: Reached target Local File Systems (Pre).
Apr 06 19:24:02 nas-homezone systemd[1]: Reached target Swap.
Apr 06 19:24:02 nas-homezone systemd[1]: Starting udev Coldplug all Devices...
Apr 06 19:24:02 nas-homezone kernel: md/raid:md127: not enough operational devices (2/6 failed)
Apr 06 19:24:02 nas-homezone kernel: RAID conf printout:
Apr 06 19:24:02 nas-homezone kernel:  --- level:5 rd:6 wd:4
Apr 06 19:24:02 nas-homezone kernel:  disk 0, o:1, dev:sdb3
Apr 06 19:24:02 nas-homezone kernel:  disk 3, o:1, dev:sdd3
Apr 06 19:24:02 nas-homezone kernel:  disk 4, o:1, dev:sdf3
Apr 06 19:24:02 nas-homezone kernel:  disk 5, o:1, dev:sde3

Notice that sdc3 is not included in the raid array. The device sdc matches disk2.vdi, which was a clone of disk2 - if you recall, disk2 was the drive that fell out of sync in the original ReadyNAS HW unit. This forced a 'resync', against disk2, which lead to disk3 failing and the volume dying. 

I wonder if this means disk2 is also bad and unusable for rebuilding the array?