Yes, a dumb error on my part.
#/dev/sda /raid/fc0 ext3
defaults,usrquota 1 2
#/dev/sdb /raid/fc1 ext3
defaults,usrquota 1 2
#/dev/sdc /raid/fc2 ext3
defaults,usrquota 1 2
should have been
#/dev/sda1 /raid/fc0 ext3
defaults,usrquota 1 2
#/dev/sdb1 /raid/fc1 ext3
defaults,usrquota 1 2
#/dev/sdc1 /raid/fc2 ext3
defaults,usrquota 1 2
I made those changes. and also ran e2label on each partition and each
one came back with the expected label.
It would appear that the problem is when during the boot process the
system checks to see if each partition needs to have fsck run. When
it reaches these partitions is when it gives the superblock error. If
I change the last digit in the fstab for these partitions from 2 to 0
it does not check and everything seems to mount just fine.
Bruce
On Mar 30, 2006, at 1:26 PM, Alfred Hovdestad wrote:
e2label PARTITION
simply returns the label for the partition.
e2label PARTITION NEWLABEL
replaces the label on the partition. It does not change any of the
data on the partition.
Alfred
Bruce W. Martin wrote:
I will not be able to check until next week but I think this may
be enough hints to fix this.
I will report back when I get more information and answers to
your questions.
BTW, when using e2label to create a label is it destructive to
the partition? I don't want to lose data on these partitions.
Thanks,
Bruce
On Mar 30, 2006, at 9:57 AM, Alfred Hovdestad wrote:
What does 'fdisk -l /dev/sda' return? How about for sdb and
sdc? Did you create partitions (/dev/sda1, /dev/sdb1, /dev/sdc1)?
If you did create partitions, what does 'e2label /dev/sda1'
return? If not, how about 'e2label /dev/sda'?
Alfred Hovdestad, RHCE
University of Saskatchewan
--
redhat-list mailing list
unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/redhat-list
--
redhat-list mailing list
unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/redhat-list
