Timed out waiting for device dev-disk-byx2duuid-C829x2dC4C1.device
I had formatted efi partition and installed windows again. I have dual boot Windows and Linux, then I installed the grub bootloader again from a live usb using these commands:
mount /dev/sda* /mnt
mount --bind /dev /mnt/dev
mount --bind /proc /mnt/proc
mount --bind /sys /mnt/sys
mount /dev/sda* /mnt/boot/efi
mount /mnt/hostrun
mount --bind /run /mnt/hostrun
chroot /mnt
grub-install /dev/sda
update-grub
exit
Then I unmounted all of this again. When I tried to boot, I got this messages:
[ TIME ] Timed out waiting for device dev-disk-byx2duuid-C829x2dC4C1.device.
[DEPEND] Dependency failed for file system check on /dev/disk/by-uuid/C829-C4C1.
[DEPEND] Dependency failed for /boot/efi.
[DEPEND] Dependency failed for Local File System.
and it turns me into emergency mode. How can I solve this problem?
uefi multiboot
asked Sep 27 '18 at 1:28
Mido AhmedMido Ahmed
135
add a comment |
I had formatted efi partition and installed windows again. I have dual boot Windows and Linux, then I installed the grub bootloader again from a live usb using these commands:
mount /dev/sda* /mnt
mount --bind /dev /mnt/dev
mount --bind /proc /mnt/proc
mount --bind /sys /mnt/sys
mount /dev/sda* /mnt/boot/efi
mount /mnt/hostrun
mount --bind /run /mnt/hostrun
chroot /mnt
grub-install /dev/sda
update-grub
exit
Then I unmounted all of this again. When I tried to boot, I got this messages:
[ TIME ] Timed out waiting for device dev-disk-byx2duuid-C829x2dC4C1.device.
[DEPEND] Dependency failed for file system check on /dev/disk/by-uuid/C829-C4C1.
[DEPEND] Dependency failed for /boot/efi.
[DEPEND] Dependency failed for Local File System.
and it turns me into emergency mode. How can I solve this problem?
uefi multiboot
asked Sep 27 '18 at 1:28
Mido AhmedMido Ahmed
135
Welcome , Check the UUID's in your/etc/fstabusingblkidcommand.
– GAD3R
Sep 27 '18 at 17:39
I've experienced this sort of issue before. It's because when you reformat a file system its UUID changes and your /etc/fstab is using the old UUID. As a filesystem with the old UUID no longer exists udev fails to find it and you get this error. Update the UUID in /etc/fstab using blkid and your system will manage to correctly boot again as this error will be gone.
– Brenton Horne
Sep 28 '18 at 11:34
thanks, i checked it and it was with different UUID. now it's working
– Mido Ahmed
Sep 28 '18 at 15:42
add a comment |
I had formatted efi partition and installed windows again. I have dual boot Windows and Linux, then I installed the grub bootloader again from a live usb using these commands:
mount /dev/sda* /mnt
mount --bind /dev /mnt/dev
mount --bind /proc /mnt/proc
mount --bind /sys /mnt/sys
mount /dev/sda* /mnt/boot/efi
mount /mnt/hostrun
mount --bind /run /mnt/hostrun
chroot /mnt
grub-install /dev/sda
update-grub
exit
Then I unmounted all of this again. When I tried to boot, I got this messages:
[ TIME ] Timed out waiting for device dev-disk-byx2duuid-C829x2dC4C1.device.
[DEPEND] Dependency failed for file system check on /dev/disk/by-uuid/C829-C4C1.
[DEPEND] Dependency failed for /boot/efi.
[DEPEND] Dependency failed for Local File System.
and it turns me into emergency mode. How can I solve this problem?
uefi multiboot
asked Sep 27 '18 at 1:28
Mido AhmedMido Ahmed
135
I had formatted efi partition and installed windows again. I have dual boot Windows and Linux, then I installed the grub bootloader again from a live usb using these commands:
mount /dev/sda* /mnt
mount --bind /dev /mnt/dev
mount --bind /proc /mnt/proc
mount --bind /sys /mnt/sys
mount /dev/sda* /mnt/boot/efi
mount /mnt/hostrun
mount --bind /run /mnt/hostrun
chroot /mnt
grub-install /dev/sda
update-grub
exit
Then I unmounted all of this again. When I tried to boot, I got this messages:
[ TIME ] Timed out waiting for device dev-disk-byx2duuid-C829x2dC4C1.device.
[DEPEND] Dependency failed for file system check on /dev/disk/by-uuid/C829-C4C1.
[DEPEND] Dependency failed for /boot/efi.
[DEPEND] Dependency failed for Local File System.
and it turns me into emergency mode. How can I solve this problem?
uefi multiboot
uefi multiboot
asked Sep 27 '18 at 1:28
Mido AhmedMido Ahmed
135
asked Sep 27 '18 at 1:28
Mido AhmedMido Ahmed
135
edited Sep 27 '18 at 17:29
Mido Ahmed
asked Sep 27 '18 at 1:28
Mido AhmedMido Ahmed
135
asked Sep 27 '18 at 1:28
Mido AhmedMido Ahmed
135
asked Sep 27 '18 at 1:28
Mido AhmedMido Ahmed
135
135
Welcome , Check the UUID's in your/etc/fstabusingblkidcommand.
– GAD3R
Sep 27 '18 at 17:39
I've experienced this sort of issue before. It's because when you reformat a file system its UUID changes and your /etc/fstab is using the old UUID. As a filesystem with the old UUID no longer exists udev fails to find it and you get this error. Update the UUID in /etc/fstab using blkid and your system will manage to correctly boot again as this error will be gone.
– Brenton Horne
Sep 28 '18 at 11:34
thanks, i checked it and it was with different UUID. now it's working
– Mido Ahmed
Sep 28 '18 at 15:42
add a comment |
Welcome , Check the UUID's in your/etc/fstabusingblkidcommand.
– GAD3R
Sep 27 '18 at 17:39
I've experienced this sort of issue before. It's because when you reformat a file system its UUID changes and your /etc/fstab is using the old UUID. As a filesystem with the old UUID no longer exists udev fails to find it and you get this error. Update the UUID in /etc/fstab using blkid and your system will manage to correctly boot again as this error will be gone.
– Brenton Horne
Sep 28 '18 at 11:34
thanks, i checked it and it was with different UUID. now it's working
– Mido Ahmed
Sep 28 '18 at 15:42
Welcome , Check the UUID's in your
/etc/fstab using blkid command.– GAD3R
Sep 27 '18 at 17:39
Welcome , Check the UUID's in your
/etc/fstab using blkid command.– GAD3R
Sep 27 '18 at 17:39
I've experienced this sort of issue before. It's because when you reformat a file system its UUID changes and your /etc/fstab is using the old UUID. As a filesystem with the old UUID no longer exists udev fails to find it and you get this error. Update the UUID in /etc/fstab using blkid and your system will manage to correctly boot again as this error will be gone.
– Brenton Horne
Sep 28 '18 at 11:34
I've experienced this sort of issue before. It's because when you reformat a file system its UUID changes and your /etc/fstab is using the old UUID. As a filesystem with the old UUID no longer exists udev fails to find it and you get this error. Update the UUID in /etc/fstab using blkid and your system will manage to correctly boot again as this error will be gone.
– Brenton Horne
Sep 28 '18 at 11:34
thanks, i checked it and it was with different UUID. now it's working
– Mido Ahmed
Sep 28 '18 at 15:42
thanks, i checked it and it was with different UUID. now it's working
– Mido Ahmed
Sep 28 '18 at 15:42
add a comment |
1 Answer
1
active
oldest
votes
Windows formatted you EFI partition and thus its ID changed...
you need to add the UUID of the new partition to the one in your /etc/fstab.
if you enter maintenance mode or have a terminal which seems you do, do this...
sudo blkid
write down the UUID of the EFI partition then
sudo nano /etc/fstab
change the UUID of the old EFI partition to the one you wrote down.
if you don't know which is your EFI partition look in sudo blkid output. the should be a partition where it says type=efi...
edited Jan 24 at 16:30
JJD
2922722
answered Sep 28 '18 at 13:35
NhlalukoGNhlalukoG
361
I am fighting with a similar issue - maybe you have an advice.
– JJD
Jan 24 at 14:57
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "106"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f471716%2ftimed-out-waiting-for-device-dev-disk-by-x2duuid-c829-x2dc4c1-device%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Windows formatted you EFI partition and thus its ID changed...
you need to add the UUID of the new partition to the one in your /etc/fstab.
if you enter maintenance mode or have a terminal which seems you do, do this...
sudo blkid
write down the UUID of the EFI partition then
sudo nano /etc/fstab
change the UUID of the old EFI partition to the one you wrote down.
if you don't know which is your EFI partition look in sudo blkid output. the should be a partition where it says type=efi...
edited Jan 24 at 16:30
JJD
2922722
answered Sep 28 '18 at 13:35
NhlalukoGNhlalukoG
361
I am fighting with a similar issue - maybe you have an advice.
– JJD
Jan 24 at 14:57
add a comment |
Windows formatted you EFI partition and thus its ID changed...
you need to add the UUID of the new partition to the one in your /etc/fstab.
if you enter maintenance mode or have a terminal which seems you do, do this...
sudo blkid
write down the UUID of the EFI partition then
sudo nano /etc/fstab
change the UUID of the old EFI partition to the one you wrote down.
if you don't know which is your EFI partition look in sudo blkid output. the should be a partition where it says type=efi...
edited Jan 24 at 16:30
JJD
2922722
answered Sep 28 '18 at 13:35
NhlalukoGNhlalukoG
361
I am fighting with a similar issue - maybe you have an advice.
– JJD
Jan 24 at 14:57
add a comment |
Windows formatted you EFI partition and thus its ID changed...
you need to add the UUID of the new partition to the one in your /etc/fstab.
if you enter maintenance mode or have a terminal which seems you do, do this...
sudo blkid
write down the UUID of the EFI partition then
sudo nano /etc/fstab
change the UUID of the old EFI partition to the one you wrote down.
if you don't know which is your EFI partition look in sudo blkid output. the should be a partition where it says type=efi...
edited Jan 24 at 16:30
JJD
2922722
answered Sep 28 '18 at 13:35
NhlalukoGNhlalukoG
361
Windows formatted you EFI partition and thus its ID changed...
you need to add the UUID of the new partition to the one in your /etc/fstab.
if you enter maintenance mode or have a terminal which seems you do, do this...
sudo blkid
write down the UUID of the EFI partition then
sudo nano /etc/fstab
change the UUID of the old EFI partition to the one you wrote down.
if you don't know which is your EFI partition look in sudo blkid output. the should be a partition where it says type=efi...
edited Jan 24 at 16:30
JJD
2922722
answered Sep 28 '18 at 13:35
NhlalukoGNhlalukoG
361
edited Jan 24 at 16:30
JJD
2922722
edited Jan 24 at 16:30
JJD
2922722
edited Jan 24 at 16:30
JJD
2922722
2922722
answered Sep 28 '18 at 13:35
NhlalukoGNhlalukoG
361
answered Sep 28 '18 at 13:35
NhlalukoGNhlalukoG
361
answered Sep 28 '18 at 13:35
NhlalukoGNhlalukoG
361
361
I am fighting with a similar issue - maybe you have an advice.
– JJD
Jan 24 at 14:57
add a comment |
I am fighting with a similar issue - maybe you have an advice.
– JJD
Jan 24 at 14:57
I am fighting with a similar issue - maybe you have an advice.
– JJD
Jan 24 at 14:57
I am fighting with a similar issue - maybe you have an advice.
– JJD
Jan 24 at 14:57
add a comment |
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f471716%2ftimed-out-waiting-for-device-dev-disk-by-x2duuid-c829-x2dc4c1-device%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Welcome , Check the UUID's in your
/etc/fstabusingblkidcommand.– GAD3R
Sep 27 '18 at 17:39
I've experienced this sort of issue before. It's because when you reformat a file system its UUID changes and your /etc/fstab is using the old UUID. As a filesystem with the old UUID no longer exists udev fails to find it and you get this error. Update the UUID in /etc/fstab using blkid and your system will manage to correctly boot again as this error will be gone.
– Brenton Horne
Sep 28 '18 at 11:34
thanks, i checked it and it was with different UUID. now it's working
– Mido Ahmed
Sep 28 '18 at 15:42