installed ATA RAID, now cannot boot - get mountroot prompt

LiQuiD liquid at homebass.ca
Wed Aug 25 11:07:18 PDT 2004


I'm by no means an expert, and thus the reason for my "crude and
unscientific" solution that I'm proposing

Seeing as you now know what it'll turn into upon adding this RAID card
to your system, why don't you try the "crude" method of undoing
everything, booting successfully, and then editing /etc/fstab
accordingly just prior to shutting it back down to allow for a
successful boot once you put the new hardware back in?

The link to the FAQ mentioned below won't work for this scenario IMO
because his /etc/fstab is currently inaccurate.  Merely typing mount /
would still generate an error.  You could however type mount /dev/da0s1e
/ perhaps to get what you want though.

> -----Original Message-----
> From: owner-freebsd-questions at freebsd.org [mailto:owner-freebsd-
> questions at freebsd.org] On Behalf Of Lowell Gilbert
> Sent: Wednesday, August 25, 2004 12:15 PM
> To: iwrTech at iwr.ru.ac.za
> Cc: freebsd-questions at freebsd.org
> Subject: Re: installed ATA RAID, now cannot boot - get mountroot
prompt
> 
> "DA Forsyth" <iwrTech at iwr.ru.ac.za> writes:
> 
> > I'm searching the web for answers on this too, but so far nothing
> > useful.  hard to know what question to ask the search engines!
> 
> "I made a mistake in rc.conf, or another startup file, and now I
> cannot edit it because the filesystem is read-only. What should I do?"
>
http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/admin.html#RCCONF-
> READONLY
> _______________________________________________
> freebsd-questions at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to "freebsd-questions-
> unsubscribe at freebsd.org"



More information about the freebsd-questions mailing list