I can try to replace the SATA cable for sdb. if that doesn't work I also have a different SATA port I can try.
Raid 5 array missing after failed rebuild
-
- OMV 2.x
- zachlow
-
-
I can try to replace the SATA cable for sdb. if that doesn't work I also have a different SATA port I can try.
That sounds like a good plan, when you get done come back, and we can get that drive added, and get yourself a backup drive, backup and start again with either OMV4 or OMV5.
-
-
Perfect! I really appreciate your help geaves!
No problem glad I could help
-
Plugged in a new SATA cable and connected it to a different SATA port. As soon as the server started back up the raid began recovering on its own.
-
Plugged in a new SATA cable and connected it to a different SATA port. As soon as the server started back up the raid began recovering on its own.
Excellent, but I would look at getting your backup up to date then moving your OMV to 4 or 5.
-
Thats the plan! I got my new backup drive working and as soon as the raid rebuilds I'll back it up. Also I'm planning on rebuilding my NAS this weekend and an upgrade to OMV 4 or 5 was in the plans. Again thank you very much for your help!
-
@geaves......bad news. The rebuild failed. Here is the array details.
Code
Alles anzeigenVersion : 1.2 Creation Time : Tue Apr 5 15:38:53 2016 Raid Level : raid5 Array Size : 14650675200 (13971.97 GiB 15002.29 GB) Used Dev Size : 2930135040 (2794.39 GiB 3000.46 GB) Raid Devices : 6 Total Devices : 6 Persistence : Superblock is persistent Update Time : Fri Mar 20 00:28:11 2020 State : clean, FAILED Active Devices : 4 Working Devices : 5 Failed Devices : 1 Spare Devices : 1 Layout : left-symmetric Chunk Size : 512K Name : NAS:NASvol1 (local to host NAS) UUID : 9a74f8dd:30a95450:999e44c3:e36af552 Events : 31056 Number Major Minor RaidDevice State 0 0 0 0 removed 1 8 16 1 active sync /dev/sdb 2 8 32 2 active sync /dev/sdc 6 8 80 3 active sync /dev/sdf 5 8 48 4 active sync /dev/sdd 5 0 0 5 removed 4 8 64 - faulty spare /dev/sde 7 8 96 - spare /dev/sdg
-
So sde is now faulty, back to the drawing board,
mdadm --stop dev/md0
mdadm --assemble --force --verbose /dev/md0 /dev/sd[bcdfg]
-
No dice.
root@NAS:~# mdadm --stop dev/md0
mdadm: error opening dev/md0: No such file or directory
root@NAS:~# mdadm --assemble --force --verbose /dev/md0 /dev/sd[bcdfg]
mdadm: looking for devices for /dev/md0
mdadm: /dev/sdb is busy - skipping
mdadm: /dev/sdc is busy - skipping
mdadm: /dev/sdd is busy - skipping
mdadm: /dev/sdf is busy - skipping
mdadm: /dev/sdg is busy - skipping
-
If the array doesn't stop running the second command will fail, cat /proc/mdstat
-
root@NAS:~# cat /proc/mdstat
Personalities : [raid6] [raid5] [raid4]
md0 : active raid5 sdb[1] sdg[7](S) sde[4](F) sdd[5] sdf[6] sdc[2]
14650675200 blocks super 1.2 level 5, 512k chunk, algorithm 2 [6/4] [_UUUU_]
unused devices: <none>
-
I take it although it's active it's not visible
-
I can see it in the webgui the state is clean, failed. Also it's visible on my network
-
So you can access the shares and files?
-
Yes and no. I can see the files but can’t read any of them.
-
Yes and no. I can see the files but can’t read any of them.
I think the option now is to leave it alone, get your backup restored and ready, then there are a number of options to get the data off the raid to your backup drive, that's if the files can be moved. I have not come across your situation before but it's a proceed with caution.
There is one option you could try if you have a W10 machine install WinScp and login to the server as root using WinScp and see if you can browse the files on the array, if you can then try and move one file to your W10, if that fails then I have another idea.
-
I was able to transfer some files but they are a fraction of the size
-
I was able to transfer some files but they are a fraction of the size
That means it's not reading the files on the array, I thought that would be the case, but worth a try, so one option, in your post 28 sde was displayed as faulty spare. I think that's the drive that failed the array, is that drive showing any SMART errors, so suggestion is this,
Locate where sde is in your server so that you can disconnect the sata cable.
Shut the server down and disconnect that drive either via the sata port on the board or removing the sata cable from the drive.
Restart the server, I'm hoping the array will come back up clean/degraded.
-
sde is showing SMART errors.
Jetzt mitmachen!
Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!