Current UnRaid Version 7.1.2

syslog-10.42.71.10 (1).log

I have moved the USB boot drive to various locations on the motherboard, both inside the chassis on the motherboard and on the rear I/O panel.

I have replaced the USB drive once, Samsung FIT Plus 32GB, with a brand new Samsung FIT Plus 32GB.

I have upgraded Unraid from 7.0.1 to 7.1.2.

I have also replaced the Motherboard Supermicro X9DRi-LN4F+ Rev 1.20A, with an identical Motherboard.

I've even tried the plugin "Flash Remount" without success.

And yet this problem still remains. After a couple of days it appears as if the USB disconnects and the system effectively crashes. Sometimes I can open the local console and attempt to gracefully reboot, sometimes the console is just unresponsive.

Edited June 8, 20251 yr by The Crazy Squirrel

Jun 2 11:12:39 Cthulhu kernel: SQUASHFS error: xz decompression failed, data probably corrupt

Jun 2 11:12:39 Cthulhu kernel: SQUASHFS error: Failed to read block 0x1d18acec: -5

Jun 2 11:12:39 Cthulhu kernel: SQUASHFS error: xz decompression failed, data probably corrupt

Jun 2 11:12:39 Cthulhu kernel: SQUASHFS error: Failed to read block 0x1d18acec: -5

Jun 2 11:12:39 Cthulhu kernel: SQUASHFS error: xz decompression failed, data probably corrupt

This is typically a flash drive problem, try a different one, ideally from a different brand/model

Ok, I have once again replaced my USB boot drive. This time with a PNY 32GB USB 2.0 drive.

I'll cross my fingers and hope for the best. I'll come back to this thread in about a week and give an update. Sooner if I run into problems again.

It's been nearly two weeks since the latest USB drive replacement, and my system has been working.

So now this is where I add my voice to the numerous requests for Limetech to please allow users to tie their system boot drive to something other than a USB drive. After having a new USB drive that I took out of the packaging immediately fail, is a worse than terrible user experience. Because after having the new USB drive immediately fail in the same way as the previous drive, I assumed that the fault must be in some other component of the system. What are the chances of that actually happening? Well looking through various forum posts across the internet I find that this does, on rare occasions, happen to some people. And please don't respond with "my USB drive has been working for years, so there isn't a problem." or "If a USB drive fails, it's real easy to replace, so there isn't a problem." I don't find these type of responses to be very helpful, and only really goes to frustrate anyone who has had unusual problems with the USB drive requirement.

Anyway, I would like to thank JorgeB for the response to try a different brand/model of USB drive, since I probably would have just gone with a third Samsung FIT.

I did have a single error show up in the syslog a few days after the switch to the PNY USB drive...

Jun 13 02:38:52 Cthulhu kernel: usb 2-1.1: reset high-speed USB device number 3 using ehci-pci
Jun 13 02:38:52 Cthulhu kernel: sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x07 driverbyte=DRIVER_OK cmd_age=2s
Jun 13 02:38:52 Cthulhu kernel: sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x28 28 00 00 10 a4 78 00 00 f0 00
Jun 13 02:38:52 Cthulhu kernel: I/O error, dev sda, sector 1090680 op 0x0:(READ) flags 0x84700 phys_seg 30 prio class 0

Since my system appears to be running properly, and this error has only occured once, I think I'm OK. But I'm not sure what this error is.

This might just be a bad block in the USB drive. If anyone else has any ideas what this error might be I would appreciate the assistance. I'm including this here instead of starting a new tread just in case this is somehow related to the problem I was having earlier, and there really is something wrong with the hardware of my system.

That looks more like a USB reset, if it happens again, try a different port.