View previous topic :: View next topic |
Author |
Message |
austinramsay n00b
Joined: 25 Oct 2010 Posts: 53
|
Posted: Mon Jun 25, 2018 12:09 am Post subject: Timed out waiting for device dev-nvme0n1p2.device |
|
|
Kernel version 4.9.95 with systemd. Dell XPS 13 9370 (UEFI)
On boot I am getting a
Quote: | (1 of 2) A start job is running for dev-nvme0n1p2.device |
Followed by a 1 minute and 30 second timer that leads to:
Quote: | (2 of 2) Timed out waiting for device dev-nvme0n1p2.device |
This is met with a couple "Depend" errors:
Quote: | "Dependency failed for /boot."
"Dependency failed for Local File Systems."
|
And the same then happens for my swap partition after:
Quote: | (2 of 2) Timed out waiting for device dev-nvme0n1p3.device
Dependency failed for /dev/nvme0n1p3
Dependency failed for Swap. |
/dev/nvme0n1p2 is my /boot partition
/dev/nvme0n1p3 is my swap partition
/dev/nvme0n1p4 is my root partition
/etc/fstab:
Quote: | /dev/nvme0n1p2 /boot vfat defaults,noatime 0 2
/dev/nvme0n1p3 none swap sw 0 0
/dev/nvme0n1p4 / ext4 noatime 0 1
|
I am able to use the maintenance shell after the errors are given with /boot not being mounted obviously..
What exactly do these errors mean and what can I look through to see what's happening? |
|
Back to top |
|
|
russK l33t
Joined: 27 Jun 2006 Posts: 665
|
|
Back to top |
|
|
austinramsay n00b
Joined: 25 Oct 2010 Posts: 53
|
Posted: Mon Jun 25, 2018 4:42 am Post subject: |
|
|
Yes. Grep from .config returns:
Quote: | CONFIG_BLK_DEV_NVME=y
# CONFIG_BLK_DEV_NVME_SCSI is not set
|
|
|
Back to top |
|
|
olger901 l33t
Joined: 17 Mar 2005 Posts: 625
|
Posted: Mon Jun 25, 2018 12:08 pm Post subject: |
|
|
A few questions to get this issue clearer:
- Is support for swap and FAT filesystems compiled into your kernel?
- Are dosfstools installed?
What happens if you remove /boot and swap from the fstab? Does it still throw an error then?
Could you post the output of print from parted or output from cfdisk, so we can get a clearer view? |
|
Back to top |
|
|
eccerr0r Watchman
Joined: 01 Jul 2004 Posts: 9677 Location: almost Mile High in the USA
|
Posted: Mon Jun 25, 2018 2:32 pm Post subject: |
|
|
I've seen systemd sometimes get confusled when it translates fstab to its internal representation.
Try changing the hardcoded /dev/nvm* to label/partuuid/uuid=XXX
use "blkid" to determine the partuuid/label/uuid identifiers. _________________ Intel Core i7 2700K/Radeon R7 250/24GB DDR3/256GB SSD
What am I supposed watching? |
|
Back to top |
|
|
austinramsay n00b
Joined: 25 Oct 2010 Posts: 53
|
Posted: Mon Jun 25, 2018 4:51 pm Post subject: |
|
|
olger901 wrote: | - Is support for swap and FAT filesystems compiled into your kernel?
- Are dosfstools installed?
What happens if you remove /boot and swap from the fstab? Does it still throw an error then?
Could you post the output of print from parted or output from cfdisk, so we can get a clearer view? |
Yes support for swap and FAT is compiled into the kernel.
Just tried removing /boot and swap from fstab and it allowed me to boot without any problems, works fine! Then I was able to just manually mount them with no issues after logging in.
Output of parted print:
Quote: | (parted) print
Model: NVMe Device (nvme)
Disk /dev/nvme0n1: 256GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags:
Number Start End Size File system Name Flags
1 1049kB 3146kB 2097kB fat32 grub bios_grub
2 3146kB 137MB 134MB fat32 boot boot, esp
3 137MB 674MB 537MB linux-swap(v1) swap
4 674MB 256GB 255GB ext4 rootfs |
eccerr0r wrote: | I've seen systemd sometimes get confusled when it translates fstab to its internal representation.
Try changing the hardcoded /dev/nvm* to label/partuuid/uuid=XXX
use "blkid" to determine the partuuid/label/uuid identifiers. |
I also did change to partuuid form to test it out, and no change unfortunately.[/quote] |
|
Back to top |
|
|
russK l33t
Joined: 27 Jun 2006 Posts: 665
|
|
Back to top |
|
|
austinramsay n00b
Joined: 25 Oct 2010 Posts: 53
|
Posted: Wed Jun 27, 2018 7:34 am Post subject: |
|
|
Mind blown on how you found this...seriously. I havent tried it yet but thats obviously a potential fix. How did you know where to look for this, or at least realize this might be a solution? Since we’re on the topic now..When else is it necessary to issue a “systemctl daemom-reload”? |
|
Back to top |
|
|
russK l33t
Joined: 27 Jun 2006 Posts: 665
|
Posted: Wed Jun 27, 2018 9:12 pm Post subject: |
|
|
After using systemd (begrudgingly) for a couple years, I knew of the necessity. So I googled for some kind of documentation to point you to, and experienced the all too familiar face meets palm moment, as I posted it. |
|
Back to top |
|
|
|