November 29, 20178 yr I'm getting a repeated errors in the dmesg, and my server had been crashing after a few minutes of running a parity check. This happens in safe mode as well, so I'm certain it isn't plugin related. Quote [ 14.227007] usb 1-6: device descriptor read/64, error -71 [ 13.558011] usb 1-6: new high-speed USB device number 4 using ehci-pci [ 13.674010] usb 1-6: device descriptor read/64, error -71 [ 13.899011] usb 1-6: device descriptor read/64, error -71 Any idea?
November 30, 20178 yr You don't tell what that USB is used for. So not easy to guess the implications for the programs that receives the -71 error code.
November 30, 20178 yr Community Expert Connect a monitor to your server. Install 'Fix Common Problems' plugin. Turn on the Trouble shooting mode. This will write a series of Log files in the logs folder on your flash drive. Now run the parity check. Wait for the 'crash' Upload those files from the logs folder and a photo of the screen. (Make sure that your photo is sharp, not-blurred, no flash spot and contains all of the information on the monitor.) With that post, also include a list of all of the hardware that is installed on your server. To your question, I have never of a parity check being the actual cause of a crash. I tend to suspect that something else is going on...
December 1, 20178 yr Author 13 hours ago, pwm said: You don't tell what that USB is used for. So not easy to guess the implications for the programs that receives the -71 error code. The only USB plugged in is the unraid usb.
December 1, 20178 yr OK. It it just now that it has started to give read errors? Is it a new thumb drive or might it be a drive that suffers from wear and needs to be replaced? Since the system boots from the thumb drive, it's vital that it never gives read/write errors.
December 1, 20178 yr Community Expert It is simple to replace your Flash drive. Stop the array first. Then make a backup copy of the flash drive to a folder on your PC. (The config folder is the most important one to get off!) If your copy operation is successful. It is simple from that point. Copy everything to a new good quality (Brand name is a way to achieve this) Flash Drive (less than 32GB). Run the appropriate make-bootable script for your OS. Reboot with the new Flash Drive. Use these instructions to get your new key file: https://lime-technology.com/replace-key/ If the copy was not successful, could you copy the config folder? You could also pull the drive and run chkdsk on it to see if it is repairable.
Archived
This topic is now archived and is closed to further replies.