Jump to content

I really screwed up my fstab I need to restore it


riorama
 Share

Recommended Posts

Greetings,

I just built a screeming new computer (all for linux 9.1) and had a hard time getting the permissions on my cd drives to work (cdrom, cdrw).

Now that Ive messed with it, I can't seem to unmount my drives because they're 'busy'

 

Here whats left of my fstab, Any hints what to erase?

 

/dev/hda1 / ext3 defaults 1 1

none /dev/pts devpts mode=0620 0 0

/dev/hda6 /home ext3 defaults 1 2

none /mnt/cdrom supermount dev=/dev/hdd,fs=auto,ro,--,user,iocharset=iso8859-1,codepage=850,noauto,umask=0 0 0

/dev/scd0 /mnt/cdrom2 iso9660 user,noauto,defaults 0 0

/dev/sda1 /mnt/windows vfat iocharset=iso8859-1,codepage=850,umask=0 0 0

none /proc proc defaults 0 0

/dev/hdc1 /storage ext3 defaults 1 2

/dev/hda5 swap swap defaults 0 0

/dev/hdd /mnt/cdrom auto user,owner,exec,dev,suid,rw,noauto 1 1

/dev/scd0 /mnt/cdrom2 auto exec,dev,suid,rw 1 1

 

 

Any hints would be really cool. This is making me crazy!

 

Ken

 

PS My new computer rocks! Only had to install one set of drivers for motherboard and video, and its rolling.

Link to comment
Share on other sites

Sometimes an open window will cause that (especially konq browser).

 

anyway, here's my cd rom entries in a default Mandrake 9.1 install after setting up k3b:

none /mnt/cdrom supermount dev=/dev/scd0,fs=auto,ro,--,iocharset=iso8859-1,codepage=850,umask=0 0 0

none /mnt/cdrom2 supermount dev=/dev/hdd,fs=auto,ro,--,iocharset=iso8859-1,codepage=850,umask=0 0 0

 

Should be one line per device. You also have each CD drive listed twice. (Hard to really tell with this word wrapping here)

Link to comment
Share on other sites

i agree with ixthusdan about supermount. disable it & you'll have less drive problems. i'd first clean up your fstab, though. here's what mine looks like without supermount for my cd drives. i leave it enabled for the floppy drive because i rarely use that & it's never given me a problem with it enabled there.

 

/dev/hdc7 / ext2 defaults 1 1

none /dev/pts devpts mode=0620 0 0

/dev/hdc10 /home ext2 defaults 1 2

/dev/scd0 /mnt/cdrom auto user,noauto,ro,exec 0 0

/dev/scd1 /mnt/cdrom2 auto user,noauto,ro,exec 0 0

none /mnt/floppy supermount 

dev=/dev/fd0,fs=auto,--,iocharset=iso8859-1,sync,codepage=850,umask=0 0 0

/dev/hdc1 /mnt/win_c vfat iocharset=iso8859-1,codepage=850,umask=0 0 0

/dev/hdc5 /mnt/win_d vfat iocharset=iso8859-1,codepage=850,umask=0 0 0

/dev/hdc6 /mnt/win_e vfat iocharset=iso8859-1,codepage=850,umask=0 0 0

none /proc proc defaults 0 0

/dev/hdc9 /usr ext3 defaults 1 2

/dev/hdc8 swap swap defaults 0 0

 

your entries may vary slightly, depending on where your drives are mounted (IE: drive letter) & whether you have ide or scsi drives.

 

if you're a bit more adventurous, you can always open MCC & reset all of your mount points from there. it's pretty easy & it walks you through it without much head scratching.

 

once you get things squared away, i would recommend backing up your good, working fstab file. that way, if you bugger something up again, you can always replace the bad version with the good. i do this as a safety net with all of my major config files.

 

finally, the magic commands to disable & enable supermount are......

 

go to terminal, su to root

 

to disable:

supermount -i disable

 

to enable:

supermount -i enable

 

Chris

Link to comment
Share on other sites

Yeah,

Konqueror can easily lock a drive I tend to close stuff then try and eject.

The worst culprit I found was Galeon though....

It 'helpfully' scans each directory in a directory and lost the number of files it contains.

 

So if your in /mnt it will scan /mnt/cdrom etc.

Thus you need to be in / so that it counts files in /mnt BUT no /mnt/cdrom

 

supermount is an ugly **** that causes more probs than its worth.

 

Sometimes you might have a background process trying to access your drives.

You can use a

ps -ef for this and and try and grep on /mnt or cdrom.

You can then try and kill this process by hand....

One strange thing in linux Ive found is that you can't always kill a process unlike solaris or other UNIX's. Ive never had a process owndwed by me I couldn't kill in solaris but it happens frequently in linux.

Link to comment
Share on other sites

Yeah,

Konqueror can easily lock a drive I tend to close stuff then try and eject.

The worst culprit I found was Galeon though....

It 'helpfully' scans each directory in a directory and lost the number of files it contains.

 

Are you sure you're not talking about Nautlius? Galeon is a stand-alone web browser with very limited file management capabilities.

Link to comment
Share on other sites

This is what I changed it to, seems to work well now, So Far :roll:

 

/dev/hda1 / ext3 defaults 1 1

none /dev/pts devpts mode=0620 0 0

/dev/hda5 swap swap defaults 0 0

/dev/hda6 /home ext3 defaults 1 2

/dev/hdb /mnt/cdrom auto user,defaults 0 0

/dev/scd0 /mnt/cdrom2 auto user,defaults 0 0

/dev/sda1 /mnt/windows vfat iocharset=iso8859-1,codepage=850,umask=0 0 0

none /proc proc defaults 0 0

/dev/hdc1 /storage ext3 defaults 1 2

 

Do have Any idea what the none / lines mean ?

The other ones seem to make sense. What the heck are these?

 

Ken

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
 Share

×
×
  • Create New...