Jump to content

runraid

Members
  • Content Count

    86
  • Joined

  • Last visited

Everything posted by runraid

  1. USB stick is now in a USB 2.0 port (was a 3.0). Stopped the array. Rebooted the system. Came up with "unclean shutdown detected". It's now doing a full parity check. Nothing appears to have been lost (I love unraid). > Array Started•Parity-Check 0.1 %• Dynamix webGui v2017.03.30 I'm going to purchase a high quality USB stick. I wish unraid didn't depend on the USB stick though
  2. Put the USB drive into my PC and it immediately said it had errors. Running checkdisk now. This is two USB sticks with issues in about 4 days.
  3. Thanks all. I'll do a shutdown, USB swap, then parity check. I'll report back if it this happens again.
  4. @Squid when I did a shut down in the UI, at that time I was not having any USB issues. A day later (right now) I've started having the issue
  5. @trurl Yes I did use the UI to shut down. But the odd thing is, when it started back up, it said I did an unclean shutdown and it had to do a full parity check. I might have been ssh'ed into the machine at that time which could have prevented a clean shutdown. For now on, I will stop the array, then do the shut down just to make sure I get a clean shutdown.
  6. @trurl I shut it down a day or two ago, but things were fine until today. I did not do anything else on the machine. @Squid I want to say that I have it plugged into a USB 3 port (during both failures). I'll move to a USB 2 port.
  7. I didn't shut the system down at all. Nor was I working on it. I just opened the UI and noticed the errors. The first time this happened, I had the USB stick plugged in the front USB port. The second time (this time), with a brand new, completely different USB stick, I have it plugged in the back USB port. Can I just unplug the USB stick to run checkdisk without my unraid server going down?
  8. This is the second time that this has happened in 4 days. It's happened across two different USB sticks (brand new ones). I assume I need to replace the USB stick yet again? Apr 10 14:26:58 Tower kernel: FAT-fs (sda1): Directory bread(block 8199) failed Apr 10 14:26:58 Tower kernel: FAT-fs (sda1): Directory bread(block 8200) failed Apr 10 14:26:58 Tower kernel: FAT-fs (sda1): Directory bread(block 8201) failed Apr 10 14:27:01 Tower root: Apr 10 14:27:01 Tower root: Warning: file_put_contents(/boot/config/docker.cfg): failed to open stream: No such file or directory in /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/dockerconfig.php on line 35 Apr 10 14:27:01 Tower root: Apr 10 14:27:01 Tower root: Warning: file_put_contents(/boot/config/domain.cfg): failed to open stream: No such file or directory in /usr/local/emhttp/plugins/dynamix.vm.manager/scripts/libvirtconfig.php on line 39 Apr 10 14:27:07 Tower kernel: fat__get_entry: 150 callbacks suppressed Apr 10 14:27:07 Tower kernel: FAT-fs (sda1): Directory bread(block 8192) failed Apr 10 14:27:07 Tower kernel: FAT-fs (sda1): Directory bread(block 8193) failed Apr 10 14:27:07 Tower kernel: FAT-fs (sda1): Directory bread(block 8194) failed Apr 10 14:27:07 Tower kernel: FAT-fs (sda1): Directory bread(block 8195) failed Apr 10 14:27:07 Tower kernel: FAT-fs (sda1): Directory bread(block 8196) failed Apr 10 14:27:07 Tower kernel: FAT-fs (sda1): Directory bread(block 8197) failed Apr 10 14:27:07 Tower kernel: FAT-fs (sda1): Directory bread(block 8198) failed Apr 10 14:27:07 Tower kernel: FAT-fs (sda1): Directory bread(block 8199) failed Apr 10 14:27:07 Tower kernel: FAT-fs (sda1): Directory bread(block 8200) failed Apr 10 14:27:07 Tower kernel: FAT-fs (sda1): Directory bread(block 8201) failed Apr 10 14:27:16 Tower kernel: fat__get_entry: 54 callbacks suppressed Apr 10 14:27:16 Tower kernel: FAT-fs (sda1): Directory bread(block 8192) failed Apr 10 14:27:16 Tower kernel: FAT-fs (sda1): Directory bread(block 8193) failed Apr 10 14:27:16 Tower kernel: FAT-fs (sda1): Directory bread(block 8194) failed Apr 10 14:27:16 Tower kernel: FAT-fs (sda1): Directory bread(block 8195) failed Apr 10 14:27:16 Tower kernel: FAT-fs (sda1): Directory bread(block 8196) failed Apr 10 14:27:16 Tower kernel: FAT-fs (sda1): Directory bread(block 8197) failed Apr 10 14:27:16 Tower kernel: FAT-fs (sda1): Directory bread(block 8198) failed Apr 10 14:27:16 Tower kernel: FAT-fs (sda1): Directory bread(block 8199) failed Apr 10 14:27:16 Tower kernel: FAT-fs (sda1): Directory bread(block 8200) failed Apr 10 14:27:16 Tower kernel: FAT-fs (sda1): Directory bread(block 8201) failed Apr 10 14:27:25 Tower kernel: fat__get_entry: 54 callbacks suppressed Apr 10 14:27:25 Tower kernel: FAT-fs (sda1): Directory bread(block 8192) failed Apr 10 14:27:25 Tower kernel: FAT-fs (sda1): Directory bread(block 8193) failed Apr 10 14:27:25 Tower kernel: FAT-fs (sda1): Directory bread(block 8194) failed Apr 10 14:27:25 Tower kernel: FAT-fs (sda1): Directory bread(block 8195) failed Apr 10 14:27:25 Tower kernel: FAT-fs (sda1): Directory bread(block 8196) failed Apr 10 14:27:25 Tower kernel: FAT-fs (sda1): Directory bread(block 8197) failed Apr 10 14:27:25 Tower kernel: FAT-fs (sda1): Directory bread(block 8198) failed Apr 10 14:27:25 Tower kernel: FAT-fs (sda1): Directory bread(block 8199) failed Apr 10 14:27:25 Tower kernel: FAT-fs (sda1): Directory bread(block 8200) failed Apr 10 14:27:25 Tower kernel: FAT-fs (sda1): Directory bread(block 8201) failed