Hey,

 

Was just trying to setup a windows install that could be both booted  via unraid and single booted.

It was an nvme drive with windows installed natively.

I went into the system devices tool and choose to bind the nvme drive on boot, then rebooted.

It showed up fine in the vm template i choose to attach it to a new vm and booted it with vnc.

I then saw it loading the windows installer and assumed i did something wrong so tried to stop the vm, it didnt stop so i tried force killing the vm and my whole unraid became unresponsive.

 

So i decided to hard reboot and then when i loaded the dashboard up i was getting VFIO binding errors saying the device couldnt be found?

sure enough its not listed in system devices anymore and its not even showing up the in bios, i manually removed it from the binding and rebooted but its no change.

Have i just killed the nvme drive?

 

I don't have any logs from when it all went down but i have attached the latest boot

 

any help would be appreciated

backupbox-syslog-20240901-0704.zip

Edited September 1, 20241 yr by phyzical

Please post the diagnostics.

Ah sorry to waste your time, honestly not sure whats happened. i tried updating my bios out of a whim and it reset my bios as part of it and it began reporting again

its like unraid affected the bios config not sure. now i cant boot unraid as it only shows a usb partition not the uefi boot, haha time to find what new setting to disable to get that back..

 

i post a diagnostic if it happens again when i get it back up.

Edited September 1, 20241 yr by phyzical

lol.. aaand it all just works the second time around.. i must have just configured something wrong the first time

Thanks again for the rubber ducking @JorgeB

okay so it was up for a day, i went to reboot and the system locked up on array shutting down. hard reset and once i loaded back in unraid was reporting the bind error again

 

nvme stopped showing up until i reset my bios again

 

attached diagnostics

backupbox-diagnostics-20240902-1322.zip

Edited September 2, 20241 yr by phyzical

hmm actually i think just a full power down restores the drive not the bios reset, but soft reboots persists the issue

1 hour ago, phyzical said:

just a full power down restores the drive not the bios reset, but soft reboots persists the issue

That's typical, you can try adding this to see if it helps with the device dropping:

 

On the main GUI page click on the flash drive, scroll down to "Syslinux Configuration", make sure it's set to "menu view" (top right) and add this to your default boot option, after "append initrd=/bzroot"

nvme_core.default_ps_max_latency_us=0 pcie_aspm=off

e.g.:

append initrd=/bzroot nvme_core.default_ps_max_latency_us=0 pcie_aspm=off

Reboot and see if it makes a difference.

thanks for the tip ill give it a go.

Out of curiosity any idea why it goes into permanent hibernation? does it just get stuck in "power saving mode" after the first reboot due to the interactions of unraid/ syslinux stuff?

5 hours ago, phyzical said:

Out of curiosity any idea why it goes into permanent hibernation?

Do you mean the server or a VM?

neither the nvme drive itself, just based on what `default_ps_max_latency_us` does, from waht i could see is it disables power management of the drive

5 hours ago, phyzical said:

i could see is it disables power management of the drive

Correct.