Date: Sat, 24 Feb 2001 19:57:48 -0500 (EST) From: <cornwall@intelos.net> To: Jonathan Hanna <pangolin@home.com> Cc: William Denton <buff@pobox.com>, freebsd-stable@FreeBSD.ORG Subject: RE: "cannot find label (no disk label)" Message-ID: <Pine.GSO.4.21.0102241955450.16539-100000@flanders.intelos.net> In-Reply-To: <200102250034.f1P0Y0D77815@cr222190-a.crdva1.bc.wave.home.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Jonathan, I may be mistaken, but it looks to me as if there may be some problem with your boot sector. Is that where you have it? If so maybe you could use your boot floppy to access the hard-drive and edit the boot profile from there. John On Sat, 24 Feb 2001, Jonathan Hanna wrote: > > I am seeing something similar on an old Pentium (that i don't have > physical access to, grrr). I attempted to upgrade from 4.0 to 4.2-stable of a > couple of days ago and when the new kernel boots the > "no disk label: and "Root mount failed: 22" also appear. > I am told that there is also > "ad0: hard read error blk=64 stat=54 ..." or some such. > > Any ideas? > > > On 05-Feb-01 William Denton wrote: > > I have two machines, a fast one and a slow one. The fast one I keep > > fairly current to STABLE, and upgraded it today to the latest source. > > All went well. The slow one, a 486, was running a STABLE from last > > October or so, but I used NFS and exported a pre-built world and kernel to > > it, and the installworld and installkernel went fine. I ran mergemaster, > > and at the end it said I should run MAKEDEV all because a new MAKEDEV had > > been installed, and I did so (I'd done the same on the fast machine, and > > had rebooted fine). When I rebooted the slow one, though, I got: > > > > ad0: ... > > ad2: ... > > (null): MODE-SENSE-BIG - UNIT ATTENTION asc=29 ascq=00 error=04 > > acd0: ... > > Mounting root from ufs:/dev/ad0s1a > > ad0: cannot find label (no disk label) > > ad0s1: cannot find label (no disk label) > > Root mount failed: 22 > > > > Then the same things repeated twice for wd0 and wd0s1, and it asks me > > where it should look for a root filesystem. > > > > I looked around trying to find out what this meant, but the closest I > > could find, because I'd read it a week or two ago, was an excerpt from an > > IRC log, where Jordan Hubbard helps Dan Langille (of www.freebsddiary.org) > > recover from a similar error. Jordan chastises him for having run MAKEDEV > > all, which "rebuilds all the wd* and sd* targets, and those remove all the > > *slice* entries by default so that the disk entry list is nice and clean." > > > > What happened to /dev/ad0s1a? Was I wrong to run MAKDEV all? Everything > > else about the upgrade to today's -STABLE went fine, > > > > I downloaded the three floppies from 4.2-RELEASE, and booted up kern and > > mfsroot in order to get to the fixit floppy, but when mfsroot's menu > > comes up, my keyboard locks up and I can't do anything! I've never had > > any problems with it before, but now I can't even get to the fixit. Am I > > completely screwed? > > > > Bill > > -- > > William Denton : Toronto, Canada : http://www.miskatonic.org/ : Caveat lector. > > Jonathan Hanna <pangolin@home.com> > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.GSO.4.21.0102241955450.16539-100000>