Re: ATA RAID - sysinstall solution
> OK, i tested this. Sysinstall works fine now, and the system installs OK > from the SNAP 5 ftp server. ON reboot, however, the computer thing refuses > to boot of the RAID device. After the BIOS message "verifying > DMI.."(or similar) the system hangs. Because of the offset 10, sysinstall wrote the fdisk table to the wrong location on the disk... The following little patch fixes this. This should work for both 4 and 5 trees: - look for .. += rdp->offset in ata-raid.c - make this line conditional if (buf1->drive) .. += rdp->offset Of course, as Soren pointed out, you're risking screwing your first partition if you're NOT using an fdisk compatible layout. However, without this patch the RAID is not bootable, so for me the case is clear:-) I've used this with a RAID0 here successfully (incl. booting off it). About the other suggestion, initially installing on the single drive, and then mirroring it (turning it into a RAID1): should work, but be careful not to use the original disk up to the last cylinder. The RAID will be (just) slightly smaller than the individual disk, and if you filled your single disk to the end, FreeBSD will reject the last partition as being out of disk limits. You'll have to adjust the disklabel after the change. Of course, this will also only work with the above patch, or the disklabel won't be found. Good luck, Markus BTW: and many thanks to Soren for his work! -- KPNQwest Switzerland Ltd P.O. Box 1600, Hohlstrasse 550, CH-8048 Zuerich Tel: +41-1-439-4390, Fax: +41-1-439-4391 Markus Wild, Manager Network Operations, e-mail: [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
RE: ATA RAID - sysinstall solution
I have the same problem on 4, and I have a response from Soren: --- start --- Ugh, booting from the HPT RAID is not supported as is. This is due to the HPT using sector #9 for the RAID config stuff, this is not compatible with our bootcode/loader as in some circumstances it would happily overwrite this config info, trashing the RAID in the process. Therefore the code uses an offset of 10 into the physical disks. However if you always use an fdisk partition table, and newer uses the first 10 sectors on the disk, you could make the offset 0 in the driver, and have booting work that way, or buy a promise :) I'm not sure I've used the rigth thing as default here, but at least this was POLA seen with my dangerously dedicated eyes... --- end --- This is bad, but I hope we will help Soren to sort thing out on how to get to do it. We will keep in touch. Ivan -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Wednesday, November 08, 2000 4:44 PM To: Ivan Debnár Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: Re: ATA RAID - sysinstall solution OK, i tested this. Sysinstall works fine now, and the system installs OK from the SNAP 5 ftp server. ON reboot, however, the computer thing refuses to boot of the RAID device. After the BIOS message "verifying DMI.."(or similar) the system hangs. Does anybody know why this could be? jan To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ATA RAID - sysinstall solution
OK, i tested this. Sysinstall works fine now, and the system installs OK
from the SNAP 5 ftp server. ON reboot, however, the computer thing refuses
to boot of the RAID device. After the BIOS message "verifying
DMI.."(or similar) the system hangs.
Does anybody know why this could be?
jan
On Mon, 6 Nov 2000, [iso-8859-2] Ivan Debnár wrote:
> I'm using HTP 370 ATA RAID controller, which should have been supported in
> stable and current according to CVS messages from Soren.
>
> But as few of us found, it is not, in fact.
>
> KERNEL recognises device ar0.
>
> 4.2 sysinstall does not offer ar0 as disk drive
> 5.0-current sysinstall offers it, but is not able to create slices on it.
> (DEBUG: MakeDev unknown major/minor).
>
> So I looked through sysinstall source and libdisk source and guess what ! -
> libdisk doesn't know about ar? devices yet.
>
> Could someone update the libdisk source in stable and current to include the
> device?
> The files affected are:
>
> /src/lib/libdisk/create_chunk.c
> /src/lib/libdisk/disk.c
>
> --- disk.c.orig Thu Sep 14 14:10:45 2000
> +++ disk.c Mon Nov 6 23:41:45 2000
> @@ -461,7 +461,7 @@
> }
> #endif
>
> -static char * device_list[] = {"wd", "ad", "da", "wfd", "fla", "idad",
> "mlxd", "amrd", "twed", 0};
> +static char * device_list[] = {"wd", "ad", "da", "wfd", "fla", "idad",
> "mlxd", "amrd", "twed", "ar", 0};
>
> char **
> Disk_Names()
>
>
> --- create_chunk.c.orig Fri Jul 14 08:30:59 2000
> +++ create_chunk.c Mon Nov 6 23:46:59 2000
> @@ -300,6 +300,8 @@
> cmaj = 147, p += 4;
> else if (!strncmp(p, "da", 2)) /* CAM support */
> cmaj = 13, p += 2;
> +else if (!strncmp(p, "ar", 2)) /* ATA RAID */
> + cmaj = 157, p += 2;
> else {
> msgDebug("MakeDev: Unknown major/minor for devtype %s\n", p);
> return 0;
>
> Unfortunately I am not able to compile and try this, but if someone can
> create a set of 4-STABLE or 5-CURRENT installation disks and e-mail them,
> I'm willing to try.
>
> Those diffs are against 2000-10-30 stable, so they are just to show changes
> what I thing should be done to actual current files. This should make
> Current install on ATA RAID hopefully. I don't know, if it will make STABLE
> sysinstall recognize the ar device. I hope so.
>
>
> Ivan Debnár
> Online Consulting, s.r.o.
>
> tel.://+421 88 4146721
> fax://+421 88 4142231
> http://www.o-c.sk
>
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: ATA RAID - sysinstall solution
> So I looked through sysinstall source and libdisk source and guess what ! - > libdisk doesn't know about ar? devices yet. Committed, thanks! - Jordan To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
