June 23, 20179 yr After booting, I can start and access the array without issue. However, after between 1d12h and 2days of uptime, all the disks disappear from the web UI and are inaccessible over the network. I can, though, SSH into the system, sync and reboot. When the system comes back up, all the disks show up in the web UI and the array will stay up for another couple of days. The cycle then repeats. I've tried not starting the array to see if that action is the catalyst, however the same outcome still occurs after about 2 days. Prior to this, I was using version 5 without issue. Edited June 23, 20179 yr by imdoug
June 23, 20179 yr Author 3 minutes ago, bonienl said: Can you post your diagnostics file, see Tools -> Diagnostics tower-diagnostics-20170622-2356.zip
June 23, 20179 yr The diagnostics are from after you rebooted the system and don't hold errors. Looking again to your screenshot it looks like your flash device goes offline. Try a different USB port, preferably USB2 and see if that improves your situation.
June 23, 20179 yr Author 5 hours ago, bonienl said: The diagnostics are from after you rebooted the system and don't hold errors. Looking again to your screenshot it looks like your flash device goes offline. Try a different USB port, preferably USB2 and see if that improves your situation. I'll have to wait about a day before the failure occurs, again. I'll grab new diagnostics at that time, and then try a different USB port (all the USB ports on my unRAID system motherboard, an ASRock C2750D4I, are USB 2.0). I appreciate your help.
June 25, 20179 yr Author On 6/23/2017 at 3:51 AM, bonienl said: The diagnostics are from after you rebooted the system and don't hold errors. Looking again to your screenshot it looks like your flash device goes offline. Try a different USB port, preferably USB2 and see if that improves your situation. The failure occurred again a short time ago. I cannot seem to get diagnostics in this condition. When I attempt to download them, I get a 404 error.
June 27, 20179 yr Author On 6/25/2017 at 3:27 AM, bonienl said: Move your USB device to another port. It becomes inaccessible after while. I tried a different USB port on the rear I/O, but it had no effect. I'm presuming that the problem is either with the rear I/O USB bus, or the USB device, itself. I'm now trying a port on the front of the case.
July 7, 20179 yr Author On 6/25/2017 at 3:27 AM, bonienl said: Move your USB device to another port. It becomes inaccessible after while. It does not appear to be the ports or the device. I changed the appropriate setting to automatically start the array after booting. I figured that, if I had to keep rebooting every couple of days, the extra seconds taken to manually start the array would add up. I don't know why or how, but empirically, that seems to have solved things. Current uptime is 3 days.
July 7, 20179 yr 9 minutes ago, imdoug said: I changed the appropriate setting to automatically start the array after booting By itself, that won't make a difference.
July 7, 20179 yr Author 1 minute ago, Squid said: By itself, that won't make a difference. I agree, I don't see how it could possibly impact the issue, but unless I was sleepwalking, that was the only change I had made since the last reboot.
August 25, 20178 yr 15 hours ago, HellDiverUK said: Another dodgy AsRock...will people ever learn? Nothing wrong with ASRock that I haven't found with other makers including Asus, Gigabyte, etc... They can all have problems. I think it is more based on model then Manufacturer - and often bios updates correct those errors.
Archived
This topic is now archived and is closed to further replies.