A start job is running for dev-disk-byx2dpar…dffa6b3c0a51f.device no limit
Clash Royale CLAN TAG#URR8PPP
I have a VCSA that won't boot. It gets as far as:
A start job is running for dev-disk-byx2dpar...dffa6b3c0a51f.device (no limit)
What I'm trying to do is track down that UUID so I can start troubleshooting. This what I've attempted so far:
- Tried emergency mode - can't get past the start job
- Mounted an Ubuntu Live ISO, mounted the / filesystem and checked fstab - No mention of 'dffa6b3c0a51f' or anything close
- Commented out the swap entries in /etc/fstab - same issue upon boot
- Checked /var/log/messages for any clues - last entry was 12/11/18
- Checked and force repaired all of the filesystem - including LVMs
- Copied the system.journal to the rescue system and attempted to read the entries - No entries, last entry was on 12/11/18
- Researched the error. Suggestions so far have been:
systemctl show -p RequiredBy -p WantedBy dev-disk-by...
systemctl list-units | grep dev-disk
The problem here is that I can't get past the start job message as it's set to infinite and I can't cancel it. I've tried adjusting the timeout in systemd.conf to 90s but it didn't take.
This is the fstab from the mounted partition:
This is what I'm seeing on boot:
So here I am. Has anyone encountered this before and if so, how did you fix it?
filesystems systemd lvm vmware
asked Jan 28 at 12:46
Moif MurphyMoif Murphy
1176
add a comment |
I have a VCSA that won't boot. It gets as far as:
A start job is running for dev-disk-byx2dpar...dffa6b3c0a51f.device (no limit)
What I'm trying to do is track down that UUID so I can start troubleshooting. This what I've attempted so far:
- Tried emergency mode - can't get past the start job
- Mounted an Ubuntu Live ISO, mounted the / filesystem and checked fstab - No mention of 'dffa6b3c0a51f' or anything close
- Commented out the swap entries in /etc/fstab - same issue upon boot
- Checked /var/log/messages for any clues - last entry was 12/11/18
- Checked and force repaired all of the filesystem - including LVMs
- Copied the system.journal to the rescue system and attempted to read the entries - No entries, last entry was on 12/11/18
- Researched the error. Suggestions so far have been:
systemctl show -p RequiredBy -p WantedBy dev-disk-by...
systemctl list-units | grep dev-disk
The problem here is that I can't get past the start job message as it's set to infinite and I can't cancel it. I've tried adjusting the timeout in systemd.conf to 90s but it didn't take.
This is the fstab from the mounted partition:
This is what I'm seeing on boot:
So here I am. Has anyone encountered this before and if so, how did you fix it?
filesystems systemd lvm vmware
asked Jan 28 at 12:46
Moif MurphyMoif Murphy
1176
add a comment |
I have a VCSA that won't boot. It gets as far as:
A start job is running for dev-disk-byx2dpar...dffa6b3c0a51f.device (no limit)
What I'm trying to do is track down that UUID so I can start troubleshooting. This what I've attempted so far:
- Tried emergency mode - can't get past the start job
- Mounted an Ubuntu Live ISO, mounted the / filesystem and checked fstab - No mention of 'dffa6b3c0a51f' or anything close
- Commented out the swap entries in /etc/fstab - same issue upon boot
- Checked /var/log/messages for any clues - last entry was 12/11/18
- Checked and force repaired all of the filesystem - including LVMs
- Copied the system.journal to the rescue system and attempted to read the entries - No entries, last entry was on 12/11/18
- Researched the error. Suggestions so far have been:
systemctl show -p RequiredBy -p WantedBy dev-disk-by...
systemctl list-units | grep dev-disk
The problem here is that I can't get past the start job message as it's set to infinite and I can't cancel it. I've tried adjusting the timeout in systemd.conf to 90s but it didn't take.
This is the fstab from the mounted partition:
This is what I'm seeing on boot:
So here I am. Has anyone encountered this before and if so, how did you fix it?
filesystems systemd lvm vmware
asked Jan 28 at 12:46
Moif MurphyMoif Murphy
1176
I have a VCSA that won't boot. It gets as far as:
A start job is running for dev-disk-byx2dpar...dffa6b3c0a51f.device (no limit)
What I'm trying to do is track down that UUID so I can start troubleshooting. This what I've attempted so far:
- Tried emergency mode - can't get past the start job
- Mounted an Ubuntu Live ISO, mounted the / filesystem and checked fstab - No mention of 'dffa6b3c0a51f' or anything close
- Commented out the swap entries in /etc/fstab - same issue upon boot
- Checked /var/log/messages for any clues - last entry was 12/11/18
- Checked and force repaired all of the filesystem - including LVMs
- Copied the system.journal to the rescue system and attempted to read the entries - No entries, last entry was on 12/11/18
- Researched the error. Suggestions so far have been:
systemctl show -p RequiredBy -p WantedBy dev-disk-by...
systemctl list-units | grep dev-disk
The problem here is that I can't get past the start job message as it's set to infinite and I can't cancel it. I've tried adjusting the timeout in systemd.conf to 90s but it didn't take.
This is the fstab from the mounted partition:
This is what I'm seeing on boot:
So here I am. Has anyone encountered this before and if so, how did you fix it?
filesystems systemd lvm vmware
filesystems systemd lvm vmware
asked Jan 28 at 12:46
Moif MurphyMoif Murphy
1176
asked Jan 28 at 12:46
Moif MurphyMoif Murphy
1176
asked Jan 28 at 12:46
Moif MurphyMoif Murphy
1176
asked Jan 28 at 12:46
Moif MurphyMoif Murphy
1176
asked Jan 28 at 12:46
Moif MurphyMoif Murphy
1176
1176
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
This is your device entry in crypttab having an error. Those generators are the only ones that tweak the device unit's timeout (if you didn't) and set it to infinity. This is because device units are exposing system resources, and systemd doesn't control their starting and stopping. However, it uses the start job as a way to wait for a device's appearance. This also means that device units cannot wait on another unit.
Now, for encrypted devices, they will never become active before the user enters the password (or unlocks the device through something equivalent), but the device unit cannot wait on the password prompt unit. This means that the device unit is set to wait infinitely long for the appearance of a device, which means the start job keeps running with no limits set on it. Dependents will be waiting on the running start job.
answered yesterday
Jonathon KowalskiJonathon Kowalski
12
New contributor
Jonathon Kowalski is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
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%2f497188%2fa-start-job-is-running-for-dev-disk-by-x2dpar-dffa6b3c0a51f-device-no-limit%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
This is your device entry in crypttab having an error. Those generators are the only ones that tweak the device unit's timeout (if you didn't) and set it to infinity. This is because device units are exposing system resources, and systemd doesn't control their starting and stopping. However, it uses the start job as a way to wait for a device's appearance. This also means that device units cannot wait on another unit.
Now, for encrypted devices, they will never become active before the user enters the password (or unlocks the device through something equivalent), but the device unit cannot wait on the password prompt unit. This means that the device unit is set to wait infinitely long for the appearance of a device, which means the start job keeps running with no limits set on it. Dependents will be waiting on the running start job.
answered yesterday
Jonathon KowalskiJonathon Kowalski
12
New contributor
Jonathon Kowalski is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
This is your device entry in crypttab having an error. Those generators are the only ones that tweak the device unit's timeout (if you didn't) and set it to infinity. This is because device units are exposing system resources, and systemd doesn't control their starting and stopping. However, it uses the start job as a way to wait for a device's appearance. This also means that device units cannot wait on another unit.
Now, for encrypted devices, they will never become active before the user enters the password (or unlocks the device through something equivalent), but the device unit cannot wait on the password prompt unit. This means that the device unit is set to wait infinitely long for the appearance of a device, which means the start job keeps running with no limits set on it. Dependents will be waiting on the running start job.
answered yesterday
Jonathon KowalskiJonathon Kowalski
12
New contributor
Jonathon Kowalski is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
This is your device entry in crypttab having an error. Those generators are the only ones that tweak the device unit's timeout (if you didn't) and set it to infinity. This is because device units are exposing system resources, and systemd doesn't control their starting and stopping. However, it uses the start job as a way to wait for a device's appearance. This also means that device units cannot wait on another unit.
Now, for encrypted devices, they will never become active before the user enters the password (or unlocks the device through something equivalent), but the device unit cannot wait on the password prompt unit. This means that the device unit is set to wait infinitely long for the appearance of a device, which means the start job keeps running with no limits set on it. Dependents will be waiting on the running start job.
answered yesterday
Jonathon KowalskiJonathon Kowalski
12
New contributor
Jonathon Kowalski is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
This is your device entry in crypttab having an error. Those generators are the only ones that tweak the device unit's timeout (if you didn't) and set it to infinity. This is because device units are exposing system resources, and systemd doesn't control their starting and stopping. However, it uses the start job as a way to wait for a device's appearance. This also means that device units cannot wait on another unit.
Now, for encrypted devices, they will never become active before the user enters the password (or unlocks the device through something equivalent), but the device unit cannot wait on the password prompt unit. This means that the device unit is set to wait infinitely long for the appearance of a device, which means the start job keeps running with no limits set on it. Dependents will be waiting on the running start job.
answered yesterday
Jonathon KowalskiJonathon Kowalski
12
New contributor
Jonathon Kowalski is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
answered yesterday
Jonathon KowalskiJonathon Kowalski
12
New contributor
Jonathon Kowalski is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
answered yesterday
Jonathon KowalskiJonathon Kowalski
12
answered yesterday
Jonathon KowalskiJonathon Kowalski
12
12
New contributor
Jonathon Kowalski is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
Jonathon Kowalski is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Jonathon Kowalski is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
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.
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%2f497188%2fa-start-job-is-running-for-dev-disk-by-x2dpar-dffa6b3c0a51f-device-no-limit%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
