Hello!

Unraid will occasionally lock up for me. The webui, terminal, ssh, whatnot all hang. The server is on the network still and the cursor blinks at the local terminal and I can type stuff in, but it processes nothing so I can't stop the array or clean shutdown when this happens.

I would post my diagnostics, but the UI locked up when I tried to download it.

Checking the logs the following lines are of particular interest to me

Nov 6 10:27:17 Chiliad kernel: usb 1-1.4: reset high-speed USB device number 3 using ehci-pci
Nov 6 10:27:18 Chiliad kernel: sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x05 driverbyte=0x00
Nov 6 10:27:18 Chiliad kernel: sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x28 28 00 00 14 ea 2f 00 00 01 00
Nov 6 10:27:18 Chiliad kernel: blk_update_request: I/O error, dev sda, sector 1370671

sda is the flash drive I booted off of, so this indicates to me that the drive is giving me problems. After shutting down, I ran chkdsk /f /r on this drive in Windows but Windows reported no issues.

I am wondering, is this not uncommon for Windows to say the drive is all good, but in this case it is still not fit enough?

Maybe I have a different issue entirely? Is the USB device supposed to be resetting like that? (reset high-speed USB device number 3 using ehci-pci) Does unraid work better with certain BIOS settings?

I have also attached my syslog

syslog.txt

Try a different port, preferably USB2.

Thanks for the response.

Interestingly enough, although Windows said the disk was fine, running fsck on macOS found some free space errors on this partition.

This cleared up the I/O errors, but I noticed I was having many of these warnings when I tried running unraid again.

Nov 6 14:02:01 Chiliad kernel: FAT-fs (sda1): Directory bread(block 7862) failed

Which searching through some other posts here, people suggest are caused when the server thinks the drive is being repeatedly inserted and removed. (https://lime-technology.com/forum/index.php?topic=38011.msg351843#msg351843)

 

@Trurl, I believe you are on to something here specifiying USB 2. This was already plugged into a USB 2 port and I tried a different port, first in a different iommu group and then in a different bus. Both times I had similar results, however disabling USB 3.0 in my BIOS seems to have stopped those issues.

 

I have not extensively tested this yet, so I do not know if my problems are 100% gone yet, however if anyone has a similar problem and stumbles across here, or if anyone else has any other ideas/suggestions; it turns out my problem was related to a Windows 10 Vm I was trying to run with my onboard USB 3.0 controller passed through it and USB mode was set to XHCI (usb 3.0) in the xml. Setting the USB mode to EHCI (usb 2.0) for the VM seems to have cleared the issue up even when I have USB 3.0 enabled again in my BIOS. Additionally, even though my USB mode is set to EHCI in the VM, Windows device manager still recognizes the controller as "USB 3.0 eXtensible Host Controller" so thats fine and dandy.

 

My problems seem to have come back. Seems to only happen when I shut a Windows 10 VM down.

I cannot figure out how to resolve this, I only know that it probably has something to do with USB 3 vs USB 2 usage. Unless anyone has any suggestions, my trial is almost up and I probably won't make a purchase to continue to figure this out. Unraid has been excellent, but I just need to be running Windows and this sort of prevents it.

If anyone in the future has this issue; I could probably disable USB 3 in my BIOS, but I'm not going to do that, since for my use case its too much of a compromise.