jimbobulator

Members
  • Posts

    123
  • Joined

  • Last visited

Converted

  • Gender
    Undisclosed
  • Location
    France

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

jimbobulator's Achievements

Apprentice

Apprentice (3/14)

0

Reputation

  1. Hello, thank you for the response. I checked and re-set the drive connectors and did a hard reboot to see if it would come back. I could hear a drive doing a click / click / click routine, and now it's showing disk2 as not installed. I'm thinking it's completely toast? I'm going to start moving the data off that drive in preparation for removal.
  2. Hello, Woke up to a disabled disk today, having trouble deciphering exactly what's going wrong. Diagnostics attached. I had some read errors a few months ago on both older drives (disk2 and disk4, both 6TB drives, both older 4-5 yrs old) but smart looked fine on both, so I continued running. Server is getting older, built in 2014. Parity check started yesterday but didn't finish due to disk2 failure. disk2 failure happened late in the parity check and this drive likely wasn't doing anything at that point, as it's 1/2 the size of parity. I'm seeing recurring out of memory errors happening between 3-4am each day, along with Plex being killed each time. I can't really make sense of what's going on, clearly more than just a failed drive. Maybe someone can help? Should I run memtest? I don't have a spare disk at the moment, but I can copy the data to another disk in the array and remove the failed disk, or copy it off the array if that's safer. Thanks!
  3. Check your vpn container env. variables. I had to add the VPN_INPUT_PORTS variable per the FAQ recently to fix this.
  4. Just to follow up, parity swap has completed successfully. Preclear went at reasonable speeds. All is good, so thank you kindly for the assistance. Feels good to have survived my first ever drive failure in 20 years of computing. Now to preclear the drive with errors and see what happens!
  5. Yeah it's odd. I checked my old 3TB 7200rpm reports from 7 years ago and they took 30h. I didn't shuck this 6TB, so I'm assuming that I precleared over SATA. But I do have a bunch of USB3 enclosures kicking around, maybe I used one for the preclear, and was affected by the same USB2 issues above. I have no way to know, unfortunately! Drive is working fine, read/write speeds are fine in the array. The 12TBs are on track to complete preread in 20-30 hours, I think, which seems ok. Not sure why they started slow.
  6. 8 hours later, one is reading at 130MB/s and one at 137MB/s.
  7. Yes, it's supposed to be USB3. I can't imagine someone making a 12TB enclosure that didn't support USB3!
  8. I just looked up my last preclear report, 6TB from a couple years ago, this one was connected on SATA. This one was slow too! Oof. Is this normal? I remember pre-clearing my first unraid drives back in 2013 and seeing 180MB/s. Maybe I should post in the preclear thread.... ############################################################################################################################ # # # unRAID Server Preclear of disk # # Cycle 1 of 1, partition start on sector 64. # # # # # # Step 1 of 5 - Pre-read verification: [41:50:01 @ 39 MB/s] SUCCESS # # Step 2 of 5 - Zeroing the disk: [41:52:52 @ 39 MB/s] SUCCESS # # Step 3 of 5 - Writing unRAID's Preclear signature: SUCCESS # # Step 4 of 5 - Verifying unRAID's Preclear signature: SUCCESS # # Step 5 of 5 - Post-Read verification: [63:14:18 @ 26 MB/s] SUCCESS # # # # # # # # # # # # # # # ############################################################################################################################ # Cycle elapsed time: 146:57:14 | Total elapsed time: 146:57:14 # ############################################################################################################################ ############################################################################################################################ # # # S.M.A.R.T. Status default # # # # # # ATTRIBUTE INITIAL CYCLE 1 STATUS # # 5-Reallocated_Sector_Ct 0 0 - # # 9-Power_On_Hours 0 147 Up 147 # # 194-Temperature_Celsius 43 57 Up 14 # # 196-Reallocated_Event_Count 0 0 - # # 197-Current_Pending_Sector 0 0 - # # 198-Offline_Uncorrectable 0 0 - # # 199-UDMA_CRC_Error_Count 0 0 - # # # # # # # # # # # ############################################################################################################################ # SMART overall-health self-assessment test result: PASSED # ############################################################################################################################ --> ATTENTION: Please take a look into the SMART report above for drive health issues. --> RESULT: Preclear Finished Successfully!.
  9. It's late here so I'm calling it a day. The pre-read speeds are slowing creeping up, started around 20MB/s and now at 30MB/s. If it gets past 60 I guess it's not stuck at high speed / usb2, but not sure why it would be this low. Could it be that it's just reading at the middle of the platters and it's naturally slower, and will speed up over time? That still seems crazy slow though. Cheers!
  10. I couldn't get a video output working to get into the BIOS, so I had to open the case and reset it manually. I went through all the settings, including enabling the xHCI/EHCI handoffs. Now lsusb is showing 5Gbps connections for my connected USB drives (success?), but the preclear is proceeding at the same speed as before (fail!). Argh. Edit: removed diagnostics
  11. Hello, I'm trying to preclear some 12TB drives in external enclosures over USB. Currently pre-reading at ~20MB/s. Yikes, should be ~200MB/s. lsusb indicates that it's a 480Mbps interface, and there's not any usb 3.0 interfaces shown at all. A one point a few years ago I was having difficulty passing through USB devices to VMs, and spent some time messing around with BIOS settings for xHCI/EHCI handoff, perhaps I've left this setting in a weird state and it's disabled usb3 capability? I don't remember ow I left it. Kids are streaming a movie at the moment and I need to drag up a monitor/keyboard to check BIOS settings. Will update when I get a chance. Thanks!
  12. Right, of course. Thank you very much for the prompt and efficient help!
  13. Agreed, this is strange. It's how it went down, though. The drive is still disabled - I assume Unraid keeps the drive disabled on successive boots after a write error, to ensure no further damage? This was my thoughts as well. I've got a plan now: copy off critical files to an external disk (paranoia), then attempt a parity swap with a bigger drive. Will report back in a few days or a week once it's *hopefully* cleared up.
  14. Well, unfortunately my server rebooted today for unknown reasons. I got a notification that "array turned good", which was sent after the reboot. So sadly I don't have the juicy syslogs, and stupidly I turned turned off the syslog to flash setting a while back. Doh. Here is a recap of the notifications I got today. 07:36 - Notice: Parity Check Started 10:54 - Alert: Disk 2 in error state (disk dsbl) 10:54 - Warning: array has errors. Array has 1 disk with read errors 15:11 - Notice: array turned good. Array has 0 disks with read errors 15:11 - Notice: Parity check has finished (0 errors). Duration 17 hours, 53 minutes, 19 seconds. Average Speed nan B/s Notes After the notification at 10:54 I logged in remotely and saw the disk2 was disabled, and the "Main" page summary that disk2 had 2048 errors. I couldn't see the SMART data for disk. The parity check was now a 'read check' I wasn't able to log back in throughout the day. The parity check notification is bugged - clearly wasn't 17 hours, and probably should've said 'Read check has finished", I suppose? Anyway, disk2 now shows 88 reallocated sectors. Most of the contents of this disk are non-important media, but there are some things with clear priority that I'd like to try and save. What's the best step forward? Diagnostics removed.
  15. Thanks for the answers! Unraid only disables a disk for write errors. It is possible for a read error to cause Unraid to get the data for the failed read from the parity calculation and try to write it back to the disk. If that write-back fails then the disk would be disabled. Ok, the notification just said read errors, but I'll check tonight. This is confusing, I suspect because you are confused about what "format" does. You must let Unraid format any disk it will use in the array, and you must NEVER format a disk you are rebuilding. And you must NEVER format any disk that has data on it you want to keep. I just don't see how the idea of "format" figures into this at all. Right that was not clear at all. First and foremost, my priority is to recover the data from the failed disk and get the array healthy again. I could buy a 6TB drive and rebuild disk2 onto that one. But I'd rather not buy another 6TB drive, as I have limited physical space in my server. So if the replacement drive could be bigger than my current parity disk, I might consider that. As it's not a normal procedure, let's scrap this idea. This is why I asked... What I was thinking, which is likely the 'short-stroking' you mention: Could I assign a new disk2 that is larger than parity and let it rebuild? Would Unraid would limit the size of the filesystem to parity size? Then later on, I'd replace parity with a drive matching or exceeding disk2's true capacity, copy of the data from the disk2 somewhere else, and then format disk2 it to it's true capacity. Ok, this might work... I'm already at the device limit for my Unraid Basic license and the limit of SATA ports on my mobo, so I'm not sure I can do all the steps yet. Will read more closely and see if this is a possible solution.