March 15, 20251 yr Didn't have much luck trying with the old google search so here i am. I started a mission to move over to a supermicro 45 JBOD i wasn't using for anything. Then i though while I'm at it i could update some hardware (mobo and cpu) too while I'm at it. Everything moved over fine for the hardware. Unraid USB was locked in write protect mode. Ok get a new drive made from the back up and off we go. Start up the array and one of my drives seems to have failed. Damn, so i got a new drive and attempt to rebuild the array. Gets about 20 to 30 gigs into rebuild and errors out. drive checked out fine when in a different machine. swapped to a different bay in the JBOD and unassigned, power cycle, and try again and got same thing. Tried to pull the cable and HBA from other working system still has the same happen. So I'm not sure if its the JBOD here or something from the move. tower-diagnostics-20250315-0630.zip
March 15, 20251 yr Community Expert You rebooted before getting diagnostics, can't see what happened before boot. Is it the same drive each time?
March 15, 20251 yr Community Expert Just now, trurl said: Is it the same drive each time? You have a lot of drives, so if you could help us narrow it down by specifying which is the problem. I do see a couple of unassigned disks that might have been assigned disks until they disconnected. So many drives also makes me suspect power.
March 15, 20251 yr Author The parity two i was trying to start to upgrade my parity to my newer larger drives i picked up to put in, but now im dealing with the loss of disk 28 on the array. Even pre clear fails. Ill try to mount again and pull a new log.
March 15, 20251 yr Community Expert 3 minutes ago, kylenut2 said: LYVK That one is unassigned sde in the diagnostics. 1 minute ago, kylenut2 said: The parity two i was trying to start to upgrade my parity to my newer larger drives i picked up to put in Unclear. Did you have 2 parity drives?
March 15, 20251 yr Community Expert unassigned sdag 26TB FJMY would be large enough for parity or parity2
March 15, 20251 yr Community Expert Just now, kylenut2 said: no just one drive for parity before. Wow! You really should reconsider that with so many disks.
March 15, 20251 yr Author yep that's the goal after i fix my disk 28 problem. I have new drives for this. one fire at time....
March 15, 20251 yr Community Expert 5 minutes ago, trurl said: 10 minutes ago, kylenut2 said: LYVK That one is unassigned sde SMART for that disk looks OK and it isn't very old. It has never had an extended SMART self-test though.
March 15, 20251 yr Author rebuild is trying to work. Should fail soon. then ill download new diagnostics file.
March 15, 20251 yr Community Expert Lots of this ... Mar 15 05:25:39 Tower kernel: sd 5:0:3:0: Power-on or device reset occurred Mar 15 05:25:39 Tower kernel: mpt2sas_cm0: log_info(0x31120303): originator(PL), code(0x12), sub_code(0x0303) ### [PREVIOUS LINE REPEATED 3 TIMES] ### before this Mar 15 05:25:39 Tower kernel: sd 5:0:3:0: [sde] tag#88 UNKNOWN(0x2003) Result: hostbyte=0x0b driverbyte=DRIVER_OK cmd_age=6s Mar 15 05:25:39 Tower kernel: sd 5:0:3:0: [sde] tag#88 CDB: opcode=0x8a 8a 00 00 00 00 00 00 04 b9 58 00 00 04 00 00 00 Mar 15 05:25:39 Tower kernel: I/O error, dev sde, sector 309592 op 0x1:(WRITE) flags 0x0 phys_seg 128 prio class 2 Mar 15 05:25:39 Tower kernel: md: disk28 write error, sector=309528 Mar 15 05:25:39 Tower kernel: md: disk28 write error, sector=309536 Mar 15 05:25:39 Tower kernel: md: disk28 write error, sector=309544 Mar 15 05:25:39 Tower kernel: md: disk28 write error, sector=309552 Mar 15 05:25:39 Tower kernel: md: disk28 write error, sector=309560 ... and so on How is this drive powered? Do you have a backplane?
March 15, 20251 yr Community Expert Mar 15 05:24:23 Tower kernel: sd 5:0:3:0: Power-on or device reset occurred Mar 15 05:24:24 Tower kernel: mpt2sas_cm0: log_info(0x31120303): originator(PL), code(0x12), sub_code(0x0303) ### [PREVIOUS LINE REPEATED 3 TIMES] ### Mar 15 05:24:24 Tower kernel: sd 5:0:3:0: Power-on or device reset occurred These usually mean a power/connection issue, or weak PSU.
March 15, 20251 yr Author yeah its on a back plane. i moved the drive to other empty spots and it was still doing the same. Tried moving one of the other working drives to the spot i had that drive in and the working drive showed up and ran like normal.
March 15, 20251 yr Community Expert 45 minutes ago, kylenut2 said: Tried moving one of the other working drives to the spot i had that drive in and the working drive showed up and ran like normal. But did it work with all the other disks spunup? Rebuild requires access of all disks simultaneously.
March 15, 20251 yr Author all other disk have been working fine and spin up fine. data on the parity is emulated so array is working. just anything new i put into any spot is not working.
March 15, 20251 yr Author Solution yep, ended up going back to the old 36 bay and its rebuilding fine now. Guessing its my expander on the backplane
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.