crash987_9

Members
  • Posts

    34
  • Joined

  • Last visited

Converted

  • Gender
    Undisclosed

Recent Profile Visitors

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

crash987_9's Achievements

Noob

Noob (1/14)

2

Reputation

  1. i am running my unraid server as a VM inside proxmox with a HBA card passed through to it. After preforming an update on proxmox, i am receiving many kernel panics after having the server up for 3 days. I have attached a screenshot of the latest system crash, not sure if this will help with anything. any ideas of what could be the cause of the problem would be a big help
  2. I will be moving my unraid setup to my threadripper 1950X build and combining it with the gaming pc that is running on it. As the unrad server setup right now is using 7 drives, GPU for plex and DVD/BD drive for makeMKV, I will be moving all the drives to a HBA card and have the DVD/BD drives connected to the motherboard. The gaming computer is quite happy running in a VM on another unraid setup. What I would like to do is have unraid and the gaming computer all running in proxmox in separate environments, the only thing I just need to sort out is getting DVD/BD drives passed to the unraid VM, but I am happy running unraid then have all VM inside it. Are there any nay benefits to having proxmox running on the metal with everything in a VM, or is it better to just run unraid on the metal and setup VM computers inside unraid
  3. you are probably better to have the Vm running in proxmox with the GPU passed to that VM
  4. Just want to update people on this. The Adaptec 71605 turned out to have a bad bios, got a replacement card from the seller, after installing it into the computer. it fired up and working fine. Everything is working fine now
  5. So to update people on the problems. the usb drive was so badly corrupted that i was getting checksum errors on boot, when it did boot, drives were not in a bool, and drives that were originally reporting fine had errors. I was able to recover the unraid usb drive and everything OS wise is working fine. about the Adaptec 71605, i don't know what i am doing wrong, on system boot i do not get any bios reading from the card. I have also put in a rocket RAID 2720, both cards have a HDD connected to them and i get no readings from them. I am running a 4790K on a Gigabyte Z97X-Gaming G1 WIFI-BK running the latest bios update. i have had the rocket raid card working once under unraid on a different system, but the last time i put the card in the same pc, i had no reading from it. I have read online that raid cards need to be setup as UEFI bios boot and not legacy boot in the pc bios/UEFI, correct me if I'm wrong, aren't the cards plug and play or do they really need setting up to work
  6. sorry. HBA card. it is a Adaptec 71605. from what it looks like to start with, supper corrupted unraid drive. just about to see if a windows install can see the drive or not
  7. crash987_9

    Quick help

    I am trying to get a pcie vga card and a sata raid card working on my computer. I know the video card is in good working order and the raid card is new, when I boot the computer, bios doesn't detect the raid card but vga card works fine, when booting into unraid, video output is all a mess Am I looking at faulty pcie lanes or just some type of bios not configured properly Thanks
  8. it might be looking like the drive is on its last legs. i tried to recover the old image but i kept receiving an error for the file bzfirmware. did a scan disk and was able to copy it over. ill have to start looking into a replacement drive
  9. i have just updated my server and now i am getting kernel panics on startup. i made a post here about the problem. hope i am able to recover from this
  10. I have just updated my server to the new RC3 build, after the reboot it was taking a long time to become available on the network. when i turned on the monitor for the server i am getting a kernel panic. i am getting this with every restart both in normal and safe mode. hope i am not the first with this problem
  11. so i think i have an odd system setup compared to other users. I have to run my threadripper vm setup to only boot into legacy mode to be able to passthrough the gpu properly to a vm. if i boot the system in uefi mode, i am able to pass the gpu but receive a code 43 error. But if i boot into legacy mode, i cam pass the gpu to the vm and get full use of it. I have a 980TI and 1080TI installed into the system both the vbios for each card passthrough. I would like to see what other people have setup and to see if maybe my system if just being temperamental
  12. i had made t thread about this here. it is referring to this video youtube - craft computing using proxmox to emulate a GTX9xx to RTX 30xx to visible as a nvidia tesla card. but as proxmox and unraid both use the same emulation software, surely there would be a way to getting unraid to do the same thing. it would be great being able to to have 2 gaming pcs using the same gpu
  13. So i was busy looking on youtube some time ago for things to watch. I then came across this video from Craft Computing on how to make prxomox see a NVidia GTX9xx to the RTX30xx as a NVidia Pascal vgpu. Basically you can split up say a GTX 1080TI with 11GBvram into 11x1GB vram gpu. What i would like to know is, is this at all possible to do in unraid then use parsec to remote into the pc. I would say watch the video from Craft Computing to get an idea of what i am talking about. it would be great to be able to have 2 or 3 gaming computers all running from the 1 gpu.
  14. Is there any walkthrough on how to add new users, I followed the steps that spaceinvader one put up but it is only for one user. Other threads I have found online say there is a button to press to add new users, that is the one thing I can not find
  15. thanks for the tip, i have left the computer with that last night and all is good. i will now stress it and see if it might be something else, i am having a feeling that it is ether a sata controller that's on its way out or it could be a hdd that is making the kernel panic (all hdd pass SMART test)