pendo

Will shut down and check cables when I get back to the server in the next couple hours.

Disk 6 and parity are newer (to me) disks in the array. They're SAS drives connected to the built via the built-in lsi card on my mobo. However, my case doesn't have slots for them, and they are mounted in urethane disk spacers in the bottom of the case, but otherwise not mounted rigidly. The tower got moved recently and all of a sudden started getting errors on disk 6 and it went offline. (Red X, emulated). I reseated the cables and did a SMART check and thought it was fine. However, I don't think I followed the correct procedure in getting it back into the array, as it started a complete rebuild. It was after this that I started seeing the errors for disk 2 and disk 5 dropped off. I was under the impression that the rebuild finished alright, though. Definitely need to get more storage, I know. I can add more SAS drives but don't have the physical space in this case, but mobo does NOT have 8088 connection on back. Only have the 8087 mini SAS internal connections. Ideally, it's time for complete upgrade (case, p/s, mobo, cpu, etc) but that's not in budget at this time. Here's my dashboard now

Disk 7 is only a 1 TB disk, and I'm unsure why it is empty, as it's been in the array for a while iirc. Disk 5 is the disk that is emulated as it's offline. The diagnostics is the standard one from the tools menu. Do I need to do something specific in order for it to be included in diagnostics? Disk 2 is the one that says it will fail in less than 24 hours. Seek error problems

Hello, I am seeking advice on how to proceed. I've got one disk with the red x, and another that is reporting failing in less than 24 hours. I've attached diagnostics. Do I shut down completely until new disks arrive? tower-diagnostics-20240323-0926.zip

Thank you. This was what I arrived at, too. I've contacted the seller, who has sold thousands of these drives. I'm sure it will get sorted in the end. Sorry for not posting diagnoatics. I thought extracted the relavent info from the syslog, but I still should have attached them. Unfortunately, I'm not where I can post diagnostics at the moment, but I will be in a few hours. If there's any other tests I should do when I get to the machine, let me know. Thanks again!

Hello all, I think I got a bad drive on my recent eBay purchase, but as this is my first ever use of an SAS drive, I wanted to double check here for anything I might have missed. I acquired an ASRock board with a built in lsi 2308 controller. I had read that I did not need to flash to IT mode on this board, but I did end up doing that as part of my troubleshooting. Now at 20.0.4.0 IT. Here's what I'm seeing in syslog: Sep 8 11:36:35 tower kernel: mpt2sas_cm0: hba_port entry: 00000000b5bc9d14, port: 255 is added to hba_port list Sep 8 11:36:35 tower kernel: mpt2sas_cm0: host_add: handle(0x0001), sas_addr(0x500138f000007ca0), phys(8) Sep 8 11:36:35 tower kernel: mpt2sas_cm0: handle(0x9) sas_address(0x5000cca26aa0cc69) port_type(0x1) Sep 8 11:36:35 tower kernel: mpt2sas_cm0: port enable: SUCCESS Sep 8 11:36:35 tower kernel: scsi 1:0:0:0: Direct-Access HGST HUH721010AL42C0 A38K PQ: 0 ANSI: 6 Sep 8 11:36:35 tower kernel: scsi 1:0:0:0: SSP: handle(0x0009), sas_addr(0x5000cca26aa0cc69), phy(4), device_name(0x5000cca26aa0cc6b) Sep 8 11:36:35 tower kernel: scsi 1:0:0:0: enclosure logical id (0x500138f000007ca0), slot(4) Sep 8 11:36:35 tower kernel: scsi 1:0:0:0: qdepth(254), tagged(1), scsi_level(7), cmd_que(1) Sep 8 11:36:35 tower kernel: scsi 1:0:0:0: Power-on or device reset occurred Sep 8 11:36:35 tower kernel: sd 1:0:0:0: Attached scsi generic sg6 type 0 Sep 8 11:36:35 tower kernel: end_device-1:0: add: handle(0x0009), sas_addr(0x5000cca26aa0cc69) Sep 8 11:36:35 tower kernel: sd 1:0:0:0: [sdg] Unit Not Ready Sep 8 11:36:35 tower kernel: sd 1:0:0:0: [sdg] Sense Key : 0x4 [current] Sep 8 11:36:35 tower kernel: sd 1:0:0:0: [sdg] ASC=0x3e ASCQ=0x3 Sep 8 11:36:35 tower kernel: sd 1:0:0:0: [sdg] 2441609216 4096-byte logical blocks: (10.0 TB/9.10 TiB) Sep 8 11:36:35 tower kernel: sd 1:0:0:0: [sdg] Write Protect is off Sep 8 11:36:35 tower kernel: sd 1:0:0:0: [sdg] Mode Sense: f7 00 10 08 Sep 8 11:36:35 tower kernel: sd 1:0:0:0: [sdg] Write cache: enabled, read cache: enabled, supports DPO and FUA Sep 8 11:36:35 tower kernel: sd 1:0:0:0: attempting task abort!scmd(0x00000000b7a35679), outstanding for 30022 ms & timeout 30000 ms Sep 8 11:36:35 tower kernel: sd 1:0:0:0: tag#2370 CDB: opcode=0xa3, sa=0xc a3 0c 01 12 00 00 00 00 02 00 00 00 Sep 8 11:36:35 tower kernel: scsi target1:0:0: handle(0x0009), sas_address(0x5000cca26aa0cc69), phy(4) Sep 8 11:36:35 tower kernel: scsi target1:0:0: enclosure logical id(0x500138f000007ca0), slot(4) Sep 8 11:36:35 tower kernel: sd 1:0:0:0: task abort: SUCCESS scmd(0x00000000b7a35679) Sep 8 11:36:35 tower kernel: sd 1:0:0:0: [sdg] Unit Not Ready Sep 8 11:36:35 tower kernel: sd 1:0:0:0: [sdg] Sense Key : 0x4 [current] Sep 8 11:36:35 tower kernel: sd 1:0:0:0: [sdg] ASC=0x3e ASCQ=0x3 Sep 8 11:36:35 tower kernel: sd 1:0:0:0: [sdg] Read Capacity(16) failed: Result: hostbyte=0x00 driverbyte=DRIVER_OK Sep 8 11:36:35 tower kernel: sd 1:0:0:0: [sdg] Sense Key : 0x4 [current] Sep 8 11:36:35 tower kernel: sd 1:0:0:0: [sdg] ASC=0x3e ASCQ=0x3 Sep 8 11:36:35 tower kernel: sd 1:0:0:0: [sdg] Read Capacity(10) failed: Result: hostbyte=0x00 driverbyte=DRIVER_OK Sep 8 11:36:35 tower kernel: sd 1:0:0:0: [sdg] Sense Key : 0x4 [current] Sep 8 11:36:35 tower kernel: sd 1:0:0:0: [sdg] ASC=0x3e ASCQ=0x3 Sep 8 11:36:35 tower kernel: sd 1:0:0:0: [sdg] 0 4096-byte logical blocks: (0 B/0 B) Sep 8 11:36:35 tower kernel: sdg: detected capacity change from 19532873728 to 0 Sep 8 11:36:35 tower kernel: sd 1:0:0:0: [sdg] Unit Not Ready Sep 8 11:36:35 tower kernel: sd 1:0:0:0: [sdg] Sense Key : 0x4 [current] Sep 8 11:36:35 tower kernel: sd 1:0:0:0: [sdg] ASC=0x3e ASCQ=0x3 Sep 8 11:36:35 tower kernel: sd 1:0:0:0: [sdg] Read Capacity(16) failed: Result: hostbyte=0x00 driverbyte=DRIVER_OK Sep 8 11:36:35 tower kernel: sd 1:0:0:0: [sdg] Sense Key : 0x4 [current] Sep 8 11:36:35 tower kernel: sd 1:0:0:0: [sdg] ASC=0x3e ASCQ=0x3 Sep 8 11:36:35 tower kernel: sd 1:0:0:0: [sdg] Read Capacity(10) failed: Result: hostbyte=0x00 driverbyte=DRIVER_OK Sep 8 11:36:35 tower kernel: sd 1:0:0:0: [sdg] Sense Key : 0x4 [current] Sep 8 11:36:35 tower kernel: sd 1:0:0:0: [sdg] ASC=0x3e ASCQ=0x3 Sep 8 11:36:35 tower kernel: sd 1:0:0:0: [sdg] Attached SCSI disk Manual attempts to format fail: sg_format --format -v /dev/sg6 HGST HUH721010AL42C0 A38K peripheral_type: disk [0x0] PROTECT=1 << supports protection information>> Unit serial number: 2TJVEELD LU name: 5000cca26aa0cc68 mode sense(10) cdb: [5a 00 01 00 00 00 00 00 fc 00] Mode Sense (block descriptor) data, prior to changes: Number of blocks=2441609216 [0x91880000] Block size=4096 [0x1000] A FORMAT UNIT will commence in 15 seconds ALL data on /dev/sg6 will be DESTROYED Press control-C to abort A FORMAT UNIT will commence in 10 seconds ALL data on /dev/sg6 will be DESTROYED Press control-C to abort A FORMAT UNIT will commence in 5 seconds ALL data on /dev/sg6 will be DESTROYED Press control-C to abort Format unit cdb: [04 18 00 00 00 00] Format unit: transport: Host_status=0x03 [DID_TIME_OUT] Format unit command: Transport error, driver or interconnect error FORMAT UNIT failed I was originally using a mini-SAS to SAS cable that had SATA power pigtails. After learning about the power-disable 'feature' the hard way, I received the above errors. In the process of elimination, I ordered a new mini-SAS to SAS cable that had molex power connections, but I still have the same result. I believe I have a bad drive, but, being as green as I am I wanted to double check with someone. Thanks!

Okay, so I found the P16 firmware and instructions for my board. But...when it gets here, I'm going to try it first, as is, and check the system logs to see how/if a drive connected through the mini-sas connection is recognized. If it is detected, and recognized, then I think ill leave the LSI alone. Thanks, guys, for the help!

Yes, this is what I thought I was going to need to do, but while struggling to find the LSI firmware for the ASRock board, I found nother post saying that they didn't have to do that with this board. It's an old ASRock extended mini-itx lga 1150 board. I am going to need to modify the drive cage in my case a tad, I think (move it to the other side) base on another post I read. I did find a link to the ASRock LSI firmware on a freenas forum, but the link was bad. So far, I haven't gotten a reply from ASRock support. So, at this point, I'm kinda just hoping it will work, as it did for the other unraider. Four of my drives will be connected to the same type of sata controller as before. But two will need to go on one of the mini-sas ports. What if I boot up the "new" machine with just a single array drive on the mini-sas to see if unRAID recognizes the serial number? If it does, all good? I still feel like it would be best to get it to IT mode, though... This little server is gettting on in age, now, at just over 7.5 years old. But, it has been working wonderfully for me, and don't really feel the need to upgrade, other than I just need more room. Moving to this board provides a very economical way to do just that. After all said and done, total array storage is moving from 16TB to 40TB (1TB single cache).

Thank you. I'm hoping it will be fairly simple. I'm most concerned about the long parity rebuild, but a recent health check shows all drive are in good shape, albeit *very* full. One 4TB drive is showing only a little over 2GB free 😖

Sorry for necro, but this seems like the right place to ask... I'm swapping out motherboards and the new board has 2 mini-sas ports that some of my drives will be connecting through. In addition to bringing over all of the old drives, I will be adding a couple of larger drives, one of which will be the new parity drive. All drives are sata, except there might be 1 new sas drive, as well. Current plan is to replace the parity drive and let it build out. (After preclearing, obviously) Take picture of drive assignments in GUI. Assuming that goes well, then swap out boards, but connecting the array drives is where I'm concerned. The board has 4 sata ports and an integrated LSI 2308 with 2 mini-sas connectors. There's 6 total sata drives (including parity) and 1 sas drive. I was planning on using a mini-sas to sata breakout cable for 2 sata drives, and a mini-sas to sas to the single sas drive. Not sure what problems I'll run into with assigning drives in the array.

Is there a way to for Ombi to reprocess existing requests? An issue that has now come up twice for me has been that my Couch Potato database became corrupt and had to be deleted. I was thinking it would be super handy if there was a way to reprocess existing requests as a way to quickly rebuild your Couch Potato database.

+1 I get the same thing.