Jump to content

headnail

Members
  • Content Count

    14
  • Joined

  • Last visited

Community Reputation

0 Neutral

About headnail

  • Rank
    Member

Converted

  • Gender
    Undisclosed

Recent Profile Visitors

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

  1. Sorry to revive a topic over 3 years old, but did you ever find a solution to your problem? I am faced with the same scenario, upon first boot (from off-state) my GPU (secondary GPU - Asus GTX 970) is virtually dead silent the fan is spinning but at a very low rate. Upon VM start-up things are normal as well and fan speed is linked with GPU loads - under low load very low fan speed is observed. However once I shutdown the VM (Win 10) the fans ramp up. Rebooting Unraid solves the problem until the next VM cycle. I prefer to not keep the VM running at all times - waste of CPU horsepower and energy, is there any way to fix this? I am running the latest available BIOS for the card as well...
  2. I have run into a similar problem with my old system in the past... Never managed to find a solution for, expect for not hooking up a monitor to my rig, which worked without a hitch for about 2 years. Changed platform (Dell T1650 motherboard and E3-1220 v2) and have not had any issues with the controller (SASLP-MV8).
  3. Thanks!! Made a new Unraid USB and grabbed the go script from there....everything appears to be working! Much appreciated! I did notice that there is a large number of FSCK**** files on my main Unraid flash drive, also Windows reported issues on the drive (when attempting to copy I could not access plugins_previous), is it possible that my USB stick is dying?
  4. Hello, I have been using Unraid for a number of years now without any issues (even changed platform without any issues!), always keeping up-to-date with the latest stable release without any issues until I just updated to 6.6.5. It might be useful to note that while I consider myself reasonably tech literate, my Linux experience is somewhat limited. I have no clue what went wrong, followed the same procedure I always do (download stable update, stop array, reboot), however once rebooted I no longer had access to my server. I hooked up a monitor and observed the boot procedure, everything went smooth right up to "Starting Samba; /usr/sbin/nmbd -D /user/sbin/smbd -D /usr/sbin/winbindd -D" Following which I get the following error: "/var/tmp/go: line 1: $'\377\377\377 (a bunch more \377\)': command not found I do get an IP assigned but access the web interface. Tried the GUI boot mode but still no access to the web interface (cannot connect to localhost). Attempted to revert the update (copied contents from /previous), managed to downgrade to 6.6.4 but the problem still persists. I have attached my syslog file and the diagnostics file. Any help would be highly appreciated!
  5. I guess it's safe to label my post at "solved", in summary: 1) First system (AMD - Asus M4A78L-M LE/Athlon II X3): The SASLP-MV8 controller did not appear to play nice with my MB, never managed to figure out what exactly was causing the issues. 2) Second system (Intel - Asus P5KC/E7200): SASLP-MV8 controller had "IRQ16 nobody cared" issues whenever a monitor was plugged into the video card, or if already plugged in - turned on. With no monitor attached to the system I have had over 5 days up-time with no stability issues - during which time numerous disks where pre-cleared, data transferred between disks and a parity was created. Current system is as follows: Unraid 6.1.7 Pro CPU: Intel E7200 RAM: 6 GB DD2 (2x2GB + 2x1GB) MB: Asus P5KC Video: Quadro FX 580 Controller: Supermicro AOC-SASLP-MV8 HDDs: 2 x 3 TB WD Red (1 of which parity) 1 x 2 TB WD Green 1 x 1 TB WD Black 2 x 1 TB Hitachi 2 x 1 TB Seagate 1 x 300 GB WD VelociRaptor (cache) PSU: Corsair VX550W
  6. You could also try moving the NIC to a different slot on the motherboard (if that's an option of course). What output do you get from "cat /proc/interrupts"?
  7. Had a similar issue, except in my case it was IRQ16 which was going dead. IRQ16 on my system was shared between USB and supermicro saslp-mv8 controller (PCIe slots on MB), however according to the motherboard (P5KC) manual the IRQs on the two PCIe slots where shared as well. After some research and experimentation I established that basically the problem manifests itself whenever I have a monitor hooked up or hookup/turn on a monitor (I have a Quadro FX 580 on PCIe slot 1 -and the mv8 on the PCIe slot 2), which apparently causes some interrupt that some driver does not know how to handle. Running the system with no monitor hooked up (and no USB devices besides Unraid USB boot stick) I have experienced no issues (currently around 96 hours and going). You could try the following 1) Disable all unused integrated motherboard peripheral in BIOS (serial port etc..) 2) Set "Plug & Play OS" in BIOS to "NO" and determine whether or not you can manually assign IRQs to different devices 3) Disable all unnecessary integrated LAN (assuming that's what you are using) features (wake-on-lan etc.) 4) you could try booting with the "irqpoll"option, I have never tried this and my understanding is that in most cases it does not solve the issue Of course you could also try a dedicated LAN card...
  8. Well initial impressions can indeed be wrong, while I did not run into my previous problem I did run into a new one...IRQ 16 disabled. After reading up on the issue I am now testing with no monitor attached to the video card (quadro fx 580), hopefully this resolves the issues, just to be on the safe side no keyboard is attached either. Memory has been pushed up to 6gb.
  9. I moved over to a new case, new MB - Asus P5KC, CPU - E7200, 4 Gb DDR2, initial results seem promising, no issues during large volume data transfers. Will test more transfers and pre-clear of a 2TB disk tomorrow and report back.
  10. Thanks for the info, I did actually bend the card holder as to be sure that it sits perfectly in the PCIe slot and it appeared seated quite well. I will be testing my setup with a different MB and case today, hope that an intel chipset might do the trick
  11. Any idea if the problems where isolated to preclears alone? I have read about speed related issues with the controller but nothing similar to my problems and I am somewhat reluctant to use the controller until I have a better understanding of the underlaying issues. I am inclined (mainly due to feedback from linux familiar friends) that the issue is either driver related or some hardware incompatibility (MB and controller).
  12. Thanks! Guess I have to hook up the controller again and get a complete diagnostic dump, have you ever encountered errors similar to the ones in the log?
  13. Thanks for the advice, I am indeed running 6.1.6, firmware of the controller is .21 My main issues is that once the system "crashes" web gui is inaccessible, my only option is telnet into the machine. I did manage to get a copy of the syslog befor reboot (pastebin). Array was not even started, just a preclear on one disk runing. The best I can tell smart data on the disk was ok (viewed before preclear start), preclear on onboard SATA controller completed sucesfully on the same disk. Again the issue seems to be isolated to the controller (saslp-mv8). Managed to pr clear the disk running of the onboard controller with no issues and I currently 10 hours in preclearing 3 disks simultaneously (onboard again).
  14. After months of procrastinating setting up my first Unraid home server, I finally got around to it with help from a friend of mine. My current hardware setup is as follows: CPU: Athlon II X3 440 RAM: 4 GB DD2 (2x2GB) MB: Asus M4A78L-M LE Video: Onboard CPU: Corsair VX550W HDDs: 2 x 3 TB WD Red (1 to be used for parity) 1 x 2 TB WD Green 1 x 1 TB WD Black 2 x 1 TB Hitachi 2 x 1 TB Seagate 1 x 750 GB Seagate 1 x 300 GB WD Raptor (to be used as cache) The controller is a Supermicro AOC-SASLP-MV8, flashed with the appropriate firmware. I am currently in the process of pre-clearing some of the HDDs, and I constantly come across system crashes/hang-ups - web interface dead, system accessible via telnet. I have tried two separate identical controllers (SASLP-MV8) and different cables with no success, system crashes with errors that I cannot honestly decipher (limited linux experience). Please see log-file, any help on this issue would be greatly appreciated (the error appears to be identical on every crash occasion). Full system log available at http://pastebin.com/nVeQs4KG I considered the possibility that it might be a hardware related issue (MB/CPU/RAM), however I managed to get through 24 hours of memtest without an issue (3 CPU cores used). Furthermore, using the on-board SATA controller the system appears to be rock solid (32 hour pre-clear on a 3TB drive with no issues).