Date: Wed, 20 Mar 2002 22:41:34 GMT From: Carlos Antonio Ruggiero <toto@sdf.lonestar.org> To: freebsd-hackers@freebsd.org Subject: booting from extended slice -news Message-ID: <200203202241.g2KMfYm05289@sdf.lonestar.org>
next in thread | raw e-mail | index | archive | help
Hi,
I've been trying to boot 4.5R from an extended partition
(slice). I could boot the kernel directly, but not through the loader
as told in a previous post.
The problem seems to be in libi386, more precisely
/usr/src/sys/boot/i386/libi386/biosdisk.c in function
bd_checkextended(struct open_disk *od, int slicenum). I 've changed it
and now, when I boot the loader, lsdev -v reports the extended
partitions correctly. I'm finally able to boot the kernel through the
loader after doing set currdev=disk1s10a:. I can mount linprocfs now
and run vmware. So my problem is solved ;-) but:
1) Is libi386 used anywhere else, particularly in the kernel?
2) I have a funny problem with fstab. If I set root as:
/dev/ad0s10a / ufs rw 1 1
dmesg says (only the relevant bit shown...):
......
ad0: 76345MB <MAXTOR 6L080J4> [155114/16/63] at ata0-master UDMA100
ad1: 38172MB <QUANTUM FIREBALLlct20 40> [77557/16/63] at ata0-slave UDMA100
ad4: 39082MB <Maxtor 94098U8> [79406/16/63] at ata2-master UDMA66
ad6: 38172MB <QUANTUM FIREBALLP AS40.0> [77557/16/63] at ata3-master UDMA100
acd0: CD-RW <HL-DT-ST GCE-8160B> at ata1-master using PIO4
Waiting 5 seconds for SCSI devices to settle
Mounting root from ufs:/dev/ad0s10a
junk after name
setrootbyname failed
ffs_mountroot: can't find rootvp
Root mount failed: 6
Manual root filesystem specification:
<fstype>:<device> Mount <device> using filesystem <fstype>
eg. ufs:/dev/da0s1a
? List valid disk boot devices
<empty line> Abort manual input
mountroot> da0 at ahc0 bus 0 target 0 lun 0
da0: <IBM DCAS-34330W S65A> Fixed Direct Access SCSI-2 device
da0: 20.000MB/s transfers (10.000MHz, offset 8, 16bit)
da0: 4134MB (8467200 512 byte sectors: 255H 63S/T 527C)
usf\^H \^H\^H \^Hfs:/dev/ad0s10\^H \^H\^H \^H\^H \^Ha
Mounting root from ufs:/dev/ad0a
/dev/vmmon: Module vmmon: registered with major=200 minor=0 tag=$Name: build-570 $
.............
What is this "junk after name" thing? I am sure the name is typed correctly.
Is it the fact that there are 2 digits after s? Anyway, if I replace
ad0s10a with ad0a, everything works..
Thanks
Toto
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200203202241.g2KMfYm05289>