steve1977 Posted February 10, 2018 Share Posted February 10, 2018 One of my disks just disabled. Not clear to me whether this is an actual HD error or "just" again cabling (which I used to have historically quite a bit). The issue appears to be new / different this time though. I cannot run a SMART test as it says that the disk needs to spin up. Log pre-restart below tower-diagnostics-20180210-0009.zip Link to comment
steve1977 Posted February 10, 2018 Author Share Posted February 10, 2018 I did the restart of Unraid and it now runs an extended smart (the short one was fine). I'll post a new log after extended SMART, but would also be good to know if you see anything in the pre-restart log posted above. Link to comment
JorgeB Posted February 10, 2018 Share Posted February 10, 2018 5 hours ago, steve1977 said: but would also be good to know if you see anything in the pre-restart log posted above. No, because the disk dropped offline so there's no SMART report, and all 3 syslog files are spammed with messages similar to this: Feb 9 23:59:37 Tower shfs: error: shfs_create, 2074: No space left on device (28): assign_disk: TV/Ncis/Season 3/NCIS - S03E18 - Bait - Bluray-1080p.mkv.partial~ Feb 9 23:59:37 Tower shfs: error: shfs_create, 2074: No space left on device (28): assign_disk: TV/Ncis/Season 3/NCIS - S03E14 - Light Sleeper - Bluray-1080p.mkv.partial~ Feb 9 23:59:37 Tower shfs: error: shfs_create, 2074: No space left on device (28): assign_disk: TV/Ncis/Season 3/NCIS - S03E13 - Deception - Bluray-1080p.mkv.partial~ Feb 9 23:59:38 Tower shfs: error: shfs_create, 2074: No space left on device (28): assign_disk: TV/Ncis/Season 3/NCIS - S03E12 - Boxed In - Bluray-1080p.mkv.partial~ Feb 9 23:59:38 Tower shfs: error: shfs_create, 2074: No space left on device (28): assign_disk: TV/Ncis/Season 3/NCIS - S03E08 - Under Covers - Bluray-1080p.mkv.partial~ Link to comment
John_M Posted February 10, 2018 Share Posted February 10, 2018 It looks as though you need to check your user share settings. It looks as though you have the Minimum free space parameter set too low. Increase it to be larger than the largest file you expect to write to your array. Otherwise it will keep trying to write files to your almost completely full disk and failing instead of moving on to the next one. Link to comment
steve1977 Posted February 10, 2018 Author Share Posted February 10, 2018 Got it. Let me increase the minimum free space. Assuming the extended SMART completes without errors, what would be the better way to setup the array. Just reconfig again or rebuild the same disk via parity (which falsely got disabled)? Link to comment
JorgeB Posted February 10, 2018 Share Posted February 10, 2018 Rebuilding to the same disk can be riskier if another disk fails during the rebuild, not so much risk with dual parity, but always check that the contents on the emulated disk look correct before rebuilding, doing a new config also has risks since the array will be unprotected until the sync finishes and it's only an option if you're sure nothing was written to the emulated disk (or doen't mind losing that data). Best option would be rebuilding to a new disk, closely followed by rebuilding to the same if you have dual parity. Link to comment
steve1977 Posted February 12, 2018 Author Share Posted February 12, 2018 thanks. extended smart was fine. i’m now doing a new config.could the “user share issue” have caused the disabling of the disk?Sent from my iPhone using Tapatalk Link to comment
itimpi Posted February 12, 2018 Share Posted February 12, 2018 1 hour ago, steve1977 said: could the “user share issue” have caused the disabling of the disk? No. Thar can only result in you losing data because files end up being zero length. Link to comment
Recommended Posts
Archived
This topic is now archived and is closed to further replies.