Results 1 to 9 of 9

Thread: problems with create auto mounted file systems

  1. #1
    Junior Member
    Join Date
    Nov 2004
    Posts
    4

    problems with create auto mounted file systems

    Hi,
    I am trying to create an auto mounted file system when system is rebooted. I altered the /etc/fstab file and changed the option to "auto".
    But after I reboot the system,the fstab file doesn't take affect and the accociated file system option restroed to "noauto".It seem that when system reboot ,the file fstab is rewriten.Following is my file fstab and I didn't change anything.

    /dev/hda6 / ext3 defaults,errors=remount-ro 0 1
    proc /proc proc defaults 0 0
    /dev/fd0 /floppy vfat defaults,user,noauto,showexec,umask=022 0 0
    usbdevfs /proc/bus/usb usbdevfs defaults 0 0
    sysfs /sys sysfs defaults 0 0
    /dev/cdrom /cdrom iso9660 defaults,ro,user,noexec,noauto 0 0
    /dev/dvd /dvd iso9660 defaults,ro,user,noexec,noauto 0 0
    /dev/cdaudio /cdaudio iso9660 defaults,ro,user,noexec,noauto 0 0
    # Added by KNOPPIX
    /dev/hda1 /mnt/hda1 ntfs noauto,users,exec,ro,umask=000 0 0
    # Added by KNOPPIX
    /dev/hda2 /mnt/hda2 vfat noauto,users,exec,umask=000 0 0
    # Added by KNOPPIX
    /dev/hda5 /mnt/hda5 ntfs noauto,users,exec,ro,umask=000 0 0
    # Added by KNOPPIX
    /dev/hda7 /mnt/hda7 auto noauto,users,exec 0 0
    # Added by KNOPPIX
    /dev/hda8 /mnt/hda8 ext2 noauto,users,exec 0 0
    # Added by KNOPPIX
    /dev/hda9 /mnt/hda9 vfat noauto,users,exec,umask=000 0 0

    Thanks. [/quote][/b]

  2. #2
    Senior Member registered user
    Join Date
    May 2003
    Posts
    981
    What type of HD install is is? If it is Knoppix-style, Knoppix re-writes fstab with each boot so it will overwrite your changes. To make it stop doing this, add 'nofstab' to the 'append=' line in /etc/lilo.config then re-run lilo.

  3. #3
    Junior Member
    Join Date
    Nov 2004
    Posts
    4
    Hi CrashedAgain,
    Thanks for your consideration.I tried but it does not work.First,I updated the lilo.conf file and add 'nofstab' after 'append='.Then i ran lilo and updated auto option of file system in the fstab file.Then i reboot the system. I checked the fstab file and it is rewriten by system.
    What i used is Knoppix 3.6 HD instal.I am wondering.

  4. #4
    Senior Member registered user
    Join Date
    May 2003
    Posts
    981
    Quote Originally Posted by Reven
    Hi CrashedAgain,
    Thanks for your consideration.I tried but it does not work.First,I updated the lilo.conf file and add 'nofstab' after 'append='.Then i ran lilo and updated auto option of file system in the fstab file.Then i reboot the system. I checked the fstab file and it is rewriten by system.
    What i used is Knoppix 3.6 HD instal.I am wondering.
    Hmmm. It should have worked. post your /etc/lilo.conf file. I'm sure the nofstab option is the same in Knoppix 3.6 as in 3.4.

  5. #5
    Senior Member registered user
    Join Date
    May 2003
    Posts
    981
    Here is my lilo.conf:

    Code:
     boot=/dev/hda
    map=/boot/map
    vga=normal
    default="Linux(new)"
    prompt
    nowarn
    timeout=100
    #message=/boot/message
    menu-scheme=wb:bw:wb:bw
    lba32
    
    # Boot Knoppix24 on hda5
    image=/boot/vmlinuz-2.4.26
     label="Knoppix24"
     root=/dev/hda5
     initrd=/boot/initrd.img-2.4.26
     append="lang=us apm=power-off ramdisk_size=100000 init=/etc/init nomce quiet nofstab wheelmouse"
     read-only
    
    # Boot Knoopix26 on hda5
    image=/boot/vmlinuz-2.6.6
     label="Linux(new)"
     root=/dev/hda5
     initrd=/boot/initrd.img-2.6.6
     append="lang=us apm=power-off ramdisk_size=100000 init=/etc/init nomce nofstab wheelmouse"
     read-only
    
    # Boot Mandrake on hda8
    image=/mnt/hda8/boot/vmlinuz
     label="Linux(old)"
     root=/dev/hda8
     initrd=/mnt/hda8/boot/initrd.img
     append="devfs=mount hdc=ide-scsi acpi=ht resume=/dev/hda6"
     read-only
     
    # Boot Windows on hda1
    other=/dev/hda1
     label="Windows"
     table=/dev/hda
    
    # Boots Knoppix 'toHD' install on hda1
    image=/mnt/hda1/bootlinux/isolinux/linux24
     label="backup"
     initrd=/mnt/hda1/bootlinux/isolinux/minirt24.gz
     append="home=scan myconfig=scan fromhd=/dev/hda1"

  6. #6
    Junior Member
    Join Date
    Nov 2004
    Posts
    4
    Hi CrashedAgain,
    Followings are my lilo.conf file.There is a little different from yours.Thanks again.
    Code:
    lba32
    
    # Overrides the default mapping between harddisk names and the BIOS'
    # harddisk order. Use with caution.
    #disk=/dev/hde
    #    bios=0x81
    
    #disk=/dev/sda
    #    bios=0x80
    
    # Specifies the boot device.  This is where Lilo installs its boot
    # block.  It can be either a partition, or the raw device, in which
    # case it installs in the MBR, and will overwrite the current MBR.
    #
    boot=/dev/hda
    
    # Specifies the device that should be mounted as root. ('/')
    #
    root=/dev/hda6
    
    # Enable map compaction:
    # Tries to merge read requests for adjacent sectors into a single
    # read request. This drastically reduces load time and keeps the
    # map smaller.  Using 'compact' is especially recommended when
    # booting from a floppy disk.  It is disabled here by default
    # because it doesn't always work.
    #
    # compact
    
    # Default menu for Debian. (Using the images from debian-bootscreen)
    # from Philipp Wolfer <phil@newswriter.org>.
    bitmap=/usr/share/lilo/debianlilo.bmp
    bmp-colors=1,,0,2,,0
    bmp-table=120p,173p,1,15,17
    bmp-timer=254p,432p,1,0,0
    
    # Install the specified file as the new boot sector.
    # LILO supports built in boot sectory, you only need
    # to specify the type, choose one from 'text', 'menu' or 'bitmap'.
    # new: install=bmp      old: install=/boot/boot-bmp.b
    # new: install=text     old: install=/boot/boot-text.b
    # new: install=menu     old: install=/boot/boot-menu.b or boot.b
    # default: 'menu' is default, unless you have a bitmap= line
    # Note: install=bmp must be used to see the bitmap menu.
    # install=menu
    # install=bmp
    install=bmp
    
    # Specifies the number of _tenths_ of a second LILO should
    # wait before booting the first image.  LILO
    # doesn't wait if DELAY is omitted or if DELAY is set to zero.
    
    delay=20
    
    # Prompt to use certaing image. If prompt is specified without timeout,
    # boot will not take place unless you hit RETURN
    prompt
    timeout=50
    
    # Specifies the location of the map file. If MAP is
    # omitted, a file /boot/map is used.
    map=/boot/map
    
    # Specifies the VGA text mode that should be selected when
    # booting. The following values are recognized (case is ignored):
    #   NORMAL  select normal 80x25 text mode.
    #   EXTENDED  select 80x50 text mode. The word EXTENDED can be
    #     abbreviated to EXT.
    #   ASK  stop and ask for user input (at boot time).
    #   <number>  use the corresponding text mode. A list of available modes
    #     can be obtained by booting with  vga=ask  and pressing [Enter].
    vga=791
    
    # You can set a password here, and uncomment the 'restricted' lines
    # in the image definitions below to make it so that a password must
    # be typed to boot anything but a default configuration.  If a
    # command line is given, other than one specified by an 'append'
    # statement in 'lilo.conf', the password will be required, but a
    # standard default boot will not require one.
    #
    # This will, for instance, prevent anyone with access to the
    # console from booting with something like 'Linux init=/bin/sh',
    # and thus becoming 'root' without proper authorization.
    #
    # Note that if you really need this type of security, you will
    # likely also want to use 'install-mbr' to reconfigure the MBR
    # program, as well as set up your BIOS to disallow booting from
    # removable disk or CD-ROM, then put a password on getting into the
    # BIOS configuration as well.  Please RTFM 'install-mbr(8)'.
    #
    # password=tatercounter2000
    
    # You can put a customized boot message up if you like.  If you use
    # 'prompt', and this computer may need to reboot unattended, you
    # must specify a 'timeout', or it will sit there forever waiting
    # for a keypress.  'single-key' goes with the 'alias' lines in the
    # 'image' configurations below.  eg: You can press '1' to boot
    # 'Linux', '2' to boot 'LinuxOLD', if you uncomment the 'alias'.
    #
    # message=/boot/bootmess.txt
    #       prompt
    #       single-key
    #       delay=100
    #       timeout=100
    
    # Kernel command line options that apply to all installed images go
    # here.  See: The 'boot-prompt-HOWO' and 'kernel-parameters.txt' in
    # the Linux kernel 'Documentation' directory.
    #
    append="nofstab"
    # Boot up Linux by default.
    #
    default="Linux"
    
    image=/boot/vmlinuz
            label="Linux"
            initrd=/boot/initrd.img
            append="ramdisk_size=100000 init=/etc/init lang=us apm=power-off nomce quiet"
            read-only
    image=/boot/vmlinuz-2.4.27
            label="Linux(2.4)-1"
            initrd=/boot/initrd.img-2.4.27
            append="ramdisk_size=100000 init=/etc/init lang=us apm=power-off nomce quiet"
            read-only
    
    image=/boot/vmlinuz-2.6.7
            label="Linux(2.6)-2"
            initrd=/boot/initrd.img-2.6.7
            append="ramdisk_size=100000 init=/etc/init lang=us apm=power-off nomce quiet"
            read-only
    [/code]undefined

  7. #7
    Senior Member registered user
    Join Date
    Jun 2004
    Posts
    788
    # Kernel command line options that apply to all installed images go
    # here. See: The 'boot-prompt-HOWO' and 'kernel-parameters.txt' in
    # the Linux kernel 'Documentation' directory.
    #
    append="nofstab"
    # Boot up Linux by default.
    #
    Never put cheatcodes on this "append" line....It won't work.
    Put cheatcode on append line after you declare your image.
    Do like Crashed did:

    Code:
    image=/boot/vmlinuz-2.6.6 
     label="Linux(new)" 
     root=/dev/hda5 
     initrd=/boot/initrd.img-2.6.6 
     append="lang=us apm=power-off ramdisk_size=100000 init=/etc/init nomce nofstab wheelmouse" 
     read-only
    and yours should look like this:
    Code:
    image=/boot/vmlinuz-2.4.27 
            label="Linux(2.4)-1" 
            initrd=/boot/initrd.img-2.4.27 
            append="ramdisk_size=100000 init=/etc/init lang=us apm=power-off nomce quiet nofstab" 
            read-only

  8. #8
    Junior Member registered user
    Join Date
    Jun 2004
    Location
    Australia
    Posts
    17

    Re: problems with create auto mounted file systems

    Quote Originally Posted by Reven
    It seem that when system reboot ,the file fstab is rewriten.
    Only the part of the file after the first line "#Added by KNOPPIX" is rewritten.

    So make changes above that line, like this:

    Code:
    /dev/hda6  /  ext3  defaults,errors=remount-ro  0  1
    proc  /proc  proc  defaults  0  0
    /dev/fd0  /floppy  vfat  defaults,user,noauto,showexec,umask=022  0  0
    usbdevfs  /proc/bus/usb  usbdevfs  defaults  0  0
    sysfs  /sys  sysfs  defaults  0  0
    /dev/cdrom /cdrom  iso9660  defaults,ro,user,noexec,noauto  0  0
    /dev/dvd /dvd  iso9660  defaults,ro,user,noexec,noauto  0  0
    /dev/cdaudio /cdaudio  iso9660  defaults,ro,user,noexec,noauto  0  0
    
    # Put your changes here
    /dev/whatever /mountpoint ...
    
    # Added by KNOPPIX
    /dev/hda1 /mnt/hda1 ntfs noauto,users,exec,ro,umask=000 0 0
    
    ....
    Then you will still get the nice feature of Knoppix adding lines to your fstab - for example, if you have a USB drive plugged in when you turn on the computer, Knoppix will add a line for it in fstab and you can access it using a desktop icon.

    Also, with my version (3.4) I had to change the system initialisation sequence for the drive to actually be mounted, by doing the following in a console:
    Code:
    su root
    ln -s /etc/init.d/mountall.sh /etc/rcS.d/S39mountall

  9. #9
    Junior Member
    Join Date
    Nov 2004
    Posts
    4
    Hi,
    I tried two ways you recommended.For my case,the update of lilo.conf doesn't work and the update of fstab works.now I know that the comment line "Added by knoppix " in fstab file is not only a comment.
    Thanks both of you for help.

Similar Threads

  1. QTparted - how do you add other file systems?
    By Oxyacetylene in forum Customising & Remastering
    Replies: 4
    Last Post: 03-18-2005, 08:26 PM
  2. Mounting Sun Solaris file systems
    By aallenaia in forum General Support
    Replies: 1
    Last Post: 10-26-2004, 04:05 AM
  3. Replies: 0
    Last Post: 07-25-2003, 04:04 PM
  4. Encrypted File Systems
    By Incubii in forum Hdd Install / Debian / Apt
    Replies: 4
    Last Post: 07-16-2003, 08:04 AM
  5. auto: auto: no such file or directory
    By maddany in forum Hdd Install / Debian / Apt
    Replies: 1
    Last Post: 04-16-2003, 02:19 AM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  


IBM System X3500 M4 7383AC1 (E5-2650 v2 2.60GHz - 192GB RAM - M2000 - NO OS/HDD) picture

IBM System X3500 M4 7383AC1 (E5-2650 v2 2.60GHz - 192GB RAM - M2000 - NO OS/HDD)

$264.92



IBM Power S822 12-Bay Server System Power8 Core 3.42Ghz DVD-Rom Drive 64GB No HD picture

IBM Power S822 12-Bay Server System Power8 Core 3.42Ghz DVD-Rom Drive 64GB No HD

$399.99



IBM 7944AC1 System x3550 M3 Server 1*Intel Xeon X5650 2.67GHz 4GB SEE NOTES picture

IBM 7944AC1 System x3550 M3 Server 1*Intel Xeon X5650 2.67GHz 4GB SEE NOTES

$27.25



IBM Power 740 8205-E6C Express 8-SFF Power7 3.55GHz CPU 64GB RAM *No HDD* Server picture

IBM Power 740 8205-E6C Express 8-SFF Power7 3.55GHz CPU 64GB RAM *No HDD* Server

$191.99



IBM System x3250 M4 Server Intel Xeon E3-1220 3.10GHz 8GB RAM No HDDs picture

IBM System x3250 M4 Server Intel Xeon E3-1220 3.10GHz 8GB RAM No HDDs

$65.02



IBM Power 720 POWER7 00E6516 3.6GHz CPU 64GB RAM Server  picture

IBM Power 720 POWER7 00E6516 3.6GHz CPU 64GB RAM Server

$209.98



ibm server z series picture

ibm server z series

$16000.00



IBM Lenovo X3650 M5 2U 8x 2.5” CTO Rack Server – 2x HS, 2x 750W picture

IBM Lenovo X3650 M5 2U 8x 2.5” CTO Rack Server – 2x HS, 2x 750W

$199.00



IBM 8203 E4A p520 Server 8203-E4A 4.2GHz 2-Core POWER6 32GB RAM / NO HDD USED picture

IBM 8203 E4A p520 Server 8203-E4A 4.2GHz 2-Core POWER6 32GB RAM / NO HDD USED

$99.99



IBM System x3250 M1 1U Server Intel Pentium D @3.4 2GB RAM x2 250GB DRIVES NO OS picture

IBM System x3250 M1 1U Server Intel Pentium D @3.4 2GB RAM x2 250GB DRIVES NO OS

$27.99