Date: Mon, 28 May 2007 12:35:25 -0400 (CLT) From: "Daniel Molina Wegener" <dmw@unete.cl> To: "WarrenHead" <warrenhead@gmail.com> Cc: freebsd-questions@freebsd.org Subject: Re: machine will no longer boot Message-ID: <43243.64.117.137.69.1180370125.squirrel@webmail.ifxnw.cl> In-Reply-To: <465AFDBB.8050304@gmail.com> References: <465AFDBB.8050304@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Hello,
Try booting from a FreeBSD Install CD, load the needed modules before
booting the kernel, start the sysinstall. From sysinstall in the Install
CD, start a "Fixit" shell. From the shell set the partitions booteable and
write changes. Do not resize or apply newfs to the partitions, just set
booteable and write the partition info. Mount your / slice, and install
the BTX loader into the MBR using:
boot0cfg -vB -b /boot/boot0 /dev/TheDiskDevice
That works for me on my SATA disks.
Regards
DMW
El Lun, 28 de Mayo de 2007, 12:05, WarrenHead escribió:
> Hi list,
>
> Yesterday I installed a new sata disk into my server, which is connected
> to a highpoint rocket raid card. I plugged in only one disk, so no raid yet.
>
> I ran sysinstall and then fdisk and disklabel. All was fine and I placed
> files onto the disk. Then I realized I had made a mistake, I had made
> only one partition with fdisk, and two slices with disklabel.
> (Mountpoints pointing to /mnt/x and /mnt/y.)
> Somehow I got another mountpoint automatically which mounted the entire
> disk as one, to /media/z. Weird.
>
> So I ran sysinstall again and used fdisk to erase everything and create
> two partitions. I wrote these changes successfully to the disk.
>
> I then started disklabel (still from within sysinstall) and created the
> two mount points for the two partitions again.
> I tried to write these changes to the disk, but that failed.
>
> Mmm, weird. So, perhaps I needed to reboot first?
> Which I did, and now I cannot boot anymore.
>
> The error messages that show on screen are something like this:
> Can't stat /dev/ad4sd1 No such file or directory
> Can't stat /dev/ad4se1 No such file or directory
> After that I get a bogus shell which can do virtually nothing. I have no
> idea what it is.
> I can cat /etc/fstab though and noticed that the two lines with
> mountpoints for the new disk are indeed the new lines. I guess disklabel
> was partially succesfull?
>
> Perhaps I should simply remove these lines in /etc/fstab?
> Unfortunately, with this ridiculous shell, I don't know how to.
>
> So I tried a livecd (Knoppix 5.1). Since the system disk was formatted
> as ufstype=5xbsd, I have trouble writing to it. Bummer.
>
> But... should I remove these lines in /etc/fstab? Will this matter?
>
> Luckily I can read the disk, so if necessary I can start over, but I
> hope there is something I can do from within that odd shell.
>
> Please advise, this particular problem is not fun.
>
> Cheers, Warren
> _______________________________________________
> freebsd-questions@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org"
>
--
.O. | Daniel Molina Wegener | C/C++ Developer
..O | dmw [at] unete [dot] cl | FOSS Coding Adict
OOO | BSD & Linux User | Standards Rocks!
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?43243.64.117.137.69.1180370125.squirrel>