Announcement

Collapse
No announcement yet.

[Solved] /home: waiting for /dev/disk/by-uuid

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

    [Solved] /home: waiting for /dev/disk/by-uuid

    Recently, well at least I think soo because I haven't rebooted this machine since KK release, I am getting this message:
    /home: waiting for /dev/disk/by-uuid/5517cdab-xxx-xxx
    /Data: waiting for /dev/disk/by-uuid/77cc-6b54

    Which considerably retards boot.

    The uuids are correct:
    fintan@fintanws2:~$ sudo fdisk -l
    [sudo] password for fintan:

    Platte /dev/sda: 251.0 GByte, 251000193024 Byte
    255 Köpfe, 63 Sektoren/Spuren, 30515 Zylinder
    Einheiten = Zylinder von 16065 × 512 = 8225280 Bytes
    Disk identifier: 0xcdadf915

    Gerät boot. Anfang Ende Blöcke Id System
    /dev/sda1 * 1 2152 17285908+ 83 Linux
    /dev/sda2 2153 30515 227825797+ f W95 Erw. (LBA)
    /dev/sda5 2153 15659 108494946 b W95 FAT32
    /dev/sda6 15660 15933 2200873+ 82 Linux Swap / Solaris
    /dev/sda7 15934 20048 33053706 83 Linux
    /dev/sda8 20049 22094 16434463+ 83 Linux
    /dev/sda9 22095 23796 13671283+ 83 Linux
    /dev/sda10 23797 30515 53970336 83 Linux

    Platte /dev/sdb: 120.0 GByte, 120034123776 Byte
    255 Köpfe, 63 Sektoren/Spuren, 14593 Zylinder
    Einheiten = Zylinder von 16065 × 512 = 8225280 Bytes
    Disk identifier: 0xfe6fdddd

    Gerät boot. Anfang Ende Blöcke Id System
    /dev/sdb1 2 14593 117210240 f W95 Erw. (LBA)
    /dev/sdb5 * 2 12492 100333926 83 Linux
    /dev/sdb6 12493 14593 16876251 83 Linux
    fintan@fintanws2:~$
    Bug?

    HP Pavilion dv6 core i7 (Main)
    4 GB Ram
    Kubuntu 18.10

    #2
    Re: /home: waiting for /dev/disk/by-uuid

    Those aren't UUIDs. Console, type:
    Code:
    blkid
    Compare the output to your fstab entries.
    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


      #3
      Re: /home: waiting for /dev/disk/by-uuid

      Sorry it is very early in the morning here
      fintan@fintanws2:~$ sudo blkid
      $/dev/sda6: UUID="f1a65db9-86d0-4203-8468-5b94a5b87f6a" TYPE="swap"
      /dev/sda8: UUID="8afa29fc-03cb-4344-adbb-ecacb49f3865" TYPE="ext4"
      /dev/sda9: UUID="6f2a0b1a-efa6-4674-9b53-0dbea6e60a44" TYPE="ext4"
      /dev/sdb6: UUID="ed81d0b1-a1f1-43cd-afcd-aa8b6707a63c" TYPE="ext4"
      /dev/sda1: UUID="71e3089b-50a5-4d1c-914b-519852dd8868" TYPE="ext4"
      /dev/sda5: UUID="47CC-6B54" TYPE="vfat"
      /dev/sda7: LABEL="/home" UUID="5517cdab-5747-4901-bcea-d81c24d99116" TYPE="ext3"
      /dev/sda10: LABEL="Vmware2" UUID="0a1f1736-90d7-439d-8f3f-ace44df6ccba" TYPE="ext3"
      /dev/sdb5: UUID="7ee5edf3-a181-4480-a9bb-f73458461346" TYPE="ext4"
      /dev/sdh1: UUID="492E-6AED" TYPE="vfat"
      fintan@fintanws2:~$ $

      HP Pavilion dv6 core i7 (Main)
      4 GB Ram
      Kubuntu 18.10

      Comment


        #4
        Re: /home: waiting for /dev/disk/by-uuid



        Okay, so UUIDs. And your fstab? Hard to compare the two when only one has been provided.
        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


          #5
          Re: /home: waiting for /dev/disk/by-uuid

          Yeah it is still early:
          # /etc/fstab: static file system information.
          #
          # Use 'blkid -o value -s UUID' to print the universally unique identifier
          # for a device; this may be used with UUID= as a more robust way to name
          # devices that works even if disks are added and removed. See fstab(5).
          #
          # <file system> <mount point> <type> <options> <dump> <pass>
          proc /proc proc defaults 0 0
          # / was on /dev/sda1 during installation
          UUID=71e3089b-50a5-4d1c-914b-519852dd8868 / ext4 errors=remount-ro 0 1
          # /Data was on /dev/sda5 during installation
          UUID=47CC-6B54 /Data vfat utf8,umask=007,gid=46 0 1
          # /Data2 was on /dev/sdb5 during installation
          UUID=7ee5edf3-a181-4480-a9bb-f73458461346 /Data2 ext4 defaults 0 2
          # /Vmware was on /dev/sda10 during installation
          UUID=0a1f1736-90d7-439d-8f3f-ace44df6ccba /Vmware ext3 defaults 0 2
          # /home was on /dev/sda7 during installation
          UUID=5517cdab-5747-4901-bcea-d81c24d99116 /home ext3 defaults 0 2
          # swap was on /dev/sda6 during installation
          UUID=f1a65db9-86d0-4203-8468-5b94a5b87f6a none swap sw 0 0
          /dev/scd0 /media/cdrom0 udf,iso9660 user,noauto,exec,utf8 0 0
          /dev/fd0 /media/floppy0 auto rw,user,noauto,exec,utf8 0 0
          /dev/scd0 /media/floppy1 auto rw,user,noauto,exec,utf8 0 0
          The machine boots but it takes ages
          HP Pavilion dv6 core i7 (Main)
          4 GB Ram
          Kubuntu 18.10

          Comment


            #6
            Re: /home: waiting for /dev/disk/by-uuid

            Looks okay to me. I do notice the following:
            # /Data was on /dev/sda5 during installation
            UUID=47CC-6B54 /Data vfat utf8,umask=007,gid=46 0 1
            Normally the only partition that is 0 1 is root, and all other partitions are 0 2.

            Is what you first posted:
            Recently, well at least I think soo because I haven't rebooted this machine since KK release, I am getting this message:
            /home: waiting for /dev/disk/by-uuid/5517cdab-xxx-xxx
            /Data: waiting for /dev/disk/by-uuid/77cc-6b54
            from a copy/paste, or did you type what you saw? The underlined don't match the UUIC for the /Data partition based on what blkid reports. The underlined 7 'should' be a 4; the cc should be UPPERCASE; the b should be UPPERCASE.
            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


              #7
              Re: /home: waiting for /dev/disk/by-uuid

              Did I say it was early when I wrote the first post?

              Yes, of course you are right.
              77cc-6b54
              is
              47CC-6b54

              I will try setting 01 to 02 on /data and see how that goes.
              HP Pavilion dv6 core i7 (Main)
              4 GB Ram
              Kubuntu 18.10

              Comment


                #8
                Re: /home: waiting for /dev/disk/by-uuid

                Thank you for point out the 0 1.

                Solved by setting all partitions except / to 0 0
                HP Pavilion dv6 core i7 (Main)
                4 GB Ram
                Kubuntu 18.10

                Comment


                  #9
                  Re: [Solved] /home: waiting for /dev/disk/by-uuid

                  Hmm.

                  How to fstab

                  fstab Syntax

                  Quote:
                  [Device] [Mount Point] [File_system] [Options] [dump] [fsck order]
                  Dump
                  Dump: Dump field sets whether the backup utility dump will backup file system. If set to "0" file system ignored, "1" file system is backed up.

                  Fsck order
                  Fsck: Fsck order is to tell fsck what order to check the file systems, if set to "0" file system is ignored.
                  Setting all but root to Fsck order 0 - file system (check) is ignored - probably isn't a good idea.
                  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


                    #10
                    Re: [Solved] /home: waiting for /dev/disk/by-uuid

                    Fsck order
                    Fsck: Fsck order is to tell fsck what order to check the file systems, if set to "0" file system is ignored.
                    I know but I do it manually anyway every two weeks
                    HP Pavilion dv6 core i7 (Main)
                    4 GB Ram
                    Kubuntu 18.10

                    Comment


                      #11
                      Re: [Solved] /home: waiting for /dev/disk/by-uuid

                      Originally posted by Fintan
                      Fsck order
                      Fsck: Fsck order is to tell fsck what order to check the file systems, if set to "0" file system is ignored.
                      I know but I do it manually anyway every two weeks
                      That's good practice, but I'd still leave boot time checks on for linux native filesystems (unclean shutdowns is a major cause of filesystem errors).

                      Did you try setting your Data partition (vfat) as 0 0, and native filesystems extX as 0 2 (root 0 1)?

                      Comment


                        #12
                        Re: [Solved] /home: waiting for /dev/disk/by-uuid

                        Hey, I remember seeing those messages the first time I booted after the 9.04->9.10 upgrade. The boot took slightly longer than it takes now, and I no longer see them during boot. Is there something wrong with my fstab?

                        Comment


                          #13
                          Re: [Solved] /home: waiting for /dev/disk/by-uuid

                          Originally posted by barbolani
                          Is there something wrong with my fstab?
                          Absolutely no way to answer that question without seeing your fstab entries.
                          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


                            #14
                            Re: [Solved] /home: waiting for /dev/disk/by-uuid

                            I have no blind idea abut fstab.

                            - Could you have a look on my one please ?

                            Code:
                            # <file system> <mount point>  <type> <options>    <dump> <pass>
                            proc      /proc      proc  defaults    0    0
                            
                            # / was on /dev/sda1 during installation
                            UUID=7b1658be-763b-404b-81ed-d125e9392434 /   ext3  errors=remount-ro 0    1
                            
                            # /home was on /dev/sda5 during installation
                            UUID=ff228e05-b2f3-4a8c-b47f-498ad919b243 /home   ext3  defaults    0    2
                            
                            # swap was on /dev/sda6 during installation
                            UUID=4913a46a-4e84-4d36-acf4-e258f57d895a none   swap  sw       0    0
                            
                            /dev/scd0    /media/cdrom0  udf, iso9660 user, noauto, exec, utf8       0    0
                            Code:
                            # <file system> <mount point>  <type> <options>    <dump> <pass>
                            proc      /proc      proc  defaults    0    0
                            
                            # / was on /dev/sda1 during installation
                            UUID=7b1658be-763b-404b-81ed-d125e9392434 /        ext3  errors=remount-ro 0    1
                            
                            # /home was on /dev/sda5 during installation
                            UUID=ff228e05-b2f3-4a8c-b47f-498ad919b243 /home      ext3  defaults    0    2
                            
                            # swap was on /dev/sda6 during installation
                            UUID=4913a46a-4e84-4d36-acf4-e258f57d895a none      swap  sw       0    0
                            
                            /dev/scd0    /media/cdrom0  udf,iso9660 user,noauto,exec,utf8 0    0
                            Both from fstab. I made gaps for clearer view.

                            I made clean installation. Error during boot (just after power up) keeps coming up.
                            I can't get the message my whole log looks like that:
                            Code:
                            2009-11-09 09:50:09	aspire	wpa_supplicant[1158]	CTRL-EVENT-SCAN-RESULTS 
                            2009-11-09 09:51:36	aspire	PackageKit	WARNING: Recursive dependencies are not implemented
                            PS - what to change to see all boot messages on screen during boot?
                            Kubuntu Karmic Koala AMD64bit Acer Aspire 7520

                            Comment


                              #15
                              Re: [Solved] /home: waiting for /dev/disk/by-uuid

                              Unfortunately, there isn't anything 'easily' done to have *all* the boot messages logged. Logging the boot messages was something that used to occur, but was 'removed' quite some time ago. Back when UnicornRider was still here, he found a way to 'unlock' that capability and sent me the script for doing so. Unfortunately, that was back when I was running Edgy Eft, and I have long since lost the instructions, and UnicornRider is no more.

                              What is the issue with your booting and the fstab file? What isn't happening? Are you able to boot fully or no?
                              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