Jump to content

DingHo

Members
  • Content Count

    51
  • Joined

  • Last visited

Community Reputation

0 Neutral

About DingHo

  • Rank
    Advanced Member

Converted

  • Gender
    Undisclosed
  • Location
    Singapore

Recent Profile Visitors

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

  1. updated from 6.6.7 without issue. thanks
  2. Loving unraid for 9 years or so. It’s irrational how much I want one of those badges.
  3. I figured this out. Not sure the original cause of the hung docker update, but reinstalling the docker didn't pick up the saved container paths. Simply putting all the paths back manually fixed it up.
  4. I was doing a routine update of docker containers. The process hung for quite some time, so I eventually did a reboot through the UnRAID UI. When it came back up all dockers were missing and after some time the UI and ssh were completely unresponsive. I did a hard reset and everything seemed to come back OK, except the Plex docker is now gone. I read in another thread to just reinstall the docker as all the appdata is still present. I was able to reinstall it, and it picks up all the existing metadata, however it seems all the paths are missing as nothing will play. I've attached the diagnostic .zip. Any help would be appreciated. Thank you. scour-diagnostics-20190429-1800.zip
  5. I picked up an IBM m1015, flashed it to rev. P20. Rebuild has been proceeding successfully for ~9 hours. Disk 7 SMART test was fine. Assuming the rebuild successfully completes by the time I wake up tomorrow, am I good to go? i.e. Can I re-add my previous disk 7 after a preclear, or should I run a parity check or anything else first? Really appreciate the help I've received here.
  6. Thanks for the advice. I've been thinking of doing that.
  7. Thanks for confirming. Thought the SAS2LP would be more reliable. 😥 Will do. I'll update when I get the LSI card.
  8. @johnnie.black Thanks, I really appreciate your help. I'll rebuild with a new disk. Do these steps look correct? 1. Stop array 2. Remove Parity2 from array. (will use as new rebuild disk) 3. Power down 4. Replace SAS2LP with 8211-8i 5. Power on 6. Check SMART on disk7, confirm OK 7. Stop array, set disk7 to 'No Device' 8. Add old Parity2 as replacement disk7 for rebuilding 9. Profit.
  9. Thanks. I found an LSI 8211-8i for sale locally. I can probably get it in the next day or so. Would you be so kind as to outline the steps I'd need to take to get back up and running given my current state of affairs?
  10. I spoke too soon about the parity sync still running. The data drive I moved to the SAS2LP is now showing as offline. (red X). I stopped the parity sync. Now I'm a bit nervous about next steps. Any help appreciated. scour-diagnostics-20190116-1144.zip
  11. Thanks @johnnie.black. I tried swapping parity2 and a data drive that was on the Intel SATA controller. My [faulty] thinking was the 2nd parity might work if not on the troublesome SAS2LP. Parity Sync started after reboot, ran for a bit, then started throwing up a ton of this error: Jan 16 11:06:03 Scour kernel: REISERFS error (device md3): vs-7000 search_by_entry_key: search_by_key returned item position == 0 I was able to get the diag file this time. The parity sync is actually still running now after all those errors. With the new logs, can you tell with more certainty this likely a SAS2LP issue? Should I just pony up the dough for and LSI controller at this point? Thanks again. scour-diagnostics-20190116-1102.zip
  12. Thank you. Had to do a hard reset, but everything comes back up fine. scour-diagnostics-20190116-0729.zip
  13. Hello, I just bought 2 new 4TB drives with the intention of adding one for data and the other as a 2nd parity drive. Both successfully pre-cleared. I then ran a parity check successfully. I stopped the array, added one as data, restarted the array successfully. Stopped the array again, added the next drive as 2nd parity, started the array and began the rebuild. It ran fine for about 6 hours then slowed to a crawl. I stopped the rebuild. I found several errors in the log: Jan 15 14:36:44 Scour kernel: sas: sas_eh_handle_sas_errors: task 0x00000000675fa35a is aborted Jan 15 14:36:44 Scour kernel: sas: ata11: end_device-9:2: cmd error handler Jan 15 14:36:44 Scour kernel: sas: ata9: end_device-9:0: dev error handler Jan 15 14:36:44 Scour kernel: sas: ata10: end_device-9:1: dev error handler Jan 15 14:36:44 Scour kernel: sas: ata11: end_device-9:2: dev error handler Jan 15 14:36:44 Scour kernel: ata11.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen Jan 15 14:36:44 Scour kernel: ata11.00: failed command: READ DMA EXT Jan 15 14:36:44 Scour kernel: ata11.00: cmd 25/00:00:98:12:6e/00:04:a7:00:00/e0 tag 17 dma 524288 in Jan 15 14:36:44 Scour kernel: res 40/00:80:28:0d:71/00:00:29:00:00/40 Emask 0x4 (timeout) Jan 15 14:36:44 Scour kernel: ata11.00: status: { DRDY } Jan 15 14:36:44 Scour kernel: ata11: hard resetting link Jan 15 14:36:44 Scour kernel: sas: ata12: end_device-9:3: dev error handler Jan 15 14:36:44 Scour kernel: sas: sas_form_port: phy2 belongs to port2 already(1)! Jan 15 14:36:47 Scour kernel: drivers/scsi/mvsas/mv_sas.c 1435:mvs_I_T_nexus_reset for device[2]:rc= 0 Jan 15 14:36:47 Scour kernel: ata11.00: configured for UDMA/100 Jan 15 14:36:47 Scour kernel: ata11: EH complete Jan 15 14:36:47 Scour kernel: sas: --- Exit sas_scsi_recover_host: busy: 0 failed: 1 tries: 1 Jan 15 15:10:38 Scour kernel: sas: Enter sas_scsi_recover_host busy: 1 failed: 1 Jan 15 15:10:38 Scour kernel: sas: trying to find task 0x00000000691cfafa Jan 15 15:10:38 Scour kernel: sas: sas_scsi_find_task: aborting task 0x00000000691cfafa Jan 15 15:10:38 Scour kernel: sas: sas_scsi_find_task: task 0x00000000691cfafa is aborted Jan 15 15:10:38 Scour kernel: sas: sas_eh_handle_sas_errors: task 0x00000000691cfafa is aborted Jan 15 15:10:38 Scour kernel: sas: ata11: end_device-9:2: cmd error handler Jan 15 15:10:38 Scour kernel: sas: ata9: end_device-9:0: dev error handler Jan 15 15:10:38 Scour kernel: sas: ata10: end_device-9:1: dev error handler Jan 15 15:10:38 Scour kernel: sas: ata11: end_device-9:2: dev error handler Jan 15 15:10:38 Scour kernel: ata11.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen Jan 15 15:10:38 Scour kernel: ata11.00: failed command: READ DMA EXT Jan 15 15:10:38 Scour kernel: ata11.00: cmd 25/00:00:60:95:db/00:04:b7:00:00/e0 tag 19 dma 524288 in Jan 15 15:10:38 Scour kernel: res 40/00:00:67:17:b6/00:00:7b:00:00/e0 Emask 0x4 (timeout) Jan 15 15:10:38 Scour kernel: ata11.00: status: { DRDY } Jan 15 15:10:38 Scour kernel: sas: ata12: end_device-9:3: dev error handler Jan 15 15:10:38 Scour kernel: ata11: hard resetting link Jan 15 15:10:39 Scour kernel: sas: sas_form_port: phy2 belongs to port2 already(1)! Jan 15 15:10:41 Scour kernel: drivers/scsi/mvsas/mv_sas.c 1435:mvs_I_T_nexus_reset for device[2]:rc= 0 Jan 15 15:10:41 Scour kernel: ata11.00: configured for UDMA/100 Jan 15 15:10:41 Scour kernel: ata11: EH complete Jan 15 15:10:41 Scour kernel: sas: --- Exit sas_scsi_recover_host: busy: 0 failed: 1 tries: 1 Jan 15 16:46:31 Scour emhttpd: req (13): startState=STARTED&file=&csrf_token=****************&cmdNoCheck=Cancel Jan 15 16:46:31 Scour kernel: mdcmd (48): nocheck Jan 15 16:46:41 Scour kernel: md: md_do_sync: got signal, exit... Jan 15 16:46:49 Scour kernel: md: recovery thread: completion status: -4 Jan 15 16:47:01 Scour sSMTP[18094]: Creating SSL connection to host Jan 15 16:47:01 Scour sSMTP[18094]: SSL connection using ECDHE-RSA-CHACHA20-POLY1305 Is there a way to determine which drives are ATA 9-12? I have a SAS2LP-MV8 installed, in addition to the Intel and ASMedia sata ports. I've tried to d/l the diagnostics, but it seems to have hung, and I can't access any shares anymore so I'll just power it down for now. Any help is appreciated.
  14. I think it's a Windows issue because Windows is reporting 2 different counts (network vs local). The krusader and windows local count agree. It's only the windows network count that differs. Either way, I agree something is very strange. Looking in the forums, it seems several people are having the same issue.
  15. Thanks for the suggestion. I just tried it, but no luck. Still getting identical results. I'm guessing this is a windows issue.