May 21, 20197 yr Hello, earlier this month one my drives was spitting out errors and unraid ended up disabling it (Disk 1) tower-diagnostics-20190502-1415.zip, after previous issues with this happening and on recommendations from other members I replaced my raid card with an LSI 9211-8i. Once I got it installed and went through the process of de selecting the drive, starting then stopping the array, reelecting the drive and rebuilding it tower-diagnostics-20190521-1004.zip has had this "Unmountable: No file system" in its details (see attached screenshot). Being relatively new to unraid I was not sure or not if that when it rebuilt the array it would make the drive function again as normal. I am just asking what I should be doing to correct this, or is the drive potentially just not functioning properly and have likely lost the data that was on it? (as it is not on any of the other drives). Edited May 22, 20197 yr by J0my added more information
May 21, 20197 yr Community Expert Check filesystem on disk1: https://wiki.unraid.net/Check_Disk_Filesystems#Checking_and_fixing_drives_in_the_webGui or https://wiki.unraid.net/Check_Disk_Filesystems#Drives_formatted_with_XFS
May 21, 20197 yr Community Expert @johnnie.black I wonder if it is worth suggesting that when an Unmountable file system occurs it should become a link in the GUI rather than simply text.? That link could be to either the instructions in the wiki or to the relevant part of the gui (which is probably better as it does not require an Internet link) for running a file system check. Do you think this might make the correct behavior more discoverable? Is it worth raising as a feature request do you think? If so it feels like a change that can happen purely at the GUI level without needing a change to core Unraid code! Edited May 21, 20197 yr by itimpi
May 21, 20197 yr Community Expert 39 minutes ago, itimpi said: Is it worth raising as a feature request do you think? Sure, but only when the error is "no file system", if it's "invalid partition layout" it's a different problem.
May 21, 20197 yr Author 1 hour ago, johnnie.black said: Check filesystem on disk1: https://wiki.unraid.net/Check_Disk_Filesystems#Checking_and_fixing_drives_in_the_webGui or https://wiki.unraid.net/Check_Disk_Filesystems#Drives_formatted_with_XFS @johnnie.black Thanks for that, as per the wiki I ran -nv and it gave me these results, I put it in a txt doc to save this page getting super long xfs_repair status -nv .txt I am not going to pretend I know what any of that means so if possible what would the next step be based on its findings?
May 21, 20197 yr Author 3 minutes ago, johnnie.black said: Remove -n (no modify) @johnnie.blackso that would be just -v then?
May 21, 20197 yr Author 1 minute ago, johnnie.black said: Yes, if can then ask to zero the log, if yes use -vL. @johnnie.black Apologies, just the wording sounds a bit odd, that I don't quite understand. Are you just telling me to use -vL or are you saying do -v and then do -vL?
May 21, 20197 yr Author @johnnie.black here is the result of doing the -v xfs_repair status -v.txt xfs_repair status -v.txt Edited May 21, 20197 yr by J0my
May 21, 20197 yr Author @johnnie.black ok took it down from Maint mode and started the array and it seems to be present and working now with the files present. Is it after that you meant to now put it back into maint mode and do the -vL or leave it as is now. Then final question should I do a parity check again or is that not necessary (as it was disk 1 and not the parity drive that was having the problems).
May 21, 20197 yr Community Expert 6 minutes ago, J0my said: @johnnie.black ok took it down from Maint mode and started the array and it seems to be present and working now with the files present. Is it after that you meant to now put it back into maint mode and do the -vL or leave it as is now. Then final question should I do a parity check again or is that not necessary (as it was disk 1 and not the parity drive that was having the problems). As long as you ran the file system repair either from the Unraid GUI or from a command line against a /dev/mdX type device then parity will have been maintained (and updated appropriately as the repair took place). You can run a parity check if you like but it should not be necessary (although doing so will not do any harm either).
May 21, 20197 yr Author @itimpi thanks for your input, I did the repair from the Unraid GUI. It is scheduled to do the next parity check at the first of every month so I might just leave it for now. Thanks again to @johnnie.black it was a great help ❤️
Archived
This topic is now archived and is closed to further replies.