December 22, 20169 yr My unraid boot device shows up as unassigned after a few hours of running. This issue has been driving me crazy so I decided to just do a clean wipe, I wiped all my drives (taking over 16 hours) wiped the boot usb and re-installed unraid and then I set everything back up again. I am on a trial key. I let the parity sync run and it completed without issues. All I have currently done: -Fresh install -Changed date, static IP and added two shares -Created a windows 10 VM running off an ssd not part of the array (used unassigned devices to mount it) -Added community plugins and unassigned devices The reason this is an issue is because before the wipe, eventually something tries to access something on the boot usb and then errors occur and then things start crashing (like the VM) I don't even know where to start with finding the issue and I would be really grateful for any help
December 22, 20169 yr It started as sda, then showed up later as sdj. That means it lost the connection, and later reconnected. This is serious, as you'll have all kinds of problems when unRAID loses the boot drive, as it has above, because it will still expect it to be on sda, will never see it on sdj. drawde's suggestions are good, try a different port first, and make sure it's well seated.
December 22, 20169 yr Author I really appreciate the replies. I had already tested different ports on a seperate bus on my motherboard so I doubt that is the problem, I am currently trying a different USB and I will report back as soon as I know
Archived
This topic is now archived and is closed to further replies.