Announcement

Collapse
No announcement yet.

feisty>gutsy: could not mount disks anymore

Collapse
This topic is closed.
X
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    #16
    Re: feisty>gutsy: could not mount disks anymore

    If you are going to do a new installation, which I agree should not be required but sometimes is the best way to go, I would offer this for consideration:

    - put the root filesystem in a sdx0 partition, if you can, and set the "boot" flag on it
    - using the Alternate Install CD, you can easily set the "/", "/home", and "swap" partitions, and the others will be automatically mounted on /media/sdxx mount points.
    - the installation process will create a /etc/fstab file with the appropriate UUID and fs_passno values

    You should come out with an /etc/fstab file that looks more like this (in form, if not content):

    Code:
    # /etc/fstab: static file system information.
    #
    # <file system> <mount point>  <type> <options>    <dump> <pass>
    proc /proc proc defaults 0 0
    # /dev/sdb1
    UUID=1991a076-aba8-4e5d-9db9-65be3b608f11 / xfs nouser,defaults,atime,auto,rw,dev,exec,suid 0 1
    # /dev/sdb3
    UUID=4fe0930c-b56d-455f-b8be-504a214c9b31 /home xfs nouser,atime,auto,rw,dev,exec,suid 0 2
    # /dev/sda1
    UUID=e731c3cf-e2ff-4692-8353-ede2a3dcb85e /media/sda1 xfs nouser,defaults,atime,auto,rw,dev,exec,suid 0 2
    # /dev/sdc2
    UUID=a50bfecb-c48b-4f1e-bcf4-8597166eae6c /media/sdc2 reiserfs nouser,defaults,atime,auto,rw,dev,exec,suid 0 2
    # /dev/sdc3
    UUID=003245d2-a1dc-4c1c-bc52-32601bc65e46 /media/sdc3 reiserfs nouser,defaults,atime,auto,rw,dev,exec,suid 0 2
    # /dev/sdc4
    UUID=f98e6bb6-0ed4-45a8-b596-9ed76e2d2364 /media/sdc4 reiserfs nouser,defaults,atime,auto,rw,dev,exec,suid 0 2
    # /dev/sdd1
    UUID=92c0453f-2a35-40d5-8013-b8870ed66127 /media/sdd1 xfs nouser,defaults,atime,auto,rw,dev,exec,suid 0 2
    # /dev/sdd2
    UUID=f4e36b39-af7d-475c-8990-b2093f558295 /media/sdd2 xfs nouser,defaults,atime,auto,rw,dev,exec,suid 0 2
    # /dev/sdd3
    UUID=eba33247-0dbb-482c-9351-81505a953864 /media/sdd3 xfs nouser,defaults,atime,auto,rw,dev,exec,suid 0 2
    # /dev/sde1
    UUID=ae2cd406-8e2a-4581-b422-9337e6bb3bc7 /media/sde1 xfs nouser,defaults,atime,auto,rw,dev,exec,suid 0 2
    # /dev/sdc1
    UUID=b132702a-c995-42d6-be8e-5b1444bea405 none swap sw 0 0
    /dev/scd0 /media/cdrom0 udf,iso9660 user,atime,noauto,rw,dev,exec,suid 0 0
    /dev/fd0 /media/floppy0 auto user,atime,noauto,rw,dev,exec,suid 0 0
    And then fsck should be happy with it.

    Comment


      #17
      Re: feisty&gt;gutsy: could not mount disks anymore

      Please also note that I had a typo - missing the additional 'U' in the UUID entry for /
      I've corrected each of the posts.
      Windows no longer obstructs my view.
      Using Kubuntu Linux since March 23, 2007.
      "It is a capital mistake to theorize before one has data." - Sherlock Holmes

      Comment


        #18
        Re: feisty&gt;gutsy: could not mount disks anymore

        Thanks for all your hard tries guys but it fail again I used the following fstab (btw I didn't make the mistake forgotting the /proc entry

        Code:
        # /etc/fstab: static file system information.
        #
        # <file system> <mount point> <type> <options>   <dump> <pass>
        proc /proc proc defaults 0 0
        
        # hda IDE Master 20G (C:)
        #/dev/hda2 / ext3 nouser,defaults,errors=remount-ro,atime,auto,rw,dev,exec,suid 0 1
        UUID="83c97eaa-ebba-47db-9674-dc5d88d1885a" / ext3 nouser,defaults,errors=remount-ro,atime,auto,rw,dev,exec,suid 0 1
        #/dev/hda1 /media/hda1 vfat defaults,utf8,umask=007,uid=0,gid=46,auto,rw,nouser 0 1
        UUID="2131-0C00" /media/hda1 vfat defaults,utf8,umask=007,uid=0,gid=46,auto,rw,nouser 0 2
        #/dev/hda3 none swap sw 0 0
        UUID="ef7e9d9f-9a64-40fa-8d76-d77781eeef8d" none swap sw 0 0
        
        # hdb IDE Slave 180G (D:)
        #/dev/hdb1 /media/hdb1 vfat defaults,utf8,umask=007,uid=0,gid=46,auto,rw,nouser 0 1
        UUID="2FA8-F95A" /media/hdb1 vfat defaults,utf8,umask=007,uid=0,gid=46,auto,rw,nouser 0 2
        #/dev/hdb2 /data2 ext3 nouser,defaults,errors=remount-ro,atime,auto,rw,dev,exec,suid 0 1
        UUID="ea725ee0-a80d-41e1-b26f-83ec7039e6ca" /data2 ext3 nouser,defaults,errors=remount-ro,atime,auto,rw,dev,exec,suid 0 2
        
        # sda Sata 500G
        #/dev/sda1 /home ext3 nouser,defaults,errors=remount-ro,atime,auto,rw,dev,exec,suid 0 1
        UUID="340380e4-63d4-4547-9f38-6c486fd9c2e3" /home ext3 nouser,defaults,errors=remount-ro,atime,auto,rw,dev,exec,suid 0 2
        #/dev/sda2 /data1 ext3 nouser,defaults,errors=remount-ro,atime,auto,rw,dev,exec,suid 0 1
        UUID="8b248171-0fd8-4c1d-9ed8-20c333948137" /data1 ext3 nouser,defaults,errors=remount-ro,atime,auto,rw,dev,exec,suid 0 2
        
        # clubpocket USB
        #/dev/clubpocket1 /data3 vfat auto,user,rw,nosuid,nodev,noatime,uid=1000,gid=46,utf8,shortname=lower
        But I'm now not really sure that fstab stuff is the problem, there should be something else, I could not believe that fstab became so fragile... or that such an upgrade broke something so basic so easily. I suspect something related with kernel modules should be the problem (just an intuition)

        best

        Comment


          #19
          Re: feisty&gt;gutsy: could not mount disks anymore

          Glad that you caught that!

          I'm not sure why you have the / partition options the way you do:
          nouser,defaults,errors=remount-ro,atime,auto,rw,dev,exec,suid 0 1
          These are my / partition options:
          defaults,errors=remount-ro 0 1
          Try changing your / partition options to mine.
          Windows no longer obstructs my view.
          Using Kubuntu Linux since March 23, 2007.
          "It is a capital mistake to theorize before one has data." - Sherlock Holmes

          Comment


            #20
            Re: feisty&gt;gutsy: could not mount disks anymore

            I'm suspicious of vfat filesystems -- I think they're kind of fragile. Is that what fsck is having trouble with?

            Comment


              #21
              Re: feisty&gt;gutsy: could not mount disks anymore

              I finaly reinstalled from scratch and it works perfectly (except some few configurations changes).

              For info the fstab generated is:
              Code:
              # /etc/fstab: static file system information.
              #
              # <file system> <mount point>  <type> <options>    <dump> <pass>
              proc      /proc      proc  defaults    0    0
              # /dev/hda2
              UUID=bf94c5ae-236e-4597-a959-67a641e8a206 /        ext3  defaults,errors=remount-ro 0    1
              # /dev/sda2
              UUID=8b248171-0fd8-4c1d-9ed8-20c333948137 /data1     ext3  defaults    0    2
              # /dev/hdb2
              UUID=ea725ee0-a80d-41e1-b26f-83ec7039e6ca /data2     ext3  defaults    0    2
              # /dev/sda1
              UUID=340380e4-63d4-4547-9f38-6c486fd9c2e3 /home      ext3  defaults    0    2
              # /dev/hda1
              UUID=2131-0C00 /media/hda1   vfat  defaults,utf8,umask=007,gid=46 0    1
              # /dev/hdb1
              UUID=2FA8-F95A /media/hdb1   vfat  defaults,utf8,umask=007,gid=46 0    1
              # /dev/hda3
              UUID=ef7e9d9f-9a64-40fa-8d76-d77781eeef8d none      swap  sw       0    0
              /dev/hdd    /media/cdrom0  udf,iso9660 user,noauto,exec 0    0
              /dev/fd0    /media/floppy0 auto  rw,user,noauto,exec 0    0
              I don't see any major differences between this one and the one that was there before (except the order) ... this confirm that the problem was an upgrade problem of the kernel...

              thanks again for your help

              Comment


                #22
                Re: feisty&gt;gutsy: could not mount disks anymore

                Relook at post #17. The fstab you showed us has quotes (") around all the UUID= strings. That would have caused the problem!

                Looking at my 01 January 2008, 11:51:58 post, where I provided the modified fstab, I see that I left in one single ":
                UUID="83c97eaa-ebba-47db-9674-dc5d88d1885a / ext3 nouser,defaults,errors=remount-ro,atime,auto,rw,dev,exec,suid 0 1
                All the other lines were correct. If my error on the line above was what caused you to include the quotes in your fstab, my appologies. It is my belief, that had you not had the quotes in the fstab file you used, you would not have had to reinstall. :P

                Windows no longer obstructs my view.
                Using Kubuntu Linux since March 23, 2007.
                "It is a capital mistake to theorize before one has data." - Sherlock Holmes

                Comment

                Working...
                X