linux-kernel - sata_mv and Highpoint RocketRAID 230x, corruption?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 20 Oct 2010 21:03:44 +0100
From:	Mathias Burén <mathias.buren@...il.com>
To:	linux-kernel@...r.kernel.org
Subject: sata_mv and Highpoint RocketRAID 230x, corruption?

Hi mailing list,

(please cc me as I'm not subscribed)

I'm currently migrating my system from pure LVM to HDD partitions >
mdadm RAID5 > lvm > filesystem(s). I got a bit worried when I saw this
in dmesg:

"sata_mv 0000:05:00.0: version 1.28
sata_mv 0000:05:00.0: PCI INT A -> Link[LN4A] -> GSI 19 (level, low) -> IRQ 19
sata_mv: Highpoint RocketRAID BIOS CORRUPTS DATA on all attached
drives, regardless of if/how they are configured. BEWARE!
sata_mv: For data safety, do not use sectors 8-9 on "Legacy" drives,
and avoid the final two gigabytes on all RocketRAID BIOS initialized
drives.
sata_mv 0000:05:00.0: Gen-IIE 32 slots 4 ports SCSI mode IRQ via INTx
sata_mv 0000:05:00.0: setting latency timer to 64
"

I'm currently not using the BIOS of the raid controller for anything
else then staggered disk spinup. The HDD partitions start at sector
2048 (to get a 1MB alignment since they're 4k sector drives, WD20EARS)
and end at the last sector.
What I'm worried about is the corruption mentioned in dmesg, is this
explained somewhere in more detail? Google didn't reveal much. Am I in
danger?

Thanks,

// Mathias on Archlinux
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/