sniggil

OK, thank you, I can remove memory to look for additional possible root causes, however as a point of information, I had cable issues (SATA power) that I believe was responsible for the underlying issue. A power adapter (4-pin molex to SATA power) was used because I could not order extra type 5 SATA power cables from Corsair. They are still out of stock many months later, but Corsair agreed to send me (2) type 5 SATA power connectors under warranty. The responsible cables (not suspect, but confirmed as I heard a drive's power drop while the case was open) have been replaced. I briefly mentioned this in the "Background" section, but didn't excessively elaborate on the issue as your time is very valuable and appreciated. My apologies if the lack of detail caused you to waste time. Again, I do not mind looking for additional possible causes to rule out likely suspects, but I also don't want to chase ghosts. Let me know, while I work on the backups and FS recreation for a bit.

My apologies. All aborted. results attached

Memtest passed. btrfs check output attached. Thank you.

OK. Will do.

Background: I had cable issues that have been resolved. Thinking I was in the clear, I ran a docker app, until I found the cache filled and mover did not move files as expected. Digging into the issue, I found a disk that I could not even 'manually move' (via unraid GUI) the files to. Issue: Digging further I ran Check File System and found 3 disks with errors. I was considering the --repair option, but after reading the help section, which advises not to do so unless advised to do so, I stopped and came to the forums. Therefore, I'm requesting help. Request: Should I rerun the Check File System with the --repair option or is there another path forward I should take? Attached is a recent diagnosis.

I’ll double check the physical connections. Any suggestions to correct this ?

I’ve rebuilt the server. Got rid of the JBOD box in case there are backplane issues and moved everything internal in a new case and a new controller. Currently I’m getting high CPU usage with BTRFS: errors and warnings along with device resets. Is there a chance someone could take a look and see if I’m missing something obvious. marlin-diagnostics-20240219-2032.zip

My apologies I've replaced all the cables and still had the UDMA CRC errors increasing. Might need to consider replacing the JBOD case cables / backplanes next. I have reseated them. disk7 and disk11 are disabled and emulated disk11 has already been zero'd I believe if it is only in reconstruct write aka turbo wrote mode ? maybe so, but unraid disabled it... read errors Not sure which way to go at this point. I thought removing disk11 and rebuilding 7 was the way to go.

Good morning, I had 2 drives with smart errors and a 3rd with read errors (disk2, disk8 and disk11). I decided to replace two and remove one. I didn't want to lose parity in the event more failed, so I thought shrinking the array may be best. I ordered new drives, pre-clear them, and began the #2 procedure (from the legacy documentation) to shrink the array. Two drives ended up failing, the one being zero'ed (disk 11) and another (disk7). Now I'm faced with decision to continue the shrinking procedure to remove disk 11, while disk7 is emulated OR allow a rebuild although disk2 and disk8 still have smart errors (btw, I've checked/replaced cables, but still have those smart errors). I am looking for advice on a couple fronts. 1) Does the fact that disk 11 failed during zero'ing and continued zero'ing as an emulated drive cause problems continuing with the shrinking procedure and 2) Can I use the new config tool, remove disk 11 and leave emulated disk7 or will the new config tool (keeping assignments for parity and disk7, but not disk11 AND checking the valid parity option) wipe out disk7's emulation? I hope these question make sense as presented. Thank you for your time ! marlin-diagnostics-20240112-1037.zip

Was having crc errors on cache1. Decided to shutdown system, replace the data cable and restart. Upon restart, parity check started informing me the shutdown was not clean. I noticed the cache was unmountable and restarted again, then started the array in maintenance mode. Please advise and provide this noob with guidance. Mike marlin-diagnostics-20220218-1544.zip

I have tried that and yes, the 9207-8e has recognized the corresponding drives. The system boots much slower, CPU usage is relatively high and the system is overall sluggish, such as when I assigned those drives and started the array. Attached is an updated diagnostics file which seems to indicate some problems. It may be related to the old firmware as Squid has pointed out. I will look to get that updated asap. If I can get this worked out and get a different card with 4 ports, the DL1600 may become a viable solution even if the QNAP card is not viable. pinfish-diagnostics-20211218-0537.zip

Thank you. It's strange that I can not find it in the BIOS. I'll get the LSI BIOS updated as soon as I can get my hands on a windows box. Dropping the QNAP card and using the LSI card as suggested by Vy2lo is making the system sluggish. I'll update the diagnostics file and respond to Vr2lo.

I've placed it in PCIEX16 and checked the MB BIOS and the card does not show up, nor are any PCI slots selectable in the BIOS. They are greyed out. At this point I would not know how to enter the bios of the LSI card. Attached are the diagnostics. pinfish-diagnostics-20211217-2212.zip

I plan to move an existing unraid from a Chenbro box and bought (abbreviated list): GIGABYTE Z590 VISION D LGA 1200 Intel Z590 ATX Motherboard LSI SAS 9207-8e in IT mode and a JBOD box and also a QNAP TL-D1600S JBOD box along with its PCIe SATA Interface Card (QXP-1600eS) I adjusted the BIOS and have a trial version of unraid working without issue. It's a huge upgrade from the dual Xeon L5640. Unfortunately, I can not see either SATA card, only the MB provided ports. After reviewing the forums for a few days and tinkering with the BIOS, I haven't been able to 'see' the cards. Any advise or suggestions would be great.

Thank you again. Followed your guidance. Everything works. No issues. New Flash BackUp made.

Thank you.

I changed devices, but if I correct the config/pools/cache.cfg file would that be enough ?

Good afternoon. Long time listener, first time caller... I'm using Unraid 6.9.2. My flash drive crashed. My flash backup of 3-AUG was prior to replacing 2 of 4 cache drives in a Btrfs pool. I should have, but didn't make another backup after the drive replacement. The first two slots did not change, only the second two. Since I replaced the last two with identical drives as the first two, I think I should: 1) Use flash creator to prep a new flash drive 2) modify the cache config file (config/pools/cache.cfg) to reflect the changed the serial numbers to match the new drives, 3) install the flash drive and boot the server Is this the best approach? If I have the slot position of the last 2 cache drives backwards... for example diskId.2="Samsung_SSD_860_EVO_1TB_serialnumberxx1" diskId.3="Samsung_SSD_860_EVO_1TB_serialnumberxx2" vs diskId.2="Samsung_SSD_860_EVO_1TB_serialnumberxx2" diskId.3="Samsung_SSD_860_EVO_1TB_serialnumberxx1" will it be a problem ?