Talos

So the backplane uses 2x SATA and 2x PATA connectors to power the 9 drives.. so i'd need to connect both SATA and both PATA connectors from the PSU (as you say 2x peripheral ports on the PSU).. is that going to overload the 2 PSU ports? im also tossing up just keeping my existing ATX power supply and swapping out the existing 120mm tower cooler on the CPU for a front mounted 240 AIO.. but thats gonna be a lot of cable and tubing in there to try and cable manage nicely so i think i'd prefer to go the SFX route instead and keep the existing tower cooler.

Heya - im looking at changing my case over to a Jonsbo N6 and will be wanting to drop my powersupply down to SFX from ATX to maximise cooling capacity in the case. The system in the case will consist of Intel 2500k Asus Maximus Gene III 2x8gb G.Skill DDR3 IBM m1015 HBA 9x18tb Seagate Exos x18s 3xNoctua NF-A12 G2's 2xNoctua NF-A12x15 Slim fans I have an old Silverstone ST45SF-G 450w SFX psu laying around but just not sure if thats going to be enough to cover 9 exos's on spinup or if i need to look at a bigger PSU (SF750 or something like that) to avoid issues?

ok looks like it was the M.2 to SATA adaptor that went bad. replaced pretty much everything in the system except the motherboard and the crashing seemed to stop after removing that adaptor. Will look for a replacement one of those and hopefully will all be good from then. Have enough ports on the motherboard for the moment for all the drives in the array so only need the adaptor for when i look to fill the 3 empty bays in the N3 case.

memtest appears to be running ok.. 14 hours down and 14 passes with no error and no reboot... ill try pulling a stick of ram and letting the server run to see if it crashes again

thanks trying memtest now. ill report back in a few hours..

I built a server for a friend about a year ago and its started randomly rebooting out of nowhere recently. The server consists of the following: MW MW-NAS-N5105 motherboard 16gb ram 4x 16tb EXOS X16 drives in the array ASM1166 M.2 - SATA expansion card 128gb Crucial SATA SSD for running docker (only jellyfin) Jonsbo N3 case 500w SFX powersupply Ive had a look at the syslog and cant see any errors jumping out that would be causing reboots.. I've enabled the persistent logs but it doesn't appear to have saved anything prior to the last reboot? any ideas where to start looking would be greatly appreciated. cheers tower-diagnostics-20250808-1523.zip

Thanks for the help trurl - its just finished rebuilding onto the drive and all data appears to be ok. Passed with zero warnings or errors this time.

Awesome thanks mate... I powered down, checked all the cables etc (everything appeared to be solidly connected but we will see i guess), powered it backup and am now starting that rebuild process.. hopefully ill just report back tomorrow when its all done

hmmm ok maybe i bumped a cable when i had it open replacing the old drive.. although that should have shown during the rebuild of the old drive to the new one i would have thought?? Ill power down and check all the cables etc... so when i power it back up will it recognize the drive and automatically add it to the array or will i have to do a rebuild onto that same disabled drive?

hey trurl - diagnostics attached now.. forgot that one sorry theburrow-diagnostics-20250401-0841.zip

Last night being the first of the month my server started its monthly parity check. When i woke up this morning one of my drives (a seagate exos 16tb drive) was marked with a red X instead of the usual green ball and it looks like that parity check paused about an hour into the run. Ive checked the disk log info and its showing the following: Apr 1 01:08:02 THEBURROW kernel: sd 3:0:3:0: [sde] tag#2679 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s Apr 1 01:08:02 THEBURROW kernel: sd 3:0:3:0: [sde] tag#2679 Sense Key : 0x2 [current] Apr 1 01:08:02 THEBURROW kernel: sd 3:0:3:0: [sde] tag#2679 ASC=0x4 ASCQ=0x0 Apr 1 01:08:02 THEBURROW kernel: sd 3:0:3:0: [sde] tag#2679 CDB: opcode=0x8a 8a 00 00 00 00 00 6e 7f 7c 30 00 00 04 00 00 00 Apr 1 01:08:02 THEBURROW kernel: I/O error, dev sde, sector 1853848624 op 0x1:(WRITE) flags 0x0 phys_seg 128 prio class 2 I ran a smart report on the drive and it came back with zero errors (attached to post) Looking at the system log (also attached) and it appeared the parity check kicked off ok at midnight but then at 1:08am filled the log with read errors on the drive in question; Apr 1 01:08:02 THEBURROW kernel: mpt2sas_cm0: log_info(0x31110d00): originator(PL), code(0x11), sub_code(0x0d00) Apr 1 01:08:02 THEBURROW kernel: mpt2sas_cm0: log_info(0x31110d00): originator(PL), code(0x11), sub_code(0x0d00) Apr 1 01:08:02 THEBURROW kernel: mpt2sas_cm0: log_info(0x31110d00): originator(PL), code(0x11), sub_code(0x0d00) Apr 1 01:08:02 THEBURROW kernel: sd 3:0:3:0: [sde] tag#2653 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=3s Apr 1 01:08:02 THEBURROW kernel: sd 3:0:3:0: [sde] tag#2653 Sense Key : 0x2 [current] Apr 1 01:08:02 THEBURROW kernel: sd 3:0:3:0: [sde] tag#2653 ASC=0x4 ASCQ=0x0 Apr 1 01:08:02 THEBURROW kernel: sd 3:0:3:0: [sde] tag#2653 CDB: opcode=0x88 88 00 00 00 00 00 6e 7f 88 30 00 00 04 00 00 00 Apr 1 01:08:02 THEBURROW kernel: I/O error, dev sde, sector 1853851696 op 0x0:(READ) flags 0x0 phys_seg 128 prio class 2 Apr 1 01:08:02 THEBURROW kernel: md: disk1 read error, sector=1853851632 Apr 1 01:08:02 THEBURROW kernel: md: disk1 read error, sector=1853851640 Apr 1 01:08:02 THEBURROW kernel: md: disk1 read error, sector=1853851648 A couple of weeks ago I replaced an 8tb drive in the array with a 18tb drive and it successfully rebuilt the drive into the array so this exos drive has been working fine up till now as far as i can tell. Any advice on what to try? could it be a disk issue if the SMART is coming back clean? could it be something else i need to check? The drives are hooked up to an M1015 HBA via a fan out cable which has been working fine in the system for 12+ years. theburrow-smart-20250401-0733.zip theburrow-syslog-20250331-2050.zip

Yeah that was my concern. With two drives showing the seek errors and only being able to replace them one at a time and still keep the array parity protected I'm not sure the other drive would survive a parity rebuild... I was thinking i would have to do the break the array and restart parity and then copy the info from the removed drives as you said via unassigned devices. The data that is on those two erroring drives is just movies/tv shows which I've made a full listing of so worst case scenario i can just reacquire it if the drive dies completely in the middle of the process. So by doing a "New Config" it will not erase any of the existing disks in my array and allow me to rebuild a new parity based on the new drives Ive inserted plus those I'm keeping from the existing array?

Hello, Recently i had two drives in my array show up as failing SMART due to Seek Error Rate thresholds exceeded. They've since stopped showing this but i dont trust those drives now and I'd been planning on changing up my array anyway so I bought 4x16tb drives to replace those two and some others in my array. My current configuration is: Parity - 18TB Disk 1 - 8TB Disk 2 - 6TB - This is one of the dying drives Disk 3 - 6TB - This is the other dying drive Disk 4 - 3TB Disk 5 - 3TB Disk 6 - 3TB Disk 7 - 6TB Disk 8 - 8TB Disk 9 - 18TB Disk 10 - 6TB I want to remove the two drives that showed the SMART errors, and consolidate the 3tb drives and 6tb drives to single 16tb drives, shrinking my array configuration down to 8 drives from 11 and end up with the following configuration: Parity - 18TB Disk 1 - 16TB Disk 2 - 16TB Disk 3 - 16TB Disk 4 - 16TB Disk 5 - 8TB Disk 6 - 8TB Disk 7 - 18TB I'm hoping someone can suggest the best method to do this. I've only ever expanded my array by adding more or larger drives over the past 15 years, I've never actually shrunk the number of drives used in the array. My end goal is to end up with a smaller case and less power hungry setup to try and save on some electricity running costs as well as claim back some desk space. I've already pre-cleared the 4x16tb drives and they are all sweet. Any guidance would be greatly appreciated. Cheers,

Thanks for clarifying my options itimpl. I finished the array expansion overnight and all is working as expected. Cheers!

Hi, I currently have a 9 drive array. It consists of: Parity - 6Tb (X300 Toshiba) Disk 1 - 6Tb (X300 Toshiba) Disk 2 - 6Tb (X300 Toshiba) Disk 3 - 6Tb (X300 Toshiba) Disk 4 - 3tb (Hitachi 7200rpm) Disk 5 - 3tb (Hitachi 7200rpm) Disk 6 - 3tb (Hitachi 7200rpm) Disk 7 - 3tb (Hitachi 7200rpm) Disk 8 - 3tb (Hitachi 7200rpm) Ive just moved my system into a new case (a Meshify 2) which gives me capacity for 11 drives. I've bought 2 new 8tb Ironwolfs and plan to expand my array by 2 drives. Ive already pre-cleared both the new ironwolf drives and both came back clean. The new array configuration i want is: Parity - 8Tb (New Ironwolf) Disk 1 - 6Tb (Same position) Disk 2 - 6Tb (Same position) Disk 3 - 6Tb (Same position) Disk 4 - 3tb (Same position) Disk 5 - 3tb (Same position) Disk 6 - 3tb (Same position) Disk 7 - 3tb (Same Position) Disk 8 - 3tb (Same Position) Disk 9 - 8tb (New IronWolf) Disk 10 - 6tb (Old Parity) Ive had a search on the forum and seen the posts about the Parity Swap Method and other people saying just replace the parity drive but i'm confused and don't want to risk blanking my array and losing all my data. Previously when i've upgraded my drives i've built a whole new server and copied the data from the old server to new one but i dont have the luxury of doing that this time. So what is the best method for me to 1) upgrade my Parity to support the larger drives in the array and 2) repurpose the old parity into the array and add in the 2nd ironwolf? Any help would be greatly appreciated. Cheers! Edit: Forgot to mention i'm running Unraid Pro 6.8.3 currently.