Hi

I noticed today that my Nextcloud instance was no longer reachable. I tried logging into the unraid UI to see why, but it results in an "Unable to Connect" error.

Strangely, my Plex and Lyrion Music Server Dockers remain working fine.

I was running a Win 11 VM (named Wednesday), and had used a Powershell script to schedule its shutdown for 10 mins in the future before I noticed the problem with Nextcloud, so I was wondering if the problem could be a hanging VM. (I use that script all the time without problems)

I can use my BMC to get to the Unraid terminal, so I tried the command:

virsh stop Wednesday

But it returned the error:

error: failed to connect to the hypervisor

error: failed to connect socket to 'var/run/libvirt/libvirt-sock' : Connection refused

So I tried

diagnostics

and get

-bash: diagnostics: command not found

similarly when I try

powerdown

I get

-bash: powerdown: command not found

so I tried:

cp /var/log/syslog /boot/syslog.txt

and get

cp: cannot create regular file '/boot/syslog.txt' : Input/Output error

top

gets

-bash: top: command not found

What can I do?

What has happened?

Thanks for your help.

Edited July 31, 2025Jul 31 by jademonkee

tail and cat seem to still work. See attached screenshot for the output of tail.

The time for when the machine froze aligns with. the timestamp seen in the log.

If anyone knows how to get more of the syslog, let me know.

See if you can get the syslog:

cp /var/log/syslog /boot/syslog.txt

4 minutes ago, JorgeB said:

See if you can get the syslog:

cp /var/log/syslog /boot/syslog.txt

As mentioned above, it just results in:

cp: cannot create regular file '/boot/syslog.txt' : Input/Output error

Following your idea, I instead did:

cp /var/log/syslog /mnt/user/public/syslog.txt

and it executed correctly.

However, I cannot mount that dir, as my mac can't connect to willow.local to mount the 'public' share

Edited July 31, 2025Jul 31 by jademonkee

I gave up and forced a shutdown via the power button.

Looks like my flash drive died.

Gonna go find a backup and restore it. (hopefully it's not the USB controller...)

Ok, I restored from a backup and it booted succesfully.

Going to order a new (industrial grade) flash drive now. Hopefully it arrives before another problem occurs.

Attached is the syslog. Hopefully the last lines in it cam shed some light on what happened.

Many thanks for your help and insight.

syslog.txt

Jul 31 16:24:53 Willow kernel: usb 1-9: reset high-speed USB device number 5 using xhci_hcd

Jul 31 16:24:54 Willow kernel: sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x03 driverbyte=DRIVER_OK cmd_age=30s

Jul 31 16:24:54 Willow kernel: sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x28 28 00 00 88 a7 18 00 00 08 00

Jul 31 16:24:54 Willow kernel: I/O error, dev sda, sector 8955672 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0

Flash drive issues, though I cannot say if it's the flash drive or the USB controller, you can try a different USB port first; if the same, replace the flash drive.

A new flash drive will arrive Monday to replace my old one.

Hopefully the problem doesn't happen again.

I'll report back if it does.

Edited August 1, 2025Aug 1 by jademonkee