Dirk Pitt

Sorry for the delay. This wipefs worked after a reboot. My other two M.2 is in Raid1 came back on reboot without issue. Thanks, you saved me a ton of time! What do you think I should do with the zombie M.2 (the one that came back to life). Remove it, clear it and put it back in service, ??

I get bash: "/sys/block/nvme0n1/device/delete: Permission denied". I am logged in as root. An internet search seems to be limited to using chmod to change permissions but when change to the folder there isn't a file called delete. I get this ... root@Kraken:/sys/block/nvme0n1/device# delete bash: delete: command not found I would expect delete to be a command (not a file) but in this line "echo 1 > /sys/block/nvme0n1/device/delete" it is used like a file. I love the idea of testing this without opening the case.

Thanks for the help! Label: none uuid: 90031dc7-05cb-47c5-84e5-c64b59d0f80e Total devices 2 FS bytes used 7.01TiB devid 1 size 9.09TiB used 7.08TiB path /dev/sdi1 devid 2 size 9.09TiB used 7.08TiB path /dev/sdh1 Label: none uuid: fa25ed97-097e-4b62-94de-f31b162ef879 Total devices 1 FS bytes used 4.80GiB devid 1 size 100.00GiB used 8.02GiB path /dev/loop2 Label: none uuid: 4d281c88-5bbf-4b6f-b2d1-55bf9ecc13f2 Total devices 2 FS bytes used 189.06GiB devid 2 size 1.82TiB used 198.03GiB path /dev/nvme1n1p1 devid 3 size 1.82TiB used 198.03GiB path /dev/nvme2n1p1

Pre-Hurricane I lost an M.2 which was part of a Raid 1 cache with my appdata. I didn't open the case to troubleshoot but the bios didn't recognize the drive so I assumed it failed. I restored the Raid 1 using a different M.2 in the box and made a note to investigate later. This was about one week ago. Along came Hurricane Milton. As I was getting my phone out to shutdown my Unraid server, we had a strange power fluctuation that went on for about a minute. Living in FL, we are used to power fluctuations during storms but this one was strange. Seemed to go on forever. I wasn't worried as my server is connected to a UPS (CyberPower CP1500PFCLCD PFC Sinewave UPS 1500VA) which has "sinewave" power protection. When I did go to shutdown the server, I found that it had rebooted during the power fluctuation. I double checked to ensure the server was plugged into one of the Surge+Battery slots and then shut it down and unplugged it for the duration of the storm. The next day I started the server again to find out that ... 1. TWO DEAD M.2s: The Two M.2s that I have in Raid 1 config which held appdata were both listed under "Unmountable disk present". 2. ONE M.2 ROSE FROM THE GRAVE (SORT OF): The M.2 that was not showing up in the bios Pre-Hurricane was now showing up in the bios and in Unraid. However, when I tried to mount the drive it apparently fails (without message). All it does is display "Reboot" next to the drive (see attached image). Rebooting didn't help. 3. All the spinning rust drives and the boot flash appear to be fine. I tried formatting by checking the "Yes, I want to do this (format)" for the two M.2s but when I click format the browser window refreshes a couple of times and then it apparently fails as it returns to the "Format" button being greyed out and both stay listed under "Unmountable disk present". To make things stranger ... 1. We never lost power. None of the clocks need resetting. Additionally, when we do get power surges usually some low voltage stuff like garage door openers get fried first but nothing else in the house is damaged. The server, which again was connected to a UPS, was the sole recipient of the demonic targeted surge. 2. All three of the M.2 drives pass a SMART short self-test even though one of them won't mount and the other two won't format. 3. I restored the appdata by using the "Backup/Restore Appdata" functionality (amazingly easy) but when I logged in today to write this, all of the drives were blank under the "Main" tab (see attached image). I checked that Plex would play a movie and it did. Thus, the drives were working even if they weren't showing. When I rebooted it returned to normal. At this point I am faced with two unlikely possibilities. 1. The surge had nothing to do with the failures and the MB (ASUS TUF Gaming Z790-Plus WiFi LGA 1700) is just bad. This would explain why an M.2 disappeared and came back. But the timing is amazingly coincidental. 2. The surge killed something but somehow didn't impact anything else in the house and sort of restored the missing M.2. The next obvious troubleshooting step would be to try the M.2s in a different computer but getting everything out of the closet is difficult for us old people. I've attached the syslog for reference. Any suggestions would be appreciated. syslog.txt

Thanks itimpi. I did unmount the drive in Unraid and the same problem exist. The still shows up in file explorer. Windows won't format the drive either. It doesn't even show up in "Disk Management" (in Windows). When I right click on the drive in File Explorer and choose "Format Drive" it doesn't do anything.

For various reasons I want to run DropBox from a Windows 11 VM on Unraid. I don't want to use Rclone for various reasons. First I tried using a mapped network drive. Dropbox will have none of that. I know that I can buy Boxifier to make DB use a network drive, but I'd really like not to go down that route. Then I tried using Virtiofs share to a mapped folder. That made the share on Unraid appear as a drive in the Windows VM, but Dropbox wasn't happy as it wasn't formatted NTFS. I have an extra HD sitting around so I purchased an external USB enclosure and formatted the HD NTFS. I mounted this as an Unassigned Drive and shared the drive. I used the Virtiofs Mode again but this time used the source path as /mnt/disks/USBBackup. Again, Windows can see this as a drive, and the properties show it as NTFS. Dropbox still refuses to set this as the Dropbox Folder Location. The reason given by Dropbox is that the drive isn't formatted as NTFS. Yet it is formatted NTFS. Does anyone have an idea of how to get Dropbox to use a Dropbox Folder Location that is either 1) a folder on the array, 2) a disk on the array, or 3) an Unassigned Drive?

Thanks Jonathan! For anyone searching in the future, this is what worked. 1. I went to https://schneegans.de/windows/unattend-generator/ and generated an XML file and I checked "Allow Windows 11 to be installed without internet connection" under the heading Setup Settings. Export the XML to your PC (use the button way at the bottom). Note: the site will generate an iso, but it is too small to contain Win 11. It looks like from the documentation that iso is for downloading Windows 11 during install. That wouldn't work for my purposes since the whole point of this is that internet isn't available during install. So don't use the downnload iso button, download the XML file and then follow on to step 2. 2. Download the Windows 11 iso from https://www.microsoft.com/software-download/windows11. You should now have the xml and iso and you need to combined them (move the xml into the iso). 3. The youtube link below shows how to move the xml into the iso. The video shows two methods, the first I don't think will work with Unraid (not really sure) but the second method creates an iso and is super easy. On the video, skip to about 18:30. The early part of the video is where to download an example xml but I didn't need this as the schneegans website generates that for you. It does require downloading the free program anyburn but it was trivial to use. 4. Take the resulting iso (now with the xml inside) and copy it to the "isos" folder on unraid. 5. For the rest I used the space invader video at the link below. This video is quite old and most of the first half doesn't apply anymore. Starting the video right after he installs the icons (not required in 2024) at about 10:24. I used Ed's settings from that point on.

I'm trying to install Windows 11 and am stuck at the "Let's connect you to a network" screen. I've seen that you should press Shift+F10 to open the command prompt, but that doesn't work. Things I've tried ... 1. Some help on the internet mentioned Shift + Fn + F10 but no luck. I've tried about every possible combination of Shift + Fn + Cntrl + 10 to no avail. 2. I tried from two different PCs 3. The floating toolbar on the left of VNC has a "show keyboard" but when I press it, no keyboard shows up. I've also tried pressing that button and combinations of Shift + Fn + F10 but no luck. I know the command is OOBE\BYPASSNRO to bypass the network but I can't get the command prompt to appear.

Update as of 2024, go to Apps then Community Applications then Allow install of second instance: = Yes