FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Debian > Debian User

 
 
LinkBack Thread Tools
 
Old 04-05-2008, 07:14 PM
Butch Kemper
 
Default Disk Drive Order Changes - Again

Back in February, I asked a question about problems I was having with
the hard disks sequence flip-flopping when I would boot: disk #1
would be hda and disk #2 would be hdc; or disk #1 would be hde and
disk #2 would be hda.


I receive answers about using labels with the partitions so, I
labeled the partitions and updated /etc/fstab. This is how things now look:


IDE #1 Partition Label Mount Point
1 / /
2 swap1 swap file
3 /usr /usr
4
5 /usr/local /usr/local
6 /var /var

IDE #2 Partition Label Mount Point
1 /var/poptemp /var/poptemp
2 /var/mail /var/mail

The /etc/fstab:

# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc defaults 0 0
LABEL=/ / ext3 defaults,errors=remount-ro 0 1
LABEL=/usr /usr ext3 defaults 0 2
LABEL=/usr/local /usr/local ext3 defaults 0 2
LABEL=/var /var ext3 defaults 0 2
LABEL=/var/poptemp /var/poptemp ext3 defaults 0 2
LABEL=/var/mail /var/mail ext3 defaults 0 2
LABEL=swap1 none swap sw 0 0

Now the partitions and mount points get assigned correctly no matter
which order the drives are assigned.


The remaining problem is with the GRUB and the kernel. It was
suggested that a LABEL specification be placed in the
/boot/grub/menu.1st entry so that:


# kopt=root=/dev/hda1 becomes
# kopt=root=LABEL=/

Using a LABEL in the Grub menu does not work because the kernel get confused:

1. If kopt=root=/dev/hda1 and the disk order changes to make
the boot disk be /dev/hde, the boot process stops and drops
into a prompt. I can unmount /boot, mount /boot on the
correct drive, give a CTL-D to the prompt, and the system
would continue to boot.

2. If kopt=root=LABEL=/, the boot process will stop and drop
into a prompt WITHOUT /boot being mounted. I can mount
/boot on the correct drive, give a CTL-D to the prompt,
and the system will continue to boot.

No where have I been able to find any documentation that shows that
the Kernel boot command root= can have a LABEL specified.


So, how do I make the kernel consistently detect and assign the disks
in the correct order? Someone suggested the problem lies with UDEV
and the parallel hardware detection process.


Thanks for any suggestions.

Butch


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
 
Old 04-05-2008, 07:23 PM
Alex Samad
 
Default Disk Drive Order Changes - Again

On Sat, Apr 05, 2008 at 02:14:17PM -0500, Butch Kemper wrote:
> Back in February, I asked a question about problems I was having with
> the hard disks sequence flip-flopping when I would boot: disk #1 would be
> hda and disk #2 would be hdc; or disk #1 would be hde and disk #2 would
> be hda.
>
> I receive answers about using labels with the partitions so, I labeled
> the partitions and updated /etc/fstab. This is how things now look:
>
> IDE #1 Partition Label Mount Point
> 1 / /
> 2 swap1 swap file
> 3 /usr /usr
> 4
> 5 /usr/local /usr/local
> 6 /var /var
>
> IDE #2 Partition Label Mount Point
> 1 /var/poptemp /var/poptemp
> 2 /var/mail /var/mail
>
> The /etc/fstab:
>
> # <file system> <mount point> <type> <options> <dump> <pass>
> proc /proc proc defaults 0 0
> LABEL=/ / ext3 defaults,errors=remount-ro 0 1
> LABEL=/usr /usr ext3 defaults 0 2
> LABEL=/usr/local /usr/local ext3 defaults 0 2
> LABEL=/var /var ext3 defaults 0 2
> LABEL=/var/poptemp /var/poptemp ext3 defaults 0 2
> LABEL=/var/mail /var/mail ext3 defaults 0 2
> LABEL=swap1 none swap sw 0 0
>
> Now the partitions and mount points get assigned correctly no matter
> which order the drives are assigned.
>
> The remaining problem is with the GRUB and the kernel. It was suggested
> that a LABEL specification be placed in the /boot/grub/menu.1st entry so
> that:
>
> # kopt=root=/dev/hda1 becomes
> # kopt=root=LABEL=/
did you do an update-initramfs to build a new initrd ?

>
> Using a LABEL in the Grub menu does not work because the kernel get confused:
>
> 1. If kopt=root=/dev/hda1 and the disk order changes to make
> the boot disk be /dev/hde, the boot process stops and drops
> into a prompt. I can unmount /boot, mount /boot on the
> correct drive, give a CTL-D to the prompt, and the system
> would continue to boot.
>
> 2. If kopt=root=LABEL=/, the boot process will stop and drop
> into a prompt WITHOUT /boot being mounted. I can mount
> /boot on the correct drive, give a CTL-D to the prompt,
> and the system will continue to boot.
>
> No where have I been able to find any documentation that shows that the
> Kernel boot command root= can have a LABEL specified.
>
> So, how do I make the kernel consistently detect and assign the disks in
> the correct order? Someone suggested the problem lies with UDEV and the
> parallel hardware detection process.
>
> Thanks for any suggestions.
>
> Butch
>
>
> --
> To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org with a
> subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
>
>

--
birth, n:
The first and direst of all disasters.
-- Ambrose Bierce, "The Devil's Dictionary"
 
Old 04-05-2008, 08:23 PM
Steve Kemp
 
Default Disk Drive Order Changes - Again

On Sun Apr 06, 2008 at 05:23:45 +1000, Alex Samad wrote:

> did you do an update-initramfs to build a new initrd ?

If you *must* reply to a post with only a single line
of new text please have the decency to trim the message,
rather than quoting it in its entirety.

Steve
--
http://www.steve.org.uk/


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
 
Old 04-05-2008, 10:06 PM
Andrew Sackville-West
 
Default Disk Drive Order Changes - Again

On Sat, Apr 05, 2008 at 02:14:17PM -0500, Butch Kemper wrote:
> Back in February, I asked a question about problems I was having with
> the hard disks sequence flip-flopping when I would boot: disk #1 would be
> hda and disk #2 would be hdc; or disk #1 would be hde and disk #2 would
> be hda.
>
> I receive answers about using labels with the partitions so, I labeled
> the partitions and updated /etc/fstab. This is how things now look:
>
> IDE #1 Partition Label Mount Point
> 1 / /
> 2 swap1 swap file
> 3 /usr /usr
> 4
> 5 /usr/local /usr/local
> 6 /var /var
>
> IDE #2 Partition Label Mount Point
> 1 /var/poptemp /var/poptemp
> 2 /var/mail /var/mail
>
> The /etc/fstab:
>
> # <file system> <mount point> <type> <options> <dump> <pass>
> proc /proc proc defaults 0 0
> LABEL=/ / ext3 defaults,errors=remount-ro 0 1


>
> # kopt=root=/dev/hda1 becomes
> # kopt=root=LABEL=/

I think Alex is right, that you should rebuild the initrd. But the
other thought that occurs to me is perhaps using "/" as a label
is a problem.

.02

A
 
Old 04-05-2008, 10:28 PM
Alex Samad
 
Default Disk Drive Order Changes - Again

On Sat, Apr 05, 2008 at 03:06:09PM -0700, Andrew Sackville-West wrote:
> On Sat, Apr 05, 2008 at 02:14:17PM -0500, Butch Kemper wrote:
[snip]>
> >
> > # kopt=root=/dev/hda1 becomes
> > # kopt=root=LABEL=/
>
> I think Alex is right, that you should rebuild the initrd. But the
> other thought that occurs to me is perhaps using "/" as a label
> is a problem.
I have been using / as a label for a while with no problems
>
> .02
>
> A



--
An apple a day makes 365 apples a year.
 
Old 04-05-2008, 10:40 PM
Andrew Sackville-West
 
Default Disk Drive Order Changes - Again

On Sun, Apr 06, 2008 at 08:28:16AM +1000, Alex Samad wrote:
> On Sat, Apr 05, 2008 at 03:06:09PM -0700, Andrew Sackville-West wrote:
> > On Sat, Apr 05, 2008 at 02:14:17PM -0500, Butch Kemper wrote:
> [snip]>
> > >
> > > # kopt=root=/dev/hda1 becomes
> > > # kopt=root=LABEL=/
> >
> > I think Alex is right, that you should rebuild the initrd. But the
> > other thought that occurs to me is perhaps using "/" as a label
> > is a problem.

> I have been using / as a label for a while with no problems

Fair enough. just a thought. BTW, it's darn hard to find your
responses with no whitespace around them...

A
 
Old 04-06-2008, 04:17 PM
Hugo Vanwoerkom
 
Default Disk Drive Order Changes - Again

Butch Kemper wrote:
Back in February, I asked a question about problems I was having with
the hard disks sequence flip-flopping when I would boot: disk #1 would
be hda and disk #2 would be hdc; or disk #1 would be hde and disk #2
would be hda.


I receive answers about using labels with the partitions so, I labeled
the partitions and updated /etc/fstab. This is how things now look:


IDE #1 Partition Label Mount Point
1 / /
2 swap1 swap file
3 /usr /usr
4
5 /usr/local /usr/local
6 /var /var

IDE #2 Partition Label Mount Point
1 /var/poptemp /var/poptemp
2 /var/mail /var/mail

The /etc/fstab:

# <file system> <mount point> <type> <options> <dump>
<pass>

proc /proc proc defaults 0 0
LABEL=/ / ext3 defaults,errors=remount-ro 0 1
LABEL=/usr /usr ext3 defaults 0 2
LABEL=/usr/local /usr/local ext3 defaults 0 2
LABEL=/var /var ext3 defaults 0 2
LABEL=/var/poptemp /var/poptemp ext3 defaults 0 2
LABEL=/var/mail /var/mail ext3 defaults 0 2
LABEL=swap1 none swap sw 0 0

Now the partitions and mount points get assigned correctly no matter
which order the drives are assigned.


The remaining problem is with the GRUB and the kernel. It was suggested
that a LABEL specification be placed in the /boot/grub/menu.1st entry so
that:


# kopt=root=/dev/hda1 becomes
# kopt=root=LABEL=/

Using a LABEL in the Grub menu does not work because the kernel get
confused:


1. If kopt=root=/dev/hda1 and the disk order changes to make
the boot disk be /dev/hde, the boot process stops and drops
into a prompt. I can unmount /boot, mount /boot on the
correct drive, give a CTL-D to the prompt, and the system
would continue to boot.

2. If kopt=root=LABEL=/, the boot process will stop and drop
into a prompt WITHOUT /boot being mounted. I can mount
/boot on the correct drive, give a CTL-D to the prompt,
and the system will continue to boot.

No where have I been able to find any documentation that shows that the
Kernel boot command root= can have a LABEL specified.





# kopt=root=LABEL=wd80_0jd-60.05 ro noapic vga=791 apm=on ddcon=1
network quiet


WFM

but you are still stuck with the GRUB root command, which does not
accept a label.

So I changed grub (0.97-29) to accept this:


find /ST380011A.03
root FILE=/ST380011A.03


and then where he finds file ST380011A.03 that is where the root will be.

Now I have a truly LABEL driven system and the drive devices can be
wherever they are and I don't care...


Hugo


So, how do I make the kernel consistently detect and assign the disks in
the correct order? Someone suggested the problem lies with UDEV and the
parallel hardware detection process.





--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
 
Old 04-07-2008, 01:52 AM
Butch Kemper
 
Default Disk Drive Order Changes - Again

At 11:17 AM 4/6/2008, Hugo Vanwoerkom wrote:

Butch Kemper wrote:
Back in February, I asked a question about problems I was having
with the hard disks sequence flip-flopping when I would boot: disk
#1 would be hda and disk #2 would be hdc; or disk #1 would be hde
and disk #2 would be hda.
I receive answers about using labels with the partitions so, I
labeled the partitions and updated /etc/fstab. This is how things now look:

IDE #1 Partition Label Mount Point
1 / /
2 swap1 swap file
3 /usr /usr
4
5 /usr/local /usr/local
6 /var /var
IDE #2 Partition Label Mount Point
1 /var/poptemp /var/poptemp
2 /var/mail /var/mail
The /etc/fstab:
# <file system> <mount point> <type> <options> <dump>
<pass>
proc /proc proc defaults 0 0
LABEL=/ / ext3 defaults,errors=remount-ro 0 1
LABEL=/usr /usr ext3 defaults 0 2
LABEL=/usr/local /usr/local ext3 defaults 0 2
LABEL=/var /var ext3 defaults 0 2
LABEL=/var/poptemp /var/poptemp ext3 defaults 0 2
LABEL=/var/mail /var/mail ext3 defaults 0 2
LABEL=swap1 none swap sw 0 0
Now the partitions and mount points get assigned correctly no
matter which order the drives are assigned.
The remaining problem is with the GRUB and the kernel. It was
suggested that a LABEL specification be placed in the
/boot/grub/menu.1st entry so that:

# kopt=root=/dev/hda1 becomes
# kopt=root=LABEL=/
Using a LABEL in the Grub menu does not work because the kernel get confused:
1. If kopt=root=/dev/hda1 and the disk order changes to make
the boot disk be /dev/hde, the boot process stops and drops
into a prompt. I can unmount /boot, mount /boot on the
correct drive, give a CTL-D to the prompt, and the system
would continue to boot.
2. If kopt=root=LABEL=/, the boot process will stop and drop
into a prompt WITHOUT /boot being mounted. I can mount
/boot on the correct drive, give a CTL-D to the prompt,
and the system will continue to boot.
No where have I been able to find any documentation that shows that
the Kernel boot command root= can have a LABEL specified.



# kopt=root=LABEL=wd80_0jd-60.05 ro noapic vga=791 apm=on ddcon=1
network quiet


WFM

but you are still stuck with the GRUB root command, which does not
accept a label.

So I changed grub (0.97-29) to accept this:


find /ST380011A.03
root FILE=/ST380011A.03


and then where he finds file ST380011A.03 that is where the root will be.

Now I have a truly LABEL driven system and the drive devices can be
wherever they are and I don't care...


Hugo


So, how do I make the kernel consistently detect and assign the
disks in the correct order? Someone suggested the problem lies
with UDEV and the parallel hardware detection process.


Hugo,

I understand the "find" command and the results that it returns. But
I am unable to locate any mention of the "root" command having a
"FILE=" option.


So, did you modify Grub to make the "root" command have a FILE= parameter?

Butch


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
 
Old 04-08-2008, 01:33 PM
Hugo Vanwoerkom
 
Default Disk Drive Order Changes - Again

Butch Kemper wrote:

At 11:17 AM 4/6/2008, Hugo Vanwoerkom wrote:

Butch Kemper wrote:
Back in February, I asked a question about problems I was having with
the hard disks sequence flip-flopping when I would boot: disk #1
would be hda and disk #2 would be hdc; or disk #1 would be hde and
disk #2 would be hda.
I receive answers about using labels with the partitions so, I
labeled the partitions and updated /etc/fstab. This is how things
now look:

IDE #1 Partition Label Mount Point
1 / /
2 swap1 swap file
3 /usr /usr
4
5 /usr/local /usr/local
6 /var /var
IDE #2 Partition Label Mount Point
1 /var/poptemp /var/poptemp
2 /var/mail /var/mail
The /etc/fstab:
# <file system> <mount point> <type> <options> <dump>
<pass>
proc /proc proc defaults
0 0
LABEL=/ / ext3 defaults,errors=remount-ro
0 1
LABEL=/usr /usr ext3 defaults
0 2
LABEL=/usr/local /usr/local ext3 defaults
0 2
LABEL=/var /var ext3 defaults
0 2
LABEL=/var/poptemp /var/poptemp ext3 defaults
0 2
LABEL=/var/mail /var/mail ext3 defaults
0 2
LABEL=swap1 none swap sw
0 0
Now the partitions and mount points get assigned correctly no matter
which order the drives are assigned.
The remaining problem is with the GRUB and the kernel. It was
suggested that a LABEL specification be placed in the
/boot/grub/menu.1st entry so that:

# kopt=root=/dev/hda1 becomes
# kopt=root=LABEL=/
Using a LABEL in the Grub menu does not work because the kernel get
confused:

1. If kopt=root=/dev/hda1 and the disk order changes to make
the boot disk be /dev/hde, the boot process stops and drops
into a prompt. I can unmount /boot, mount /boot on the
correct drive, give a CTL-D to the prompt, and the system
would continue to boot.
2. If kopt=root=LABEL=/, the boot process will stop and drop
into a prompt WITHOUT /boot being mounted. I can mount
/boot on the correct drive, give a CTL-D to the prompt,
and the system will continue to boot.
No where have I been able to find any documentation that shows that
the Kernel boot command root= can have a LABEL specified.



# kopt=root=LABEL=wd80_0jd-60.05 ro noapic vga=791 apm=on ddcon=1
network quiet


WFM

but you are still stuck with the GRUB root command, which does not
accept a label.

So I changed grub (0.97-29) to accept this:


find /ST380011A.03
root FILE=/ST380011A.03


and then where he finds file ST380011A.03 that is where the root will be.

Now I have a truly LABEL driven system and the drive devices can be
wherever they are and I don't care...


Hugo


So, how do I make the kernel consistently detect and assign the disks
in the correct order? Someone suggested the problem lies with UDEV
and the parallel hardware detection process.


Hugo,

I understand the "find" command and the results that it returns. But I
am unable to locate any mention of the "root" command having a "FILE="
option.


So, did you modify Grub to make the "root" command have a FILE= parameter?



Right. FIND saves where it found the file and root with FILE= uses that
saved info. So I don't have to specify absolute locations. I can send
the diff if you tell me where.


Hugo






--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
 
Old 04-08-2008, 02:56 PM
steef
 
Default Disk Drive Order Changes - Again

Hugo Vanwoerkom wrote:

Butch Kemper wrote:

At 11:17 AM 4/6/2008, Hugo Vanwoerkom wrote:

Butch Kemper wrote:


hugo wrote

but you are still stuck with the GRUB root command, which does not
accept a label.

So I changed grub (0.97-29) to accept this:


find /ST380011A.03
root FILE=/ST380011A.03


and then where he finds file ST380011A.03 that is where the root
will be.


Now I have a truly LABEL driven system and the drive devices can be
wherever they are and I don't care...


Hugo



Hugo,

I understand the "find" command and the results that it returns. But
I am unable to locate any mention of the "root" command having a
"FILE=" option.


So, did you modify Grub to make the "root" command have a FILE=
parameter?




Right. FIND saves where it found the file and root with FILE= uses
that saved info. So I don't have to specify absolute locations. I can
send the diff if you tell me where.


Hugo




i'll remember this one! learned something nifty again.

thanks, lads,

steef


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
 

Thread Tools




All times are GMT. The time now is 06:36 AM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright 2007 - 2008, www.linux-archive.org