Jump to content

johnnie.black

Members
  • Content Count

    19159
  • Joined

  • Last visited

  • Days Won

    235

johnnie.black last won the day on October 10

johnnie.black had the most liked content!

Community Reputation

2009 Hero

About johnnie.black

  • Rank
    ti-ti jorge

Converted

  • Gender
    Male

Recent Profile Visitors

5817 profile views
  1. That's fine. Yes, parity will need to be synced after new config.
  2. I meant rebuilding to a new disk, you can use the array for a while with disk1 disable, but since you don't have dual parity if another disk fails in the meantime it will be unrecoverable.
  3. Normal copy will error out on any disk error, you'll need to skip those files, but if the files are easily replaceable or not important it's the easier option.
  4. You can disable disk1 and copy everything from the emulated disk to the other disks, but it will require reeding all the other disks, one of them will read and write simultaneouly, so puts more stress than a regular rebuild, which IMHO is the best option, unless you don't plan on replacing that disk soon or ever.
  5. It did, but the errors were a disk problem: Error 3 [2] occurred at disk power-on lifetime: 14448 hours (602 days + 0 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER -- ST COUNT LBA_48 LH LM LL DV DC -- -- -- == -- == == == -- -- -- -- -- 40 -- 51 05 40 00 01 b0 76 60 c8 e0 00 Error: UNC 1344 sectors at LBA = 0x1b07660c8 = 7255515336 UNC @ LBA means a media error, power on hours 14448 so about 20H ago, these errors can be intermittent, but not a good sign, keep monitoring the disk, especially these attributes: Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAGS VALUE WORST THRESH FAIL RAW_VALUE 1 Raw_Read_Error_Rate POSR-K 200 200 051 - 47 200 Multi_Zone_Error_Rate ---R-- 200 200 000 - 4 If they keep climbing you'll likely get more errors soon.
  6. Also not looking good, your plan sounds good to me, alternatively you can use ddrescue to clone the failing disks and recover as much data as possible, if there are read errors some files will likely be corrupt but you can identify which ones.
  7. Disk1 is failing, there's no SMART report for disk5 on the diags, try grabbing one manually and post it.
  8. Dis stopped responding and dropped offline, now on the onboard SATA ports: Oct 16 17:02:50 Tower kernel: ata1: link is slow to respond, please be patient (ready=0) Oct 16 17:02:55 Tower kernel: ata1: COMRESET failed (errno=-16) Oct 16 17:03:00 Tower kernel: ata1: link is slow to respond, please be patient (ready=0) Oct 16 17:03:01 Tower sshd[5655]: Accepted none for root from 192.168.178.44 port 63121 ssh2 Oct 16 17:03:05 Tower kernel: ata1: COMRESET failed (errno=-16) Oct 16 17:03:10 Tower kernel: ata1: link is slow to respond, please be patient (ready=0) Oct 16 17:03:40 Tower kernel: ata1: COMRESET failed (errno=-16) Oct 16 17:03:40 Tower kernel: ata1: limiting SATA link speed to 3.0 Gbps Oct 16 17:03:45 Tower kernel: ata1: COMRESET failed (errno=-16) Oct 16 17:03:45 Tower kernel: ata1: reset failed, giving up Oct 16 17:03:45 Tower kernel: ata1.00: disabled So likely a bad disk.
  9. Impossible to say without any diags, post current ones so we can at least see SMART report.
  10. If it happens again try downloading the diags by typing diagnostics on the console, if that doesn't work enable syslog server for the next time.
  11. Bios setting is what matters, 2133 is fine for 4 single rank DIMMs.
  12. NFS is crashing, do you need NFS shares enable? Try disabling if not, if you need it maybe someone else can chime in since I've never used it.
  13. Only share currently with data to move with your current configuration is the system share, and that data will only be moved if the docker/VM services are stopped.