Date: Sat, 10 Aug 2002 17:54:37 +0800 (CST) From: "spf@xslt.cs.nccu.edu.tw" <spf@Brice.dorm9.nccu.edu.tw> To: FreeBSD-gnats-submit@FreeBSD.org Cc: spf@xslt.cs.nccu.edu.tw Subject: misc/41515: boot0cfg corrupts slice table Message-ID: <200208100954.g7A9sbe0000372@Brice.dorm9.nccu.edu.tw>
next in thread | raw e-mail | index | archive | help
>Number: 41515
>Category: misc
>Synopsis: boot0cfg corrupts slice table
>Confidential: no
>Severity: non-critical
>Priority: low
>Responsible: freebsd-bugs
>State: open
>Quarter:
>Keywords:
>Date-Required:
>Class: sw-bug
>Submitter-Id: current-users
>Arrival-Date: Sat Aug 10 03:00:06 PDT 2002
>Closed-Date:
>Last-Modified:
>Originator: spf
>Release: FreeBSD 4.6.1-RELEASE-p10 i386
>Organization:
>Environment:
System: FreeBSD Brice.dorm9.nccu.edu.tw 4.6.1-RELEASE-p10 FreeBSD 4.6.1-RELEASE-p10 #3: Thu Aug 8 07:49:33 CST 2002 root@Brice.dorm9.nccu.edu.tw:/usr/obj/usr/src/sys/spf i386
>Description:
my disk usage: ad0s1 NTFS (active), ad0s2 extended (NTFS)
ad2s1 NTFS, ad2s2 extended (NTFS), ad2s3 freebsd boot slice(activ
e)
When I use ad2s3 boot with boot0 installed in ad0 option "update" enabled,
it will make ad0s1's flag 80->0, make it "not active".
Then next execution of boot0 won't find no active partion.
This situation won't happen if I boot from ad0s1 or I disable option "update".
>How-To-Repeat:
fdisk -u ad0
fdisk -u ad2
(make sure ad0s1 and ad2s3 is set active)
boot0cfg ad0
(then install boot0 on ad0, default option "update" is enabled)
reboot
boot from ad2s3
>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?200208100954.g7A9sbe0000372>