[SOLVED] mount problem

[mykyi]

Hey guys,

I recently decided to delete my windows partition since i hadn't accessed it in 3 months. I downloaded GPARTED Live and deleted and refomatted the ntfs partition to EXT3, also resized root. After doing this I edited fdisk and changed //dev/hda1 from ntfs to ext3 with defaults of 0 0. When i do a sudo mount-a it says //dev/hda1 is already mounted or is busy. I already went to the psychocats website and followed their tutorial step by step. I'll post my fdisk output when I get home from work. Thanks,

Mykyi.

[spydon]

Have you tried rebooted after you did it?

[mykyi]

DUH!!! Man, that better not be the fix. I can't remember if I rebooted or not. That's the first thing I'll try. I'll keep you posted.

[mykyi]

Nope, that didn't do it.


# /etc/fstab: static file system information.
#
# -- This file has been automaticly generated by ntfs-config --
#
# <file system> <mount point> <type> <options> <dump> <pass>

proc /proc proc default$
# Entry for /dev/hda2 :
UUID=c39ebf91-603e-4fc6-8304-0402a811f999 / ext3 default$
# Entry for /dev/hda5 :
UUID=e9150d47-f962-478d-b45b-7508cabcd3f3 none swap sw $
/dev/hdc /media/cdrom0 udf,iso9660 user,no$
/dev/hdd /media/cdrom1 udf,iso9660 user,no$
/dev/hda1 /media/hda1 ext3 default$
/dev/hda2 /media/hda2 ext3 default$
/dev/hda5 /media/hda5 swap default$
/dev/sda1 /media/4 GB-4GB/music vfat $
/dev/sda1 /media/sda1 vfat default$


and this is what i get when i try to mount.

mike@mike-desktop:~$ sudo mount -a
mount: /dev/hda1 already mounted or /media/hda1 busy
mount: unknown filesystem type 'GB-4GB/music'
mount: special device /dev/sda1 does not exist


hopefully it's something i just missed.

thanks


mykyi

[Victormd]

Check the link on my signature and see if that helps. Using gparted to edit the partition may have changed the device name and that's probably why it's not mounting...

[mykyi]

I'll give that a try. I use the same info if I'm running Gutsy right?

[Victormd]

Yeah, it's all the same... I entitled it for Hardy because Gutsy normally mounts NTFS drives automatically while Hardy doesn't. I know yours is formated in EXT3, but it works just the same.

[mykyi]

OK tried all that. I tried changing where the mountpoint is also, still didn't work. How can I check the label? Is the contents of fdisk accurate or could it be giving me the wrong label.

Fdisk output


Disk /dev/hda: 120.0 GB, 120034123776 bytes
255 heads, 63 sectors/track, 14593 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x0bb80c1c

Device Boot Start End Blocks Id System
/dev/hda1 1 10682 85803133+ 83 Linux
/dev/hda2 10683 14507 30724312+ 83 Linux
/dev/hda3 14508 14593 690795 5 Extended
/dev/hda5 14508 14593 690763+ 82 Linux swap / Solaris

Disk /dev/dm-0: 87.8 GB, 87862408704 bytes
255 heads, 63 sectors/track, 10681 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x00000000

Disk /dev/dm-0 doesn't contain a valid partition table


thanks

mykyi

[mykyi]

forgot to add FSTAB




# /etc/fstab: static file system information.
#
# -- This file has been automaticly generated by ntfs-config --
#
# <file system> <mount point> <type> <options> <dump> <pass>

proc /proc proc defaults 0 0
# Entry for /dev/hda2 :
UUID=c39ebf91-603e-4fc6-8304-0402a811f999 / ext3 defaults,errors=remount-ro 0 1
# Entry for /dev/hda5 :
UUID=e9150d47-f962-478d-b45b-7508cabcd3f3 none swap sw 0 0
/dev/hdc /media/cdrom0 udf,iso9660 user,noauto,exec 0 0
/dev/hdd /media/cdrom1 udf,iso9660 user,noauto,exec 0 0
/dev/hda1 /media/storage ext3 defaults 0 0
/dev/hda2 /media/hda2 ext3 defaults 0 0
/dev/hda5 /media/hda5 swap defaults 0 0
/dev/sda1 /media/4 GB-4GB/music vfat 0 0
/dev/sda1 /media/sda1 vfat defaults 0 0

[Victormd]

Looks like you're trying to mount hda2 and hda5 twice:

# /etc/fstab: static file system information.
#
# -- This file has been automaticly generated by ntfs-config --
#
# <file system> <mount point> <type> <options> <dump> <pass>

proc /proc proc defaults 0 0
# Entry for /dev/hda2 :
UUID=c39ebf91-603e-4fc6-8304-0402a811f999 / ext3 defaults,errors=remount-ro 0 1
# Entry for /dev/hda5 :
UUID=e9150d47-f962-478d-b45b-7508cabcd3f3 none swap sw 0 0
/dev/hdc /media/cdrom0 udf,iso9660 user,noauto,exec 0 0
/dev/hdd /media/cdrom1 udf,iso9660 user,noauto,exec 0 0
/dev/hda1 /media/storage ext3 defaults 0 0
/dev/hda2 /media/hda2 ext3 defaults 0 0
/dev/hda5 /media/hda5 swap defaults 0 0
/dev/sda1 /media/4 GB-4GB/music vfat 0 0
/dev/sda1 /media/sda1 vfat defaults 0 0

Since hda5 is your swap, it might be overriding it (??) but the same is not true for hda2.

Check the UUID in the first hda2 entry to see if that matches what's being shown in fstab.

sudo vol_id -u /dev/hda2

If it matches, delete the second entry, otherwise, correct the first entry and delete the second one or delete the first entry...

[mykyi]

Ok so I should probably delete the line that is //dev/hda2. This is my root partition. Will I mess up anything if I delete it? Also, when I created the new ext3 partition (//dev/hda1) it only gave me the option to make it a primary partition and not a logical one. Would that cause this problem??

[Victormd]

This is how I would modify your fstab:

# /etc/fstab: static file system information.
#
# -- This file has been automaticly generated by ntfs-config --
#
# <file system> <mount point> <type> <options> <dump> <pass>

proc /proc proc defaults 0 0
# Entry for /dev/hda2 :
UUID=c39ebf91-603e-4fc6-8304-0402a811f999 / ext3 defaults,errors=remount-ro 0 1
# Entry for /dev/hda5 :
UUID=e9150d47-f962-478d-b45b-7508cabcd3f3 none swap sw 0 0
/dev/hdc /media/cdrom0 udf,iso9660 user,noauto,exec 0 0
/dev/hdd /media/cdrom1 udf,iso9660 user,noauto,exec 0 0
/dev/hda1 /media/storage ext3 defaults 0 0
/dev/sda1 /media/4 GB-4GB/music vfat 0 0
/dev/sda1 /media/sda1 vfat defaults 0 0
and check the highlighted items to see if they match (UUID) and exist (/media/storage)

[Victormd]

Ok so I should probably delete the line that is //dev/hda2. This is my root partition. Will I mess up anything if I delete it? Also, when I created the new ext3 partition (//dev/hda1) it only gave me the option to make it a primary partition and not a logical one. Would that cause this problem??

That would change your UUID.

You can delete /dev/hda2, but first, check to see if the UUID matches the first instance of hda2.

I prefer to use UUID because from what I've noticed, it's more consistent. I had a similar problem as your using the /dev/hda alternative.

Post the output of

sudo blkid
and the changes you've made to fstab before rebooting... :)

[mykyi]

Here's the output


/dev/hda1: UUID="9b9e683c-10c3-4e81-8efd-d4c5f2ec4269" SEC_TYPE="ext2" TYPE="ext3"
/dev/hda2: UUID="c39ebf91-603e-4fc6-8304-0402a811f999" SEC_TYPE="ext2" TYPE="ext3"
/dev/hda5: TYPE="swap" UUID="e9150d47-f962-478d-b45b-7508cabcd3f3"
/dev/dm-0: UUID="9b9e683c-10c3-4e81-8efd-d4c5f2ec4269" SEC_TYPE="ext2" TYPE="ext3"


The only changes i made to fstab was to change /dev/hda1 from ntfs to ext 3.
I also tried changing the mountpoint from /media/hda1 to /media/storage.

[Victormd]

Dumb observation but many people miss it: when changing the mountpoint, be sure to create the corresponding folder otherwise it won't mount... :)

Let me know if it worked...

[mykyi]

Ahhhh! I doublechecked and /media/storage and /storage does as well. I also checked the UUID and they match. Let me try that fstab edit and hopefully that'll do it.

[Victormd]

I just saw that you also have a problem with your sda1 partition

mike@mike-desktop:~$ sudo mount -a
mount: /dev/hda1 already mounted or /media/hda1 busy
mount: unknown filesystem type 'GB-4GB/music'
mount: special device /dev/sda1 does not exist
in your fstab you also have it listed twice (sorry I missed this).

/dev/sda1 /media/4 GB-4GB/music vfat $
/dev/sda1 /media/sda1 vfat default$
Furthermore, instead of "4 GB-4GB" remove the space so it looks like "4GB-4GB" or delete that line altogether (you can only have 1 anyway) and mount to /media/sda1.

[mykyi]

OK, fstab is cleaned up now but hda1 still fails to mount

FDISK


Disk /dev/hda: 120.0 GB, 120034123776 bytes
255 heads, 63 sectors/track, 14593 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x0bb80c1c

Device Boot Start End Blocks Id System
/dev/hda1 1 10682 85803133+ 83 Linux
/dev/hda2 10683 14507 30724312+ 83 Linux
/dev/hda3 14508 14593 690795 5 Extended
/dev/hda5 14508 14593 690763+ 82 Linux swap / Solaris

Disk /dev/dm-0: 87.8 GB, 87862408704 bytes
255 heads, 63 sectors/track, 10681 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x00000000

Disk /dev/dm-0 doesn't contain a valid partition table


FSTAB


# /etc/fstab: static file system information.
#
# -- This file has been automaticly generated by ntfs-config --
#
# <file system> <mount point> <type> <options> <dump> <pass>

proc /proc proc defaults 0 0
# Entry for /dev/hda2 :
UUID=c39ebf91-603e-4fc6-8304-0402a811f999 / ext3 defaults,errors=remount-ro 0 1
# Entry for /dev/hda5 :
UUID=e9150d47-f962-478d-b45b-7508cabcd3f3 none swap sw 0 0
/dev/hdc /media/cdrom0 udf,iso9660 user,noauto,exec 0 0
/dev/hdd /media/cdrom1 udf,iso9660 user,noauto,exec 0 0
/dev/hda1 /media/storage ext3 errors=remount-ro 0 0

SAME ERROR


mike@mike-desktop:~$ sudo mount -a
[sudo] password for mike:
mount: /dev/hda1 already mounted or /media/storage busy

[Victormd]

Your fstab looks fine but you might want to rethink your hda1 line to include the defaults option and set it to be checked after hda2:

/dev/hda1 /media/storage ext3 defaults,errors=remount-ro 0 2

So let's go to the source of your problems and try to fix it from there. You mentioned that you used the gparted live CD to create the partition. Since it's not mounting, you can can install and use the version from the repos. and try to recreate the partition.

sudo apt-get install gparted

[mykyi]

I found that every once in a while when ubuntu started up or shut down I get a device-mapper: table: 245:1: linear: dm-linear: device lookup failed repeating down the page I did a search for it and found that evms was causing this I did a sudo aptitude remove evms and rebooted and the partition showed up. I do have a new issue. There is a Lost and found folder in the new partition and 4.3 gig show used.

[Victormd]

Hummm... I'm inclined to say that, if it's a new partition that you just created (assuming you totally wiped out NTFS and formated in EXT3), delete that lost and found folder, you didn't lose anything... :)

[mykyi]

Thanks for your help on this Victor. Do you know why 4.3 gb would be taken up on a new partition?

[Victormd]

Not really. My guess is that during the mount/unmount issues you were having something funky happened but I wouldn't know what... Just out of curiosity, how much of your original NTFS partition was used?

[mykyi]

probably around 60 to 80 GB of it was used. My root partition used to be 13 GB. I resized it and wiped my ntfs. How much should I allocate to SWAP?

[Victormd]

I have only 512MB allocated. Anywhere between 512MB - 2GB should be fine. How much RAM do you have?

[mykyi]

2gb ram

[Victormd]

Then 512MB should be fine...

[mykyi]

Sweet!!! Thanks for your help on this.:biggrin: Onto the next discovery....

[Victormd]

Any time! :)