willison.joshua

Members
  • Posts

    12
  • Joined

  • Last visited

Converted

  • Gender
    Undisclosed

willison.joshua's Achievements

Noob

Noob (1/14)

0

Reputation

  1. I am having the same unreachable problem with 6.7 stable. I went to the physical machine and was able to update bzroot to boot into GUI (awesome feature btw!!). Everything looked ok from localhost GUI. I performed an OS roll back, but I am still unable to access via web GUI. I plan to continue troubleshooting by performing memtest, and then cracking open the case and removing both SAS cards (Supermicro AOC-SAS2LP-MV8). Is there anything else that can be done?
  2. thanks Johnnie! I had to use the CLI (could not access cache via network) but I was able to delete the files. Any idea how this happened? Should I consider this a fluke or try to investigate further to prevent it from happening again
  3. Makes sense. How do I delete the file from the cache drive? I cant seem to figure it out via GUI
  4. thanks for the mover logging tip, that added a little more clarity. The log is now saying that the file exists: mover: started move: file [redacted] move_object: [redacted] File exists mover: finished Any way to either delete from the cache drive or override the move action to force the overwrite?
  5. Yes I understand, and wouldn't be concerned expect there is content showing up when I open the file viewer and in the share tab there is a warning that one of my shares is not fully protected. Sent from my Pixel 2 XL using Tapatalk
  6. I noticed that the cache drive had about 300mb of space used. I have not saved anything to the unRAID system in a few days so I manually invoked the mover. Nothing happened, the space used on the cache drive is still being used, and the drives did not throw any errors. I have performed a filesystem check on each drive and rebooted the server several times. All with the same outcome- nothing's changed. I cannot figure out how to invoke the mover. diagnosis zip is below, after a fresh reboot and a manual press of 'move now'. tower-diagnostics-20181024-1505.zip
  7. Thanks for the help I unplugged the optical drive, and that allowed the array to start. I will further troubleshoot the optical drive, but for now the immediate need of getting to my data has been addressed.
  8. There are no hardware changes, but I'll investigate ata13 in case something died.
  9. Good Point tower-diagnostics-20170721-1453.zip
  10. I dont think I did, but perhaps without thinking I attempted to start it again. Let me know if I need to provide another log It better be 1000, but thats a different problem for me to investigate later once the array is back online.
  11. From a cold boot, the array does not start (either automatically or manually). OS boots, GUI works, all drives light up green. No errors with the array or drives shown on GUI. Troubleshooting steps so far: removed the USB drive containing the OS and scanned it using a Windows system checking for errors, none found Installed Fix Common Problems plugin, ran it, fixed issues concerning notifications and SS plugin for cache drives. Scan did not run in detail because array was not started ran SMART reports, all drives passed. Reboots and Turn On/ Off and repeated scans have not worked. I have attached the diagnosis zip diagnostics-20170721-1115.zip