TedatTNT

Members
  • Posts

    61
  • Joined

  • Last visited

Everything posted by TedatTNT

  1. I'll be following this thread with interest!
  2. I've updated to 6.2.0 beta 18 and tested. So far, I have not had this problem. I'll continue to monitor and report back.
  3. When it fails to load with a kernel error, it says: Kernel Offset: disabled ---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) Does anyone know what this means?
  4. Okay, I've tried these steps - twice. Copying the bzroot-gui file was the easiest, so I started with that, even re-downloading the zip and copying it over. And, in addition to reformatting, I tried a different flash drive -- still no help. It doesn't load enough to have anything logged that I can post. The best I can offer is a video of it failing to fully load: https://www.dropbox.com/s/oh139mvkzu4xhef/Unraid.mp4?dl=0 Thanks, Ted
  5. Yeah, that was issue #1. But, after manually copying it, I ran into the other issue, and had to hard-power-down the server as it was locked. Even after copying it over, I cannot successfully boot into the GUI mode.
  6. I'm having issues with the Unraid GUI. First, I was running 6.x (not sure which version). I then initiated the installation using these instructions from the 6.2 post: ...and then I went to the Flash syslink config and moved the "default" line to the GUI mode section. After rebooting, I was stuck in a boot loop, trying to launch bzroot-gui, but never getting the OK -- just back to the options page with a timer before launching the default. I intervened by selecting the non-GUI version. I checked the flash drive, and found that bzroot-gui was missing from the flash drive. I downloaded the zip file and manually copied it over. I rebooted again. This time, there was no boot loop. Things began loading and then the last lines were: Kernel Offset: disabled ---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) I am still able to reboot in the non-GUI mode, but but GUI mode does this every time. Ideas?
  7. Send us an e-mail on it. I'll need to have Tom look at it. I've not heard anything back -- should I be expecting an email?
  8. Okay, I was finally able to copy the syslog from the console. It is attached. syslog-2016-03-09-003.txt
  9. Send us an e-mail on it. I'll need to have Tom look at it. I sent an email with a link to this thread.
  10. Drives are 34 - 39 degrees Not sure how to find the CPU temp. There is an addon for it, but you aslo need to install nerd pack and perl from the nerd pack. I just got a heat warning for one drive - 46 degrees.
  11. Silly question... How do I send a message to support? Is there a forum username that I use?
  12. Yes, the dual NIC's are the Marvell Yukon 88E8053's. I have the some issues no matter which is being used. Is there a HIGHLY recommended GB LAN card that I could purchase and test with? I'm asking because the Marvell Yukon's are on the hardware compatibility list.
  13. Okay, I've collected some video -- I'm hoping that this helps. I've edited it down to a 4-minute file and added a few notes and I'm hoping that for somebody, it will be clear what is going on. I can't attach a video here, so this is a link to the video on Dropbox... https://dl.dropboxusercontent.com/u/53914472/UNRAID-001.mp4 Thanks in advance... Ted
  14. When I went to take a photo, the lines were changing pretty quick, so I missed a bunch of them -- should I do it again -- maybe shoot video? Ted So, very strange... It only took a moment to make it freeze before -- just accessed a few files and hadn't even begun the Parity Check. This time, with a video camera recording the screen, I have transferred dozens of GB's of data and been running a Parity Check concurrently and it hasn't failed. I even tried accessing identical files. It seems that the fix is to keep a video camera recording the screen -- that was easier than I thought.
  15. When I went to take a photo, the lines were changing pretty quick, so I missed a bunch of them -- should I do it again -- maybe shoot video? Ted
  16. I have a new 3TB just sitting here and an empty slot - could definitely start with this. The only plugin (other than the included UNRAID Server OS and Dynamix webGUI) is ProFTPd -- I share files with others, occasionally. To test without it, can it be temporarily disabled, or would I have to uninstall it completely and reconfigure it again later?
  17. Drives are 34 - 39 degrees Not sure how to find the CPU temp.
  18. When this happens, I can no longer access the UNRAID server via any means by which one would access it over a network. No web GUI, no telnet, no shares, nothing. Yes, after a reboot (and starting the array), everything works until the next time that it doesn't. Any reading/writing via the network fails. The parity check completes successfully. Keyboard/mouse -- I have a keyboard/mouse/monitor attached to my UNRAID server. These still work and do not appear to have suffered an issue. I can still type in commands directly and they still work. I'm not running headless -- is there a different method that I should employ? I was able to spin up all drives and it worked fine. I could browse files / open files on various drives. I don't know what cache_dirs is.
  19. Thanks -- I will look into this. My fear, though, is that the system would 'hang' during the process and I'd have a hell of a time getting it completed. Still, I'm very tempted to proceed.
  20. I upgraded the motherboard a couple of years ago from from an ASRock MB that was short on PCIe to an ASUS P5W-DH Deluxe board that was retired from being a HTPC. I also added PCIe for additional SATA ports. It seemed to work beautifully for weeks. I also updated the software at that point. A couple of months later, I began to notice problems.
  21. To clarify, these are the issues that I have had THROUGH the last two software updates. Every time I use the UNRAID heavily (moving/saving/accessing large files or LOTS of small files), I lose the ability to communicate with my UNRAID server via Telnet or via the web GUI. I can still use a keyboard/mouse/monitor. Every time I perform a parity check (or one is performed automatically), I lose the ability to communicate with my UNRAID server via Telnet or via the web GUI. I can still use a keyboard/mouse/monitor. This has been an issue for more than a year! I have posted and asked for help numerous times, but even though there are some very helpful folks here, we haven't found a solution and I am about a month away from giving up and buying a Drobo. Here are things that we've tried: posting the diagnostic report (attached) - although I can only get it after a reboot, so it isn't real helpful moving the Ethernet cable to the other NIC on my MB -- both NICs use chipsets recommended on the HCL Using a PCI-based, add-on NIC Replacing one drive that reported some SMART issues Running memtest, swapping memory, running again, etc. Replacement of the power supply Replacement/reloading the USB flash drive I'm at my wit's end -- I'm hoping somebody has some insight that will help me regain the stability that I had four/five years ago, but haven't had in over a year. unraid-diagnostics-20160309-0811.zip
  22. Follow up -- Days later, still working well...