Date: Mon, 22 Feb 1999 22:12:03 +0000 From: Jon Drukman <jsd@gamespot.com> To: freebsd-questions@freebsd.org Subject: panic: cannot mount root Message-ID: <36D1D633.4CB92339@gamespot.com>
next in thread | raw e-mail | index | archive | help
just upgraded to 3.1-RELEASE from 2.2.7-RELEASE. installation went smoothly. however, i am unable to boot kernels that i have compiled. with the line: config kernel root on da0 the boot sequence halts like this: changing root to da0s1a changing root to da0a error 6: panic: cannot mount root (2) i edited /etc/fstab before booting. it looks like this: /dev/da0s1b none swap sw 0 0 /dev/da0s1a / ufs rw 1 1 /dev/da0s1f /usr ufs rw 2 2 /dev/da0s1e /var ufs rw 2 2 proc /proc procfs rw 0 0 i can boot just fine with kernel.GENERIC. just my own kernels won't boot. i also tried config kernel root on da0s1a but that gave the same panic. while booted with kernel.GENERIC, here is the result of df: Filesystem 1K-blocks Used Avail Capacity Mounted on /dev/da0s1a 31775 24940 4293 85% / /dev/da0s1f 1834946 1432923 255228 85% /usr /dev/da0s1e 29727 5952 21397 22% /var procfs 4 4 0 100% /proc as far as i can tell, da0s1a is the root filesystem and that's what should be booting. here's dmesg (when booted with kernel.GENERIC): changing root device to da0s1a da0 at ahc0 bus 0 target 0 lun 0 da0: <SEAGATE ST32550N 0019> Fixed Direct Access SCSI-2 device da0: 10.0MB/s transfers (10.0MHz, offset 15), Tagged Queueing Enabled da0: 2047MB (4194058 512 byte sectors: 255H 63S/T 261C) -- Jon Drukman jsd@gamespot.com ----------------------------------------------------------------------- Fear the government that fears your computer. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?36D1D633.4CB92339>