Fedora 7 - Second hard drive won't mount

Discussion in 'Installation/Configuration' started by andyofne, Jul 23, 2007.

  1. andyofne

    andyofne New Member


    I've searched around and can't find a replication of my exact problem.

    I had a reasonably nice file server running at home. I ended up killing the motherboard but that's not the subject of this post.

    I did a fresh install of Fedora 7 on an older Pentium III box I had in the garage.

    I took the data drive from my other (now not booting) server and tried to set it up as the second drive in the new box.

    I can see the drive, listed as sdb1, and fdisk shows the following information:

    Disk /dev/sdb: 250.0 GB, 250059350016 bytes
    255 heads, 63 sectors/track, 30401 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes

    Device Boot Start End Blocks Id System
    /dev/sdb1 * 1 30401 244196001 83 Linux

    I used the e2label command to assign a label name to the drive, as follows:

    /sbin/e2label /dev/sdb1 /netstore

    Then I added the label to the fstab file as follow:

    /dev/VolGroup00/LogVol00 / ext3 defaults 1 1
    LABEL=/boot /boot ext3 defaults 1 2
    LABEL=/netstore /netstore 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/VolGroup00/LogVol01 swap swap defaults 0 0

    I created a directory /netstore

    I attempted to manually mount the drive from the command line but it doesn't work.

    It just keeps telling me:

    [[email protected] ~]# mount /netstore
    mount: mount point /netstore does not exist

    Now I'm troubled by the results of the following command;

    Disk /dev/sdb1: 250.0 GB, 250056705024 bytes
    255 heads, 63 sectors/track, 30400 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes

    Disk /dev/sdb1 doesn't contain a valid partition table

    What happened to my partition table? Is my data gone?

    It's a serious load of MP3s...

    I might add, thought I don't know if it has anything to do with anything... the BIOS on the computer doesn't show a 250GB drive but a 136GB drive... as I mentioned, it's an old computer.

    When I did the installation I deselected the second drive and told Fedora to only use the 40GB primary drive.

    Would it have touched the second drive in any way during installation?
    Last edited: Jul 23, 2007
  2. falko

    falko Super Moderator ISPConfig Developer

    That doesn't look good. But you can try to repair the partition table with TestDisk: http://www.howtoforge.com/data_recovery_with_testdisk
  3. rayman

    rayman New Member

    I've been having similar problems with fedora7

    Its refreasing to see that I'm not the only one who's had problems with fedora 7 and partitions

    It seems they have taken a step backwards when they dropped the core from the name did they drop the ball from there game...?

    I've noticed problems accessing partitions (dos & fat 32) in particular and how come all the tools seem to have gone out of the standard install..?

    I thought the live fedora core6 disc was a little light but fedora7 seems to be squeezed in to a size zero little black dress "metaforically" that is, looks good till you get inside..

    as our noble mentor has taken the time to present us with such great "perfect set ups"
    I even followed that and there again no access to a fat32 extended partition....

    And guess where all my virtual machine files are kept...?

    access isn't a problem when bootup from windows ..and I've tryed a couple of live distro's that refuse point blank to read the fedora partitions even when they recognised the lvm volume

    I smell commercialism creeping in ...

    cheers for listening ray

Share This Page