stop at mount: /new:root [Solved]

pipes · 2023-02-19 10:08:33

hello, when starting ArchLinux, I randomly receive this message: mount: /new_root: unknow filesystem type 'ntfs'
I have posted my fstab

# Static information about the filesystems.
# See fstab(5) for details.

# <file system> <dir> <type> <options> <dump> <pass>
# /dev/nvme0n1p2
UUID=dc000e8d-8463-4b9a-be10-e0e2bfafb82d / ext4 rw,relatime 0 1

# /dev/nvme0n1p3
UUID=83d9284e-1d01-4b25-8582-44768fbe8c1a /home ext4 rw,relatime 0 2

# /dev/nvme0n1p1
UUID=3076-3D5F /boot/efi vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro 0 2

Sorry for other language, I didn't notice the google translate language

Last edited by pipes (2023-02-26 22:23:40)

WorMzy · 2023-02-19 11:02:58

Mod note: moving to Other Languages NC.

Last edited by WorMzy (2023-02-19 15:23:09)

seth · 2023-02-19 12:32:37

https://wiki.archlinux.org/title/NTFS
"ntfs3" or "ntfs-3g", but from the limited output it's not possible to say why the system feels like mounting an ntfs partition itfp - it's not in your fstab

lsblk -f

( please use code tags, https://bbs.archlinux.org/help.php#bbcode )

pipes · 2023-02-19 13:23:19

this is the output

NAME FSTYPE FSVER LABEL UUID FSAVAIL FSUSE% MOUNTPOINTS
sda
└─sda1 ntfs DATI 7EA49D4FA49D0AB3
sr0
nvme1n1
├─nvme1n1p1
└─nvme1n1p2 ntfs 341252D1125297A6
nvme0n1
├─nvme0n1p1 vfat FAT32 3076-3D5F
├─nvme0n1p2 ext4 1.0 dc000e8d-8463-4b9a-be10-e0e2bfafb82d 166,4G 10% /
└─nvme0n1p3 ext4 1.0 83d9284e-1d01-4b25-8582-44768fbe8c1a 339,4G 48% /home

seth · 2023-02-19 13:33:34

seth wrote:

please use code tags

What is sda1 ?

pipes · 2023-02-19 13:35:41

seth wrote:

seth wrote:
please use code tags
What is sda1 ?

It's a data disk where I save my files

seth · 2023-02-19 13:40:52

What about nvme1n1p2 ?
What kind of bootloader do you use?
Post its config.

Chances are you're addressing the rot partition by nvme1* and the order isn't static, so you accdentally try to boot from the other nvme (w/ the ntfs partition on it)

pipes · 2023-02-19 13:48:40

seth wrote:

What about nvme1n1p2 ?
What kind of bootloader do you use?
Post its config.
Chances are you're addressing the rot partition by nvme1* and the order isn't static, so you accdentally try to boot from the other nvme (w/ the ntfs partition on it)

nvme1n1p2 it's windows partition, i use refind for bootloader.
On fstab there are no information of windows disk, there is bootloader partition in vfat, after disable vfat partiton the problem disappear
this is refind_linux.conf

"Boot with standard options" "rw root=/dev/nvme0n1p2 quiet splash initrd=\boot\initramfs-%v.img initrd=\boot\intel-ucode.img noibrs noibpb nopti nospectre_v2 nospectre_v1 l1tf=off nospec_store_bypass_disable no_stf_barrier mds=off mitigations=off"
"Boot to single-user mode" "rw root=/dev/nvme0n1p2 single"
"Boot with minimal options" "ro root=/dev/nvme0n1p2"

seth · 2023-02-19 13:56:04

seth wrote:

seth wrote:
please use code tags

I'm not saying it again.
Edit and fix your previous posts.

seth wrote:

you're addressing the rot partition by nvme1* and the order isn't static, so you accdentally try to boot from the other nvme (w/ the ntfs partition on it)

https://wiki.archlinux.org/title/REFInd … linux.conf

pipes · 2023-02-19 14:12:46

seth wrote:

seth wrote:
seth wrote:
please use code tags
I'm not saying it again.
Edit and fix your previous posts.
seth wrote:
you're addressing the rot partition by nvme1* and the order isn't static, so you accdentally try to boot from the other nvme (w/ the ntfs partition on it)
https://wiki.archlinux.org/title/REFInd … linux.conf

bootloader partition is loaded on /boot/efi folder
initramfs is on partition nvme0n1p2 parttion

seth · 2023-02-19 14:28:32

You're missing the point. Don't address the root partition as "/dev/nvme0n1p2"

And fix your previous posts.

pipes · 2023-02-19 17:35:51

seth wrote:

You're missing the point. Don't address the root partition as "/dev/nvme0n1p2"
And fix your previous posts.

I understand but do you mean in the fstab or in refind_linux.conf?

loqs · 2023-02-19 17:41:14

pipes wrote:

I understand but do you mean in the fstab or in refind_linux.conf?

The fstab you posted is already using Persistent block device naming and the link seth provided you with was for refind configuration.

pipes · 2023-02-19 21:30:00

tomorrow I try to change the name to refind, the problem was that using partuuid it didn't start the kernel properly, giving me the error mount: new_root :....
Thanks for help

seth · 2023-02-19 21:40:12

nb. that UUID and PARTUUID are not the same.

lsblk -o NAME,MOUNTPOINT,FSTYPE,SIZE,UUID,PARTUUID

And according to https://wiki.archlinux.org/title/REFInd … ot_stanzas refind will only accept uppercase *UUIDs

pipes · 2023-02-21 18:26:45

seth wrote:

nb. that UUID and PARTUUID are not the same.
lsblk -o NAME,MOUNTPOINT,FSTYPE,SIZE,UUID,PARTUUID
And according to https://wiki.archlinux.org/title/REFInd … ot_stanzas refind will only accept uppercase *UUIDs

Using Uuid does not start the system and tells me that Filsystem Unknow: NFS
You mean uppercase, uppercase is UUID and that I know, Do you also mean the letters that make up UUID must be capitalized?

Watch if is good now?

# Static information about the filesystems.
# See fstab(5) for details.

# <file system> <dir> <type> <options> <dump> <pass>
# /dev/nvme0n1p2
PARTUUID=602b875d-c937-974f-a875-9ae62125679f	/         	ext4      	rw,relatime	0 1

# /dev/nvme0n1p3
PARTUUID=035c8478-8788-ca4e-8318-a5455137f50b	/home     	ext4      	rw,relatime	0 2

# /dev/nvme0n1p1
PARTUUID=af91752c-7755-43ae-b46a-c330e6b1901f      	/boot/efi 	vfat      	rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro	0 2

 "Boot with standard options"  "rw root=PARTUUID=602b875d-c937-974f-a875-9ae62125679f quiet splash initrd=\boot\initramfs-%v.img initrd=\boot\intel-ucode.img noibrs noibpb nopti nospectre_v2 nospectre_v1 l1tf=off nospec_store_bypass_disable no_stf_barrier mds=off mitigations=off"
"Boot to single-user mode"    "rw root=PARTUUID=602b875d-c937-974f-a875-9ae62125679f single"
"Boot with minimal options"   "ro root=PARTUUID=602b875d-c937-974f-a875-9ae62125679f"

Last edited by pipes (2023-02-21 19:23:23)

Scimmia · 2023-02-21 18:31:53

You pointed it to the UUID of an NFS drive? I didn't even think that was possible.

Post the actual config

pipes · 2023-02-21 19:21:59

Scimmia wrote:

You pointed it to the UUID of an NFS drive? I didn't even think that was possible.
Post the actual config

I don't know why but the only partition I have other than the linux ones is the efi formatted in FAT32

pipes · 2023-02-21 19:25:56

Scimmia wrote:

You pointed it to the UUID of an NFS drive? I didn't even think that was possible.
Post the actual config

you can read it in the previous message, however here it is

 # Static information about the filesystems.
# See fstab(5) for details.

# <file system> <dir> <type> <options> <dump> <pass>
# /dev/nvme0n1p2
PARTUUID=602b875d-c937-974f-a875-9ae62125679f	/         	ext4      	rw,relatime	0 1

# /dev/nvme0n1p3
PARTUUID=035c8478-8788-ca4e-8318-a5455137f50b	/home     	ext4      	rw,relatime	0 2

# /dev/nvme0n1p1
PARTUUID=af91752c-7755-43ae-b46a-c330e6b1901f      	/boot/efi 	vfat      	rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro	0 2

"Boot with standard options"  "rw root=PARTUUID=602b875d-c937-974f-a875-9ae62125679f quiet splash initrd=\boot\initramfs-%v.img initrd=\boot\intel-ucode.img noibrs noibpb nopti nospectre_v2 nospectre_v1 l1tf=off nospec_store_bypass_disable no_stf_barrier mds=off mitigations=off"
"Boot to single-user mode"    "rw root=PARTUUID=602b875d-c937-974f-a875-9ae62125679f single"
"Boot with minimal options"   "ro root=PARTUUID=602b875d-c937-974f-a875-9ae62125679f"

seth · 2023-02-21 21:13:53

Idk. whether this is true, but iff refind requires the *UUIDs to be uppercase: 602b875D-C937-974F-A875-9AE62125679F
Does the system boot now?

Did you previously try sth. like "root=UUID=602b875d-c937-974f-a875-9ae62125679f"?

loqs · 2023-02-21 21:24:12

Using refind here with root of the format "root=UUID=602b875d-c937-974f-a875-9ae62125679f" Is the issue actually the root option? Which the kernel and boot loader should be passing through as there is an initrd specified?
If you remove the root option entirely is the error the same? Can you post a link to a screenshot of the exact error?

pipes · 2023-02-22 08:39:04

seth wrote:

Idk. whether this is true, but iff refind requires the *UUIDs to be uppercase: 602b875D-C937-974F-A875-9AE62125679F
Does the system boot now?
Did you previously try sth. like "root=UUID=602b875d-c937-974f-a875-9ae62125679f"?

no, written that way it won't start, written in uppercase and lowercase, generate same problem
Only write /dev/nvme0n1p2 work fine

Last edited by pipes (2023-02-22 08:39:40)

seth · 2023-02-22 08:53:59

"UUID=602b875d-c937-974f-a875-9ae62125679f" is *wrong* in any event.
It would be, in doubt:

root=PARTUUID=602b875D-C937-974F-A875-9AE62125679F

loqs wrote:

If you remove the root option entirely is the error the same? Can you post a link to a screenshot of the exact error?

Edit

Only write /dev/nvme0n1p2 work fine

Apparently not, because then we would not be here.

Last edited by seth (2023-02-22 08:54:30)

pipes · 2023-02-25 10:12:19

this thread can closed like solved.
Thanks to all

seth · 2023-02-25 10:19:08

Please always remember to mark resolved threads by editing your initial posts subject - so others will know that there's no task left, but maybe a solution to find.
Thanks.

Also elaborate on what was the problem and how it was solved, https://wiki.archlinux.org/title/Genera … way_street

Arch Linux

#1 2023-02-19 10:08:33

stop at mount: /new:root [Solved]

#2 2023-02-19 11:02:58

Re: stop at mount: /new:root [Solved]

#3 2023-02-19 12:32:37

Re: stop at mount: /new:root [Solved]

#4 2023-02-19 13:23:19

Re: stop at mount: /new:root [Solved]

#5 2023-02-19 13:33:34

Re: stop at mount: /new:root [Solved]

#6 2023-02-19 13:35:41

Re: stop at mount: /new:root [Solved]

#7 2023-02-19 13:40:52

Re: stop at mount: /new:root [Solved]

#8 2023-02-19 13:48:40

Re: stop at mount: /new:root [Solved]

#9 2023-02-19 13:56:04

Re: stop at mount: /new:root [Solved]

#10 2023-02-19 14:12:46

Re: stop at mount: /new:root [Solved]

#11 2023-02-19 14:28:32

Re: stop at mount: /new:root [Solved]

#12 2023-02-19 17:35:51

Re: stop at mount: /new:root [Solved]

#13 2023-02-19 17:41:14

Re: stop at mount: /new:root [Solved]

#14 2023-02-19 21:30:00

Re: stop at mount: /new:root [Solved]

#15 2023-02-19 21:40:12

Re: stop at mount: /new:root [Solved]

#16 2023-02-21 18:26:45

Re: stop at mount: /new:root [Solved]

#17 2023-02-21 18:31:53

Re: stop at mount: /new:root [Solved]

#18 2023-02-21 19:21:59

Re: stop at mount: /new:root [Solved]

#19 2023-02-21 19:25:56

Re: stop at mount: /new:root [Solved]

#20 2023-02-21 21:13:53

Re: stop at mount: /new:root [Solved]

#21 2023-02-21 21:24:12

Re: stop at mount: /new:root [Solved]

#22 2023-02-22 08:39:04

Re: stop at mount: /new:root [Solved]

#23 2023-02-22 08:53:59

Re: stop at mount: /new:root [Solved]

#24 2023-02-25 10:12:19

Re: stop at mount: /new:root [Solved]

#25 2023-02-25 10:19:08

Re: stop at mount: /new:root [Solved]

Board footer