Mount added drive -
Bob Goodwin
bobgoodwin at wildblue.net
Thu Feb 26 19:45:54 UTC 2009
Mikkel L. Ellertson wrote:
> Bob Goodwin wrote:
>
>> This is an F-10 updated box to which I've added a second drive which is
>> not mounting automatically at boot. I have to mount it after I log in.
>> Obviously I've messed up something in configuration but I haven't been
>> able to find it.
>>
>> I am not sure what ftab should look like but presently it is:.
>>
>> [root at box9 bobg]# cat /etc/fstab
>>
>> #
>> # /etc/fstab
>> # Created by anaconda on Tue Feb 24 04:01:45 2009
>> #
>> # Accessible filesystems, by reference, are maintained under '/dev/disk'
>> # See man pages fstab(5), findfs(8), mount(8) and/or vol_id(8) for
>> more info
>> #
>> /dev/VolGroup01/LogVol00 / ext3
>> defaults 1 1
>> UUID=3c6742c9-0f68-4390-b323-b962596822d6 /boot
>> ext3 defaults 1 2
>> tmpfs /dev/shm tmpfs
>> defaults 0 0
>> devpts /dev/pts devpts
>> gid=5,mode=620 0 0
>> sysfs /sys sysfs
>> defaults 0 0
>> proc /proc proc
>> defaults 0 0
>> /dev/VolGroup01/LogVol01 swap swap
>> defaults 0 0
>>
>> /dev/VolGroup01/LogVol02 UUID=tvOhFL-1sDH-fk5y-zv00-PR6c-cA2F-xyOTAP
>> ext3 defaults 1 2
>>
>>
> Reading this, you are giving
> UUID=tvOhFL-1sDH-fk5y-zv00-PR6c-cA2F-xyOTAP as the mount point. I
> don't think this is what you are after.
>
>> I can mount it:
>>
>> [root at box9 bobg]# mount /dev/VolGroup01/LogVol02
>> [root at box9 bobg]# df
>> Filesystem 1K-blocks Used Available Use% Mounted on
>> /dev/mapper/VolGroup01-LogVol00
>> 5289592 3210420 2025496 62% /
>> /dev/sda2 194449 20859 163550 12% /boot
>> tmpfs 1292316 76 1292240 1% /dev/shm
>> /dev/mapper/VolGroup01-LogVol02
>> 76923936 222308 72794044 1%
>> /home/bobg/UUID=tvOhFL-1sDH-fk5y-zv00-PR6c-cA2F-xyOTAP
>>
>> And df shows:
>>
>> [root at box9 bobg]# df
>> Filesystem 1K-blocks Used Available Use% Mounted on
>> /dev/mapper/VolGroup01-LogVol00
>> 5289592 3210420 2025496 62% /
>> /dev/sda2 194449 20859 163550 12% /boot
>> tmpfs 1292316 76 1292240 1% /dev/shm
>> /dev/mapper/VolGroup01-LogVol02
>> 76923936 222308 72794044 1%
>> /home/bobg/UUID=tvOhFL-1sDH-fk5y-zv00-PR6c-cA2F-xyOTAP
>>
>> And lvscan:
>>
>> [root at box9 bobg]# lvscan
>> ACTIVE '/dev/VolGroup01/LogVol00' [5.12 GB] inherit
>> ACTIVE '/dev/VolGroup01/LogVol01' [4.41 GB] inherit
>> ACTIVE '/dev/VolGroup01/LogVol02' [74.53 GB] inherit
>>
>> I would like the second drive to be an extension of the first.
>>
>> Can anyone tell me what I have done wrong?
>>
>> Bob
>>
>>
> I am not sure what you are after, but if you want the second drive
> to VolGroup01-LogVol00, you do not create another logical volume -
> add it to Vol00. You will probably want to use the Logical Volume
> Management to do it. Under Gnome, it is System --> Administration
> --> Logical Volume Management.
>
> Mikkel
>
Now I'm in deeper trouble!
I thought I would simply use fdisk to rewrite the partition on /dev/sdb
which it happily did. But now when I do mkfs -t ext3 /dev/sdb1 it
protests
that "/dev/sdb1 is apparently in use by the system; will not make a
filesystem here!"
umount /dev/sdb1 says it's not mounted?
Now I'm stuck. The simplest thing would be to reinstall the system but
bandwidth for updates is killing me. Wildblue is a satellite service and
I'm limited to 17 Gigs/30 days. I hate to keep burning up my bw.
How can I access /dev/sdb1. I have no rescue disk, installed from the
live cd.
Bob
More information about the fedora-list
mailing list