Date: Sat, 17 Apr 2010 12:05:46 +0200 From: "Julian H. Stacey" <jhs@berklix.com> To: hackers@freebsd.org Subject: Bug with fixit live 8.0 memstick.img running on F1 after MBR Message-ID: <201004171005.o3HA5kfo014359@fire.js.berklix.net>
next in thread | raw e-mail | index | archive | help
Hi Hackers,
Bug found with fixit live 8.0 memstick.img running on F1 after MBR :
First I checked my PC BIOS boots OK:
I copied 8.0-RELEASE-i386-memstick.img to a raw 2G USB stick, it boots
fine, & one can go into fixit menu, using image on stick
Next
I fdisk partitioned an 8G stick & copied 8.0-RELEASE-i386-memstick.img
to F1 (da0s1), set F1 active, booted OK, went into fixit, selected
USB stick for the live media, & it failed to find a USB media.
(The live command prompt on F4 wasn't much use, no ls yet.)
I tried telling it to install to F2 (6.5 G ufs), using files from
local FS on stick, (I told it path 8.0-RELEASE ) but on 2 attempts,
it couldnt find where to install to get bins from.
I since confirmed those files are there on F1 8.0-RELEASE/ , see below.
Conclusion:
Would be nice if others tried too, to tell if it's my mistake or a bug.
WOrth doing as it also sets you up ready with a stick that can rescue/
fixit + has enough space for other file systemes with your own
personal /usr/local inc. X, ready for eg testing laptops in shops.
I since mounted my 8G stick on a normal 8.0 PC & installed F2
from /usr/src & /usr/local from hard disc. I have another 4G I
could test with MBR, but testing here is disruptive as only my
main machine has boot- off- USB functionality).
I mounted both sticks later to document what I was using:
2G stick with no MBR, (`dangerously dedicated', that worked OK:
ls -l /devusb/red -> /dev/da0a
df | grep usb
Filesystem Size Used Avail Capacity Mounted on
/devusb/red 921M 858M -11M 101% /usb/red
disklabel da0
# /dev/da0:
8 partitions:
# size offset fstype [fsize bsize bps/cpg]
a: 1803124 16 unused 0 0
c: 1803140 0 unused 0 0 # "raw" part, don't edit
disklabel: partition c doesn't cover the whole unit!
disklabel: An incorrect partition c may cause problems for standard system utilities
8G stick with MBR:
fdisk da0
******* Working on device /dev/da0 *******
parameters extracted from in-core disklabel are:
cylinders=977 heads=255 sectors/track=63 (16065 blks/cyl)
parameters to be used for BIOS calculations are:
cylinders=977 heads=255 sectors/track=63 (16065 blks/cyl)
Media sector size is 512
Warning: BIOS sector numbering starts with sector 1
Information from DOS bootblock is:
The data for partition 1 is:
sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD)
start 63, size 2988027 (1458 Meg), flag 0
beg: cyl 0/ head 1/ sector 1;
end: cyl 185/ head 254/ sector 63
The data for partition 2 is:
sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD)
start 2988090, size 12707415 (6204 Meg), flag 80 (active)
beg: cyl 186/ head 0/ sector 1;
end: cyl 976/ head 254/ sector 63
The data for partition 3 is:
<UNUSED>
The data for partition 4 is:
<UNUSED>
mount
/dev/da0s1a on /usb/sanblack.img (ufs, local)
/dev/da0s2a on /usb/sanblack.ufs (ufs, local, soft-updates)
df
Filesystem Size Used Avail Capacity Mounted on
/dev/da0s1a 921M 858M -11M 101% /usb/sanblack.img
/dev/da0s2a 6.3G 2.7M 5.8G 0% /usb/sanblack.ufs
cd /usb/sanblack.img/8.0-RELEASE
du -s kernels # 60M
ls base # base.aa - base.bl, base.inf base.mtree install.sh*
disklabel da0s1
# size offset fstype [fsize bsize bps/cpg]
a: 1803124 16 unused 0 0
c: 2988027 0 unused 0 0
disklabel da0s2
a: 12707399 16 4.2BSD 0 0 0
c: 12707415 0 unused 0 0
Cheers,
Julian
--
Julian Stacey, BSD Unix Linux C Sys Eng Consultants Munich http://berklix.com
Mail plain text, Not HTML quoted-printable Base64 http://www.asciiribbon.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201004171005.o3HA5kfo014359>