Up until today, I had my server limpng along (previous udma crc errors). I removed my SATA expansion card SY-PEX40167JMicron chipsets (JMB582/JMB575) thinking it was failing. I replaced it with a Supermicro AOC-S3008L-L8E (LSI 9300-8i clone). Once I was able to get the card to work through BIOS settings, I rebooted the server with errors.

I was going to try and go into maintenance mode and do the xfs repair however there is no option to go into maintenance mode.

Is there another way I can get Disk 6 back running so I can then deal with Disk 5?

My plan is to use unbalance to move all data from disk 5 to disk 7 and pull it out of the array and zero it out.

Any help is greatly appreciated.

tower-diagnostics-20260729-2024.zip

2 hours ago, Erik M said:

there is no option to go into maintenance mode.

In MAIN - Array Operation

Stop the array. Check the box for Maintenance mode. Start the array.

2 hours ago, Erik M said:

My plan is to use unbalance to move all data from disk 5 to disk 7 and pull it out of the array and zero it out.

Better plan, check filesystem on emulated disk5 and on disk6, then rebuild disk5.

Your plan won't work as stated, some details missing. For one thing, you can't move any data from the unmountable emulated disk5, it won't mount without repairing the filesystem. Whatever you do, you can't remove it from the array without New Config/Rebuild Parity. And why do you think you want to zero it outside the array? Zeroing it while still in the array might make sense so you can remove it with New Config without rebuilding parity.

In any case, doesn't look like there is anything wrong with either disk, just connection problems. In fact, disk6 has disconnected and is now an Unassigned Device.

Except, there is this with disk6

Jul 29 19:59:41 Tower kernel: unraidd1: attempt to access beyond end of device
Jul 29 19:59:41 Tower kernel: sdj: rw=0, sector=3910720624, nr_sectors = 8 limit=0
Jul 29 19:59:41 Tower kernel: md: disk6 read error, sector=3910720560

Not sure how to proceed with that. The disk that was assigned as Disk6 is now Unassigned Device sdl instead of sdj.

What do you get from command line with this?

fdisk -l /dev/sdl

Might also be useful to see if physical disk5 will mount as an Unassigned Device, but we can decide on that later. Hopefully someone else will chime in with some idea what to do about disk6, maybe its problems are preventing disk5 from being emulated accurately.

Stopping the array did not give me the maintainence option.

running root@Tower:~# fdisk -l /dev/sdl

fdisk: cannot open /dev/sdl: No such file or directory

running root@Tower:~# fdisk -l /dev/sdj

Disk /dev/sdj: 7.28 TiB, 8001563222016 bytes, 15628053168 sectors

Disk model: HGST HUH728080AL

Units: sectors of 1 * 512 = 512 bytes

Sector size (logical/physical): 512 bytes / 4096 bytes

I/O size (minimum/optimal): 4096 bytes / 16773120 bytes

Disklabel type: gpt

Disk identifier: A203B7E7-5C05-4BB1-8522-89E093D27450

Device Start End Sectors Size Type

/dev/sdj1 64 15628053134 15628053071 7.3T Linux filesystem

Also, because I stopped the array, it will now not let me restart it.

I'll attach a new diag, (diag 1) reboot and attach another one.

Interesting. I ran the new diag before I rebooted and now Disk 6 has returned to sdj and it will let me choose maintenance mode.

After restarting the array in maintence mode, I selected disk 6 and the check file system status gives me this

Phase 1 - find and verify superblock...
superblock read failed, offset 0, size 524288, ag 0, rval -1

fatal error -- Input/output error

and it moved it to the unassigned devices again as sdl. I can mount it as sdl and all of the files are there. (diag 2)

Reboot and (diag 3).

Issue has not been fixed.

diag 2.zip diag 1.zip diag 3.zip