So lets try starting with the basics.
It is a LSI 3108 in my Huawei server with space for 14 drives, two of which SFF.
I use Avago MSM 17.05.06.00 for all configurations.
I had 2 x 3TB Seagate drives confed as RAID1 . Checks out. Had it for a few months. Never a problem. They are on Port 0 and Port 1.
I add 2 x 3TB Toshiba drives to add some redundancy and storage and try to reconf them all to RAID5. Those are on Port 10 and 11.
As I try to make the RAID5 I see that the result is 5,5GB of space, instead of expected 9TB.
At the same time, looking in to the drive specs, somehow the "old" Seagate drives now report 2,520GB (GIGABYTE) instead of the previous normal 2,7 something TB. Both does.
All drives report 512B sector sizes, so while looking at that it does not seem to be the main issue. I looked at them using a few tools (Windows environment) and CrystalDiskInfo is able to drill through the RAID controller and report the disks SMART and all that, it also gives the same disk size as the Raid MSM software.
Tried booting in to SeaTools X on the Server but they don't see past the Raid controller. Loaded up the drives on a laptop with a USB - HDD dockingstation and booted from SeaTools there, and it can not identify any immediate obvious issues. It says capacity is 2,5GB/ 2,7GB depending on GB or GiB. I think LBA is screwed up somehow.
Any ideas as to what cause two perfectly good drives to suddenly misbehave?
It is a LSI 3108 in my Huawei server with space for 14 drives, two of which SFF.
I use Avago MSM 17.05.06.00 for all configurations.
I had 2 x 3TB Seagate drives confed as RAID1 . Checks out. Had it for a few months. Never a problem. They are on Port 0 and Port 1.
I add 2 x 3TB Toshiba drives to add some redundancy and storage and try to reconf them all to RAID5. Those are on Port 10 and 11.
As I try to make the RAID5 I see that the result is 5,5GB of space, instead of expected 9TB.
At the same time, looking in to the drive specs, somehow the "old" Seagate drives now report 2,520GB (GIGABYTE) instead of the previous normal 2,7 something TB. Both does.
All drives report 512B sector sizes, so while looking at that it does not seem to be the main issue. I looked at them using a few tools (Windows environment) and CrystalDiskInfo is able to drill through the RAID controller and report the disks SMART and all that, it also gives the same disk size as the Raid MSM software.
Tried booting in to SeaTools X on the Server but they don't see past the Raid controller. Loaded up the drives on a laptop with a USB - HDD dockingstation and booted from SeaTools there, and it can not identify any immediate obvious issues. It says capacity is 2,5GB/ 2,7GB depending on GB or GiB. I think LBA is screwed up somehow.
Any ideas as to what cause two perfectly good drives to suddenly misbehave?