Solutions
-
Bob-omb's post in [7.3.1] Upgrade error: usb usb1-port11: unable to enumerate USB device was marked as the answerI noticed that in BIOS the flash drive was not available as a boot device. Kind of strange. Another reboot seems to have solved the issue.
-
Bob-omb's post in Unraid won't boot after 7.2.5 upgrade was marked as the answerNevermind. Seems to work again after another reboot. Strange...
-
Bob-omb's post in Unraid 7.1.4 Unraid is not generating the syslog messages was marked as the answerTurns out I just had to reset the filter in Syslog Watcher
-
Bob-omb's post in 7.1.3 - "Unmountable: wrong file system" when starting the array was marked as the answerGot a replacement CPU and everything works like a dream again. I am so happy! 🥳
-
Bob-omb's post in Yet another PCIe Bus Error post was marked as the answerEdit: In the end, I decided to get rid of the LSI 9300-16i because I didn't want to take the risk of using it while not fully understanding what the error messages meant. The following part was my solution to turn off the warnings, but it might not be so wise:
OK I think I managed to turn off the warnings eating up the log file.
I am not seeing the error anymore, but I also don't know if I should be worried about it. Everything works, but only as far as I can tell.
Here is what I did:
Made a backup of the flash drive I opened the terminal in Unraid and entered: nano /boot/syslinux/syslinux.cfg I entered the pci=noaer pcie_aspm=off on line 9 CTRL + X to exit, Y to confirm, and Enter to save.
Here is the full syslinux.cfg after the change:
default menu.c32 menu title Lime Technology, Inc. prompt 0 timeout 50 label Unraid OS menu default kernel /bzimage append initrd=/bzroot pci=noaer pcie_aspm=off label Unraid OS GUI Mode kernel /bzimage append initrd=/bzroot,/bzroot-gui label Unraid OS Safe Mode (no plugins, no GUI) kernel /bzimage append initrd=/bzroot unraidsafemode label Unraid OS GUI Safe Mode (no plugins) kernel /bzimage append initrd=/bzroot,/bzroot-gui unraidsafemode label Memtest86+ kernel /memtest
-
Bob-omb's post in How can I restore docker images after reinstalling Unraid was marked as the answerOK, I copied over /config/plugins/dockerMan once again, and I got it to work. Thanks guys!
For future Unraiders the solution was namely to do as jorgeB mentioned, but more specifically:
Copy the contents of the backed-up appdata to the production version of appdata Copy the contents of config/plugins/dockerMan from your backed-up flash drive to /config/plugins/dockerMan on the production flash drive. Re-create the docker image file. Re-install the previous docker applications
-
Bob-omb's post in Pass through a hard drive to a Windows VM was marked as the answerI managed to answer my own question.
For future Unraiders:
Open the terminal in Unraid.
Enter ls -l /dev/disk/by-id/
Look for the drive you want to mount and copy the name beginning with data... In my case ata-WDC_WD221KFGX-21C2LE0_... Don't forget to include the ata at the beginning.
Edit your Windows VM
Add a 2nd vDisk Location
Set it to Manual
Enter the full path to your drive. For example /dev/disk/by-id/ata-WDC_WD221KFGX-68B9KN0...
-
Bob-omb's post in Starting fresh - Can't access GUI was marked as the answerI seem to have solved this issue. Here is what I did:
Reinstalled Unraid using the Unraid USB Creator on the same flash drive. Then I transferred my license by going to Tools ➜ Recover Key ➜ Copying the URL to the key file ➜ Pasting the key in Tools: Install key. I was kind of lucky since the flash drive itself was not physically damaged. It was just that I had messed up the config.
I would still love to see a guide on how to "start fresh". Especially if there is an option to completely start fresh but keep the array since building an array parity can take days. I kind of struggled with this, which is why I managed to mess this up.