Date: Mon, 3 Jun 2002 10:36:04 -0700 (PDT) From: Mike <FIATLUX@jazzfree.com> To: freebsd-gnats-submit@FreeBSD.org Subject: misc/38867: Boot "Read error" with offboard Promise ultra100 TX2 controller Message-ID: <200206031736.g53Ha4XM055093@www.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 38867
>Category: misc
>Synopsis: Boot "Read error" with offboard Promise ultra100 TX2 controller
>Confidential: no
>Severity: critical
>Priority: high
>Responsible: freebsd-bugs
>State: open
>Quarter:
>Keywords:
>Date-Required:
>Class: change-request
>Submitter-Id: current-users
>Arrival-Date: Mon Jun 03 10:40:02 PDT 2002
>Closed-Date:
>Last-Modified:
>Originator: Mike
>Release: 4.5
>Organization:
>Environment:
>Description:
After the installation I get the very known "Read error" message from the boot1 stage of the boot process. The cdrom kernel, in the installation, recognizes the harddisk as:
38166MB 77545/16/63 at ata2-master UDMA100 (I've a SEAGATE BARRACUDA IV in the first canal of a offboard Promise Ultra100 TX2 ide controller)
and fdisk "says" that the disk is ad4 and his geometry is 4865/255/63 ( the real geometry ).
I've installed FREEBSD with the "don't modify the MBR" option because I use BootMagic6.0 as boot manager. The FREEBSD partition begins in the 4th Gigabyte of the HD ( < 1024 cilinder ), Partition Magic says that the partition begins in 8048565 (LBA) 501/0/1 (CHS) and ends in 16707599 (LBA) 1039/254/63 (CHS). These LBA values are equal in Partition Magic and in fdisk. The slices that i've created are:
ad4s4a / UFS Y 300MB
ad4s4b swap 150MB
ad4s4e /var UFS+s Y 300MB
ad4s4f /usr UFS+s Y 3500MB
I've obtained the boot sector (8048565 sector) of the freebsd partition
and observed that is equal that the /boot/boot1 file, they shouldn't be different?.
I've tried to modify the geometry that fdisk uses, using the "change drive geometry option" but fdisk says "incorrect drive geometry".
I would like to know:
A) is there any way of activate the LBA geometry in the wd driver flags without recompiling the kernel? this is because i don't have a working FREEBSD
B) is there any way of booting my FREEBSD with a boot disk/cdrom using the "boot: 1:ad(4,a)/kernel" option?
C) could i resolve the problem using something like fdisk and a good disktab description of my HD?
Thank you!
>How-To-Repeat:
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted:
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200206031736.g53Ha4XM055093>