[prev in list] [next in list] [prev in thread] [next in thread] 

List:       linux-ppc
Subject:    Re: partition check stick
From:       Randall R Schulz <rrschulz () cris ! com>
Date:       1999-11-20 6:59:01
[Download RAW message or body]


Paul,

You've run afoul of the manner in which Linux assigns SCSI disks to 
/dev entries. /dev entries are assigned according to the order in 
which SCSI disks are found on a given bus. If you add a new drive at 
a lower SCSI ID, it will affect all the Linux device names.

The upshot is, simply: don't do that! Add new drives only at higher 
SCSI ID numbers than that of all other SCSI drives on a given bus and 
save yourself the trouble.

If there's a compelling reason to add a new drive at a lower SCSI ID, 
then you'll have to change your /etc/fstab and your BootX arguments 
and anything else that contains logical drive names (as in /dev/sdX 
or /dev/sdXnn).

Randy Schulz
Mountain View, CA USA


At 01:19 -0500 11/20/99, Paul Santa Clara wrote:
>This is a funny one.  I keep my root filesystem on what used to be my only
>SCSI hard disk(an external).  Earlier today, I added another SCSI hard disk
>at a lower SCSI ID,this time in my one of machine's drive bays, and
>although the MacOS seems to fine with it, Linux gets caught in a loop of
>"mesh" errors during the partition check phase of its boot up.  I adjusted
>by root partition from sda to sdb(reasoning that the new drive is now
>sda)but linux still insists on doing a partition check for sda, and of
>course hangs when it tries.
>
>Are there perhaps kernel arguments that I can pass to force linux to ignore
>sda?
>
>Thanks,
>-Paul
>


** Sent via the linuxppc-user mail list. See http://lists.linuxppc.org/

[prev in list] [next in list] [prev in thread] [next in thread]