Hi, I had a machine running RH9 and a 120GB SATA HDD. The HDD was ailing and occassionally giving out sector not found {Drive ready,Seek failure} errors. So i thought it was time to move in to FC3 and a new 160GB SATA HDD.
Bootup of FC3 gave me a kernel crash, and an error complaining about suggesting acpi=off, but even with acpi=off, still gave me the same warning and a crash..
I then later on figured that the SATA Enhanced mode operation would be a problem and switched it to compatibility mode. The motherboard is an ASUS P4C800, Intel 875 chipset.. Lo it worked....
That went fine through.... No problems even though initially i thought not to edit /etc/fstab by hand because it was generated by fstab-sync ? I went on to edit it by hand...
Everything went smoothly...
Now i figured that i required some files more were there on the old HDD, than compared to the backup i had...
I plugged in the OLD SATA HDD has Primary Slave, and the NEW SATA HDD as Primary master.
The initscripts failed stating about duplicate LABEL=/, LABEL=/boot, LABEL=/work...
and a hung system...
I know that if i modify the disklabels to actual device names my problems would be solved...
But, what i would like to know is whether a graceful way of doing it exists, without much hassle... I know that this is not much of an issue, but still thought it would be better if i posted the problem...
Manu
søn, 12.12.2004 kl. 13.16 skrev Manu Abraham:
Hi, I had a machine running RH9 and a 120GB SATA HDD. The HDD was ailing and occassionally giving out sector not found {Drive ready,Seek failure} errors. So i thought it was time to move in to FC3 and a new 160GB SATA HDD.
Bootup of FC3 gave me a kernel crash, and an error complaining about suggesting acpi=off, but even with acpi=off, still gave me the same warning and a crash..
I then later on figured that the SATA Enhanced mode operation would be a problem and switched it to compatibility mode. The motherboard is an ASUS P4C800, Intel 875 chipset.. Lo it worked....
That went fine through.... No problems even though initially i thought not to edit /etc/fstab by hand because it was generated by fstab-sync ? I went on to edit it by hand...
Everything went smoothly...
Now i figured that i required some files more were there on the old HDD, than compared to the backup i had...
I plugged in the OLD SATA HDD has Primary Slave, and the NEW SATA HDD as Primary master.
The initscripts failed stating about duplicate LABEL=/, LABEL=/boot, LABEL=/work...
and a hung system...
I know that if i modify the disklabels to actual device names my problems would be solved...
But, what i would like to know is whether a graceful way of doing it exists, without much hassle... I know that this is not much of an issue, but still thought it would be better if i posted the problem...
Manu
Comment out the lines, add new lines for the same stuff. Then plug it in, boot, mount the volumes, copy the stuff, shutdown, unplug, and uncomment the lines again.
On Sun December 12 2004 4:45 pm, Kyrre Ness Sjobak wrote:
søn, 12.12.2004 kl. 13.16 skrev Manu Abraham:
Hi, I had a machine running RH9 and a 120GB SATA HDD. The HDD was ailing and occassionally giving out sector not found {Drive ready,Seek failure} errors. So i thought it was time to move in to FC3 and a new 160GB SATA HDD.
Bootup of FC3 gave me a kernel crash, and an error complaining about suggesting acpi=off, but even with acpi=off, still gave me the same warning and a crash..
I then later on figured that the SATA Enhanced mode operation would be a problem and switched it to compatibility mode. The motherboard is an ASUS P4C800, Intel 875 chipset.. Lo it worked....
That went fine through.... No problems even though initially i thought not to edit /etc/fstab by hand because it was generated by fstab-sync ? I went on to edit it by hand...
Everything went smoothly...
Now i figured that i required some files more were there on the old HDD, than compared to the backup i had...
I plugged in the OLD SATA HDD has Primary Slave, and the NEW SATA HDD as Primary master.
The initscripts failed stating about duplicate LABEL=/, LABEL=/boot, LABEL=/work...
and a hung system...
I know that if i modify the disklabels to actual device names my problems would be solved...
But, what i would like to know is whether a graceful way of doing it exists, without much hassle... I know that this is not much of an issue, but still thought it would be better if i posted the problem...
Manu
Comment out the lines, add new lines for the same stuff. Then plug it in, boot, mount the volumes, copy the stuff, shutdown, unplug, and uncomment the lines again.
That's what i temporarily did to solve the problem...
Manu
søn, 12.12.2004 kl. 17.55 skrev Manu Abraham:
On Sun December 12 2004 4:45 pm, Kyrre Ness Sjobak wrote:
søn, 12.12.2004 kl. 13.16 skrev Manu Abraham:
Hi, I had a machine running RH9 and a 120GB SATA HDD. The HDD was ailing and occassionally giving out sector not found {Drive ready,Seek failure} errors. So i thought it was time to move in to FC3 and a new 160GB SATA HDD.
Bootup of FC3 gave me a kernel crash, and an error complaining about suggesting acpi=off, but even with acpi=off, still gave me the same warning and a crash..
I then later on figured that the SATA Enhanced mode operation would be a problem and switched it to compatibility mode. The motherboard is an ASUS P4C800, Intel 875 chipset.. Lo it worked....
That went fine through.... No problems even though initially i thought not to edit /etc/fstab by hand because it was generated by fstab-sync ? I went on to edit it by hand...
Everything went smoothly...
Now i figured that i required some files more were there on the old HDD, than compared to the backup i had...
I plugged in the OLD SATA HDD has Primary Slave, and the NEW SATA HDD as Primary master.
The initscripts failed stating about duplicate LABEL=/, LABEL=/boot, LABEL=/work...
and a hung system...
I know that if i modify the disklabels to actual device names my problems would be solved...
But, what i would like to know is whether a graceful way of doing it exists, without much hassle... I know that this is not much of an issue, but still thought it would be better if i posted the problem...
Manu
Comment out the lines, add new lines for the same stuff. Then plug it in, boot, mount the volumes, copy the stuff, shutdown, unplug, and uncomment the lines again.
That's what i temporarily did to solve the problem...
Manu
Sometimes, the simplest solution is the best solution :)
Kyrre Ness Sjobak wrote:
søn, 12.12.2004 kl. 17.55 skrev Manu Abraham:
On Sun December 12 2004 4:45 pm, Kyrre Ness Sjobak wrote:
søn, 12.12.2004 kl. 13.16 skrev Manu Abraham:
Hi, I had a machine running RH9 and a 120GB SATA HDD. The HDD was ailing and occassionally giving out sector not found {Drive ready,Seek failure} errors. So i thought it was time to move in to FC3 and a new 160GB SATA HDD.
Bootup of FC3 gave me a kernel crash, and an error complaining about suggesting acpi=off, but even with acpi=off, still gave me the same warning and a crash..
I then later on figured that the SATA Enhanced mode operation would be a problem and switched it to compatibility mode. The motherboard is an ASUS P4C800, Intel 875 chipset.. Lo it worked....
That went fine through.... No problems even though initially i thought not to edit /etc/fstab by hand because it was generated by fstab-sync ? I went on to edit it by hand...
Everything went smoothly...
Now i figured that i required some files more were there on the old HDD, than compared to the backup i had...
I plugged in the OLD SATA HDD has Primary Slave, and the NEW SATA HDD as Primary master.
The initscripts failed stating about duplicate LABEL=/, LABEL=/boot, LABEL=/work...
and a hung system...
I know that if i modify the disklabels to actual device names my problems would be solved...
But, what i would like to know is whether a graceful way of doing it exists, without much hassle... I know that this is not much of an issue, but still thought it would be better if i posted the problem...
Manu
Comment out the lines, add new lines for the same stuff. Then plug it in, boot, mount the volumes, copy the stuff, shutdown, unplug, and uncomment the lines again.
That's what i temporarily did to solve the problem...
Manu
Sometimes, the simplest solution is the best solution :)
I don't really understand the need for disk labels in fstab at all, in fact it has always caused me more problems while not doing anything helpful that I am aware of.
I would like to remove labels from some partitions. I have relabeled partitions but I'm not quite sure how to safely remove labels.
-Joshua
On Sun, 2004-12-12 at 12:19 -0800, Joshua Andrews wrote:
I don't really understand the need for disk labels in fstab at all, in fact it has always caused me more problems while not doing anything helpful that I am aware of.
I use them to get consistent naming for a couple of removable devices that have the same purpose but are used at different times. It's quite convenient for that kind of use. There may also be other things that cause the disk numbering to change (BIOS upgrades etc) and in that case using labels can make things just work instead of needing manual fstab fixing.
I would like to remove labels from some partitions. I have relabeled partitions but I'm not quite sure how to safely remove labels.
At least on ext2/3 I believe that there is always a filesystem label, when it's "missing" it is just set to an empty string. Any reason why just setting the label to an empty string is not good enough?
/Per
Joshua Andrews wrote:
[....SNIP....]
Sometimes, the simplest solution is the best solution :)
I don't really understand the need for disk labels in fstab at all, in fact it has always caused me more problems while not doing anything helpful that I am aware of.
I would like to remove labels from some partitions. I have relabeled partitions but I'm not quite sure how to safely remove labels.
---- # e2label /dev/sda1
# e2label /dev/sda1 /test # e2label /dev/sda1 /test # e2label /dev/sda1 "" # e2label /dev/sda1
# ----
Comment out the lines, add new lines for the same stuff. Then plug it in, boot, mount the volumes, copy the stuff, shutdown, unplug, and uncomment the lines again.
That's what i temporarily did to solve the problem...
Manu
Sometimes, the simplest solution is the best solution :)
I don't really understand the need for disk labels in fstab at all, in fact it has always caused me more problems while not doing anything helpful that I am aware of.
In fact, having disk labels is immensely helpful when adding/deleting partitions changes the partition minor numbers. With disk labels being used in fstab and grub.conf, you don't have to manually edit all the device names that have got incremented/decremented.
-- Uday
I would like to remove labels from some partitions. I have relabeled partitions but I'm not quite sure how to safely remove labels.
-Joshua
-- fedora-test-list mailing list fedora-test-list@redhat.com To unsubscribe: http://www.redhat.com/mailman/listinfo/fedora-test-list
On Thursday 16 December 2004 17:50, Uday Kumar Reddy wrote:
In fact, having disk labels is immensely helpful when adding/deleting partitions changes the partition minor numbers. With disk labels being used in fstab and grub.conf, you don't have to manually edit all the device names that have got incremented/decremented.
Surely if you add partitions you will have to edit fstab anyway. I would actually think disk-labels would be more likely to cause confusion. Can you give an example where disk-lables would help when adding a partition?
I think disk-labels are moderately (not immensely, don't exaggerate) helpful to a small proportion of Linux users. But they are confusing and annoying to a far larger number.
On Thu, 16 Dec 2004 23:25:34 +0000, Timothy Murphy tim@birdsnest.maths.tcd.ie wrote:
On Thursday 16 December 2004 17:50, Uday Kumar Reddy wrote:
In fact, having disk labels is immensely helpful when adding/deleting partitions changes the partition minor numbers. With disk labels being used in fstab and grub.conf, you don't have to manually edit all the device names that have got incremented/decremented.
Surely if you add partitions you will have to edit fstab anyway. I would actually think disk-labels would be more likely to cause confusion. Can you give an example where disk-lables would help when adding a partition?
When you have a disk label for a given partition, you don't have to worry about updating that particular entry (line) in fstab irrespective of how many partitions you have added or deleted before that particular partition on the disk. Now, if you have labels for all your partitions, /, /home, etc... you can just forget about these entries in fstab. Obviously, you have to add/delete an entry when you add/delete a partition, but you don't have to bother about the other entries; do you ever have to edit anything else (except the swap partition entry may be or when you have FAT/NTFS partitions)?
Though labels may cause trouble and confusion when you add another hard-disk, which of these happens more frequently --- adding a hard-disk (temporarily/permanently) OR partition numbers getting changed due to adding/deleting a partition? Also, the trouble caused in the latter case is much more sometimes because partition table entries not being in the disk order is very easy to overlook.
-- Uday
I think disk-labels are moderately (not immensely, don't exaggerate) helpful to a small proportion of Linux users. But they are confusing and annoying to a far larger number.
-- Timothy Murphy e-mail (<80k only): tim /at/ birdsnest.maths.tcd.ie tel: +353-86-2336090, +353-1-2842366 s-mail: School of Mathematics, Trinity College, Dublin 2, Ireland
-- fedora-test-list mailing list fedora-test-list@redhat.com To unsubscribe: http://www.redhat.com/mailman/listinfo/fedora-test-list
On Sun, Dec 12, 2004 at 04:16:02PM +0400, Manu Abraham wrote:
But, what i would like to know is whether a graceful way of doing it exists, without much hassle... I know that this is not much of an issue, but still thought it would be better if i posted the problem...
tune2fs will let you change the volume names. That means you can fix your real file system labels to be different.
On Sun December 12 2004 4:48 pm, Alan Cox wrote:
On Sun, Dec 12, 2004 at 04:16:02PM +0400, Manu Abraham wrote:
But, what i would like to know is whether a graceful way of doing it exists, without much hassle... I know that this is not much of an issue, but still thought it would be better if i posted the problem...
tune2fs will let you change the volume names. That means you can fix your real file system labels to be different.
Thanks... didn't know that....
Manu
-
Alan Cox -
Joshua Andrews -
Kyrre Ness Sjobak -
Manu Abraham -
Per Bjornsson -
shrek-m＠gmx.de -
Timothy Murphy -
Uday Kumar Reddy