Bug 13785
| Summary: | boot block/manager problem at installation | ||
|---|---|---|---|
| Product: | Base System | Reporter: | Jin Guojun <jin> |
| Component: | conf | Assignee: | jkh |
| Status: | Closed FIXED | ||
| Severity: | Affects Only Me | ||
| Priority: | Normal | ||
| Version: | 3.3-STABLE | ||
| Hardware: | Any | ||
| OS: | Any | ||
Responsible Changed From-To: freebsd-bugs->jkh Over to sysinstall owner State Changed From-To: open->closed This should be fixed now; please re-submit the PR if it occurs with any more recent FreeBSD release (4.1 or later). |
Two problems: (1) told installation "DO not touch the BOOT BLOCK on the first drive" ( ) BootMgr Install the FreeBSD Boot Manager ("Booteasy") ( ) Standard Install a standard MBR (no boot manager) (*) None Leave the Master Boot Record untouched but, the installation still replaced the BOOT BLOCK on the first drive that causes 2.2.8 not boot automatically, because 2.2.8 does not have /boot/loader . (2) installation program set wrong drive name (wd1) for root mounting that causes panic: panic: cannot mount root (2) because the drive name for the second disk is wd2, but not wd1. The installation should not assume the second drive is wd1 in a sequence order. If the second drive is on the second IDE bus, it can the either wd2 or wd3, but not wd1. This causes the 3.x on the second drive not bootable. Therefore, both drives are not bootable after such installation. The first can be fixed by reinstalling boot block by disklable -B wd0 but the second problem causes installation useless if the second drive is on the second IDE bus, regardless what is on the first drive. Fix: It should be somewhere in the installation code. How-To-Repeat: put one IDE drive on the first IDE controller, and put another IDE drive on the second IDE controller; then try install any 3.3-VER onto the second IDE drive (wd2).