Jeff Garzik wrote:
..
The problem is not at the chip or device level, and this is the same
problem as any number of other cards with softRAID on it. Not a new
problem, not a new solution...
..
What other cards do we support that automatically overwrite user data
without confirmation or
Jeff Garzik wrote:
..
OTOH it is quite reasonable to explore auto-loading DM on top of the
bare drive, and populating a DM table, if you see that particular BIOS
signature or [insert other detection method].
..
I am very interested to hear a more detailed explanation of this,
as I don't
Mark Lord wrote:
Jeff Garzik wrote:
...
If you pop the BIOS chip or plug the card into a non-x86 box (or any
of several other alternatives), the problem is likely to go away.
..
Yeah, I was hoping for a removable BIOS chip, but it's soldered in place.
And that's not a solution for most
Hein-Pieter van Braam wrote:
I zero'd all the disks, and now they show up as 'new' in the highpoint
BIOS again... so, I guess there IS some reserved part somewhere that's
accessible with the sata_mv driver.
..
Yeah, that's my suspicion too.. they must have just simply moved
the metadata to
Mark Lord wrote:
Hein-Pieter van Braam wrote:
I zero'd all the disks, and now they show up as 'new' in the highpoint
BIOS again... so, I guess there IS some reserved part somewhere that's
accessible with the sata_mv driver.
..
Yeah, that's my suspicion too.. they must have just simply moved
Mark Lord wrote:
Mark Lord wrote:
Hein-Pieter van Braam wrote:
I zero'd all the disks, and now they show up as 'new' in the highpoint
BIOS again... so, I guess there IS some reserved part somewhere that's
accessible with the sata_mv driver.
..
Yeah, that's my suspicion too.. they must have
Mark Lord wrote:
To do so, requires that we perhaps do a similar capacity truncation
in sata_mv, but only if we see a metadata block at the expected location
(because a Legacy mode drive will use the *real* capacity,
placing the metadata in the 9th sector instead.
Definitely _not_. This is a
Mark Lord wrote:
...
Yeah, that's my suspicion too.. they must have just simply moved
the metadata to near the end instead of sector-8.
...
They write their RAID metadata near-ish to the end of the drive.
On my 320GB drives, it ended up at about -199853 sectors from
the end of the drive. I
Jeff Garzik wrote:
Mark Lord wrote:
To do so, requires that we perhaps do a similar capacity truncation
in sata_mv, but only if we see a metadata block at the expected location
(because a Legacy mode drive will use the *real* capacity,
placing the metadata in the 9th sector instead.
Jeff Garzik wrote:
Mark Lord wrote:
To do so, requires that we perhaps do a similar capacity truncation
in sata_mv, but only if we see a metadata block at the expected location
(because a Legacy mode drive will use the *real* capacity,
placing the metadata in the 9th sector instead.
Mark Lord wrote:
Jeff Garzik wrote:
Mark Lord wrote:
To do so, requires that we perhaps do a similar capacity truncation
in sata_mv, but only if we see a metadata block at the expected location
(because a Legacy mode drive will use the *real* capacity,
placing the metadata in the 9th sector
Mark Lord wrote:
Jeff Garzik wrote:
Mark Lord wrote:
To do so, requires that we perhaps do a similar capacity truncation
in sata_mv, but only if we see a metadata block at the expected location
(because a Legacy mode drive will use the *real* capacity,
placing the metadata in the 9th sector
On Tue, 2007-12-04 at 01:17 +0100, Hein-Pieter van Braam wrote:
I'll come up with the hdparm -g output and the results of this test with
the two different drivers tomorrow.
Just a little status update, I've been getting some REALLY strange
results when using the disks as raid array, and I'm
I zero'd all the disks, and now they show up as 'new' in the highpoint
BIOS again... so, I guess there IS some reserved part somewhere that's
accessible with the sata_mv driver.
that's a bit of a problem, because if you overwrite the RAID metadata,
the raid bios won't allow booting from the
Subject: [PATCH] sata_mv: Fix broken Marvell 7042 support.
sata_mv: Fix broken Marvell 7042 support.
The Marvell 7042 chip is more or less the same as the 6042 internally,
but sports a PCIe bus. Despite having identical SATA cores, the 7042
does differ from its PCI bus counterparts in placment
] [mailto:[EMAIL PROTECTED]
Sent: Monday, December 03, 2007 9:48 AM
To: Morrison, Tom
Cc: Mark Lord; IDE/ATA development list; Jeff Garzik; Tejun Heo; Alan
Cox
Subject: RE: [PATCH] sata_mv: Fix broken Marvell 7042 support.
It doesn't quite work for me, the system locks up without discernible
error
]
Sent: Saturday, December 01, 2007 1:07 PM
To: IDE/ATA development list; Jeff Garzik
Cc: Tejun Heo; Alan Cox; Morrison, Tom; Hein-Pieter van Braam
Subject: [PATCH] sata_mv: Fix broken Marvell 7042 support.
sata_mv: Fix broken Marvell 7042 support.
The Marvell 7042 chip is more or less the same
[EMAIL PROTECTED] wrote:
It doesn't quite work for me, the system locks up without discernible
error messages (Highpoint RocketRaid 2300 PCIe) . The drives come up,
and immediately get hyper active, and I get dumped in an initrd busybox
shell, when I try to tail /dev/sda it hangs, pvscan
Mark Lord wrote:
[EMAIL PROTECTED] wrote:
It doesn't quite work for me, the system locks up without discernible
error messages (Highpoint RocketRaid 2300 PCIe) . The drives come up,
and immediately get hyper active, and I get dumped in an initrd
busybox shell, when I try to tail /dev/sda it
Jeff Garzik wrote:
Mark Lord wrote:
The BIOS on the Highpoint RR 2300 *corrupts* the GRUB image,
so GRUB won't boot for me there. I actually have to re-install
GRUB after each attempt so that the drive is usable again
with the onboard Intel (ahci) ports.
So one then wonders exactly what the
~!
-Original Message-
From: Mark Lord [mailto:[EMAIL PROTECTED]
Sent: Monday, December 03, 2007 1:32 PM
To: Jeff Garzik
Cc: [EMAIL PROTECTED]; Morrison, Tom; IDE/ATA development list; Tejun Heo;
Alan Cox
Subject: Re: [PATCH] sata_mv: Fix broken Marvell 7042 support.
Jeff Garzik wrote
Mark Lord wrote:
...
Okay, I've attempted to boot from the RocketRAID 2300 card
using a known-good boot hard disk.
No such luck.
The BIOS on the Highpoint RR 2300 *corrupts* the GRUB image,
so GRUB won't boot for me there. I actually have to re-install
GRUB after each attempt so that the
Mark Lord wrote:
The BIOS on the Highpoint RR 2300 *corrupts* the GRUB image,
so GRUB won't boot for me there. I actually have to re-install
GRUB after each attempt so that the drive is usable again
with the onboard Intel (ahci) ports.
So one then wonders exactly what the Highpoint BIOS is
Morrison, Tom wrote:
Fwiw, I'm not running an add-on card or anything like it -
no raid - nothing except a 7042 chip as the the front-end
to 2-4 harddrives in my box) - in this case - I am not
having a problem...
I write this as perhaps a hint to the 'right' direction to go
looking for the
Mark Lord wrote:
Morrison, Tom wrote:
Fwiw, I'm not running an add-on card or anything like it - no raid -
nothing except a 7042 chip as the the front-end to 2-4 harddrives in
my box) - in this case - I am not having a problem...
I write this as perhaps a hint to the 'right' direction to go
Confirmed. It writes lgcy + stuff into the 9th sector of the drive
(for my Legacy drive).
Thats quite nasty. Given that users putting volumes unpartitioned on
drives may see actual data corruption and loss perhaps we should
blacklist that controller variant with a large warning ?
Alan
-
To
Alan Cox wrote:
Confirmed. It writes lgcy + stuff into the 9th sector of the drive
(for my Legacy drive).
Thats quite nasty. Given that users putting volumes unpartitioned on
drives may see actual data corruption and loss perhaps we should
blacklist that controller variant with a large
On Mon, 2007-12-03 at 13:30 -0500, Mark Lord wrote:
Mark Lord wrote:
...
Okay, I've attempted to boot from the RocketRAID 2300 card
using a known-good boot hard disk.
No such luck.
The BIOS on the Highpoint RR 2300 *corrupts* the GRUB image,
so GRUB won't boot for me there. I
Hein-Pieter van Braam wrote:
Personally, I put all the disks in JBOD mode, but I never had these
disks connected to anything but my highpoint cards. Perhaps I should
tell you what my setup's like:
* In the system I've put 3 Highpoint RocketRaid 2300 cards.
* Two of the cards each have 4
I'll try and make a bootable USB stick with my patched 2.6.23.9 and see
what the results are then.
..
How are you booting without the USB stick?
Are you booting from the Highpoint card drives?
What bootloader ?
Thanks
-
Right now I just boot using GRUB really, perhaps the BIOS
Mark Lord wrote:
Alan Cox wrote:
Confirmed. It writes lgcy + stuff into the 9th sector of the drive
(for my Legacy drive).
Thats quite nasty. Given that users putting volumes unpartitioned on
drives may see actual data corruption and loss perhaps we should
blacklist that controller variant
Hein-Pieter van Braam wrote:
I'll try and make a bootable USB stick with my patched 2.6.23.9 and see
what the results are then.
..
How are you booting without the USB stick?
Are you booting from the Highpoint card drives?
What bootloader ?
Thanks
-
Right now I just boot using GRUB really,
Man, what a quirky BIOS!
Okay, so if I connect a drive and don't do anything in the Highpoint BIOS
setup,
it then corrupts the drive by overwriting the 9th sector on every reboot.
But.. if I connect a drive and go into the Highpoint BIOS setup,
and initialize the drive there, and then
Man, what a quirky BIOS!
Hum... I can pvcreate on the md device just fine, but after that, pvscan
won't find it...
I have a suspicion that there's a BIOS doing some sector hiding or
replacement of sorts...
*facepalm*
--
This message has been scanned for viruses and
dangerous content by
On Mon, 03 Dec 2007 23:48:44 +0100
Hein-Pieter van Braam [EMAIL PROTECTED] wrote:
Man, what a quirky BIOS!
Hum... I can pvcreate on the md device just fine, but after that, pvscan
won't find it...
I have a suspicion that there's a BIOS doing some sector hiding or
replacement of
On Mon, 2007-12-03 at 23:10 +, Alan Cox wrote:
On Mon, 03 Dec 2007 23:48:44 +0100
Hein-Pieter van Braam [EMAIL PROTECTED] wrote:
Man, what a quirky BIOS!
Hum... I can pvcreate on the md device just fine, but after that, pvscan
won't find it...
I have a suspicion that
Hein-Pieter van Braam wrote:
I did some testing:
First I zero'd the first 80 meg of the md device, then read it back and
compared, still all zero's. Then I rebooted and compared again, still
all zero's
Then I got 8MB of stuff from /dev/urandom, wrote it to a file then wrote
it to md device,
Alan Cox wrote:
On Mon, 03 Dec 2007 23:48:44 +0100
Hein-Pieter van Braam [EMAIL PROTECTED] wrote:
Man, what a quirky BIOS!
Hum... I can pvcreate on the md device just fine, but after that, pvscan
won't find it...
I have a suspicion that there's a BIOS doing some sector hiding or
On Mon, 03 Dec 2007 18:33:10 -0500
Mark Lord [EMAIL PROTECTED] wrote:
Alan Cox wrote:
On Mon, 03 Dec 2007 23:48:44 +0100
Hein-Pieter van Braam [EMAIL PROTECTED] wrote:
Man, what a quirky BIOS!
Hum... I can pvcreate on the md device just fine, but after that, pvscan
won't find it...
Hein-Pieter van Braam wrote:
Man, what a quirky BIOS!
Okay, so if I connect a drive and don't do anything in the Highpoint BIOS setup,
it then corrupts the drive by overwriting the 9th sector on every reboot.
But.. if I connect a drive and go into the Highpoint BIOS setup,
and initialize the
Mark Lord wrote:
Hein-Pieter van Braam wrote:
..
also: on a side note, let me state again, that I'm extremely displeased
with highpoint at this point... their whole 'open source linux drivers'
thing is beginning to piss me off more and more. There must be something
that can be done about this?
Their stuff has always seemed more than a little screwy to me.
The solution for us here, is sata_mv, which will replace their drivers
for this series of boards.
It just seriously pisses me off that because of their advertising 'Open
Source drivers' they now sold ELEVEN of their boards
Mark Lord wrote:
So to boot from a 7042 the only theoretical choice is the Highpoint board,
and for that we need to somehow coax it into not overwriting GRUB
every time the onboard BIOS reinitializes.
..
With the drive set-up as a JBOD volume in the HighPoint BIOS,
I've now got a system that
sata_mv: Fix broken Marvell 7042 support.
The Marvell 7042 chip is more or less the same as the 6042 internally,
but sports a PCIe bus. Despite having identical SATA cores, the 7042
does differ from its PCI bus counterparts in placment and layout of
certain bus related registers.
This patch
On Sat, 01 Dec 2007 13:07:22 -0500
Mark Lord [EMAIL PROTECTED] wrote:
sata_mv: Fix broken Marvell 7042 support.
The Marvell 7042 chip is more or less the same as the 6042 internally,
but sports a PCIe bus. Despite having identical SATA cores, the 7042
does differ from its PCI bus
Mark Lord wrote:
sata_mv: Fix broken Marvell 7042 support.
The Marvell 7042 chip is more or less the same as the 6042 internally,
but sports a PCIe bus. Despite having identical SATA cores, the 7042
does differ from its PCI bus counterparts in placment and layout of
certain bus related
46 matches
Mail list logo
