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@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
I can mount it:
[root@box9 bobg]# mount /dev/VolGroup01/LogVol02 [root@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@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@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
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
[snip]
I would like the second drive to be an extension of the first.
Can anyone tell me what I have done wrong?
Bob
/home/bobg/UUID=tvOhFL-1sDH-fk5y-zv00-PR6c-cA2F-xyOTAP shows it mounted in your $HOMEDIR as UUID=tvOhFL-1sDH-fk5y-zv00-PR6c-cA2F-xyOTAP. Wat you want to do is to extend dev/VolGroup01/LogVol00 allocating it the new hdd capacity.
the common tasks of the LVM howto should be what you are after http://tldp.org/HOWTO/LVM-HOWTO/extendlv.html
I find it is the best reference around and I *always* refer to it whenever I need to deal with lvm as I don't tend to play with them very often.
ask if anything on the howto is unclear.
hth
Thierry
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@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@box9 bobg]# mount /dev/VolGroup01/LogVol02 [root@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@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@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
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@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@box9 bobg]# mount /dev/VolGroup01/LogVol02 [root@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@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@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
Bob Goodwin wrote:
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
The reason it shows as being in use is because you have an active logical group on it. You have to deactivate VolGroup01/LogVol02 before you can do anything else with /dev/sdb1. You can use Logical Volume Management to do this as well.
Mikkel
Mikkel L. Ellertson wrote:
The reason it shows as being in use is because you have an active logical group on it. You have to deactivate VolGroup01/LogVol02 before you can do anything else with /dev/sdb1. You can use Logical Volume Management to do this as well.
Mikkel
Ok that problem is fixed. I used the gnome live cd but run xfce, so it's system-config-lvm for me.
It's rewritten the file system so I should be able to start again from scratch. This may take some time since I'm learning by doing ...
Thanks for the help.
Bob
Bob Goodwin wrote:
Mikkel L. Ellertson wrote:
The reason it shows as being in use is because you have an active logical group on it. You have to deactivate VolGroup01/LogVol02 before you can do anything else with /dev/sdb1. You can use Logical Volume Management to do this as well.
Mikkel
Ok that problem is fixed. I used the gnome live cd but run xfce, so it's system-config-lvm for me.
I am glad you found it. The GUI is usually easier for a new user to manage. You can also do it from the command line. But I worry about making a typo when I giving the command to someone else. I would hate to leave them with an unbootable system. (If I break my system, I know I can fix it...)
It's rewritten the file system so I should be able to start again from scratch. This may take some time since I'm learning by doing ...
I hope that does not mean doing a reinstall - you should not need to do that. I think that learning by doing is the best way to learn.
Thanks for the help.
I am glad to do my small part in helping you learn!
Mikkel
Bob Goodwin wrote, On 02/26/2009 02:45 PM:
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.
Suggestion: 1) in /etc/yum.conf set keepcache=1 2) every so often copy the contents of /var/cache/yum/updates/packages/ (or if your on F9 /var/cache/yum/updates-newkey/packages/) to an external media (DVDs/USBHD). 3) when you have to reinstall you can copy the rpms back to the packages/ directory and yum will see them and know that it does not have to re download them. [it still has to get/extract the headers, but they are small.]
This is also a useful trick when you have several machines to update that are running nearly the same install, i.e., by copying packages/ from the first to later machines, the later machines only have to download the packages that the first machine was not running. :)
Todd Denniston wrote:
Bob Goodwin wrote, On 02/26/2009 02:45 PM:
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.
Suggestion:
- in /etc/yum.conf set keepcache=1
- every so often copy the contents of
/var/cache/yum/updates/packages/ (or if your on F9 /var/cache/yum/updates-newkey/packages/) to an external media (DVDs/USBHD). 3) when you have to reinstall you can copy the rpms back to the packages/ directory and yum will see them and know that it does not have to re download them. [it still has to get/extract the headers, but they are small.]
This is also a useful trick when you have several machines to update that are running nearly the same install, i.e., by copying packages/ from the first to later machines, the later machines only have to download the packages that the first machine was not running. :)
Ok, I did as yous suggested and it's running update for the third time! Hopefully I will be able to use those files on this computer which I will next upgrade from F-9 to 10.
I eventually got the other computer into a state where it would no longer boot. Apparently it wanted some files on the second drive and I had repartitioned it with fdisk. They were gone.
I had already wasted several days of my spare time trying to make it work and the most expeditious way out was a reinstall. I wanted to reduce the size of the XP partition anyway in addition to adding the second drive. Once I get things running I have a pata drive I want to add to the mix. I will have build up some nerve to do that!
Thanks all.
Bob
On Thu, Feb 26, 2009 at 7:26 AM, Bob Goodwin bobgoodwin@wildblue.net 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@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
I can mount it:
[root@box9 bobg]# mount /dev/VolGroup01/LogVol02 [root@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@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@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 may be missing something obvious. Why not define a mount point for /dev/mapper/VolGroup01-LogVol02? For instance you defined "/" to be the mount point for /dev/VolGroup01/LogVol00.
~af
Aldo Foot wrote:
I may be missing something obvious. Why not define a mount point for /dev/mapper/VolGroup01-LogVol02? For instance you defined "/" to be the mount point for /dev/VolGroup01/LogVol00.
~af
The installer on the live cd did that, I added the second drive later and began messing with the lvm configuration. I didn't change anything on the first drive ... Except to make room for F-10.
Bob
-
Aldo Foot -
Bob Goodwin -
Mikkel -
Thierry -
Todd Denniston