burnaby_boy

Members
  • Posts

    76
  • Joined

Everything posted by burnaby_boy

  1. Thanks so much for your prompt reply. I'll upgrade to 4GB of RAM and try updating again.
  2. I attempted to update Unraid from 6.9.2 to 6.11.3 using Update in the Tools section. A popup window opened showing the progress of the download and when it reached about 70% it stopped and showed "download failure (File I/O error)". I have successfully used this update method in the past, but it doesn't seem to be working now. I'd certainly appreciate some help with this issue. The diagnostics file is attached. media-diagnostics-20221112-1029.zip
  3. Sorry, upon further reading, I realized that I neglected to install the Unassigned Devices app in advance of Unassigned Devices Preclear.
  4. I am running Unraid 6.9.2. After uninstalling the old preclear plugin and rebooting the server, I attempted to install the Unassigned Devices Preclear app. When I clicked on the install button a popup appeared saying "Requirements not met - The requirements for this upgrade have not been met on your system". Any ideas as to what this means? Thanks
  5. Last night I added an Intel 520 120GB SSD as a cache drive to my array which is running unRAID 6.0.1. The array is set to notify me by email with notices, warnings and alerts. This morning I began receiving emails warning me of an increasing "uncorrectable error count" on the SSD. After a quick search I discovered that this drive has a bug that causes the uncorrectable error count to increase, though there is no problem with the drive. Is there any way to shut off the SMART health warnings for just this drive?
  6. I have been having the same error message for the past couple of weeks. Nothing has been changed regarding the configuration of the server for more than 6 months, and there are no addons being used. Any suggestions?
  7. Thanks mbryanr for the link. I have reverted the server back to v5.0 beta 14 and so far so good.
  8. When I typed in "cat /var/log/syslog" into telnet I copied everything that was generated into the text document that was attached. There was nothing else to copy.
  9. Thanks for the suggestion dgaschk. I have attached the output of "cat /var/log/syslog. syslog.txt
  10. Thanks for your responses. As I mentioned in my first post, I was able to telnet into the server, but it would not generate a syslog.
  11. As a last resort, I cleared the flash drive and reloaded my backup of the v5.0-rc4 files. I restarted the server and the webgui appeared, thankfully without starting a parity check. I'm going to bed and shall investigate further in the morning.
  12. I finally powered down the system by holding down the power button and then powered it on again. I am still not able to access the gui. I expect that it started a parity check upon restarting. What do I do?
  13. I found this thread - http://lime-technology.com/forum/index.php?topic=19561.0 - which suggested restarting the web gui through telnet using: killall emhttp nohup /usr/local/sbin/emhttp & After running this and attempting to access the web gui, I get a page that says "Unable to connect - Firefox can't establish a connection to the server at media."
  14. I am running version 5-rc5. A few minutes ago, I started a parity check. Normally, when I do this the web interface changes to show the progression of the parity check. However, this time the web page is blank. I was able connect to the server via telnet, and was able to generate a smart report for one of the drives, however no syslog is available. Also, I can connect to files on the server via the windows network, although it is somewhat slow to respond. I would appreciate some guidance as to how to proceed. Cheers
  15. 5.0-rc5 seems to be working fine for me, except that copying files over the network to the server seems to be somewhat slower than with rc4. With rc4 I was averaging about 30 MB/second whereas with rc5 I'm topping out at about 24 MB/second.
  16. After the upgrade to rc1 from beta 14 I've noticed a significant decrease in speed when copying to the server (with parity) - from 27 MB/s with beta 14, down to 10 MB/s with rc1. I'm using a Gigabyte P35-DS3P with a Supermicro AOC-SASLP-MV8 and an Adaptec 1430SA. The syslog is attached. Looks like I'll head back to beta 14. Update - after copying the beta 14 files back on to the flash drive and rebooting, the web interface eventually reappeared, but with a parity check already in progress. syslog.txt
  17. The drive passed the quick WD diagnostic and is currently being precleared. I'll check the smart report when its done and go from there. Thanks again for your assistance. Cheers
  18. Thanks for the suggestion. In order to minimize the downtime, I chose to swap in a precleared spare. Data rebuilding is in progress. Cheers
  19. The HDD in question is disk 6 of 16, a WDC WD15EARS-00Z5B1 and the PSU is a Corsair TX-650.
  20. When I checked the array this morning I noticed that Disk 6 had accumulated 33 errors overnight (there is still a green dot beside the disk). I ran a smart test for the disk which shows 5 for Current_Pending_Sector and 0 for the Reallocated_Sector_Ct. I have attached both the smart report and the relevant portion of the syslog. I'd appreciate some guidance on how to proceed. Cheers
  21. I replaced the drive with a spare and let unRaid rebuild - then ran WD's Data Lifeguard Diagnostic in Windows. It failed the quick test, so it's now on its way to WD for replacement. Thankfully, it was still under warranty. Cheers
  22. Thanks for your reply. The array had not yet been stopped when I attempted to access the drive in question. Are you saying that while the array is still running, unRaid will disable a drive that has errors, and use data is being generated by the other disks and parity? Sorry, I don't quite understand.
  23. Thanks for your suggestion. I'm wondering now if the drive is actually still spinning. When I tried to access the files on it, the video file played properly, but after a refresh of the browser page, the red ball beside the drive is still flashing, which to me indicates that it did not spin up, and that the video being played was the backup copy. I wonder if something more serious is going on.