Date: Mon, 14 May 2007 08:46:37 -0700 From: David Cramblett <david@functionalchaos.net> To: Eric Anderson <anderson@freebsd.org> Cc: freebsd-hackers@freebsd.org Subject: Re: System Drops to manual mount root prompt after HDD duplication Message-ID: <4648845D.4040608@functionalchaos.net> In-Reply-To: <464856C4.2020600@freebsd.org> References: <4640EAD0.3020502@mesd.k12.or.us> <4647D88D.5060404@functionalchaos.net> <464856C4.2020600@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Eric Anderson wrote: > On 05/13/07 22:33, David Cramblett wrote: >> My FreeBSD 5.2.1 server had a 4.5 GB HDD. I decided to upgrade it >> with a larger drive. I installed a new drive on the second IDE >> channel which made it ad2, of course, my original drive was ad0. I >> created a partition, boot loader and matching slices on the new >> drive. Then I copied the old drive to the new drive using tar. Once >> finished, I removed the original drive and installed the new one on >> the primary channel. When I booted up everything appeared normal, but >> when the system starts to mount "/" it gives no error or warning and >> just drops to a "Manual mount root specification" prompt. If I type >> "ufs:ad0s1a" it boots up and everything is perfect. This is the same >> slice "/" was on the old drive as well. >> >> >> I have tried the following with no success: >> >> Checked /etc/fstab >> >> boot0cfg -v -B ad0 >> >> bsdlabel -B ad0s1 >> >> tried booting from a cd, going into post install config, fdisk, and >> set the partition as bootable, it already was. >> >> Since upgrading the hard disk, I have upgraded the system to 5.5 and >> then to 6.2. This system has been working great for over a week now, >> just have this boot problem. >> >> >> -------------- >> >> Here is my fstab: >> >> /dev/ad0s1b none swap sw 0 0 >> /dev/ad0s1a / ufs rw 1 1 >> >> -------------- >> >> Output from bsdlabel >> # bsdlabel ad0s1 >> >> # /dev/ad0s1: >> 8 partitions: >> # size offset fstype [fsize bsize bps/cpg] >> a: 585018626 1048576 4.2BSD 2048 16384 28552 >> b: 1048576 0 swap >> c: 586067202 0 unused 0 0 # "raw" part, >> don't edit > > > Could it be because your root partition is not at offset 0? > > Eric > > I don't think so, but I certainly could be wrong. Here is another system: # bsdlabel ad0s1 # /dev/ad0s1: 8 partitions: # size offset fstype [fsize bsize bps/cpg] a: 18932866 137363456 4.2BSD 2048 16384 28552 b: 1048576 0 swap c: 156296322 0 unused 0 0 # "raw" part, don't edit d: 62914560 1048576 4.2BSD 2048 16384 28552 e: 73400320 63963136 4.2BSD 2048 16384 28544 here s1a is not at offset 0, yet the system boots fine. I create the swap partition first usually, hence the offset being 0 for swap. David
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4648845D.4040608>