Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 22 Feb 2000 12:53:20 -0800 (PST)
From:      robert bowen <Robert@braingarage.com>
To:        freebsd-mobile@freebsd.org
Subject:   Disk label problems, Hello
Message-ID:  <200002222053.MAA06562@smartie.braingarage.com>

next in thread | raw e-mail | index | archive | help
Hi - I just got 3.4-RELEASE running on my Thinkpad 240.
Everything went great during the install, but I had some
strange disklabel problems after. I left a 2G win98
partition  on the machine, and booted into both OS's a
few times. Then, I booted into windows again and shut
down the computer. After I re-booted (without changing
anything), FreeBSD wouldn't boot. The boot manager came
up, but it couldn't load the boot loader or kernel. I
finally used sysinstall, but there were no slices listed
under disklabel!! Fdisk showed an active FreeBSD
partition, but disklabel showed NO slices. I was
expecting to see partitions listed with no mount point,
but there was nothing there at all. I reinstalled the
system, and foolishly booted into Windows again. Same
thing. In the end I reinstalled FreeBSD and selected no
boot manager. Now FreeBSD boots perfect and there is no
Win cause problems. I would chalk it up to weirdness,
but for the fact that I was able to boot perfectly fine
into bot systems several times. The lesson I guess is to
just get rid of the wasted Windows space. Is there any
hope of writing a program to make the machine suspend to
a FreeBSD partition??


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-mobile" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200002222053.MAA06562>