bmilcs Posted February 17, 2020 Share Posted February 17, 2020 (edited) 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, 2020 by bmilcs Quote Link to comment
JonathanM Posted February 17, 2020 Share Posted February 17, 2020 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. Quote Link to comment
bmilcs Posted February 17, 2020 Author Share Posted February 17, 2020 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 Quote Link to comment
bmilcs Posted February 17, 2020 Author Share Posted February 17, 2020 (edited) 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, 2020 by bmilcs Quote Link to comment
trurl Posted February 17, 2020 Share Posted February 17, 2020 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. Quote Link to comment
bmilcs Posted February 17, 2020 Author Share Posted February 17, 2020 (edited) 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, 2020 by bmilcs Quote Link to comment
trurl Posted February 17, 2020 Share Posted February 17, 2020 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. Quote Link to comment
trurl Posted February 17, 2020 Share Posted February 17, 2020 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? Quote Link to comment
bmilcs Posted February 17, 2020 Author Share Posted February 17, 2020 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. Quote Link to comment
trurl Posted February 17, 2020 Share Posted February 17, 2020 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. Quote Link to comment
trurl Posted February 17, 2020 Share Posted February 17, 2020 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. Quote Link to comment
bmilcs Posted February 17, 2020 Author Share Posted February 17, 2020 (edited) 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, 2020 by bmilcs Quote Link to comment
bmilcs Posted February 17, 2020 Author Share Posted February 17, 2020 (edited) 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, 2020 by bmilcs Quote Link to comment
bmilcs Posted February 17, 2020 Author Share Posted February 17, 2020 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. Quote Link to comment
itimpi Posted February 17, 2020 Share Posted February 17, 2020 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. Quote Link to comment
bmilcs Posted February 17, 2020 Author Share Posted February 17, 2020 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. Quote Link to comment
bmilcs Posted February 18, 2020 Author Share Posted February 18, 2020 Results of -L xfs and new diagnostics unraid-diagnostics-20200217-1928.zip Quote Link to comment
bmilcs Posted February 18, 2020 Author Share Posted February 18, 2020 Ran it again without -L: Quote Link to comment
bmilcs Posted February 18, 2020 Author Share Posted February 18, 2020 Running a Parity-Sync/Data-Rebuild. Wish me luck. Quote Link to comment
trurl Posted February 18, 2020 Share Posted February 18, 2020 7 minutes ago, bmilcs said: Running a Parity-Sync/Data-Rebuild. Wish me luck. Was the repaired emulated disk mountable? Quote Link to comment
trurl Posted February 18, 2020 Share Posted February 18, 2020 1 minute ago, trurl said: Was the repaired emulated disk mountable? Doesn't look like it from those last diagnostics you posted. Quote Link to comment
itimpi Posted February 18, 2020 Share Posted February 18, 2020 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. Quote Link to comment
bmilcs Posted February 18, 2020 Author Share Posted February 18, 2020 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 Quote Link to comment
Dissones4U Posted February 18, 2020 Share Posted February 18, 2020 Might the CRC error shown in the SMART for D4 be a bad/loose cable? Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.