Jump to content


  • Content Count

  • Joined

  • Last visited

  • Days Won


Auggie last won the day on October 4 2018

Auggie had the most liked content!

Community Reputation

2 Neutral

About Auggie

  • Rank
    Advanced Member


  • Gender
  • URL

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. For me, I'm concerned about running an UnRAID-based media server in VM; it doesn't matter for my backup server. All my videos are 1:1 imaged full Blu-Ray discs (which precludes running Plex or any other current media streamer) so anything that could impede performance and cause drop-outs, stuttering, or pauses in playback would be unacceptable.
  2. This would be a sufficient solution for my very narrow needs. If the multiple-array feature should eventually be incorporated, then I would definitely want to run multiple arrays (servers) on the same iron since at the max data drive capacity, my 48-bay Chenbro would never be fully utilized (prefer to run native vs virtual to reduce the potential for latency issues during media playback).
  3. I should add that I'm not seeing this issue with my other UnRAID NAS, which uses an older X9SCM motherboard with one SuperMicro AOC-SAS2LP HBA, one LSI 9211-8i (IT Mode) HBA, and one IBM M1015 (IT Mode) HBA. The X11 setup has built-in SAS3 3008 chip (IT Mode) connected to the Chenbro's built-in SAS expanders so the latest UnRAID version appears to have an issue with this setup.
  4. I noticed this sometime ago, but I wasn't sure exactly what was happening. About a month ago I noticed 128 errors after a parity check was completed but saw it only after a week or so had already passed. All SMART reports were good. I ran my monthly parity check several days ago and the exact same number of 128 errors occurred. All SMART reports were again good with zero anomalies on all drives. The syslog showed a spin down an hour or so after parity check was started (FYI, my disk settings are set to spin down after an hour) and that's when the read I/O errors occurred (specifically involving only three drives at that time). After performing an XFS repair on the three drives with zero issues, I again ran the parity last night. This morning, I noted in the syslog that again an hour after parity check was initiated, UnRAID spun down ALL drives and soon thereafter I/O errors on ALL drives were reported. Two hours later, again UnRAID spun down ALL drives and I/O errors started. This appears to be a UnRAID 6.7 bug wherein it's incorrectly spinning down drives that may be physically I/O active. I don't believe its hardware related as I've had this particular motherboard/chassis (SuperMicro X11SPH/Chenbro 48-bay RM43348) combination running for over six months now and never experienced anything like this before. Attached is my syslog (FYI, the parity check is still in progress and although there were numerous I/O errors, the parity check has reported ZERO errors thus far). syslog.txt
  5. It appears the problem is due to the Dynamix Cache Dirs, which I had installed recently. Removing it and the issue has not surfaced since.
  6. This has been an ongoing irritating issue with my Media Server for some time now; I can't pinpoint when this started happening, whether it was in recent 6.x releases or earlier releases (I don't recall experiencing this issue under v5 and certainly not under v4). Upgrading to a completely brand new system in every single aspect has not resolved the issue. As I watch a movie, every 20 minutes or so the video would freeze for 10-20 seconds. It's almost like clockwork. I have several different media players from different companies so it's not an issue specific to media players (though my Oppo 203 seems to experience this less often; however, it is used only to watch 4K). If I log onto the NAS and spinup all drives, this seems to alleviate the issue for the remainder of the movie. These movies are full copies; no re-encoding so they command a lot of NAS/network traffic when playing. Regarding network, I recently moved so the topology is completely different, with only one switch (16-port rackmount NetGear ProSafe) transferred to new LAN. My drives are set to the default 1 hour spin down delay. I don't believe the issue is with the specific drive the movie is on, but I haven't dug into the logs to see if UnRAID was attempting to spin that drive down, or any other drives. Perhaps it's when UnRAID is attempting to spin another drive down that it unexpectedly causes a problem with other drives. I have the Cache Directories, Auto Fan Control (I no longer need this and will delete), Nerd Tools, VM Wake-On-LAN, and Unassigned Drive plugins. My VMs are currently not running (haven't resolved libvert service error since hardware migration), though they have been in the past. When It happens again, I will try to review the logs at that time. Until then, has anyone else experienced this issue?
  7. Interesting. I will test on my 9211-8i to see if the LSI's are more immune to the PWDIS feature...
  8. Is there one molex connector per backplane, or two? The version with one is the newer with which the system I have had to have the pins taped. If you have the single, what HBA's are you using?
  9. It didn't with mine with 1 LSI 9211-8i, 1 SuperMicro SAS2LP, and 1 IBM M1015, connected to a Norco 4224. Not sure which of the HBA's I initially tried without taping, but it was with at least two drives that I experienced no power-up unless the pins were taped, after which I started taping them all immediately after shucking. FWIW, the Norco in this setup is the "newer" version that supports only a single PSU and thus has a differently designed "backplane". I've retired this case and relocating the X9 hardware to my older, dual-PSU capable 4224 for my backup server. And next PWDIS drive I get I'll test it without tape in both my new Chenbro as well as the Norco system (all three HBA's)... FYI, rebuilding an 8TB drive on the X9/Norco setup netted an average of 110MB/s. Rebuilding a 6TB of the same array on the new X11/Chenbro averaged 198MB/s, and replacing an 8TB with a 10TB averaged 117MB/s; the CPU utilization maybe pegged 50% now and then, but it was typically idling around 5%, unlike the X9/Pentinum which maxxed out quite often during rebuilds. Certainly a big step up, especially for my VMs. Now I have to build a noise reduction cabinet to quiet down this maddingly howling rig, and upgrade my home network to 10Gb...
  10. I got it all sorted out so this is to provide closure and hopefully help anyone else who expereinces similar networking issues. By default, UnRAID automatically activates and uses the first network interface it comes across, which may not be the physical first one (i.e. eth0, which is the case on my SuperMicro X9 board as UnRAID selected eth1 as the default), regardless of which port is physically connected to the LAN. All other network interfaces are then automatically set to inactive (shutdown). Since I didn't know the physical port order on the 2-port IBM NIC, I had plugged the ethernet cable to the most convenient one at the time of initial setup, which happened to be port 2 (eth1), which was the port closest to the motherboard PCIe slots. This caused all the problems I had experienced with no IP assignments and thus no network connectivity other than through the dedicated IPMI port. During my back and forth testing, I had by chance reconnected the ethernet cable to the other port (port 1 or eth0) when I had installed the trial UnRAID stick. This is why UnRAID network connectivity had become fully functional under that system, which I had initially attributed it to some configuration setting difference between my registered UnRAID stick and the trial; that was not the case here. It's all due to how UnRAID detects, enables, and disables the network ports it discovers. My recommended procedure for handling a new system and/or new NIC with multiple ports is to boot UnRAID into GUI mode (I had never before used the console GUI as all my UnRAID servers are headless) to determine which port had been assigned the default network port, and if it's currently active. If not, you can either switch the cable to the actively assigned port, or manually enable and assign the port you wish to use on the Network Settings page.
  11. Most of the Easystore/My Book drives are "white label" Red drives and may need pins 1-3 taped to disable the SATA 3.2+ spec Power Disable (PWDIS) function in order for most motherboards to recognize them through their SATA ports, both onboard and HBAs. The current anecdotal evidence, and my own experience, shows the 10TB Easystore's are presently assembled with white label WD100EMAX drives which have this PWDIS feature. On my SuperMicro X7 and X9 boards with a mix of SAS2LPs, 9211-8i's, and M1015 HBA's in Norco RPC-4224 chassis, I've had to tape the pins for these newer-spec'd drives. I just got my new X11 system up and running with a Chenbro RM43348 chassis and I went ahead and taped the WD100EMAZ pins but I haven't tested whether it needs it or not.
  12. OKAY, from this tidbit, I discovered how to enable the web GUI at the console via this "Boot GUI Mode" thread (I manually edited the syslinux.cfg file on another computer) but just in case, I also learned how to automatically pause console text scrolling via the "| less" command in case I needed to use it for screen capture purposes. Now, due to some SNAFU when I was fiddling behind the "retiring" server while it was performing a disk-to-disk file move operation and inadvertently bumped the power cord enough for it to turn off, I downloaded a trial UnRAID and used that to boot my new build and enable the GUI mode while my "old" server is busy checking parity. Right off the bat, the trial UnRAID recognized the PCI NIC and had acquired a network IP address, and all was well according to both the GUI and on the text console via lspci. So my next step is to retest my "Pro" UnRAID stick and see if it, too, will now recognize the PCI NIC. If not, at least I've narrowed it down to something with the configuration of the Pro stick and am prepared for further troubleshooting and tweaking with knowledge of how to enable the Web GUI locally and to control console text scrolling...
  13. Yea, I'll do that once I find the time to bring down the "retiring" machine again (I've been swapping its stick to the new machine for setup and testing). I'm also going to attach a monitor to the new machine to get better "eyes" on the output. I also have a brand new ASUS XG-C100C that is intended for my other UnRAID NAS and I'll test it in place of the IBM 1G NIC I'm having problems with to see if it get automatically recognized by UnRAID...
  14. Well, I was able to "disable" via BIOS, but I still can't seem to get UnRAID to recognize the PCI NIC now there doesn't appear to be any Ethernet NIC's available on UnRAID. The problem is that since I can't get a network-assigned IP address, I can't access UnRAID's web GUI from anywhere on the network. I can't figure out how to pause the scrolling in the small window of the SuperMicro mobo's iKVM/HTML5 screen so there's no way I can see what was scrolled out of view. I tried the Java-based console redirection but continually get errors getting the screen working. But regardless, I don't think being IBM-branded should be problematic; it's still an Intel-chipped dual-RJ45 Pro/1000 NIC. So at this time, I'm dead in the water as I just can't access unRAID's GUI nor can I effectively use the "console" as I can't pause the scrolling of pertinent information before it disappears.
  15. I know in the past that UnRAID always used the first onboard NIC it came across with no option to select any other onboard or PCI NIC. Has this changed with the current version of UnRAID? I'm in the last steps of transitioning to my new SuperMicro X11SPH-nCTPF build, but since it has a pair of SFP+ 10Gb and I haven't yet upgraded my network to 10Gb, I'm trying to use a PCI 1G-BaseT NIC and haven't been able to get UnRAID to default to it as there is no way to disable the onboard NICs via BIOS or other means. Also, I'm not sure if the IBM Intel Pro/1000 39Y6127/39Y6128 NIC is even being recognized at all if I read the lspci list correctly (I'm a real noob at this command). So, two questions: 1) How do I set up UnRAID to use a specific NIC? I came across a few threads which mentioned "stub" but those were way too technical and lacked in a "layman's" step-by-step approach that I could follow. 2) What are some UnRAID "friendly" (i.e. plug-n-play) NICs I could select from, if the one I got isn't compatible?