Roadworthy Posted March 19, 2004 Share Posted March 19, 2004 As you can probably tell from the thread title, just some simple mount problems. In the beginning (*cue grand overture*)... I had a comp with two hard disks (lets call them 'hda' and 'hdb' for originality's sake shall we?). WinXP was installed on hda, and had a seperate ntfs partition also on hda to hold data. hdb held a couple of standard linux partitions (ext3), and a FAT32 for sharing stuff between OS's. Finally decided to drop windows entirely, so moved all data off ntfs partition and used "mkfs.ext3 /dev/hda5" to format it. Modified the appropriate line in my fstab to read /dev/hda5 /mnt/storage ext3 user,uid=500,gid=500 0 0 which I thought would work. Instead, during bootup I get mount: wrong fs type, bad option, bad superblock on /dev/hda5, or too many mounted file systems Have found that I can mount it manually if I specify BOTH dev and mnt point e.g. mount /dev/hda5 /mnt/storage but just giving it one argument and letting it find the rest from the fstab gives the same error as above e.g. mount /dev/hda5 Think that's about all the info I can offer on the problem, anyone got any clue what I can do about it? Thanks for your time Chris Link to comment Share on other sites More sharing options...
MR_Candyman Posted March 19, 2004 Share Posted March 19, 2004 hmm...dunno bout passing the uid and gid...I don't do that... but if that' ok...you sure you created the directory called "/mnt/storage/"? Link to comment Share on other sites More sharing options...
kongit Posted March 19, 2004 Share Posted March 19, 2004 You can only have 4 partitions by themselves. You have to set up one to act as multiple ones. :) Link to comment Share on other sites More sharing options...
Roadworthy Posted March 19, 2004 Author Share Posted March 19, 2004 thanx for the replies guys @MR_Candyman: yeah the dir is there already ;) @kongit: when i first set it up with partition magic, it put that partition inside an extended one, but i dont know why, u think that makes a big difference? Seems strange that it mounted as hda5 when back when it was an ntfs partition. I'm stumped Chris Link to comment Share on other sites More sharing options...
kemical Posted March 19, 2004 Share Posted March 19, 2004 try using mke2fs -j /dev/hda5 for ext3 Link to comment Share on other sites More sharing options...
kongit Posted March 19, 2004 Share Posted March 19, 2004 If partition magic set it up right then no it shouldn't make a difference. go into the console or terminal, go to root. Type in fdisk dev/hda. then type p at the fdisk prompt to see what partitions you have. You should see all of your partitions there and their types. type q to quit without doing any fdisking. Link to comment Share on other sites More sharing options...
Roadworthy Posted March 19, 2004 Author Share Posted March 19, 2004 If partition magic set it up right then no it shouldn't make a difference. go into the console or terminal, go to root. Type in fdisk dev/hda. then type p at the fdisk prompt to see what partitions you have. You should see all of your partitions there and their types. type q to quit without doing any fdisking. Sorry about the late response - here's the list of partitions on that drive Disk /dev/hda: 61.4 GB, 61492838400 bytes 255 heads, 63 sectors/track, 7476 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/hda1 * 1 2550 20482843+ 7 HPFS/NTFS /dev/hda2 2551 7475 39560062+ f Win95 Ext'd (LBA) /dev/hda5 2551 7475 39560031 7 HPFS/NTFS That seems pretty strange, doesnt look as if the mkfs command changed the file type after all, even though it seemed to run fine :huh: Also tried out kemical's suggestion and it shows the same thing confused Link to comment Share on other sites More sharing options...
Roadworthy Posted March 21, 2004 Author Share Posted March 21, 2004 Ok, sorry for ressurecting my own page-old thread, but i finally managed to sort out my old problem, and have found a new one. I managed to mount the partition by removing the "uid" & "gid" arguments as they aren't supported by ext3, only vfat (as suggested by MR_Candyman). And got around the persistent ntfs-ness by deleting the partition altogether and creating it from scratch. Now, however, no matter what args I put in the fstab, or where I try to mount it (e.g. in "/mnt/storage", or in "/home/usrname/storage" - both of which already exist), it only gives write access to root :angry: If my home partition is only mounted with "defaults", and I have rw access to that, surely a disk mounted below it with the same args should have the same access rights? Any ideas anyone? Link to comment Share on other sites More sharing options...
Recommended Posts