On 25/01/2024 at 12:49, RJ Marquette wrote:
root@jackie:/home/rj# /sbin/fdisk -l /dev/sdb
Disk /dev/sdb: 2.73 TiB, 3000592982016 bytes, 5860533168 sectors
Disk model: Hitachi HUS72403
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: AF5DC5DE-1404-4F4F-85AF-B5574CD9C627
Device Start End Sectors Size Type
/dev/sdb1 2048 5860532223 5860530176 2.7T Microsoft basic data
root@jackie:/home/rj# cat /sys/block/sdb/sdb1/start
2048
root@jackie:/home/rj# cat /sys/block/sdb/sdb1/size
5860530176
The partition geometry looks correct, with standard alignment.
And the kernel view of the partition matches the partition table.
The partition type "Microsoft basic data" is neither "Linux RAID" nor
the default type "Linux flesystem" set by usual GNU/Linux partitioning
tools such as fdisk, parted and gdisk so it seems unlikely that the
partition was created with one of these tools.
It looks like this is what happened after all. I searched for "MBR
Magic aa55" and found someone else with the same issue long ago:
https://serverfault.com/questions/580761/is-mdadm-raid-toast ; Looks like
his was caused by a RAID configuration option in BIOS. I recall seeing
that on mine; I must have activated it by accident when setting the boot
drive or something.
I am a bit suspicious about this cause for two reasons:
- sde, sdf and sdg are affected even though they are connected to the
add-on Marvell SATA controller card which is supposed to be outside the
motherboard RAID scope;
- sdc is not affected even though it is connected to the onboard Intel
SATA controller.
What was contents type of the RAID array ? LVM, LUKS, plain filesystem ?
