[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[bug #2394] Problem with HPT370 Raid controller

From: TBBle
Subject: [bug #2394] Problem with HPT370 Raid controller
Date: Sat, 09 Feb 2008 14:33:42 +0000
User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.2 x64; en-US; rv: Gecko/20071110 BonEcho/ (mmoy CE K8C-X04)

Follow-up Comment #5, bug #2394 (project grub):

http://www.mail-archive.com/address@hidden/msg09759.html confirms sector 9,
BTW. http://www.wensley.org.uk/raid suggests the entirety of sector 9 except
the first 32 bytes is used.

lib/format/htp37x.h in dmraid appears to define a structure for the HPT37x
metadata, so maybe we can detect this after all?

A brief glance at this code suggests that the data is all in sector 9, but is
in sector 9 of each physical disk on the relevant machine. I can't check this
right now, I accidentally did a grub-install hd0 since my last reboot, so once
I next reboot I can confirm the metadata's presence on a machine without a
RAID setup.

Sector 9 on my second disk (also on the RAID controller) contains nulls and
then NULL NULL "Found a array member was" 0x20 x 22, repeated 8 times, up to
the 60 bytes of filler mentioned in the dmraid structure. I dunno if this
means the ondisk metadata format only applies to the first physical disk
(seems likely) and the BIOS uses sector 9 on the other disks for scratch, or

I hope that helps?

By the by, everything else in dmraid's ataformat headers stores its metadata
offset from the end of the disk, which is why this problem seems localised to
the HPT3xx devices.


Reply to this item at:


  Message sent via/by Savannah

reply via email to

[Prev in Thread] Current Thread [Next in Thread]