Port-i386 archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: Can't upgrade RAIDframe system -- won't boot from CD
Interrupt the CD boot loader (by pressing space), tell it to drop to
the boot command prompt and then say:
boot -a
When the kernel ask for the root filesystem answer: cd0a
I've tried that with two other sets of RAIDframe disks and can't get
beyond the `init path' prompt, as per the two fragments of the boot
process below (both of these are for the same RAIDframe set).
Booting from NetBSD/i386 6.0.1 install CD
-----------------------------------------
atapibus0 at atabus1: 2 targets
cd0 at atapibus0 drive 0: <LITE-ON LTR-48246S, , SS0C> cdrom removable
raid0: RAID Level 1
raid0: Components: /dev/sd0a /dev/sd1a
raid0: Total Sectors: 71720600 (35020 MB)
boot device: raid0
root device (default raid0a): cd0a
dump device (default cd0b):
file system (default generic):
root on cd0a dumps on cd0b
root file system type: cd9660
warning: no /dev/console
init path (default /sbin/init):
Booting from a non-RAID disk
----------------------------
raid0: RAID Level 1
raid0: Components: /dev/sd0a /dev/sd1a
raid0: Total Sectors: 71721600 (35020 MB)
boot device: raid0
root device (default raid0a): wd0a
dump device (default wd0b):
file system (default generic):
root on wd0a dumps on wd0b
root file system type: ffs
init path (default /sbin/init):
Nothing I type shows up on the `init path line' and hitting Enter does nothing.
When trying on another PC with the other RAIDframe set I mentioned,
some of the characters I type appear but the back-space key doesn't
work properly -- I can only delete characters after hitting it many
times, and again hitting Enter does nothing. (Now I can't be sure
if this was at the `root device' prompt or `init path') This PC has
ACPI on its motherboard so I can tell NetBSD hasn't frozen because
when I push its power button it detaches devices and shuts down
instead of just crashing.
I then tried booting from the install CD with no disks attached,
dropping into the boot prompt, typing `boot -a' and found only a few
of the many characters I typed appeared on the `root device' prompt
line. In frustration I ended up pressing my hands down on the
keyboard, typing many characters at once and this happened (maybe not
surprisingly):
root device (default cd0a): dcdfatal page fault in supervisor mode
trap type 6 code 0 eip c06689ab cs 8 eflags 10292 cr2 14 ilevel 6
kernel: supervisor trap page fault, code=0
Stopped in pid 0.2 (system)at netbsd:pckbport_poll_cmd1.clone.2+0x13: movl
1
4(%edx),%eax
db{0}> fatal page fault in supervisor mode
trap type 6 code 0 eip c06689ab cd 8eflags 10286 cf2 14 ilevel 8
kernel: supervisor trap page fault, code=0
Faulted in DDB, continuing...
dv{0}> fatal page faulit in supervisor mode
trap type 6 code 0 eip c06689ab cd 8 eflags 10286 cr2 14 ievel 8
kernel: supervisor trap page fault, code=80
Faulted in DDB: continuing...
db{0}>
I changed keyboards but the behaviour stayed the same.
I booted from an install CD which uses com0 for I/O instead of the
VGA card, dropped into the boot prompt and typing `boot -a' and it
worked fine.
I wonder what's happening?
Ray
Home |
Main Index |
Thread Index |
Old Index