Hang after bootloader, looking for device
I tried to copy my bootable partition (e.g. sda1) from a removable drive to my internal drive (e.g. at sdb2) for an openSUSE 42.3 installation. It took me a bit of time to correct the bootloader entries referencing /dev/sda1, but eventually, I thought I had updated all of the references to indicate the correct partition, and also in /etc/fstab.
But, when I select the entry in the bootloader, after the initial booting messages, the system hangs with a message like:
A start job is running for dev-sda2.device (9s / no limit)
The start job continues to run until I forcibly power off the system.
I have double and triple-checked the bootloader (/boot/grub2/grub.cfg) and /etc/fstab files to ensure that they are referencing the partition's new location, or Label, or UUID. Why would my system still have problems detecting the drive/device?
boot systemd partition boot-loader
asked Dec 10 at 7:28
palswim
1,56111731
add a comment |
I tried to copy my bootable partition (e.g. sda1) from a removable drive to my internal drive (e.g. at sdb2) for an openSUSE 42.3 installation. It took me a bit of time to correct the bootloader entries referencing /dev/sda1, but eventually, I thought I had updated all of the references to indicate the correct partition, and also in /etc/fstab.
But, when I select the entry in the bootloader, after the initial booting messages, the system hangs with a message like:
A start job is running for dev-sda2.device (9s / no limit)
The start job continues to run until I forcibly power off the system.
I have double and triple-checked the bootloader (/boot/grub2/grub.cfg) and /etc/fstab files to ensure that they are referencing the partition's new location, or Label, or UUID. Why would my system still have problems detecting the drive/device?
boot systemd partition boot-loader
asked Dec 10 at 7:28
palswim
1,56111731
This message is generated by systemd, not grub or kernel.
– Ipor Sircer
Dec 10 at 7:37
add a comment |
I tried to copy my bootable partition (e.g. sda1) from a removable drive to my internal drive (e.g. at sdb2) for an openSUSE 42.3 installation. It took me a bit of time to correct the bootloader entries referencing /dev/sda1, but eventually, I thought I had updated all of the references to indicate the correct partition, and also in /etc/fstab.
But, when I select the entry in the bootloader, after the initial booting messages, the system hangs with a message like:
A start job is running for dev-sda2.device (9s / no limit)
The start job continues to run until I forcibly power off the system.
I have double and triple-checked the bootloader (/boot/grub2/grub.cfg) and /etc/fstab files to ensure that they are referencing the partition's new location, or Label, or UUID. Why would my system still have problems detecting the drive/device?
boot systemd partition boot-loader
asked Dec 10 at 7:28
palswim
1,56111731
I tried to copy my bootable partition (e.g. sda1) from a removable drive to my internal drive (e.g. at sdb2) for an openSUSE 42.3 installation. It took me a bit of time to correct the bootloader entries referencing /dev/sda1, but eventually, I thought I had updated all of the references to indicate the correct partition, and also in /etc/fstab.
But, when I select the entry in the bootloader, after the initial booting messages, the system hangs with a message like:
A start job is running for dev-sda2.device (9s / no limit)
The start job continues to run until I forcibly power off the system.
I have double and triple-checked the bootloader (/boot/grub2/grub.cfg) and /etc/fstab files to ensure that they are referencing the partition's new location, or Label, or UUID. Why would my system still have problems detecting the drive/device?
boot systemd partition boot-loader
boot systemd partition boot-loader
asked Dec 10 at 7:28
palswim
1,56111731
asked Dec 10 at 7:28
palswim
1,56111731
edited Dec 11 at 5:37
asked Dec 10 at 7:28
palswim
1,56111731
asked Dec 10 at 7:28
palswim
1,56111731
asked Dec 10 at 7:28
palswim
1,56111731
1,56111731
This message is generated by systemd, not grub or kernel.
– Ipor Sircer
Dec 10 at 7:37
add a comment |
This message is generated by systemd, not grub or kernel.
– Ipor Sircer
Dec 10 at 7:37
This message is generated by systemd, not grub or kernel.
– Ipor Sircer
Dec 10 at 7:37
This message is generated by systemd, not grub or kernel.
– Ipor Sircer
Dec 10 at 7:37
add a comment |
1 Answer
1
active
oldest
votes
I believe openSUSE references the UUIDs of the partitions in its boot code, so I subsequently had to re-make the initialization image with mkinitrd -f.
Not being able to boot into the operating system on this partition, I had to mount the partition and then perform this operation in a chroot jail:
mount /dev/sda2 /mnt
mount -B /dev /mnt/dev
mount -B /sys /mnt/sys
mount -B /proc /mnt/proc
chroot /mnt
mkinitrd -f
yast bootloader # Possibly necessary, though I only needed the mkinitrd call
answered Dec 10 at 7:28
palswim
1,56111731
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%2f487060%2fhang-after-bootloader-looking-for-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
I believe openSUSE references the UUIDs of the partitions in its boot code, so I subsequently had to re-make the initialization image with mkinitrd -f.
Not being able to boot into the operating system on this partition, I had to mount the partition and then perform this operation in a chroot jail:
mount /dev/sda2 /mnt
mount -B /dev /mnt/dev
mount -B /sys /mnt/sys
mount -B /proc /mnt/proc
chroot /mnt
mkinitrd -f
yast bootloader # Possibly necessary, though I only needed the mkinitrd call
answered Dec 10 at 7:28
palswim
1,56111731
add a comment |
I believe openSUSE references the UUIDs of the partitions in its boot code, so I subsequently had to re-make the initialization image with mkinitrd -f.
Not being able to boot into the operating system on this partition, I had to mount the partition and then perform this operation in a chroot jail:
mount /dev/sda2 /mnt
mount -B /dev /mnt/dev
mount -B /sys /mnt/sys
mount -B /proc /mnt/proc
chroot /mnt
mkinitrd -f
yast bootloader # Possibly necessary, though I only needed the mkinitrd call
answered Dec 10 at 7:28
palswim
1,56111731
add a comment |
I believe openSUSE references the UUIDs of the partitions in its boot code, so I subsequently had to re-make the initialization image with mkinitrd -f.
Not being able to boot into the operating system on this partition, I had to mount the partition and then perform this operation in a chroot jail:
mount /dev/sda2 /mnt
mount -B /dev /mnt/dev
mount -B /sys /mnt/sys
mount -B /proc /mnt/proc
chroot /mnt
mkinitrd -f
yast bootloader # Possibly necessary, though I only needed the mkinitrd call
answered Dec 10 at 7:28
palswim
1,56111731
I believe openSUSE references the UUIDs of the partitions in its boot code, so I subsequently had to re-make the initialization image with mkinitrd -f.
Not being able to boot into the operating system on this partition, I had to mount the partition and then perform this operation in a chroot jail:
mount /dev/sda2 /mnt
mount -B /dev /mnt/dev
mount -B /sys /mnt/sys
mount -B /proc /mnt/proc
chroot /mnt
mkinitrd -f
yast bootloader # Possibly necessary, though I only needed the mkinitrd call
answered Dec 10 at 7:28
palswim
1,56111731
answered Dec 10 at 7:28
palswim
1,56111731
answered Dec 10 at 7:28
palswim
1,56111731
answered Dec 10 at 7:28
palswim
1,56111731
1,56111731
add a comment |
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.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- 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%2f487060%2fhang-after-bootloader-looking-for-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
This message is generated by systemd, not grub or kernel.
– Ipor Sircer
Dec 10 at 7:37