The disk drive for uuid = XXXX (/media/sda1) is not reday yet or not present

1. Fault

2. Online Solutions

The disk drive for/media/sda1 is not reday yet or not present

After ubuntu is installed, you may receive the following prompt every time you restart ubuntu:

The disk drive for/media/sda1 is not reday yet or not present

Contiune to wait; or Press S to skip mounting or M for manual recovery.

The cause of this error is that an error occurs when ubuntu is attached to a windows hard disk. The solution is simple,

Method 1:

Open the fstab file

Sudo vim/etc/fstab comment out the problematic partition, and add the # sign at the beginning of the line to comment out this line. Save and exit.

#/Etc/fstab: static file system information.
#
# <File system> <mount point> <type> <options> <dump> <pass>

Proc/proc nodev, noexec, nosuid 0 0
# Entry for/dev/sda8:
UUID = dc52cebd-3229-4bc9-988d-2ca727413f90/ext4 errors = remount-ro 0 1
# Entry for/dev/sda9:
UUID = bb8e2597-314b-472b-bc6a-c32d0b3b7f79/home ext4 defaults 0 2
# Entry for/dev/sda1:
UUID = 3008C33008C2F3BE/media/sda1 ntfs-3g ults, nls = utf8, umask = 0222 0
# Entry for/dev/sda7:
UUID = 35b43bc2-542b-493f-8650-4223e9e50588 none swap sw 0 0
# Entry for/dev/sda5:
/Dev/sda5/media/sda5/ntfs user, auto, umask = 002, gid = 1000, utf8 0 0
# Entry for/dev/sda6:
/Dev/sda6/media/sda6/ntfs user, auto, umask = 002, gid = 1000, utf8 0 0
Method 2:

Ls-all/dev/disk/by-uuid // display partition information. You can view the uuid of each partition.

Check whether the uuid of the faulty partition is the same as the uuid of the faulty partition in the/etc/fstab file. If the uuid is different, this error occurs, or the partition format of the hard disk is different from that in the fstab table,

For example: UUID = 3008C33008C2F3BE/media/sda1 ntfs-3g ults, nls = utf8, umask = 0222 0

Sda1 actual partition format fat32 but in the fstab mount partition format when the ntfs-3g at this time will appear this problem (hehe ran the question) to turn

Ls-all/dev/disk/by-uuid: Check the uuid Number of the faulty partition. If it is different from that in fstab, replace the uuid In the fstab file with the uuid In the ls-all command.

Replace the uuid of the partition and save and exit. This error will not occur when the partition is started.

I found the first method on the Internet. I felt that it was not very good to comment out, so I used the uuid to mount the partition to solve this problem. :
Method 3:

Cause: due to the small space allocated to/root during Ubuntu installation (only 3 GB), it is found that updates cannot be used (the disk space required for updates is larger than the remaining space ), so I want to merge/home to/root, and then create a new 10 Gb hard disk (Vmware) As/home. Everything is done. As a result, the system startup prompt/home is not mounted and cannot be started. Press S to skip or M to manually fix it. (The message is probably The disk drive for/home is not ready yet or not present)

Two key things to solve the problem:/etc/fstab (store some partition information, including UUID) and blkid command (query partition UUID) (refer to 1)

The cause is that the uuid of the/home partition in/etc/fstab is the value when Ubuntu is first installed. After the new hard disk partition is/home, this UUID is no longer applicable. Therefore, you can modify the corresponding items in/etc/fstab by referring to the query result of the blkid command (using the VI editor ).

If you are prompted that the system cannot update the Desktop (folder),. nautilus (folder), and. ICEauthority (file), you can manually create them (sudo mkdir, touch ). And then modify. ICEauthority owner (you created with the root user and used not the root user for Logon. This will cause the file to be inaccessible. The prompt "cocould not update ICEauthority file/home/sername/" is displayed /. ICEauthority) change the command to $ sudo chown user-R/home/user
(Here the user is your user name) (reference: original)

3. My solution:

It was found that due to my use:

Vmware-vdiskmanager-x l2Gb D:/UbuntuDesk/Ubuntu. vmdk

This method is used to resize the hard disk. As a result, the new UUID of the hard disk is different from the uuid of the partition in the/etc/fstab file.

Solution:

Blkid command-> query the correct UUID-> Format the new partition and write the correct UUID into the/etc/fstab file.