• Posts

  • Joined

  • Last visited

  • Days Won


1812 last won the day on August 27 2019

1812 had the most liked content!



  • Member Title


  • Gender

Recent Profile Visitors

29359 profile views

1812's Achievements


Proficient (10/14)



  1. soke too soon, having a problem with my gpu, which went from functional to not. Log shows: May 19 13:46:23 Tower kernel: nvidia-nvlink: Unregistered the Nvlink Core, major device number 245 May 19 13:46:23 Tower kernel: nvidia-nvlink: Nvlink Core is being initialized, major device number 245 May 19 13:46:23 Tower kernel: NVRM: The NVIDIA GeForce GT 730 GPU installed in this system is May 19 13:46:23 Tower kernel: NVRM: supported through the NVIDIA 470.xx Legacy drivers. Please May 19 13:46:23 Tower kernel: NVRM: visit http://www.nvidia.com/object/unix.html for more May 19 13:46:23 Tower kernel: NVRM: information. The 510.73.05 NVIDIA driver will ignore May 19 13:46:23 Tower kernel: NVRM: this GPU. Continuing probe... May 19 13:46:23 Tower kernel: NVRM: No NVIDIA GPU found. It appears that my GPU driver was automatically updated and now I have to roll back to the 470.xx option in the Nvidia plugin. Ok I guess... a bit of an annoyance to have to fix something like this that was working just fine.
  2. updated 2 machines. first one no problems. Second one had all disks in the 2 pools "missing" as the device names had changed (those using an H240). I noted the disk positions/assignments, used new config and preserved the array disks, went back to the main tab and re-assigned the pool disks, marked parity as correct, and started the array. Normal operation as expected with no loss of data (also expected).
  3. First post updated with instructions for 6.10.
  4. I already listed my hardware specs. So moving on: Firstly, don't write to the array. If you have to, make sure you're on reconstruct write. For cache use ssd/nvme cache disks if you want fastest performance. second, see here: Try that and see if your experience changes. *Note* I don't have this setting on anything but a fast network share. The speeds I posted yesterday are just a a basic share that uses a cache drive.
  5. M1 MacBook Pro > OWC Thunderbolt Pro Doc > 10gbe ethernet cable > mikrotik 4 port 10gbe switch > direct attach copper cable > mellanox connectx-2 card > hp ml30 gen9 unraid server. file copy from the server, off a cache pool of 6 data ssd's in raid10, writing is about 100MB/s slower. Reading from my spinning array gets me about 170MB/s give or take using exos drives. Writing is a little slower. So, it works for me and my Mac. YMMV depending on server/client hardware specifics and tuning.
  6. the very first post says "Installation (procedure used for unRaid 6.9.0 RC 2 and up to current stable versions, previous versions not supported). This thread will be updated/deprecated when 6.10 goes stable to reflect the changes with that version." The patch is a part of the OS currently in the RC versions, so technically it should work if you follow step 4 and 6 in the first post, rebooting after step 4. I sold my last proliant a year ago, and don't always run RC versions so I don't have the ability to test at the moment, hence why RC is not supported (plus things can unexpectedly change from version to version.) If you do try steps 4 and 5, kindly report back the results.
  7. Current does not equate to RC/beta versions. Current pertains to stable versions. But I have updated that text to reflect that since there seems to be confusion.
  8. the second will be listed as de[recated once the stable version comes out, thanks to you!
  9. She's selling a service to set it up for you.
  10. you will have to ask in this thread, as I don't maintain the script.
  11. try setting up a syslog server and it might capture any errors that occur right before it power cycles.
  12. I had an 8th gen ML350p with 2 rx580's, 2 10gbe cards, 2 hba's, and 1 gt 710 for Plex. (and maybe something else, I don't remember) The 2 rx580's went to a Macos vm plus a 10gbe solar flare card. Passthrough was fine once the RMRR issue was solved. Switching to legacy doesn't really affect anything in your setup/use. As I mentioned before I remember the onboard quad being a bit finicky. I think I disabled mine altogether since the server was on 10gbe. That doesn't help you much unless you get an aftermarket card.
  13. we'll try some troubleshooting/digging around try switching to legacy mode and boot with the 4 nics. make sure to disable UEFI in bios as well as an option. see if it works. change acs override to both in the vm manager and reboot. this shouldn't matter, but then try to start the vm with just 1 of the nics. the newer bios won't fix the rmrr issue. HP doesn't care about older hardware. the newer bios were essentially for spectre, etc... you may just have to get a quad intel nic and not use the onboard if it doesn't want to play nice.