From: Justin Piszcz <jpiszcz@lucidpixels.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org, xfs@oss.sgi.com
Subject: Re: Switching from (deprecated) IDE driver -> SATA (PATA support) (found solution)
Date: Sun, 25 Jan 2009 07:55:46 -0500 (EST) [thread overview]
Message-ID: <alpine.DEB.1.10.0901250752020.11258@p34.internal.lan> (raw)
In-Reply-To: <alpine.DEB.1.10.0901250740360.11258@p34.internal.lan>
On Sun, 25 Jan 2009, Justin Piszcz wrote:
>
>
> On Sun, 25 Jan 2009, Justin Piszcz wrote:
>
>>
>>
>> On Sun, 25 Jan 2009, Justin Piszcz wrote:
>>
>>>
>>>
>>> On Sun, 25 Jan 2009, Justin Piszcz wrote:
>>>
>>>>
>>>>
>>>> On Sun, 25 Jan 2009, Alan Cox wrote:
root=<root-device>
This specifies the device that should be mounted as root. It
may be specified as a global option. If the special name cur-
rent is used, the root device is set to the device on which the
root file system is currently mounted. If the root has been
changed with -r , the respective device is used. If the vari-
able `root' is omitted, the root device setting contained in the
kernel image is used. (And that is set at compile time using
the ROOT_DEV variable in the kernel Makefile, and can later be
changed with the rdev(8) program.)
Change root= to root=current && lilo && reboot, this works as well, note I did
have the proper UUIDs set in /etc/fstab before doing this.
Trying without changing /etc/fstab, back to old entries:
/dev/hda2 / xfs noatime 0 1
/dev/hda1 none swap sw 0 0
#UUID=77ae4251-631f-4656-a365-c5723f5c5da8 / xfs noatime 0 1
#UUID=2ef862e1-cf78-4065-a205-d1784716d633 none swap sw 0 0
(which are wrong)
p254:~# df -h
Filesystem Size Used Avail Use% Mounted on
/dev/sdd2 73G 2.2G 71G 3% /
p254:~# df -h
But using current!
p254:~# grep current /etc/lilo.conf
# case it installs in the MBR, and will overwrite the current MBR.
root=current
root=current
p254:~#
p254:~# reboot
Does it come back?
$ uptime
07:55:16 up 0 min, 1 user, load average: 0.71, 0.20, 0.07
Yes it does, so the work-around is to use root=current, fix up your /etc/fstab
and other files after.
Justin.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2009-01-25 12:56 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <alpine.DEB.1.10.0901250553430.2441@p34.internal.lan>
[not found] ` <20090125110742.4ba54c0b@lxorguk.ukuu.org.uk>
2009-01-25 12:09 ` Switching from (deprecated) IDE driver -> SATA (PATA support) Justin Piszcz
2009-01-25 12:15 ` Justin Piszcz
2009-01-25 12:28 ` Justin Piszcz
2009-01-25 12:41 ` Justin Piszcz
2009-01-25 12:55 ` Justin Piszcz [this message]
2009-01-25 13:08 ` Switching from (deprecated) IDE driver -> SATA (PATA support) (found solution (scratch that)) Justin Piszcz
2009-01-25 13:15 ` Michael Tokarev
2009-01-25 15:45 ` Switching from (deprecated) IDE driver -> SATA (PATA support) Eric Sandeen
[not found] ` <alpine.DEB.1.10.0901250726530.10805__44823.8515914001$1232890466$gmane$org@p34.internal.lan>
2009-01-25 21:13 ` Bill Davidsen
2009-01-25 21:14 ` Justin Piszcz
2009-01-29 23:44 ` Bill Davidsen
2009-01-26 22:02 ` Lennart Sorensen
2009-01-26 23:36 ` Sergei Shtylyov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.DEB.1.10.0901250752020.11258@p34.internal.lan \
--to=jpiszcz@lucidpixels.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=xfs@oss.sgi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox