Two lines seem to delay the process. hang these up. This is one of them:
andgpu 0000:00:00.0: [drm] REG WAIT timeout lus* 100000 tries - optc31 disable_crtc line:145
The other seems to be searching for btfrs file systems which I have never used. Mine are are all ext4!
How can I clean this up?
This is on a new machine which has another problem that requires another thread.
Two lines seem to delay the process. hang these up. This is one of them:
andgpu 0000:00:00.0: [drm] REG WAIT timeout lus* 100000 tries - optc31 disable_crtc line:145
The other seems to be searching for btfrs file systems which I have never used. Mine are are all ext4!
How can I clean this up?
This is on a new machine which has another problem that requires another thread.
Le 08/05/2026 a 18:42, pinnerite a ocrita:
Two lines seem to delay the process. hang these up. This is one of them:
andgpu 0000:00:00.0: [drm] REG WAIT timeout lus* 100000 tries - optc31 disable_crtc line:145
The other seems to be searching for btfrs file systems which I have never used. Mine are are all ext4!
How can I clean this up?
This is on a new machine which has another problem that requires another thread.
you have stage to start the desktop...
they are a logic step by step...
i suspect your fstab is not good...so you have a sort bad loop.
the kernel start...but after is not good...
may be is a new install ? so, see the uuid in grub cfg and in /etc/fstab
you can find grub.cfg in 2 place, first in the uefi part fat32...second
in /boot/grub
may be you boot with only a drive in your machine...but the install
don't write well /dev/sda it write /dev/sdb
so " b " is drive 2 no the principal drive...
if it is a tower...not a Trump tower, but a PC tower ok ! so see the
sata connexion...the sata 0 in not the same with sata1 !!!
some we plug in sata 1...and is not a good practice ! one here is B and
0 is A ( /dev/sda )
try that ?
after i don't !
see if boot and in the same time you others disk plugged ! uefi DON'T
like that !!! you must plug it afer when you are on desktop ! :o)
--The only drive in this machine is a 2TB NVMe, formatted tom ext4(?)
Amicalement,
Frenchy Friendly, & French touch !
german
On Fri, 8 May 2026 19:01:21 +0200
german newsgroups <usualsuspectrider@gmail.com> wrote:
Le 08/05/2026 a 18:42, pinnerite a ocrita:
Two lines seem to delay the process. hang these up. This is one of them:
andgpu 0000:00:00.0: [drm] REG WAIT timeout lus* 100000 tries - optc31 disable_crtc line:145
The other seems to be searching for btfrs file systems which I have never used. Mine are are all ext4!
How can I clean this up?
This is on a new machine which has another problem that requires another thread.
you have stage to start the desktop...
they are a logic step by step...
i suspect your fstab is not good...so you have a sort bad loop.
the kernel start...but after is not good...
may be is a new install ? so, see the uuid in grub cfg and in /etc/fstab
you can find grub.cfg in 2 place, first in the uefi part fat32...second
in /boot/grub
may be you boot with only a drive in your machine...but the install
don't write well /dev/sda it write /dev/sdb
so " b " is drive 2 no the principal drive...
if it is a tower...not a Trump tower, but a PC tower ok ! so see the
sata connexion...the sata 0 in not the same with sata1 !!!
some we plug in sata 1...and is not a good practice ! one here is B and
0 is A ( /dev/sda )
try that ?
after i don't !
see if boot and in the same time you others disk plugged ! uefi DON'T
like that !!! you must plug it afer when you are on desktop ! :o)
--
Amicalement,
Frenchy Friendly, & French touch !
german
The only drive in this machine is a 2TB NVMe, formatted tom ext4(?)
Le seul disque de cette machine est un NVMe de 2 To, formato en ext4 (?)
I will look at fstab though.
Alan
On Fri, 8 May 2026 18:48:59 +0100
pinnerite <pinnerite@gmail.com> wrote:
On Fri, 8 May 2026 19:01:21 +0200
german newsgroups <usualsuspectrider@gmail.com> wrote:
Le 08/05/2026 |a 18:42, pinnerite a |-crit-a:
Two lines seem to delay the process. hang these up. This is one of them: >>>>
andgpu 0000:00:00.0: [drm] REG WAIT timeout lus* 100000 tries - optc31 disable_crtc line:145
The other seems to be searching for btfrs file systems which I have never used. Mine are are all ext4!
How can I clean this up?
This is on a new machine which has another problem that requires another thread.
you have stage to start the desktop...
they are a logic step by step...
i suspect your fstab is not good...so you have a sort bad loop.
the kernel start...but after is not good...
may be is a new install ? so, see the uuid in grub cfg and in /etc/fstab >>>
you can find grub.cfg in 2 place, first in the uefi part fat32...second
in /boot/grub
may be you boot with only a drive in your machine...but the install
don't write well /dev/sda it write /dev/sdb
so " b " is drive 2 no the principal drive...
if it is a tower...not a Trump tower, but a PC tower ok ! so see the
sata connexion...the sata 0 in not the same with sata1 !!!
some we plug in sata 1...and is not a good practice ! one here is B and
0 is A ( /dev/sda )
try that ?
after i don't !
see if boot and in the same time you others disk plugged ! uefi DON'T
like that !!! you must plug it afer when you are on desktop ! :o)
--
Amicalement,
Frenchy Friendly, & French touch !
german
The only drive in this machine is a 2TB NVMe, formatted tom ext4(?)
Le seul disque de cette machine est un NVMe de 2 To, format|- en ext4 (?)
I will look at fstab though.
Alan
This is it:
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
# / was on /dev/nvme0n1p2 during installation UUID=ddc1434f-4a71-4e0b-925f-abd5a0e4efe2 / ext4 errors=remount-ro 0 1
# /boot/efi was on /dev/nvme0n1p1 during installation
UUID=C6E9-4EA7 /boot/efi vfat umask=0077 0 1
# /home was on /dev/nvme0n1p4 during installation UUID=a188675c-e574-4444-a06e-f17d582c60d4 /home ext4 defaults 0 2
# swap was on /dev/nvme0n1p3 during installation UUID=31191ec8-278a-43bb-bf95-73c50294d5dd none swap sw 0 0
# swap was on /dev/sdb5 during installation UUID=b57469f5-8876-41e2-a5f0-d996990f5b62 none swap sw 0 0
Alan
On Fri, 8 May 2026 18:48:59 +0100
pinnerite <pinnerite@gmail.com> wrote:
On Fri, 8 May 2026 19:01:21 +0200
german newsgroups <usualsuspectrider@gmail.com> wrote:
Le 08/05/2026 |a 18:42, pinnerite a |-crit-a:
Two lines seem to delay the process. hang these up. This is one of them: >>>>
andgpu 0000:00:00.0: [drm] REG WAIT timeout lus* 100000 tries - optc31 disable_crtc line:145
The other seems to be searching for btfrs file systems which I have never used. Mine are are all ext4!
How can I clean this up?
This is on a new machine which has another problem that requires another thread.
you have stage to start the desktop...
they are a logic step by step...
i suspect your fstab is not good...so you have a sort bad loop.
the kernel start...but after is not good...
may be is a new install ? so, see the uuid in grub cfg and in /etc/fstab >>>
you can find grub.cfg in 2 place, first in the uefi part fat32...second
in /boot/grub
may be you boot with only a drive in your machine...but the install
don't write well /dev/sda it write /dev/sdb
so " b " is drive 2 no the principal drive...
if it is a tower...not a Trump tower, but a PC tower ok ! so see the
sata connexion...the sata 0 in not the same with sata1 !!!
some we plug in sata 1...and is not a good practice ! one here is B and
0 is A ( /dev/sda )
try that ?
after i don't !
see if boot and in the same time you others disk plugged ! uefi DON'T
like that !!! you must plug it afer when you are on desktop ! :o)
--
Amicalement,
Frenchy Friendly, & French touch !
german
The only drive in this machine is a 2TB NVMe, formatted tom ext4(?)
Le seul disque de cette machine est un NVMe de 2 To, format|- en ext4 (?)
I will look at fstab though.
Alan
This is it:
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
# / was on /dev/nvme0n1p2 during installation UUID=ddc1434f-4a71-4e0b-925f-abd5a0e4efe2 / ext4 errors=remount-ro 0 1
# /boot/efi was on /dev/nvme0n1p1 during installation
UUID=C6E9-4EA7 /boot/efi vfat umask=0077 0 1
# /home was on /dev/nvme0n1p4 during installation UUID=a188675c-e574-4444-a06e-f17d582c60d4 /home ext4 defaults 0 2
# swap was on /dev/nvme0n1p3 during installation UUID=31191ec8-278a-43bb-bf95-73c50294d5dd none swap sw 0 0
# swap was on /dev/sdb5 during installation UUID=b57469f5-8876-41e2-a5f0-d996990f5b62 none swap sw 0 0
Alan
Two lines seem to delay the process. hang these up. This is one of them:
andgpu 0000:00:00.0: [drm] REG WAIT timeout lus* 100000 tries - optc31 disable_crtc line:145
The other seems to be searching for btfrs file systems which I have never used. Mine are are all ext4!
How can I clean this up?
This is on a new machine which has another problem that requires another thread.
Le 08/05/2026 a 19:51, pinnerite a ocrita:
On Fri, 8 May 2026 18:48:59 +0100
pinnerite <pinnerite@gmail.com> wrote:
On Fri, 8 May 2026 19:01:21 +0200
german newsgroups <usualsuspectrider@gmail.com> wrote:
Le 08/05/2026 a 18:42, pinnerite a ocrita:
Two lines seem to delay the process. hang these up. This is one of them: >>>>
andgpu 0000:00:00.0: [drm] REG WAIT timeout lus* 100000 tries - optc31 disable_crtc line:145
The other seems to be searching for btfrs file systems which I have never used. Mine are are all ext4!
How can I clean this up?
This is on a new machine which has another problem that requires another thread.
you have stage to start the desktop...
they are a logic step by step...
i suspect your fstab is not good...so you have a sort bad loop.
the kernel start...but after is not good...
may be is a new install ? so, see the uuid in grub cfg and in /etc/fstab >>>
you can find grub.cfg in 2 place, first in the uefi part fat32...second >>> in /boot/grub
may be you boot with only a drive in your machine...but the install
don't write well /dev/sda it write /dev/sdb
so " b " is drive 2 no the principal drive...
if it is a tower...not a Trump tower, but a PC tower ok ! so see the
sata connexion...the sata 0 in not the same with sata1 !!!
some we plug in sata 1...and is not a good practice ! one here is B and >>> 0 is A ( /dev/sda )
try that ?
after i don't !
see if boot and in the same time you others disk plugged ! uefi DON'T
like that !!! you must plug it afer when you are on desktop ! :o)
--
Amicalement,
Frenchy Friendly, & French touch !
german
The only drive in this machine is a 2TB NVMe, formatted tom ext4(?)
Le seul disque de cette machine est un NVMe de 2 To, formato en ext4 (?) >>
I will look at fstab though.
Alan
This is it:
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices # that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
# / was on /dev/nvme0n1p2 during installation UUID=ddc1434f-4a71-4e0b-925f-abd5a0e4efe2 / ext4 errors=remount-ro 0 1
# /boot/efi was on /dev/nvme0n1p1 during installation
UUID=C6E9-4EA7 /boot/efi vfat umask=0077 0 1
# /home was on /dev/nvme0n1p4 during installation UUID=a188675c-e574-4444-a06e-f17d582c60d4 /home ext4 defaults 0 2
# swap was on /dev/nvme0n1p3 during installation UUID=31191ec8-278a-43bb-bf95-73c50294d5dd none swap sw 0 0
# swap was on /dev/sdb5 during installation UUID=b57469f5-8876-41e2-a5f0-d996990f5b62 none swap sw 0 0
Alan
NaN ! i see 2 swap part for me is not good. and the uuid are unit for
each part each disk ! so yours uuid can not to be my uuid ! here i can
not to be sure for the uudi for your nvme part... i hope the disk is
convert in gpt table and they are...a efi part fat32 ...may be it could
work well without efi part fat32 if grub is in the MBR, they are a MBR
in a uefi disk ! grub => grub.cfg => kernel 'll start
your part is strange ! home in p4 swap in p3 but i think it could work,
the OS is the MASTER BIOS hight level program so, it 'll do with !
comment all lignes and try this :
/dev/nvme0n1p2 / ext4 nofail,x-systemd.device-timeout=1ms 0 0
/dev/nvme0n1p1 /boot/efi vfat umask=0077 0 0
/dev/nvme0n1p4 /home ext4 defaults 0 0
/dev/nvme0n1p3 none swap sw 0 0
--The final fstab swap line was erroneous. I checked the partition details from "Disks" and then deleted the erroneous ine.
Amicalement,
Frenchy Friendly, & French touch !
german
On Fri, 8 May 2026 20:07:38 +0200
german newsgroups <usualsuspectrider@gmail.com> wrote:
Le 08/05/2026 |a 19:51, pinnerite a |-crit-a:
On Fri, 8 May 2026 18:48:59 +0100
pinnerite <pinnerite@gmail.com> wrote:
On Fri, 8 May 2026 19:01:21 +0200This is it:
german newsgroups <usualsuspectrider@gmail.com> wrote:
Le 08/05/2026 |a 18:42, pinnerite a |-crit-a:The only drive in this machine is a 2TB NVMe, formatted tom ext4(?)
Two lines seem to delay the process. hang these up. This is one of them: >>>>>>
andgpu 0000:00:00.0: [drm] REG WAIT timeout lus* 100000 tries - optc31 disable_crtc line:145
The other seems to be searching for btfrs file systems which I have never used. Mine are are all ext4!
How can I clean this up?
This is on a new machine which has another problem that requires another thread.
you have stage to start the desktop...
they are a logic step by step...
i suspect your fstab is not good...so you have a sort bad loop.
the kernel start...but after is not good...
may be is a new install ? so, see the uuid in grub cfg and in /etc/fstab >>>>>
you can find grub.cfg in 2 place, first in the uefi part fat32...second >>>>> in /boot/grub
may be you boot with only a drive in your machine...but the install
don't write well /dev/sda it write /dev/sdb
so " b " is drive 2 no the principal drive...
if it is a tower...not a Trump tower, but a PC tower ok ! so see the >>>>> sata connexion...the sata 0 in not the same with sata1 !!!
some we plug in sata 1...and is not a good practice ! one here is B and >>>>> 0 is A ( /dev/sda )
try that ?
after i don't !
see if boot and in the same time you others disk plugged ! uefi DON'T >>>>> like that !!! you must plug it afer when you are on desktop ! :o)
--
Amicalement,
Frenchy Friendly, & French touch !
german
Le seul disque de cette machine est un NVMe de 2 To, format|- en ext4 (?) >>>>
I will look at fstab though.
Alan
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices >>> # that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
# / was on /dev/nvme0n1p2 during installation
UUID=ddc1434f-4a71-4e0b-925f-abd5a0e4efe2 / ext4 errors=remount-ro 0 1
# /boot/efi was on /dev/nvme0n1p1 during installation
UUID=C6E9-4EA7 /boot/efi vfat umask=0077 0 1
# /home was on /dev/nvme0n1p4 during installation
UUID=a188675c-e574-4444-a06e-f17d582c60d4 /home ext4 defaults 0 2
# swap was on /dev/nvme0n1p3 during installation
UUID=31191ec8-278a-43bb-bf95-73c50294d5dd none swap sw 0 0
# swap was on /dev/sdb5 during installation
UUID=b57469f5-8876-41e2-a5f0-d996990f5b62 none swap sw 0 0
Alan
NaN ! i see 2 swap part for me is not good. and the uuid are unit for
each part each disk ! so yours uuid can not to be my uuid ! here i can
not to be sure for the uudi for your nvme part... i hope the disk is
convert in gpt table and they are...a efi part fat32 ...may be it could
work well without efi part fat32 if grub is in the MBR, they are a MBR
in a uefi disk ! grub => grub.cfg => kernel 'll start
your part is strange ! home in p4 swap in p3 but i think it could work,
the OS is the MASTER BIOS hight level program so, it 'll do with !
comment all lignes and try this :
/dev/nvme0n1p2 / ext4 nofail,x-systemd.device-timeout=1ms 0 0
/dev/nvme0n1p1 /boot/efi vfat umask=0077 0 0
/dev/nvme0n1p4 /home ext4 defaults 0 0
/dev/nvme0n1p3 none swap sw 0 0
--
Amicalement,
Frenchy Friendly, & French touch !
german
The final fstab swap line was erroneous. I checked the partition details from "Disks" and then deleted the erroneous ine.
I still cannot boot up unless in Recovery Mode.
I am very tempted to reinstall, although reinitialising will be a nightmare.
On Fri, 8 May 2026 20:07:38 +0200
german newsgroups <usualsuspectrider@gmail.com> wrote:
Le 08/05/2026 |a 19:51, pinnerite a |-crit-a:
On Fri, 8 May 2026 18:48:59 +0100
pinnerite <pinnerite@gmail.com> wrote:
On Fri, 8 May 2026 19:01:21 +0200
german newsgroups <usualsuspectrider@gmail.com> wrote:
Le 08/05/2026 |a 18:42, pinnerite a |-crit-a:
Two lines seem to delay the process. hang these up. This is one of them: >>>>>>
andgpu 0000:00:00.0: [drm] REG WAIT timeout lus* 100000 tries - optc31 disable_crtc line:145
The other seems to be searching for btfrs file systems which I have never used. Mine are are all ext4!
How can I clean this up?
This is on a new machine which has another problem that requires another thread.
you have stage to start the desktop...
they are a logic step by step...
i suspect your fstab is not good...so you have a sort bad loop.
the kernel start...but after is not good...
may be is a new install ? so, see the uuid in grub cfg and in /etc/fstab >>>>>
you can find grub.cfg in 2 place, first in the uefi part fat32...second >>>>> in /boot/grub
may be you boot with only a drive in your machine...but the install
don't write well /dev/sda it write /dev/sdb
so " b " is drive 2 no the principal drive...
if it is a tower...not a Trump tower, but a PC tower ok ! so see the >>>>> sata connexion...the sata 0 in not the same with sata1 !!!
some we plug in sata 1...and is not a good practice ! one here is B and >>>>> 0 is A ( /dev/sda )
try that ?
after i don't !
see if boot and in the same time you others disk plugged ! uefi DON'T >>>>> like that !!! you must plug it afer when you are on desktop ! :o)
--
Amicalement,
Frenchy Friendly, & French touch !
german
The only drive in this machine is a 2TB NVMe, formatted tom ext4(?)
Le seul disque de cette machine est un NVMe de 2 To, format|- en ext4 (?) >>>>
I will look at fstab though.
Alan
This is it:
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices >>> # that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
# / was on /dev/nvme0n1p2 during installation
UUID=ddc1434f-4a71-4e0b-925f-abd5a0e4efe2 / ext4 errors=remount-ro 0 1
# /boot/efi was on /dev/nvme0n1p1 during installation
UUID=C6E9-4EA7 /boot/efi vfat umask=0077 0 1
# /home was on /dev/nvme0n1p4 during installation
UUID=a188675c-e574-4444-a06e-f17d582c60d4 /home ext4 defaults 0 2
# swap was on /dev/nvme0n1p3 during installation
UUID=31191ec8-278a-43bb-bf95-73c50294d5dd none swap sw 0 0
# swap was on /dev/sdb5 during installation
UUID=b57469f5-8876-41e2-a5f0-d996990f5b62 none swap sw 0 0
Alan
NaN ! i see 2 swap part for me is not good. and the uuid are unit for
each part each disk ! so yours uuid can not to be my uuid ! here i can
not to be sure for the uudi for your nvme part... i hope the disk is
convert in gpt table and they are...a efi part fat32 ...may be it could
work well without efi part fat32 if grub is in the MBR, they are a MBR
in a uefi disk ! grub => grub.cfg => kernel 'll start
your part is strange ! home in p4 swap in p3 but i think it could work,
the OS is the MASTER BIOS hight level program so, it 'll do with !
comment all lignes and try this :
/dev/nvme0n1p2 / ext4 nofail,x-systemd.device-timeout=1ms 0 0
/dev/nvme0n1p1 /boot/efi vfat umask=0077 0 0
/dev/nvme0n1p4 /home ext4 defaults 0 0
/dev/nvme0n1p3 none swap sw 0 0
--
Amicalement,
Frenchy Friendly, & French touch !
german
The final fstab swap line was erroneous. I checked the partition details from "Disks" and then deleted the erroneous ine.
I still cannot boot up unless in Recovery Mode.
I am very tempted to reinstall, although reinitialising will be a nightmare.
pinnerite wrote:
On Fri, 8 May 2026 20:07:38 +0200
german newsgroups <usualsuspectrider@gmail.com> wrote:
Le 08/05/2026 a 19:51, pinnerite a ocrita:
On Fri, 8 May 2026 18:48:59 +0100
pinnerite <pinnerite@gmail.com> wrote:
On Fri, 8 May 2026 19:01:21 +0200This is it:
german newsgroups <usualsuspectrider@gmail.com> wrote:
Le 08/05/2026 a 18:42, pinnerite a ocrita:The only drive in this machine is a 2TB NVMe, formatted tom ext4(?)
Two lines seem to delay the process. hang these up. This is one of them:
andgpu 0000:00:00.0: [drm] REG WAIT timeout lus* 100000 tries - optc31 disable_crtc line:145
The other seems to be searching for btfrs file systems which I have never used. Mine are are all ext4!
How can I clean this up?
This is on a new machine which has another problem that requires another thread.
you have stage to start the desktop...
they are a logic step by step...
i suspect your fstab is not good...so you have a sort bad loop.
the kernel start...but after is not good...
may be is a new install ? so, see the uuid in grub cfg and in /etc/fstab
you can find grub.cfg in 2 place, first in the uefi part fat32...second >>>>> in /boot/grub
may be you boot with only a drive in your machine...but the install >>>>> don't write well /dev/sda it write /dev/sdb
so " b " is drive 2 no the principal drive...
if it is a tower...not a Trump tower, but a PC tower ok ! so see the >>>>> sata connexion...the sata 0 in not the same with sata1 !!!
some we plug in sata 1...and is not a good practice ! one here is B and >>>>> 0 is A ( /dev/sda )
try that ?
after i don't !
see if boot and in the same time you others disk plugged ! uefi DON'T >>>>> like that !!! you must plug it afer when you are on desktop ! :o)
--
Amicalement,
Frenchy Friendly, & French touch !
german
Le seul disque de cette machine est un NVMe de 2 To, formato en ext4 (?) >>>>
I will look at fstab though.
Alan
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass> >>> # / was on /dev/nvme0n1p2 during installation
UUID=ddc1434f-4a71-4e0b-925f-abd5a0e4efe2 / ext4 errors=remount-ro 0 1
# /boot/efi was on /dev/nvme0n1p1 during installation
UUID=C6E9-4EA7 /boot/efi vfat umask=0077 0 1
# /home was on /dev/nvme0n1p4 during installation
UUID=a188675c-e574-4444-a06e-f17d582c60d4 /home ext4 defaults 0 2
# swap was on /dev/nvme0n1p3 during installation
UUID=31191ec8-278a-43bb-bf95-73c50294d5dd none swap sw 0 0
# swap was on /dev/sdb5 during installation
UUID=b57469f5-8876-41e2-a5f0-d996990f5b62 none swap sw 0 0
Alan
NaN ! i see 2 swap part for me is not good. and the uuid are unit for
each part each disk ! so yours uuid can not to be my uuid ! here i can
not to be sure for the uudi for your nvme part... i hope the disk is
convert in gpt table and they are...a efi part fat32 ...may be it could
work well without efi part fat32 if grub is in the MBR, they are a MBR
in a uefi disk ! grub => grub.cfg => kernel 'll start
your part is strange ! home in p4 swap in p3 but i think it could work,
the OS is the MASTER BIOS hight level program so, it 'll do with !
comment all lignes and try this :
/dev/nvme0n1p2 / ext4 nofail,x-systemd.device-timeout=1ms 0 0
/dev/nvme0n1p1 /boot/efi vfat umask=0077 0 0
/dev/nvme0n1p4 /home ext4 defaults 0 0
/dev/nvme0n1p3 none swap sw 0 0
--
Amicalement,
Frenchy Friendly, & French touch !
german
The final fstab swap line was erroneous. I checked the partition details from "Disks" and then deleted the erroneous ine.
I still cannot boot up unless in Recovery Mode.
I am very tempted to reinstall, although reinitialising will be a nightmare.
you don't have a disk image or timeshift save prior to this issue?
--
Linux Mint 22.3
| Sysop: | Amessyroom |
|---|---|
| Location: | Fayetteville, NC |
| Users: | 65 |
| Nodes: | 6 (0 / 6) |
| Uptime: | 08:03:38 |
| Calls: | 862 |
| Files: | 1,311 |
| D/L today: |
1 files (1,366K bytes) |
| Messages: | 264,936 |