Fedora 8 partition question

[ThunderRd]

No problem for Corsair to replace. They are really good about that. Glad you found the problem.

[Daniel ~]

I'm here to speak for the newb!
You can! you can just use default partitioning, I do!
But then you won't learn any more than I have....which for now, seems just enough to trouble my teachers":O}

[booman]

I looked up the Corsair RMA info, and all their RAM has Lifetime Warranties. They suggest to try the RAM in another computer, but I couldn't even run Memtest from the Fedora disk.... but I may try anyways... It could be the Asus motherboard not liking 2 gigs of RAM!?

As for partitioning, I've got Fedora 8 running, and updated. Now I have to learn how to add the second drive. At first Fedora wouldn't even see the second SATA drive and then I found in the BIOS a "combined" setting that would allow up to 2 IDE & 2 SATA drives running together. So then Fedora saw both drives during boot & install. Now I have Fedora running on the new drive and I want to mount the old "corrupt" drive. Maybe my data is still on it?

[ccperf721p]

Most likely the reason you cannot see the drive is it has the same logical volume name as the one that fedora is installed on so you will need to change the VolGroup ID.

open a terminal and su to root then run lvscan , the output will show the volume id's, if there is two VolGroup00, run vgchange -ay VolGroup01.

then, mkdir /corrupt_drive

then, mount -t ext3 /dev/VolGroup01/LogVol01 /corrupt_drive

may need to change permissions as well, if so run chown -R your user /corrupt_drive

[Daniel ~]

Seems so simple...I'd have never thought of that!! ":O}

[booman]

Cliff you ROCK! I'm trying that first thing in the morning.

I was doing some research on the Grub manual and thought that I had to add the corrupt drive in the Grub.conf because it wasn't showing up when I did:

df

or

fdisk

[booman]

Ok I tried the code Cliff postsed and this is what I get ....

ACTIVE '/dev/VolGroup00/LogVol00' [146.84 GB] inherit
ACTIVE '/dev/VolGroup00/LogVol01' [1.94 GB] inherit
ACTIVE '/dev/VolGroup01/LogVol00' [146.88 GB] inherit
ACTIVE '/dev/VolGroup01/LogVol01' [1.94 GB] inherit

[root@localhost back-up]# df /back-up
Filesystem 1K-blocks-------Used------Available------Use%--- Mounted on /dev/mapper/VolGroup01-LogVol00
--------------149186740--4064460---137421800----3% /


The funny thing is both LogVol00 & 01 have only 8 Megs difference.
I did the

mkdir /back-up

and called it "back-up" but I think it mounted on my /root drive instead of the extra hard-drive because both /home & /back-up have the same 131 Gig of free space. How do I know which drive is which when mounting? How do I know I am using the back-up or the /home drive. by the way, my /home drive is a separate partition for the Fedora installation. I hope that doesn't confuse things.

[booman]

also when I do a new install, Fedora 8 recognizes both hard-drives:

sda 152625 ATA WDC WD1600JS-00M
sdb 152586 ATA WDC WD1600AAJS-7

[Daniel ~]

Excellent! ":O}

[booman]

actually not excellent. Both drives are recognized during installation but not in the OS. I've tried what Cliff said, and thought it worked but I only created a "back-up" folder in /home. I want the back-up folder on the 2nd hard-drive which I think is: sdb

[Daniel ~]

Trust the Cliff! He'll make it right! ":O}

[booman]

I also found a good forum posts in a Linux Forum that answers my same scenario. Now I have to try and see if it works.

[booman]

Geesh, one problem after another.
I've re-named the VolGroup00 to "back-up" according to the forum post...
Now Grub won't automaticlly load the kernel
I have the Grub manual but its not giving me proper examples to load the kernel
Does anyone (Cliff) have a clue what commands will set Grub to load my linux kernel?

[booman]

ok, I plugged the "back-up" SATA drive in while Fedora was running and then re-booted. Now it boots to the correct drive automaticlly.
But, (of course) I still can't mount the drive. Or I'm doing the commands in correctly.
I'm typing:

mount -t ext3 /dev/back-up/LogVol00 /data

I'm not sure if its formatted as ext3 or not
/data is the new directory I created to point the mounted drive to

[booman]

ok I think I got it!
Now my /back-up folder shows 161 Gigs of free space
and my /home folder shows 113 Gigs of free space because I've copied my personal date on to it...
So how do I know FOR SURE the /back-up in on the other drive?

[edit]
Oops that was 161 Megs free space in /back-up
for some reason my new /back-up folder just goes right to /boot !!!???
I need some help...

[Daniel ~]

Always comes from where you least expect it! ":O}

[Daniel ~]

Sorry about my last post, was suppose to go elsewhere! Sorry for you troubles... Cliff gets very busy from time to time....

[booman]

I'm going to keep researching and see what else I can do to mount a drive correctly

[Daniel ~]

I've sent out feelers to my support group and let them know that we are struggling here! ":O}

[Gizmo]

If you just type

mount

from the command line, it'll give you a list of all the currently active mountpoints (directories), and what devices (partitions) are mounted to them.

If you want to just mount a partition, and it is listed in your /etc/fstab, then all you have to do is type:

mount mountpoint

or:

mount device

and the system will pull the necessary information to finish mounting the file system.

If you want to mount a device that isn't listed in your fstab, then you have to give the mount command a bit more info:

mount device mountpoint

USUALLY, this will be sufficient, and you'll have access to the device you just mounted in the directory that you specified. In some cases, mount may not be able to figure out with certainty what the filesystem type on the requested device is, and then you've got to explicitly tell it what filesystem to use:

mount -t fstype device mountpoint

for the more common filesystems, fstype will be ext2, ext3, jfx, xfs, reiserfs. For a complete list, type:

man mount

and look at the documentation for the -t option.

To e.g. mount the third partition on the first drive in the directory /backup using the ext3 filesystem, you would do this:

mount -t ext3 /dev/sda3 /backup

Note that from the standpoint of the existing filesystem, /backup is a perfectly valid directory, and you can store stuff in it. If you don't have something mounted there, then it will go to whatever device that directory exists on normally. However, if you mount a device to a directory, the previous contents of the directory will become inaccessible until you unmount the device again using the umount command.

Now, all of this is completely different from making a symbolic link to a directory or file using the 'ln' command. In that case, you are simply taking a file that is ALREADY visible to the file system and making it visible in another location as well.