February 17, 20206 yr Can someone give me an idea as to what's going on with this drive? It was nearly full and I was just about to add more storage. I'd greatly appreciate it! My only option is to remount it, format as XFS and rebuild it seems. Thanks WDC_WD80EMAZ-00WJTA0_1SHJY4VZ-20200217-1442 disk4 (sdc) - DISK_DSBL.txt Edited February 17, 20206 yr by bmilcs
February 17, 20206 yr 14 minutes ago, bmilcs said: My only option is to remount it, format as XFS and rebuild it seems. I'm not sure what you mean by this, if you format it all the data will be gone, and the rebuild will be an empty disk. Is that what you want? Unmountable means file system corruption, not typically a disk failure. Rebuilding an unmountable disk will result in the same unmountable corrupt content. Tools, diagnostics, attach the zip file to your next post.
February 17, 20206 yr Author I received this error this afternoon and am not sure what my next steps are. "Unmountable: No File System" for a drive that was roughly 80% full previously. When I hover over the red X, it says my drive is being emulated (from parity I'm guessing?). What is my best course of action? Is my drive dying? Unraid is giving me the option to Format Disk 4 unraid-diagnostics-20200217-1643.zip
February 17, 20206 yr Author 1 hour ago, jonathanm said: I'm not sure what you mean by this, if you format it all the data will be gone, and the rebuild will be an empty disk. Is that what you want? Unmountable means file system corruption, not typically a disk failure. Rebuilding an unmountable disk will result in the same unmountable corrupt content. Tools, diagnostics, attach the zip file to your next post. Apologies for the lack of details. I recreated the post for you here. I assume that's what you meant. Sorry if you meant reply. Edited February 17, 20206 yr by bmilcs
February 17, 20206 yr Community Expert DO NOT FORMAT!!!! The disk is disabled, and the emulated disk is unmountable, so there will have to be both filesystem repair and rebuild. Try repairing the emulated filesystem first then if it is mountable you can rebuild. There was a video about filesystem repair on that other thread you replied on. Be sure to capture the output during filesystem repair so you can post it for further advice.
February 17, 20206 yr Author 2 minutes ago, trurl said: DO NOT FORMAT!!!! The disk is disabled, and the emulated disk is unmountable, so there will have to be both filesystem repair and rebuild. Try repairing the emulated filesystem first then if it is mountable you can rebuild. There was a video about filesystem repair on that other thread you replied on. Be sure to capture the output during filesystem repair so you can post it for further advice. Thank you for the guidance. Are there any scripts that help with umounting user shares that get stuck? This occurs frequently if I simply want to take down the array. " Array Stopping•Retry unmounting user share(s)..." Edited February 17, 20206 yr by bmilcs
February 17, 20206 yr Community Expert 24 minutes ago, bmilcs said: Is my drive dying? SMART for disk4 looks OK. Syslog starts with the disk already disabled and unmountable so unless you have syslog from before you rebooted nothing else to go on.
February 17, 20206 yr Community Expert 2 minutes ago, bmilcs said: Are there any scripts that help with umounting user shares that get stuck? Do you have anything accessing user shares? Dockers, VMs, other computers?
February 17, 20206 yr Author I have mapped network drives on a Windows machine. i've tried disabling my ethernet card on it for a min or so, and it still doesn't unmount.
February 17, 20206 yr Community Expert Go to Settings - Disk Settings and disable autostart. Then when you reboot it won't start anything and you should be in a position where you can proceed with filesystem repair.
February 17, 20206 yr Community Expert 37 minutes ago, bmilcs said: Apologies for the lack of details. I recreated the post for you here. I assume that's what you meant. Sorry if you meant reply. I have merged your threads. Please don't create multiple threads for the same problem.
February 17, 20206 yr Author 5 minutes ago, trurl said: I have merged your threads. Please don't create multiple threads for the same problem. Apologies. I thought that's what was requested of me: "Tools, diagnostics, attach the zip file to your next post." 12 minutes ago, trurl said: Go to Settings - Disk Settings and disable autostart. Then when you reboot it won't start anything and you should be in a position where you can proceed with filesystem repair. I ended up doing just that. Thank you. Are the results of the xfs repair sent to a log file for me to post? Should I run it in verbose mode w/o -n to repair it? Edited February 17, 20206 yr by bmilcs
February 17, 20206 yr Author If I go ahead and mount the file system, I'll be unable to unmount it and rerun the repair. :X Edit: I think I know what's causing the issue. I recently created a User Script to do a syslog tail to the array. Could that be the issue? Disregard. Fixed the issue. Edited February 17, 20206 yr by bmilcs
February 17, 20206 yr Author Alright. I am able to now mount and unmount the array successfully. However, this error is persisting, even after remounting the array in normal mode.
February 17, 20206 yr Community Expert 4 minutes ago, bmilcs said: Alright. I am able to now mount and unmount the array successfully. However, this error is persisting, even after remounting the array in normal mode. That is saying you need to run the repair without the -n (no modify) flag and with the -L flag added. That is quite normal despite the ominous sounding warning.
February 17, 20206 yr Author Just now, itimpi said: That is saying you need to run the repair without the -n (no modify) flag and with the -L flag added. That is quite normal despite the ominous sounding warning. I was scurred. I tried running it without any arguments as -L sounds like impending doom... "may cause corruption". Running it now w/ -L.
February 18, 20206 yr Author Results of -L xfs and new diagnostics unraid-diagnostics-20200217-1928.zip
February 18, 20206 yr Community Expert 7 minutes ago, bmilcs said: Running a Parity-Sync/Data-Rebuild. Wish me luck. Was the repaired emulated disk mountable?
February 18, 20206 yr Community Expert 1 minute ago, trurl said: Was the repaired emulated disk mountable? Doesn't look like it from those last diagnostics you posted.
February 18, 20206 yr Community Expert 4 hours ago, bmilcs said: Running a Parity-Sync/Data-Rebuild. Wish me luck. What was the state of the emulated disk after running the repair? Whatever was on the emulated disk at that point is what you will end up w9th after doing a rebuild onto the physical drive.
February 18, 20206 yr Author After running xfs repair again w/o -L, the Unmountable Disk Error disappeared and I was able to begin a rebuild. Here's current diagnostics. unraid-diagnostics-20200218-0609.zip
Archived
This topic is now archived and is closed to further replies.