sonofdbn

Thanks, makes sense not to take additional risk on this, and I fortunately had an old (still in packaging) Sandisk Cruzer Blade so I shut down the server and took out the flash drive. A little testing of the flash drive on a Linux machine using fsck.fat showed a serious error, so it was clearly time to set up the new flash drive. Unfortunately that's been a huge headache. I use the Unraid Flash Creator tool, and tried to install both a backup that I just did from the flash drive as well as the backup from Unraid Connect. In both cases, the drive failed to boot. I suspect that the backups had corrupted files from the failing flash drive, so I reverted to an old backup from March 2025. Unfortunately that failed to boot as well, which was a bit surprising. (So separately I'm wondering how I can check the validity of a flash drive backup.) I have confirmed that if I download and install a fresh 7.0.1 OS (which is what I was on) the machine boots up, but I didn't proceed because I'd still prefer to avoid redoing too much of the old setup. Drive assignment should be fine, but I'm more worried about the settings I had for my Win 11 VM, which I recall were quite complicated (for me). Currently I'm writing another old flash drive backup to the flash drive, to see if that might work. But I was also wondering if there's a way to copy specific config files (especially for the VM) to a fresh install OS flash drive, so that at least some things can be recreated automatically on boot up. (To address the risk of using a corrupted config file, I would check the file against other older backups to make sure they're the same.)

I've been getting the "Directory Bread Errors found" message from the Fix Common Problems plug-in, and from what I can find, it seems that this indicates a problem with the boot flash drive. Unfortunately the flash drive is attached to an internal port on the motherboard of the server, so accessing it is a bit troublesome. So far, the server seems to be running fine (7.0.1). Obviously I could shut down and see what the problem is, but my fear is that I might have to replace the flash drive and with all the reports of the problems finding a flash drive suitable for use as a boot drive, I also worry that this might not be solved easily. So my question is whether I can live with this error, and if so, for how long? I've seen the Youtube video on booting from an internal drive coming (soon-ish?) - so am really tempted to wait for that. Just don't know how serious the Directory Bread Errors are, and whether I should focus on getting that fixed.

After upgrading to 7.2.3, the server appears in Windows Explorer Network, and so far this has persisted, including through a Windows reboot. So all is well. And my apologies for dissing the unRAID GUI earlier - my own fault with unRAID logs getting full.

Totally agree with the pinned servers - have had them for a while and totally reliable. This was more an ongoing irritation and mystery. I'm not convinced that it's solved, and tend to think it's a Windows problem, not an unRAID issue. I have a Windows VM that has no problem listing the server in Network.

Thanks for the replies. I might have sorted it out - if I set "Host access to custom networks" to Disabled under Settings/Docker I can see my unRAID server in Windows Explorer's Network section. I had two network interfaces assigned to my server's IP address: br0 and shim-br0 (apparently created by the Docker network). Removing host access removed that Docker interface (I think - can't confirm because the accursed unRAID GUI is acting up again and I can't get to the terminal) and now the server is showing up as it should in Windows. At least for now.

For a long time I've noticed that my unRAID server isn't listed in my Windows network. I can access it fine, it just doesn't show up in the Windows Network section of Explorer. I'm trying to sort this out and Gemini (apologies) helped quite a bit, and now I have the server showing up. Apparently in my case it was because the discovery service, WSD, was possibly being confused by different network services, like Tailscale and Docker shim (shim-br0). So as instructed, I ran killall wsdd2 and then /usr/sbin/wsdd2 -d -i br0 and now I can see the server listed. Now Gemini is saying that this fix will disappear on reboot, which seems logical, and it's suggesting that I disable WSD in SMB Settings and edit /boot/config/go to run the commands on boot. To me, as a novice in this, it sounds reasonable, but I know that at some point in the future, I'm going to be confused by seeing WSD disabled. I see that in SMB Settings there's "WSD options (experimental)". Is there something I can enter here to replicate the fix? Like "-d -i br0?

Of course, when I try now it works. (And I'm on exactly the same FF version on W11.) The only thing I did differently was to drag the images directly into the edit window. Previously I attached the files first and then inserted. Life is too short to test this further. If it works, it works. Thanks for verifying that it can be done.

I got Boooklore working. Here's my MariaDB setup: I left REMOTE_SQL untouched because I don't know what it does. Note the non-standard WebUI port, because I have another MariaDB container running. Here's my Booklore setup: Hope this helps, @Johnny Utah

I'm using Firefox, and just tried saving a post with two images inserted. There was text above, between and below the images. Looked fine in the input window, but when I submitted the post, only the two images appeared, and the text had been deleted. Tried twice with the same result. What am I missing?

OK, user error here. I just noticed that there is a + sign, it's just that it's right up against the left margin of the page, and it's not visible when my browser window is not at full screen. But I do feel the GUI could be improved so that the + sign is more readily noticeable. I'm using Firefox. in case it's a browser specific issue. Having said this, the + sign might not be the solution, though. I'm trying to passthrough one of those portable disks in a USB case. It appears as /dev/dis/by-id/usb-JMicron_Tech_000000778899-0:0. But if I enter that as the path for the secondary vDisk, it gets promoted to the Primary vDisk on boot (this shows on the VM config page) and the VM fails to boot (perhaps trying to boot from there) and shuts down. I've tried both USB and VirtIO as the vDisk Bus. A short while later: After trying to revert to my original setup, it seems that the original hard disk was Bitlocker encrypted and I needed to enter the recovery key because a USB device had been added to the configuration. So that's a probably reason for the VM appearing to fail. If you don't enter anything at the Bitlocker screen the VM shuts down. I saw this only because I started the VM with the console. I'd experiment further, but it's such a pain entering the Bitlocker key using the function keys, and I'm not sure if there's a simple copy and paste that I can do into the console window. Anyway, if entering the Bitlocker key is required every time I add or remove the USB drive, it's not a practical option for me. Will try to assign the USB drive as a network share instead.

Not sure about the terminology here, but long ago I followed a SpaceInvader video on how to use a "real" Windows installation on a hard disk as a VM in unRAID. It's been running fine for a few years. Now I have added an external SSD to the server as an unassigned device, and want to mount it (or however I can access it) in the VM so I can use it for additional storage. I've read advice on how to do this via the VM configuration page, but the advice typically assumes that there is already a Primary vDisk assigned and then you just click the + sign next to it to add the device as a second vDisk. In my case, there is no Primary vDisk location (entry is "None") and therefore no + sign next to it. I'm worried that if I simply add the external SSD in that Primary vDisk Location, the VM will try to boot from that device. How can I mount the SSD?

Recently I had a power outage. Although I have a UPS, the performance is a bit patchy, as I often get an unclean shutdown (something to be sorted out later). I don't have any auto-restart on power restore set up; certainly in the past (quite a few years) the unRAID (7.0.1) server hasn't restarted when power was restored. Details are a little vague because I was travelling when the power went out, but I first found out the server was down when my phone, which was on Tailscale and uses the Tailscale exit node on the server, lost internet access. I disabled the exit node and internet access was OK again. I saw in the Tailscale app on the phone that Tailscale had lost connection with the server and some docker containers running on it (like Plex and Nextcloud). I was about to call home to see what had happened when I saw that suddenly I had access to the server again and everything was up, and in the Tailscale app I could see that the Tailscale exit node was up and the containers were connected. Then last night it happened again (I was still away): lost Tailscale exit node and server seemed to be down briefly. But this time the "recovery" was not complete. The Tailscale node came back up and I got Tailscale access to the server but the Plex and Nextcloud containers didn't have Tailscale access. I was able to log in to the server and I could see that the two containers were running; they just didn't have their usual Tailscale connections. I confirmed that the Tailscale plugin was up to date. My "evidence" of unclean shutdown and restart is that both times I got an email notification that a parity check had started because of unclean shutdown. This is not a huge problem, but I'm wondering why this is happening and whether it's symptomatic of some misconfiguration on my part tower-diagnostics-20250702-1041.zip

And now they're gone! root@T2:~# lsusb -vt /: Bus 001.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/16p, 480M ID 1d6b:0002 Linux Foundation 2.0 root hub |__ Port 004: Dev 002, If 0, Class=Human Interface Device, Driver=usbfs, 1.5M ID 0665:5161 Cypress Semiconductor USB to Serial |__ Port 006: Dev 003, If 0, Class=Hub, Driver=hub/4p, 480M ID 174c:2074 ASMedia Technology Inc. ASM1074 High-Speed hub |__ Port 002: Dev 005, If 0, Class=Mass Storage, Driver=usb-storage, 480M ID 0781:5591 SanDisk Corp. Ultra Flair |__ Port 013: Dev 004, If 0, Class=Human Interface Device, Driver=usbhid, 12M ID 26ce:01a2 /: Bus 002.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/9p, 20000M/x2 ID 1d6b:0003 Linux Foundation 3.0 root hub And so far none of those error messages in the logs. So I'm considering this solved. But in case it's needed for any future issue, I've attached the current diagnostics. t2-diagnostics-20250505-2318.zip

Hmm... the only Hitachi devices I have are these HGST (Hitachi Global Storage Technologies) drives. But they're connected to SATA ports on the motherboard. (If the USB add-on card is an issue, I can remove it. It's not being used for anything.)

Here's the output: root@T2:~# lsusb -vt /: Bus 001.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/16p, 480M ID 1d6b:0002 Linux Foundation 2.0 root hub |__ Port 004: Dev 002, If 0, Class=Human Interface Device, Driver=usbfs, 1.5M ID 0665:5161 Cypress Semiconductor USB to Serial |__ Port 006: Dev 003, If 0, Class=Hub, Driver=hub/4p, 480M ID 174c:2074 ASMedia Technology Inc. ASM1074 High-Speed hub |__ Port 002: Dev 005, If 0, Class=Mass Storage, Driver=usb-storage, 480M ID 0781:5591 SanDisk Corp. Ultra Flair |__ Port 013: Dev 004, If 0, Class=Human Interface Device, Driver=usbhid, 12M ID 26ce:01a2 /: Bus 002.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/9p, 20000M/x2 ID 1d6b:0003 Linux Foundation 3.0 root hub /: Bus 003.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/1p, 480M ID 1d6b:0002 Linux Foundation 2.0 root hub |__ Port 001: Dev 002, If 0, Class=Hub, Driver=hub/4p, 480M ID 2109:3431 VIA Labs, Inc. Hub |__ Port 001: Dev 003, If 0, Class=Hub, Driver=hub/4p, 480M ID 045b:0209 Hitachi, Ltd /: Bus 004.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/4p, 5000M ID 1d6b:0003 Linux Foundation 3.0 root hub |__ Port 001: Dev 002, If 0, Class=Hub, Driver=hub/4p, 5000M ID 045b:0210 Hitachi, Ltd

I'm on 7.0.1. Was looking at shares on the GUI when it slowed to essentially a halt. In the log I saw lots of messages like this: May 5 00:42:44 T2 kernel: usb 3-1: Failed to suspend device, error -110 May 5 00:42:49 T2 kernel: hub 3-1:1.0: hub_ext_port_status failed (err = -110) May 5 00:42:51 T2 kernel: usb 3-1-port1: cannot disable (err = -110) May 5 00:42:51 T2 kernel: usb 3-1-port1: device 3-1.1 not suspended yet May 5 00:51:00 T2 root: Fix Common Problems Version 2025.03.12 May 5 00:54:51 T2 kernel: usb 3-1-port1: device 3-1.1 not suspended yet May 5 00:54:52 T2 root: Fix Common Problems Version 2025.03.12 May 5 00:55:12 T2 kernel: usb 3-1-port1: device 3-1.1 not suspended yet May 5 00:55:25 T2 kernel: x86/split lock detection: #AC: CPU 0/KVM/21420 took a split_lock trap at address: 0xfffff805bf6c218c May 5 00:55:32 T2 kernel: usb 4-1: Failed to suspend device, error -110 May 5 00:56:53 T2 kernel: usb 3-1-port1: device 3-1.1 not suspended yet May 5 00:57:26 T2 root: Fix Common Problems Version 2025.03.12 May 5 00:57:28 T2 kernel: usb 4-1: Failed to suspend device, error -110 May 5 00:57:37 T2 kernel: block nvme0n1: the capability attribute has been deprecated. May 5 00:57:48 T2 kernel: usb 3-1-port1: device 3-1.1 not suspended yet May 5 00:58:23 T2 kernel: usb 4-1: Failed to suspend device, error -110 May 5 00:58:43 T2 kernel: usb 3-1-port1: device 3-1.1 not suspended yet May 5 00:59:18 T2 kernel: usb 4-1: Failed to suspend device, error -110 May 5 00:59:38 T2 kernel: usb 3-1-port1: device 3-1.1 not suspended yet May 5 01:00:12 T2 kernel: usb 4-1: Failed to suspend device, error -110 May 5 01:00:33 T2 kernel: usb 3-1-port1: device 3-1.1 not suspended yet May 5 01:01:08 T2 kernel: usb 4-1: Failed to suspend device, error -110 May 5 01:01:28 T2 kernel: usb 3-1-port1: device 3-1.1 not suspended yet May 5 01:02:02 T2 kernel: usb 4-1: Failed to suspend device, error -110 May 5 01:02:23 T2 kernel: usb 3-1-port1: device 3-1.1 not suspended yet May 5 01:02:57 T2 kernel: usb 4-1: Failed to suspend device, error -110 May 5 01:03:17 T2 kernel: usb 3-1-port1: device 3-1.1 not suspended yet May 5 01:03:52 T2 kernel: usb 4-1: Failed to suspend device, error -110 It took a few tries to get to the Diagnostics page and then it hung on downloading diagnostics. So I restarted the server, which now seems OK, but I'm getting the same messages (see timestamps above). I do have a USB add-on card in the server, but there's nothing attached to it. Diagnostics after reboot are attached. Is this something to be worried about? t2-diagnostics-20250505-0057.zip

Thanks, yes, I'm now rebuilding Disk 3 and Disk 6 stays emulated. A bit of an edge case, so not many users are likely to see the two messages. Thanks for all the help.

But I didn't go through the stop/unassign/start/stop/reassign process for Disk 6. So unRAID will just rebuild both at the same time? I had thought unRAID would be more conservative - as in one rebuild at a time. But I suppose there's no real additional risk. So I can just go ahead?

I'm now trying to rebuild Disk 3 onto itself, but I get this warning message for both Disk 3 (understandable) and my disabled Disk 6: "All existing data on this device will be OVERWRITTEN when array is Started". What's going to happen to my Disk 6 data? Not going to proceed for now.

Waiting anxiously for my new SAS to SATA breakout cable to arrive, but now Disk 6 has read errors again and has been disabled. So now I have 2 disabled disks, with their contents being emulated. I do have dual parity, so I think I'm a bit safer than I otherwise would be, but I'm hoping to resolve this soon. To summarise, Disk 6 got disabled after read errors. I rebuilt it, but during the rebuild Disk 3 also got disabled after read errors. For a few days Disk 6 was OK, but now is disabled again with read errors. Diagnostics are attached. Assuming this is indeed all due to cable error, when the new cable arrives, I'm intending to replace the current cable then rebuild each disk (one at a time), unless the diagnostics indicate some other SMART problem. (Then I'm going to order another breakout cable as a standby.) Does this sound OK? tower-diagnostics-20250317-0953.zip

(Serial numbers are I believe correct, in case that's a concern. I have a screenshot from about a year ago that shows the same numbers.) I don't think I disturbed the disk3 connection - didn't have to touch it directly to change cables, but I suppose it's possible that the (shared) breakout cable is sensitive to any movement. What should I do now? This is what I can see in the Disk3 SMART settings in the GUI, if that's any use. (Sorry, getting late here. Will get back to this later. Appreciate the help.)

Not having much luck here. So I checked Disk 6 (emulated) contents - seemed OK, so I attached it to another cable and started rebuilding. But now on checking I have another disk, Disk 3, that is disabled. It's on the same SAS to SATA breakout cable as Disk 6 was (one of those SAS SFF-8087 to 4x SATA forward breakout cables), before I swapped cables. I've ordered a new cable, but it will take a few days to arrive. In the meantime, I've attached diagnostics - this time without rebooting. Would appreciate any information about what's causing the disk to be disabled, to see if it is/was indeed a cable problem. tower-diagnostics-20250312-0014.zip

My Disk 6 has a red X next to it and the pop up message says the device is disabled and being emulated. I don't know how to interpret the disk status, but diagnostics are attached. Does it look like I can salvage it by rebuilding it, or should it be replaced? tower-diagnostics-20250311-1615.zip

After updating to 7.0.0 my Win 11 VM failed to start, with the same error message (as in the thread title) repeated many times in the log, after which the log showed a shutdown command. (Just to be clear, not saying the upgrade to 7.0.0 had anything to do with it - hadn't used the VM for a while.) It turned out that the VM was waiting for a Bitlocker Recovery Key. I only found that out by booting up the VM again and looking at the VM Console (the NoVNC thing), which I don't usually do. Apparently something had changed in the Windows configuration (sorry, can't remember the message now). Anyway, after some mild panicking when the keyboard didn't seem to work, it turns out that the recovery key is all numbers, and you enter the numbers using the function keys. It does mention it on the screen, but it didn't obviously preclude letters, which confused me for a while. Fortunately I managed to dig up the recovery key and used the F keys to enter the number and after that all was well. This is a bit of an edge case, but I thought I'd post this in case anyone else runs into this issue.

On 6.12.13 I have a Windows 10 VM that shuts down by itself roughly once a week. Looking through the Event Viewer log, I see typically an Event ID 1074 which says The process qemu-ga.exe has initiated the power off of computer WIN10-TWR on behalf of user NT AUTHORITY\SYSTEM for the following reason: Other (Planned) Reason Code: 0x80000000 Shutdown Type: power off After a few messages associated with the shutdown, the next message (after about an hour with no log messages) in the log is an Event ID 6009, which says: Microsoft (R) Windows (R) 10.00. 19045 Multiprocessor Free. Googling tells me that this is what is reported on boot up, but oddly I see nothing in the Event Viewer that shows that initiated the boot up after the shutdown (maybe not so odd because the event log service hasn't yet restarted). What can I do to stop the VM shutting down like this? If more info is needed from the logs I can try to get it, but will need some direction on how and where to get it.