As I've said several times, it's UUID or LABEL. Period.
And then there's LVM. I recommend LVM as the solution to this problem
because contrary to the UUID the name can be meaningful, and contrary to
the LABEL, the LVM volume names don't depend on the kind of file-system
you use. Also those
On Wed, 08 May 2013 21:21:13 -0400 (EDT), Tong wrote:
All I was asking is what the working *syntax* for the
root=ID=ata-IBM-DBCA-203240_HP0HPL43952 part.
You can't use ID with root. With boot, you can, but not
with root. Not if you want a driver-independent and
discover-order-independent
Bob Proulx wrote:
One simple question, though: if you have 2 similar HDDs and one
of them starts to fail, how do you know which one it is?
I assume you mean which physical disk is which?
There are useful tools hdparm, smartctl, blkid, lsblk and probably
others too.
# hdparm -I /dev/sda
fdisk also gives some disk id.
You can also use boot script like this to static numerize your drives:
rm /dev/myhdd-0 /dev/myhdd-1
m=`cat /sys/block/sda/device/model`
if test $m = HDD0MODEL; then
ln -s sda /dev/myhdd-0
ln -s sdb /dev/myhdd-1
else
ln -s sdb /dev/myhdd-0
ln -s
On 05/09/2013 07:10 AM, st wrote:
Stefan Monnier wrote:
I see many people suggested UUIDs and other funny long names.
What I use instead: LVM. This way you get to name the disks and
partitions with meaningful names which only change when you decide to
change them.
One simple question,
On Thu, 2013-05-09 at 01:21 +, T o n g wrote:
On Wed, 08 May 2013 08:40:57 -0400, Stephen Powell wrote:
Can I use something like root=ID=ata-IBM-DBCA-203240_HP0HPL43952? I
remember nothing worked well, so I reverted to the (now troublesome)
safe /dev/sdXn.
/dev/sdXn is *not*
On Wed, May 08, 2013 at 03:28:47AM +, T o n g wrote:
Can I use something like root=ID=ata-IBM-DBCA-203240_HP0HPL43952? I
remember nothing worked well, so I reverted to the (now troublesome)
safe /dev/sdXn.
I think the idea is to replace /dev/sdXn with e.g.
On Tue, 07 May 2013 23:28:47 -0400 (EDT), Tong wrote:
On Tue, 07 May 2013 07:55:24 -0400, Stephen Powell wrote:
This problem, and its solution, are discussed at length on my LILO web
page, starting with the discussion of the boot configuration file
record.
On Wed, 08 May 2013 08:40:57 -0400, Stephen Powell wrote:
Can I use something like root=ID=ata-IBM-DBCA-203240_HP0HPL43952? I
remember nothing worked well, so I reverted to the (now troublesome)
safe /dev/sdXn.
/dev/sdXn is *not* safe. That's the whole point.
If you read my message again,
T o n g wrote:
I don't like using UUID, because, just as you said:
Warning: reformatting a partition normally changes the uuid, unless the
existing uuid is explicitly specified as an option when formatting. Thus,
commands such as mkfs (and its derivatives) and mkswap will normally
Anyone know the cure?
I see many people suggested UUIDs and other funny long names.
What I use instead: LVM. This way you get to name the disks and
partitions with meaningful names which only change when you decide to
change them.
Stefan
--
To UNSUBSCRIBE, email to
Stefan Monnier wrote:
I see many people suggested UUIDs and other funny long names.
What I use instead: LVM. This way you get to name the disks and
partitions with meaningful names which only change when you decide to
change them.
One simple question, though: if you have 2 similar HDDs and
st wrote:
Stefan Monnier wrote:
I see many people suggested UUIDs and other funny long names. What I
use instead: LVM. This way you get to name the disks and
partitions with meaningful names which only change when you decide
to change them.
One simple question, though: if you have 2
Use either partition labels or UUIDs when specifying block devices
in e.g. /etc/fstab.
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20130507091507.GA20902@debian
On Mon, 06 May 2013 23:28:01 -0400 (EDT), Tong wrote:
Recently I added an old PATA HD to my system, which previously consist of
two SATA HDs. Ever since then, the order of my SATA and PATA are keep
switching.
This problem, and its solution, are discussed at length on my LILO web
page,
On Tue, 07 May 2013 07:55:24 -0400 (EDT), Stephen Powell wrote:
Basically, use udev-created symbolic links in /etc/fstab,
/etc/initramfs/conf.d/resume, and your boot loader.
Oops! I meant to say /etc/initramfs-tools/conf.d/resume,
not /etc/initramfs/conf.d/resume.
--
.''`. Stephen
On Tue, 07 May 2013 07:55:24 -0400, Stephen Powell wrote:
Recently I added an old PATA HD to my system, which previously consist
of two SATA HDs. Ever since then, the order of my SATA and PATA are
keep switching.
This problem, and its solution, are discussed at length on my LILO web
page,
Hi,
Recently I added an old PATA HD to my system, which previously consist of
two SATA HDs. Ever since then, the order of my SATA and PATA are keep
switching.
NB, it is not that I can't boot, I can boot just fine, but half of the
time the boot process will drop to that single user PANIC
18 matches
Mail list logo