Skip to main content
Topic: Mounting the partition with the label "ROOT" fails (Read 675 times) previous topic - next topic
0 Members and 2 Guests are viewing this topic.

Mounting the partition with the label "ROOT" fails

I am trying to follow the installation guide for the using the Dinit base ISO. When I am formatting the second partition to "ext4" and assign it the label "ROOT" (following EXACTLY the steps showing in the guide), the partition formats but the label is not added. Mount will fail saying that label does not exist. It will also fail if I try to use the full partition path (which for me is "/dev/sda2").

I used "cfdisk" to format the disk and I have created two partitions. One for the EFI boot and the second one for the system. The EFI partition gets formatted (to fat32), assigned the label and mounted normally. The second one has the problem I mentioned. Any ideas?

Re: Mounting the partition with the label "ROOT" fails

Reply #1
what are the exact command you use to mount the partitions.
it should be something like
Code: [Select]
mount /dev/sda2 /mnt
mkdir /mnt/boot
mkdir /mnt/home
mount /dev/sda1 /mnt/boot
mount /dev/sda3 /mnt/home

also add "lsblk" output

Re: Mounting the partition with the label "ROOT" fails

Reply #2
what are the exact command you use to mount the partitions.
it should be something like
Code: [Select]
mount /dev/sda2 /mnt
mkdir /mnt/boot
mkdir /mnt/home
mount /dev/sda1 /mnt/boot
mount /dev/sda3 /mnt/home

also add "lsblk" output

Using the commends you say, I'm getting the following error when I'm trying to mount "/dev/sda2":

mount: /mnt: wrong fs type, bad option, bad superblock on /dev/sda2, missing codepage or helper program, or other error.

Re: Mounting the partition with the label "ROOT" fails

Reply #3
what are the exact command you use to mount the partitions.
it should be something like
Code: [Select]
mount /dev/sda2 /mnt
mkdir /mnt/boot
mkdir /mnt/home
mount /dev/sda1 /mnt/boot
mount /dev/sda3 /mnt/home

also add "lsblk" output

For the lsblk output:

fd0
loop0
sda
  - sda1
  - sad2
sr0

You are killing me if you want the full output. I just listed the devices that are shown. If you want the full output, I'll take a screenshot and give it to you somehow.

 

Re: Mounting the partition with the label "ROOT" fails

Reply #4
at first I thought maybe you might mount with wrong arguments or something.
now my bet is that your partitions does not have correct filesystems. did you format with "mkfs.ext"
check it with
Code: [Select]
sudo lsblk -f --ascii --paths
your boot part (I guess /dev/sda1) should have FSTYPE vfat
and root part (/dev/sda2) should have FSTYPE ext4

p.s. yes adding --ascii or --raw option would made it easier ┬─┬ ︵ /(.□. \)
edit: now I get why you can't show all the output "http://sprunge.us/"
Code: [Select]
sudo lsblk --ascii --paths --output NAME,FSTYPE,TYPE,LABEL,MOUNTPOINTS | curl -F 'sprunge=<-' http://sprunge.us


Re: Mounting the partition with the label "ROOT" fails

Reply #5
at first I thought maybe you might mount with wrong arguments or something.
now my bet is that your partitions does not have correct filesystems. did you format with "mkfs.ext"
check it with
Code: [Select]
sudo lsblk -f --ascii --paths
your boot part (I guess /dev/sda1) should have FSTYPE vfat
and root part (/dev/sda2) should have FSTYPE ext4

p.s. yes adding --ascii or --raw option would made it easier ┬─┬ ︵ /(.□. \)
edit: now I get why you can show all the output "http://sprunge.us/"
Code: [Select]
sudo lsblk --ascii --paths --output NAME,FSTYPE,TYPE,LABEL,MOUNTPOINTS | curl -F 'sprunge=<-' http://sprunge.us



Yes, I have made the base installation on Arch before so I'm familiar with the process. Disk names have changed from "sda" to "vda" (as I'm using virt-manager now) The command used are the following:

For "vda1" (EFI boot partition):

Code: [Select]
mkfs.fat -F 32 /dev/vda1
fatlabel /dev/vda1 ESP

For "vda2" (Root partition):

Code: [Select]
mkfs.ext4 -L "ROOT" /dev/vda2

The second, tells me that there is a filesystem and asks me if I want to override it (in which I reply "y").

I don't understand the last part of the reply. I did share it as a screenshot and uploaded in my Google Drive (to not choose a random site):

https://drive.google.com/file/d/1XF9lN-yVYTcoqM-c9flWTw1Vn6FgRa5p/view?usp=sharing

Will this do for you? It seems that there is a problem with "vda2" and it is not formatted correctly...

Re: Mounting the partition with the label "ROOT" fails

Reply #6
there seem to be a problem with the "/dev/vda2" partition.
- Check filesystem `/dev/vda2`, reporting any damaged blocks and automatically repairing them:
Code: [Select]
    sudo fsck -a /dev/vda2

also check if you can find anything suspicious in "dmesg" output.

 suggestion: don't use basic iso, use a graphical one like cinnamon. that way, you can install via terminal and have the browser open. there's no need to run Calamares installer.

Re: Mounting the partition with the label "ROOT" fails

Reply #7
there seem to be a problem with the "/dev/vda2" partition.
- Check filesystem `/dev/vda2`, reporting any damaged blocks and automatically repairing them:
Code: [Select]
    sudo fsck -a /dev/vda2

also check if you can find anything suspicious in "dmesg" output.

 suggestion: don't use basic iso, use a graphical one like cinnamon. that way, you can install via terminal and have the browser open. there's no need to run Calamares installer.

Thank you! I did used A GUI environment and opened the terminal there. At least the experience will be a little bit better but I still wasn't able to share the clipboard. The output of the command you gave me is:

Code: [Select]
ROOT: clean, 12/1081344 files, 112442/4323864 blocks

"dmesg" does not seem to contain anything suspicious...

Re: Mounting the partition with the label "ROOT" fails

Reply #8
after using 'fsck' did you try to make the filesystem again (mkfs.ext4) ?
if you still face problem, I recommend to use a GUI partition manager (those do some extra that might help).
if problem persist after that, I'm out of idea :(

Re: Mounting the partition with the label "ROOT" fails

Reply #9
after using 'fsck' did you try to make the filesystem again (mkfs.ext4) ?
if you still face problem, I recommend to use a GUI partition manager (those do some extra that might help).
if problem persist after that, I'm out of idea :(

Thanks a lot for trying to help but as this has gotten long enough, we are wasting both our times at this point, so I'll just use Calamares to do what I want to do and if I want to install Artix in real hardware in the future, we'll see!

Thanks a lot for the help and I wish you to have a beautiful day!