USB stick not booting - power brownout?

[Unoid]

Today I noticed my power flickered and my unraid UPS cycled on temporarily. Then my Unraid USB drive became unresponsive. I wrote down some syslog problems and did a reboot thinking it'd come back, but it isn't. I popped the USB stick into my win10 box and the files seems intact. Any ideas?

I do have backups of the USB stick but they're on one of my disks in my unraid server. Would have to pop one out mount on windows/linux?, and try to reformat the USB stick and copy old files back.

 

EDIT: Plugged a monitor into my server. It does boot off the USB and if I pick the default  Unraid OS, it stalls at the first step of reading /bzimage

EDIT 2: Trying to boot again and it only says: SYSLINUX 6.03 EDDBoot error

Apr 11 12:06:51 Tower kernel: usb 2-1.2: USB disconnect, device number 3
Apr 11 12:06:52 Tower kernel: usb 2-1.2: new full-speed USB device number 4 using ehci-pci
Apr 11 12:06:52 Tower kernel: hid-generic 0003:0764:0501.0002: hiddev96,hidraw0: USB HID v1.10 Device [CPS CP1350PFCLCD] on usb-0000:00:1d.0-1.2/input0
Apr 11 12:06:53 Tower kernel: xhci_hcd 0000:03:00.0: Cannot set link state.
Apr 11 12:06:53 Tower kernel: usb usb4-port2: cannot disable (err = -32)
Apr 11 12:06:53 Tower kernel: xhci_hcd 0000:03:00.0: Cannot set link state.
Apr 11 12:06:53 Tower kernel: usb usb4-port2: cannot disable (err = -32)
Apr 11 12:06:53 Tower kernel: usb 4-2: USB disconnect, device number 2
Apr 11 12:06:53 Tower kernel: sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x01 driverbyte=0x00
Apr 11 12:06:53 Tower kernel: sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x28 28 00 00 16 d9 70 00 00 40 00
Apr 11 12:06:53 Tower kernel: print_req_error: I/O error, dev sda, sector 1497456
Apr 11 12:06:53 Tower kernel: sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x01 driverbyte=0x00
Apr 11 12:06:53 Tower kernel: sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x28 28 00 00 16 d9 b0 00 00 80 00
Apr 11 12:06:53 Tower kernel: print_req_error: I/O error, dev sda, sector 1497520
Apr 11 12:06:53 Tower kernel: print_req_error: I/O error, dev loop0, sector 15008
Apr 11 12:06:53 Tower kernel: SQUASHFS error: squashfs_read_data failed to read block 0x74fa5c
Apr 11 12:06:53 Tower kernel: SQUASHFS error: Unable to read fragment cache entry [74fa5c]
Apr 11 12:06:53 Tower kernel: SQUASHFS error: Unable to read page, block 74fa5c, size 159e4
Apr 11 12:06:53 Tower kernel: print_req_error: I/O error, dev loop0, sector 15010
Apr 11 12:06:53 Tower kernel: SQUASHFS error: Unable to read fragment cache entry [74fa5c]
Apr 11 12:06:53 Tower kernel: SQUASHFS error: Unable to read page, block 74fa5c, size 159e4
Apr 11 12:06:53 Tower kernel: print_req_error: I/O error, dev loop0, sector 15012
Apr 11 12:06:53 Tower kernel: SQUASHFS error: Unable to read fragment cache entry [74fa5c]
Apr 11 12:06:53 Tower kernel: SQUASHFS error: Unable to read page, block 74fa5c, size 159e4
Apr 11 12:06:53 Tower kernel: SQUASHFS error: Unable to read fragment cache entry [74fa5c]
Apr 11 12:06:53 Tower kernel: print_req_error: I/O error, dev loop0, sector 15014
Apr 11 12:06:53 Tower kernel: SQUASHFS error: Unable to read page, block 74fa5c, size 159e4
Apr 11 12:06:53 Tower kernel: SQUASHFS error: Unable to read fragment cache entry [74fa5c]
Apr 11 12:06:53 Tower kernel: SQUASHFS error: Unable to read page, block 74fa5c, size 159e4
Apr 11 12:06:53 Tower kernel: print_req_error: I/O error, dev loop0, sector 15016
Apr 11 12:06:53 Tower kernel: SQUASHFS error: Unable to read fragment cache entry [74fa5c]
Apr 11 12:06:53 Tower kernel: SQUASHFS error: Unable to read page, block 74fa5c, size 159e4
Apr 11 12:06:53 Tower kernel: print_req_error: I/O error, dev loop0, sector 15018
Apr 11 12:06:53 Tower kernel: print_req_error: I/O error, dev loop0, sector 15020
Apr 11 12:06:53 Tower kernel: print_req_error: I/O error, dev loop0, sector 15022
Apr 11 12:06:53 Tower kernel: SQUASHFS error: squashfs_read_data failed to read block 0x3f5d8c
Apr 11 12:06:53 Tower kernel: SQUASHFS error: squashfs_read_data failed to read block 0x3f5d8c
Apr 11 12:06:53 Tower kernel: blk_partition_remap: fail for partition 1

Apr 11 12:06:54 Tower kernel: FAT-fs (sda1): Directory bread(block 324928) failed

 

Edited April 11, 2018 by Unoid

[Unoid]

Well, this is weird.

 

I moved where the plug the USB stick into and it had more errors, I fiddled with how it was plugged in and magically it's booting again now. Doens't make much sense.

 

I'm going to backup the USB stick again and buy a replacement.

 

I suppose I don't need help anymore