September 16, 20196 yr ok how to start i have a array of 20 hdd's with 2 parity about 3 days ago i had a HDD go bad thats ok im waiting on the RMA which should becoming tomorrow so disk 1 was being emulated and today i come home and found the server off when i rebooted i have my 2nd parity drive disabled and another disk from the array was saying xfs Unmountable: Unsupported partition layout
September 16, 20196 yr Community Expert 18 minutes ago, gavin_UK said: how to start Go to Tools - Diagnostics and attach the complete diagnostics zip file to your next post (of course).
September 16, 20196 yr Community Expert Try again. 8 minutes ago, trurl said: Go to Tools - Diagnostics and attach the complete diagnostics zip file to your next post
September 16, 20196 yr Author abyss-diagnostics-20190916-2308.zip thanks Edited September 16, 20196 yr by gavin_UK none
September 16, 20196 yr Community Expert It's having problems accessing disk7 and there is no SMART report for disk7 in the diagnostics. Check connections and post a new diagnostic.
September 16, 20196 yr Author sorry i gave you the wrong diagnostic i had the hdd out of the bay this is the correct oneabyss-diagnostics-20190916-2339.zip Edited September 16, 20196 yr by gavin_UK .
September 17, 20196 yr Community Expert Stop the array and restart it in Maintenance Mode. Then click on disk7 to get to its page to Check the filesystem. Post the output.
September 17, 20196 yr Author thanks for your reply this is the log Phase 1 - find and verify superblock... Phase 2 - using internal log - zero 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 - agno = 1 - agno = 2 - agno = 3 - agno = 4 - agno = 5 - agno = 6 - agno = 7 - agno = 8 - agno = 9 - agno = 10 - agno = 11 - agno = 12 - agno = 13 - process newly discovered inodes... Phase 4 - check for duplicate blocks... - setting up duplicate extent list... - check for inodes claiming duplicate blocks... - agno = 0 - agno = 1 - agno = 2 - agno = 4 - agno = 3 - agno = 5 - agno = 9 - agno = 6 - agno = 8 - agno = 7 - agno = 11 - agno = 10 - agno = 12 - agno = 13 No modify flag set, skipping phase 5 Phase 6 - check inode connectivity... - traversing filesystem ... - traversal finished ... - moving disconnected inodes to lost+found ... Phase 7 - verify link counts... No modify flag set, skipping filesystem flush and exiting.
September 17, 20196 yr Community Expert Rerun without the -n (check only) flag and the drive should then end up mountable.
September 17, 20196 yr Quick question, is the model of the drive the same as the one you RMAed? Same day of purchase, same order?
September 17, 20196 yr Author 2 hours ago, bastl said: Quick question, is the model of the drive the same as the one you RMAed? Same day of purchase, same order? the model of the drive which is a RMAed is to replace disk 1 which is a 6TB WD Red pro ive done the Rerun without the -n this is the log Phase 1 - find and verify superblock... Phase 2 - using internal log - zero log... - scan filesystem freespace and inode maps... - found root inode chunk Phase 3 - for each AG... - scan and clear agi unlinked lists... - process known inodes and perform inode discovery... - agno = 0 - agno = 1 - agno = 2 - agno = 3 - agno = 4 - agno = 5 - agno = 6 - agno = 7 - agno = 8 - agno = 9 - agno = 10 - agno = 11 - agno = 12 - agno = 13 - process newly discovered inodes... Phase 4 - check for duplicate blocks... - setting up duplicate extent list... - check for inodes claiming duplicate blocks... - agno = 0 - agno = 4 - agno = 6 - agno = 1 - agno = 3 - agno = 5 - agno = 7 - agno = 8 - agno = 9 - agno = 2 - agno = 10 - agno = 11 - agno = 12 - agno = 13 Phase 5 - rebuild AG headers and trees... - reset superblock... Phase 6 - check inode connectivity... - resetting contents of realtime bitmap and summary inodes - traversing filesystem ... - traversal finished ... - moving disconnected inodes to lost+found ... Phase 7 - verify and correct link counts... done done a restart of the array and disk 7 is Unmountable: Unsupported partition layout also as i have 2 parity drives ok parity 1 is disabled for some reason im sure that was from crc errors parity2 i hope is standing in for disk 1 which im waiting for my RMA today at some point what is the best thing to day about disk 7 ? as it looks like ive only got 1 parity drive running Edited September 17, 20196 yr by gavin_UK adding more info
September 17, 20196 yr Community Expert 2 hours ago, gavin_UK said: Unmountable: Unsupported partition layout This error means the partition is the problem, not the filesystem, i.e., the partition doesn't conform to Unraid standard, which is quite strange if it was working before, rebuilding the disk would re-create the partition and keep the data (assuming parity is valid), but I wouldn't try that before fixing the other disabled disks. Edited September 17, 20196 yr by johnnie.black
September 17, 20196 yr Community Expert To re-enable a disk (Using the same disk) do the following: Stop the array unassign the drive start the array to commit the current assignments (and ‘forget’ the drive just unassigned) Stop the array assign the drive start the array to rebuild the drive (either parity or data as appropriate).
September 17, 20196 yr Community Expert But you really need to rebuild disk1 also. And it isn't showing in your latest diagnostics. Why?
September 17, 20196 yr Author 9 minutes ago, trurl said: But you really need to rebuild disk1 also. And it isn't showing in your latest diagnostics. Why? disk one is being emulated i guess from the 2nd parity disk the drive was dead its been taking out sent back for a RMA which i should be getting today should i replace this before i try To re-enable the 1st parity disk (Using the same disk) do the following: Stop the array unassign the drive start the array to commit the current assignments (and ‘forget’ the drive just unassigned) Stop the array assign the drive start the array to rebuild the drive (either parity or data as appropriate). Edited September 17, 20196 yr by gavin_UK more info
September 17, 20196 yr Community Expert Since you have parity2 you can rebuild parity1 even with missing disk1. That would be better than your current situation, since you have no redundancy now with 2 disabled disks.
September 17, 20196 yr Author This is what im worried about when i get the replacement disk for disk 1 and go to start the array its going to say do a parity sync to copy data back over to the new disk would it also force Disk 7 (discarding all data currently on those disks) to format as thats what i keep getting on the Array Operation panel ive only got one parity drive working with a 2nd faild hdd being emulated with a 3rd hdd Unmountable: Unsupported partition layout it dont say it's disabled or being emulated does that just mean the files are not being seen
September 17, 20196 yr Author 5 minutes ago, trurl said: Since you have parity2 you can rebuild parity1 even with missing disk1. That would be better than your current situation, since you have no redundancy now with 2 disabled disks. would it not effect disk 7
September 17, 20196 yr Author ok its doing a parity sync on to the 1st parity dive only 26 hours togo disk 7 was able to stay as it was would you say after that i should replace my disk one with the new RMA'ed one and the do a parity sync to just that or format disk 7 and replace disk one and do both at the same time
September 17, 20196 yr 12 minutes ago, gavin_UK said: format disk 7 Are you ok with erasing all the data that was originally on disk7? That's what format will do.
September 17, 20196 yr Community Expert Look closer at your screenshot. The Format button is disabled. It won't format unless you check the box to enable the button then press the button.
September 17, 20196 yr Community Expert Just now, gavin_UK said: wouldn't it just be replaced from a parity sync ? Format is a write operation. It writes an empty filesystem to the disk. Unraid treats that write operation just as it does any other write operation, it updates parity. So after formatting a disk in the parity array, parity agrees the disk has an empty filesystem.
Archived
This topic is now archived and is closed to further replies.