Kboogie

Members
  • Posts

    14
  • Joined

  • Last visited

Kboogie's Achievements

Noob

Noob (1/14)

0

Reputation

  1. Thanks so much for the help. Could I drop the drive on the SAS controller from the pool and then reintroduce it without reformatting?
  2. That could be it. One of the cache drives is on the SAS controller, so it was acting weird too. Here are the results. [/dev/nvme0n1p1].write_io_errs 0 [/dev/nvme0n1p1].read_io_errs 0 [/dev/nvme0n1p1].flush_io_errs 0 [/dev/nvme0n1p1].corruption_errs 0 [/dev/nvme0n1p1].generation_errs 0 [/dev/sdi1].write_io_errs 8027649 [/dev/sdi1].read_io_errs 215782 [/dev/sdi1].flush_io_errs 266 [/dev/sdi1].corruption_errs 185739 [/dev/sdi1].generation_errs 0 Running a scrub now, although it does not seem to be progressing. Wonder if that is related to ongoing parity rebuild. UUID: 3e318b48-677a-4a28-8e79-9fefe817451e Scrub started: Fri Mar 31 07:12:03 2023 Status: running Duration: 0:02:35 Time left: 0:00:00 ETA: Fri Mar 31 07:14:38 2023 Total to scrub: 257.94GiB Bytes scrubbed: 0.00B (0.00%) Rate: 0.00B/s Error summary: no errors found
  3. It looks like you are right. I took the controller card out of the machine, reseated it and restarted parity build. We're 9 hours in and it seems to be operating as expected. The problems did start after reconnecting cables, it may have jarred the PCI connection? However, I am still having Docker issues. Dockers are not running and the Docker page will not load. One strange thing that I noticed is that the docker.img file exists on both the cache drive and disk 3 with different modification dates. It's a single file, is this correct? Disk 3 (2023-03-29 22:42) cache (2023-03-30 21:44) Edit: VMs also seem to be broken and will not start. unraid-diagnostics-20230331-0636.zip
  4. Thanks Jorge. It's been so happy for so long though!! Here's the log file after the parity build failed, in case anything stands out. Is there any way to validate that it's the card? Thanks for the help. unraid-diagnostics-20230330-2037.zip
  5. My parity drive failed. I thought it was a disk problem, replaced the disk and started rebuild. Rebuild failed in 5 min. Took all the drives out of the enclosure, reordered them. Reset all cables. Started cache rebuild and it failed again in 5 min. I am seeing additional strange behavior: * Array takes a long time to start * Array will not stop, "retry unmounting disk share(s)" * Docker takes a long time to load applications I recently swapped an SSD cache for an HDD cache drive, but there were no system related files on this cache. I also recently added a new SSD to the system cache pool and converted to raid 1 mode. This is all I can see. Nothing stands out in Fix Common Problems. Googled a bunch of stuff, couldn't find anything similar. Any thought? unraid-diagnostics-20230329-2015.zip
  6. Thanks Jorge, After shuffling the drives it does seem to be happier with parity as CMR. In particular, it's better when it comes to disk to disk transfers across members of the SAS controller. I get a sustained 40-46MB/s and it seems stable. However, the USB SATA SSD is still very inconsistent. Any thoughts on this? Is using USB as cache not a best practice?
  7. Thanks Jorge, appreciate the help. Do you think I need to replace all SMR or just the parity? I would say the performance has always been volatile, but it's never been this bad where things go down to near zero and hang.
  8. Having some drive transfer performance issues and at a loss as to how to resolve. Some details on the configuration and observations below, diagnostics attached. Curious to hear what people think. Hardware Lenovo PC, i5-8400T, 8gb ram, 256gb SSD System Cache RocketRAID 2722 SAS card (marvel), sans digital external SAS enclosure, 8 mixed drives, 2 parity Observations Network transfers start at 60mb, reduce to 40mb and then become erratic, reducing to <1mb. Confirmed same behavior with transfers using unraid UI to move data between disks Confirmed same behavior with parity check, starting at 180mb sustained and then after 10 min plummeting down to <1mb When rates drop there is a spike in CPU from resting 10% to 50%. Included some screen shots of what I see bouncing in the top CPU chart during the event. Please help! unraid-diagnostics-20230206-1619.zip
  9. It seems the issue was exacerbated by moving one of the cache drives from the SAS array to USB. I do think there is a separate persistent issue with transfer rates and volatility, but I should post separately. Can I delete this post?
  10. Having some drive performance issues and at a loss as to how to resolve. Some details on the configuration and observations below, diagnostics attached. Curious to hear what people think. I've noticed some of this behavior before, but it's gotten progressively worse and systemic as of recently. Hardware Lenovo PC, i5-8400T, 8gb ram RocketRAID 2722 SAS card (marvel), sans digital external SAS enclosure, mixed drives Observations Network transfers start at 60mb, reduce to 40mb and then become erratic, reducing to <1mb. Confirmed same behavior with transfers using unraid UI to move data between disks Confirmed same behavior with parity check, starting at 180mb sustained and then after 10 min plummeting down to <1mb When rates drop there is a spike in CPU from resting 10% to 50%. Included some screen shots of what I see bouncing in the top CPU chart during the event. Please help! unraid-diagnostics-20230203-1633.zip
  11. Thanks Jorge. When I first booted the system I see a warning. Once I remove and replace in the same position it is recognized. Any thoughts on if this warning is related? Sep 1 07:11:35 unraid kernel: ACPI: Early table checksum verification disabled Sep 1 07:11:35 unraid kernel: floppy0: no floppy controllers found Sep 1 07:11:35 unraid kernel: i915 0000:00:02.0: [drm] failed to retrieve link info, disabling eDP Sep 1 07:11:35 unraid kernel: sas: Enter sas_scsi_recover_host busy: 0 failed: 0 Sep 1 07:11:35 unraid kernel: sas: --- Exit sas_scsi_recover_host: busy: 0 failed: 0 tries: 1 Sep 1 07:11:35 unraid kernel: sas: Enter sas_scsi_recover_host busy: 0 failed: 0 Sep 1 07:11:35 unraid kernel: sas: --- Exit sas_scsi_recover_host: busy: 0 failed: 0 tries: 1 Sep 1 07:11:35 unraid kernel: sas: Enter sas_scsi_recover_host busy: 0 failed: 0 Sep 1 07:11:35 unraid kernel: sas: --- Exit sas_scsi_recover_host: busy: 0 failed: 0 tries: 1 Sep 1 07:11:35 unraid kernel: sas: Enter sas_scsi_recover_host busy: 0 failed: 0 Sep 1 07:11:35 unraid kernel: ata10.00: failed to IDENTIFY (I/O error, err_mask=0x4) Sep 1 07:11:35 unraid kernel: ata10.00: failed to IDENTIFY (INIT_DEV_PARAMS failed, err_mask=0x80) Sep 1 07:11:35 unraid kernel: ata10.00: failed to IDENTIFY (I/O error, err_mask=0x4) Sep 1 07:11:35 unraid kernel: sas: --- Exit sas_scsi_recover_host: busy: 0 failed: 0 tries: 1 Sep 1 07:11:35 unraid kernel: sas: Enter sas_scsi_recover_host busy: 0 failed: 0 Sep 1 07:11:35 unraid kernel: sas: --- Exit sas_scsi_recover_host: busy: 0 failed: 0 tries: 1 Sep 1 07:11:35 unraid kernel: sas: Enter sas_scsi_recover_host busy: 0 failed: 0 Sep 1 07:11:35 unraid kernel: sas: --- Exit sas_scsi_recover_host: busy: 0 failed: 0 tries: 1 Sep 1 07:11:35 unraid kernel: sas: Enter sas_scsi_recover_host busy: 0 failed: 0 Sep 1 07:11:35 unraid kernel: sas: --- Exit sas_scsi_recover_host: busy: 0 failed: 0 tries: 1 Sep 1 07:11:35 unraid kernel: sas: Enter sas_scsi_recover_host busy: 0 failed: 0 Sep 1 07:11:35 unraid kernel: sas: --- Exit sas_scsi_recover_host: busy: 0 failed: 0 tries: 1 Sep 1 07:11:35 unraid mcelog: failed to prefill DIMM database from DMI data
  12. Hi All, Was very excited to move into the SAS solution world, but wondering if I'm having some controller issues. Behavior: Upon reboot, not finding all disks, dropping parity disk. Requiring multiple reboots, or physical removal and reinsertion, to recognize the drives. Seems to happen most with Seagate drives that are mixed in with some WD. Hardware: Lenovo M720Q RocketRAID 2722 (Marvell 88SE9485) Bios VT-d disabled External Sans Digital 8 bay Diagnostics attached. I hope it's not the card, because it's a short length and half height card that fits in my micro chasis and I haven't seen any LSI variants that fit that bill. Many thanks. unraid-diagnostics-20220901-0824.zip
  13. Is that right? Oh no, looks like I got some bad advice. Is there anything that I can do to try to resolve the current speed issues? Previously I had no problems doing 60mb sustained.
  14. Lot's of similar issues out there, I've been reading a lot of conversations on this and have not been able to pinpoint the issue. It was performing much better before, there's been some kind of change recently that has lead to a performance drop off. When writing to the disk array, transfer starts at 100mb and then drops down to 2mb, then up to 10mb, and down to 100k. It's somewhat erratic once it makes the drop. If I enable cache, it holds at 100mb without issue. This confirms that we're not dealing with a network issue. I've enabled reconstruct-write with no apparent improvement. Any suggestions in terms of what could be happening? Hardware setup: Thinkpad w/ i7, 8gb ram, USB 2 (I know, upgrading to USB 3 shortly...) Mediasonic USB array with 4 x 8tb drives (one parity) 128GB SATA SSD Cache unraid-diagnostics-20220313-1421.zip