Failed to start Remount Root and Kernel File Systems with single OS

Hi,
I am new to linux environment.
I took a brave decision to move out form Windows to Manjaro on my home PC. After a recent update, I am not able to boot up my PC.
It shows error:
[Failed] Failed to start Remount Root and Kernel File Systems.
[Failed] Failed to start Remount Root and Kernel File Systems.

I am not using dual OS, only Manjaro. I tried to look for solutions, but I am not how to share my PC information such as blkid & ‘fstab’. Can anyone guide me on this?

I have a live USB with Manjaro.

Hi @yu_buffon,

This is apparently not your first time here, so you should know this already:

In order for us, or anyone for that matter, to be able to provide assistance, more information is necessary. To that end, please see:

Please also note and heed: Forum Rules - Manjaro

Hope you manage!


:bangbang: Tip: :bangbang:

To provide terminal output, copy the text you wish to share, and paste it here, surrounded by three (3) backticks, a.k.a grave accents. Like this:

```
pasted text
```

Or three (3) tilde signs, like this:

~~~
pasted text
~~~

This will just cause it to be rendered like this:

Portaest sed
elementum
cursus nisl nisi
hendrerit ac quis
sit
adipiscing
tortor sit leo commodo.

Instead of like this:

Portaest sed elementum cursus nisl nisi hendrerit ac quis sit adipiscing tortor sit leo commodo.

Alternatively, paste the text you wish to format as terminal output, select all pasted text, and click the </> button on the taskbar. This will indent the whole pasted section with one TAB, causing it to render the same way as described above.

Thereby improving legibility and making it much easier for those trying to be of assistance.


:bangbang::bangbang: Additionally

If your language isn’t English, please prepend any and all terminal commands with LC_ALL=C. For example:

LC_ALL=C bluetoothctl

This will just cause the terminal output to be in English, making it easier to understand and debug.

Please edit your post accordingly.

2 Likes

Thanks @Mirdarthos

I have included a picture of the error,
https://paste.pics/703167156e8898f199af75be406f77eb

I am not able to boot up, how can I access the system information?

I’d suggest booting into a live environment, from there enter a chroot environment, where you’ll be able to execute the commands and run any to try and resolve this.


How to chroot

  1. Ensure you’ve got a relatively new ISO or at least one with a still supported LTS kernel.

  2. Write/copy/dd the ISO to a USB thumb drive.

  3. When done, boot with the above mentioned USB thumb drive into the live environment.

  4. Once booted, open a terminal and enter the following command to enter the chroot encironment:

manjaro-chroot -a
  1. If you have more than one Linux installation, select the correct one to use from the list provided.

When done, you should now be in the chroot environment.

But, be careful, as you’re now in an actual root environment on your computer, so any changes you make will persist after a restart


I strongly suspect this is some kind of hard drive failure, so please also provide the output for:

fdisk --list

and

cat /etc/fstab

…from the chroot environment.

1 Like

Remounting should only happen on filesystem errors, at least in theory. So i also think it has something to do with filesystem or drive failure.

1 Like

@Mirdarthos
Below us the output.
Using the file manager from live boot, I am able to access my folders/files located in the hard drive without issues.

[manjaro /]# fdisk --list
Disk /dev/sda: 1.82 TiB, 2000398934016 bytes, 3907029168 sectors
Disk model: ST2000DM008-2FR1
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: 22388562-904E-1843-88AF-B84B5CA80174

Device          Start        End    Sectors  Size Type
/dev/sda1        4096     618495     614400  300M EFI System
/dev/sda2      618496 3875690044 3875071549  1.8T Linux filesystem
/dev/sda3  3875690045 3907024064   31334020 14.9G Linux swap

Partition 3 does not start on physical sector boundary.


Disk /dev/sdb: 115.33 GiB, 123835842560 bytes, 241866880 sectors
Disk model: DataTraveler 3.0
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x00000000

Device     Boot   Start     End Sectors  Size Id Type
/dev/sdb1  *         64 7529007 7528944  3.6G  0 Empty
/dev/sdb2       7529008 7537199    8192    4M ef EFI (FAT-12/16/32)


Disk /dev/loop0: 67.81 MiB, 71102464 bytes, 138872 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop1: 1.13 GiB, 1216016384 bytes, 2375032 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop2: 1.68 GiB, 1803116544 bytes, 3521712 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop3: 653.71 MiB, 685465600 bytes, 1338800 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
[manjaro /]# cat /etc/fstab
# /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>
UUID=AD8B-0531                              /boot/efi   vfat   umask=0077   0 2 
UUID=9e976eed-fc12-49a3-8ccc-966a3d1c7fe3   /           ext4   noatime      0 1 
UUID=08ea9edf-a18c-4f4e-8f6b-ad44ad7bf48c   swap        swap   noatime      0 0 
[manjaro /]# blkid
/dev/loop1: BLOCK_SIZE="262144" TYPE="squashfs"
/dev/sdb2: SEC_TYPE="msdos" LABEL_FATBOOT="MISO_EFI" LABEL="MISO_EFI" UUID="1517-A94A" BLOCK_SIZE="512" TYPE="vfat"
/dev/sdb1: BLOCK_SIZE="2048" UUID="2023-05-29-08-47-39-00" LABEL="MANJARO_KDE_2213" TYPE="iso9660"
/dev/loop2: BLOCK_SIZE="262144" TYPE="squashfs"
/dev/loop0: BLOCK_SIZE="262144" TYPE="squashfs"
/dev/sda2: UUID="9e976eed-fc12-49a3-8ccc-966a3d1c7fe3" BLOCK_SIZE="4096" TYPE="ext4" PARTLABEL="root" PARTUUID="2f25340e-8a12-3841-a5c8-381c4bcaacab"
/dev/sda3: LABEL="swap" UUID="08ea9edf-a18c-4f4e-8f6b-ad44ad7bf48c" TYPE="swap" PARTUUID="b913b20b-ee86-7a4b-999f-0504d747cbb1"
/dev/sda1: LABEL_FATBOOT="NO_LABEL" LABEL="NO_LABEL" UUID="AD8B-0531" BLOCK_SIZE="512" TYPE="vfat" PARTUUID="950d8d13-36e0-d448-84b9-af9cead622f8"
/dev/loop3: BLOCK_SIZE="262144" TYPE="squashfs"

@Teo
Using the file manager from live boot, I am able to access my folders/files located in the hard drive without issues.

:point_up_2: There’s your problem. :man_shrugging:

@Aragorn
Do you mean partition sda3 having issue?
Can I fix it by re-partitioning or resizing sda3? Will it affect my data on other partition?

Almost certainly.

I recommend copying everything off it with a live environment and using said live environment to then repartition the disk.

Edit:

But there’s really no way to be certain it won’t happen again. Especially if it is a disk problem. Check the SMART values of the disk. From a live environment, run:

sudo smartctl --all /dev/sda

This, obviously, assumes the disk is /dev/sda . Feel free to adjust as necessary.

sudo smartctl --all /dev/sda

Output:

smartctl 7.3 2022-02-28 r5338 [x86_64-linux-6.1.30-1-MANJARO] (local build)
Copyright (C) 2002-22, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family:     Seagate BarraCuda 3.5 (SMR)
Device Model:     ST2000DM008-2FR102
Serial Number:    WK207PAW
LU WWN Device Id: 5 000c50 0d60d9047
Firmware Version: 0001
User Capacity:    2,000,398,934,016 bytes [2.00 TB]
Sector Sizes:     512 bytes logical, 4096 bytes physical
Rotation Rate:    7200 rpm
Form Factor:      3.5 inches
TRIM Command:     Available
Device is:        In smartctl database 7.3/5319
ATA Version is:   ACS-3 T13/2161-D revision 5
SATA Version is:  SATA 3.1, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is:    Sat Nov  4 19:51:04 2023 +08
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

General SMART Values:
Offline data collection status:  (0x00) Offline data collection activity
                                        was never started.
                                        Auto Offline Data Collection: Disabled.
Self-test execution status:      (   0) The previous self-test routine completed
                                        without error or no self-test has ever 
                                        been run.
Total time to complete Offline 
data collection:                (    0) seconds.
Offline data collection
capabilities:                    (0x73) SMART execute Offline immediate.
                                        Auto Offline data collection on/off support.
                                        Suspend Offline collection upon new
                                        command.
                                        No Offline surface scan supported.
                                        Self-test supported.
                                        Conveyance Self-test supported.
                                        Selective Self-test supported.
SMART capabilities:            (0x0003) Saves SMART data before entering
                                        power-saving mode.
                                        Supports SMART auto save timer.
Error logging capability:        (0x01) Error logging supported.
                                        General Purpose Logging supported.
Short self-test routine 
recommended polling time:        (   1) minutes.
Extended self-test routine
recommended polling time:        ( 206) minutes.
Conveyance self-test routine
recommended polling time:        (   2) minutes.
SCT capabilities:              (0x30a5) SCT Status supported.
                                        SCT Data Table supported.

SMART Attributes Data Structure revision number: 10
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x000f   100   064   006    Pre-fail  Always       -       404784
  3 Spin_Up_Time            0x0003   096   096   000    Pre-fail  Always       -       0
  4 Start_Stop_Count        0x0032   100   100   020    Old_age   Always       -       731
  5 Reallocated_Sector_Ct   0x0033   100   100   010    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x000f   085   060   045    Pre-fail  Always       -       285042132
  9 Power_On_Hours          0x0032   097   097   000    Old_age   Always       -       2664h+24m+24.310s
 10 Spin_Retry_Count        0x0013   100   100   097    Pre-fail  Always       -       0
 12 Power_Cycle_Count       0x0032   100   100   020    Old_age   Always       -       731
183 Runtime_Bad_Block       0x0032   099   099   000    Old_age   Always       -       1
184 End-to-End_Error        0x0032   100   100   099    Old_age   Always       -       0
187 Reported_Uncorrect      0x0032   100   100   000    Old_age   Always       -       0
188 Command_Timeout         0x0032   100   100   000    Old_age   Always       -       0 0 0
189 High_Fly_Writes         0x003a   100   100   000    Old_age   Always       -       0
190 Airflow_Temperature_Cel 0x0022   061   055   040    Old_age   Always       -       39 (Min/Max 31/40)
191 G-Sense_Error_Rate      0x0032   100   100   000    Old_age   Always       -       0
192 Power-Off_Retract_Count 0x0032   100   100   000    Old_age   Always       -       51
193 Load_Cycle_Count        0x0032   099   099   000    Old_age   Always       -       2869
194 Temperature_Celsius     0x0022   039   045   000    Old_age   Always       -       39 (0 23 0 0 0)
195 Hardware_ECC_Recovered  0x001a   100   064   000    Old_age   Always       -       404784
197 Current_Pending_Sector  0x0012   100   100   000    Old_age   Always       -       0
198 Offline_Uncorrectable   0x0010   100   100   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x003e   200   200   000    Old_age   Always       -       0
240 Head_Flying_Hours       0x0000   100   253   000    Old_age   Offline      -       2378h+19m+33.102s
241 Total_LBAs_Written      0x0000   100   253   000    Old_age   Offline      -       7983047066
242 Total_LBAs_Read         0x0000   100   253   000    Old_age   Offline      -       5059603619

SMART Error Log Version: 1
No Errors Logged

SMART Self-test log structure revision number 1
No self-tests have been logged.  [To run self-tests, use: smartctl -t]

SMART Selective self-test log data structure revision number 1
 SPAN  MIN_LBA  MAX_LBA  CURRENT_TEST_STATUS
    1        0        0  Not_testing
    2        0        0  Not_testing
    3        0        0  Not_testing
    4        0        0  Not_testing
    5        0        0  Not_testing
Selective self-test flags (0x0):
  After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.

sudo smartctl --all /dev/sda3

Output

martctl 7.3 2022-02-28 r5338 [x86_64-linux-6.1.30-1-MANJARO] (local build)
Copyright (C) 2002-22, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family:     Seagate BarraCuda 3.5 (SMR)
Device Model:     ST2000DM008-2FR102
Serial Number:    WK207PAW
LU WWN Device Id: 5 000c50 0d60d9047
Firmware Version: 0001
User Capacity:    2,000,398,934,016 bytes [2.00 TB]
Sector Sizes:     512 bytes logical, 4096 bytes physical
Rotation Rate:    7200 rpm
Form Factor:      3.5 inches
TRIM Command:     Available
Device is:        In smartctl database 7.3/5319
ATA Version is:   ACS-3 T13/2161-D revision 5
SATA Version is:  SATA 3.1, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is:    Sat Nov  4 19:52:46 2023 +08
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

General SMART Values:
Offline data collection status:  (0x00) Offline data collection activity
                                        was never started.
                                        Auto Offline Data Collection: Disabled.
Self-test execution status:      (   0) The previous self-test routine completed
                                        without error or no self-test has ever 
                                        been run.
Total time to complete Offline 
data collection:                (    0) seconds.
Offline data collection
capabilities:                    (0x73) SMART execute Offline immediate.
                                        Auto Offline data collection on/off support.
                                        Suspend Offline collection upon new
                                        command.
                                        No Offline surface scan supported.
                                        Self-test supported.
                                        Conveyance Self-test supported.
                                        Selective Self-test supported.
SMART capabilities:            (0x0003) Saves SMART data before entering
                                        power-saving mode.
                                        Supports SMART auto save timer.
Error logging capability:        (0x01) Error logging supported.
                                        General Purpose Logging supported.
Short self-test routine 
recommended polling time:        (   1) minutes.
Extended self-test routine
recommended polling time:        ( 206) minutes.
Conveyance self-test routine
recommended polling time:        (   2) minutes.
SCT capabilities:              (0x30a5) SCT Status supported.
                                        SCT Data Table supported.

SMART Attributes Data Structure revision number: 10
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x000f   100   064   006    Pre-fail  Always       -       404784
  3 Spin_Up_Time            0x0003   096   096   000    Pre-fail  Always       -       0
  4 Start_Stop_Count        0x0032   100   100   020    Old_age   Always       -       731
  5 Reallocated_Sector_Ct   0x0033   100   100   010    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x000f   085   060   045    Pre-fail  Always       -       285042140
  9 Power_On_Hours          0x0032   097   097   000    Old_age   Always       -       2664h+26m+06.679s
 10 Spin_Retry_Count        0x0013   100   100   097    Pre-fail  Always       -       0
 12 Power_Cycle_Count       0x0032   100   100   020    Old_age   Always       -       731
183 Runtime_Bad_Block       0x0032   099   099   000    Old_age   Always       -       1
184 End-to-End_Error        0x0032   100   100   099    Old_age   Always       -       0
187 Reported_Uncorrect      0x0032   100   100   000    Old_age   Always       -       0
188 Command_Timeout         0x0032   100   100   000    Old_age   Always       -       0 0 0
189 High_Fly_Writes         0x003a   100   100   000    Old_age   Always       -       0
190 Airflow_Temperature_Cel 0x0022   061   055   040    Old_age   Always       -       39 (Min/Max 31/40)
191 G-Sense_Error_Rate      0x0032   100   100   000    Old_age   Always       -       0
192 Power-Off_Retract_Count 0x0032   100   100   000    Old_age   Always       -       51
193 Load_Cycle_Count        0x0032   099   099   000    Old_age   Always       -       2873
194 Temperature_Celsius     0x0022   039   045   000    Old_age   Always       -       39 (0 23 0 0 0)
195 Hardware_ECC_Recovered  0x001a   100   064   000    Old_age   Always       -       404784
197 Current_Pending_Sector  0x0012   100   100   000    Old_age   Always       -       0
198 Offline_Uncorrectable   0x0010   100   100   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x003e   200   200   000    Old_age   Always       -       0
240 Head_Flying_Hours       0x0000   100   253   000    Old_age   Offline      -       2378h+19m+33.102s
241 Total_LBAs_Written      0x0000   100   253   000    Old_age   Offline      -       7983047066
242 Total_LBAs_Read         0x0000   100   253   000    Old_age   Offline      -       5059603619

SMART Error Log Version: 1
No Errors Logged

SMART Self-test log structure revision number 1
No self-tests have been logged.  [To run self-tests, use: smartctl -t]

SMART Selective self-test log data structure revision number 1
 SPAN  MIN_LBA  MAX_LBA  CURRENT_TEST_STATUS
    1        0        0  Not_testing
    2        0        0  Not_testing
    3        0        0  Not_testing
    4        0        0  Not_testing
    5        0        0  Not_testing
Selective self-test flags (0x0):
  After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.
/dev/sda

Is this the only disk in your computer? From the live environment, please provide the output of:

lsblk

lsblk
Output

NAME   MAJ:MIN RM   SIZE RO TYPE MOUNTPOINTS
loop0    7:0    0  67.8M  1 loop /run/miso/sfs/livefs
loop1    7:1    0   1.1G  1 loop /run/miso/sfs/mhwdfs
loop2    7:2    0   1.7G  1 loop /run/miso/sfs/desktopfs
loop3    7:3    0 653.7M  1 loop /run/miso/sfs/rootfs
sda      8:0    0   1.8T  0 disk 
├─sda1   8:1    0   300M  0 part 
├─sda2   8:2    0   1.8T  0 part /mnt
└─sda3   8:3    0  14.9G  0 part 
sdb      8:16   1 115.3G  0 disk 
├─sdb1   8:17   1   3.6G  0 part /run/miso/bootmnt
└─sdb2   8:18   1     4M  0 part 

:smiley:

First of all, welcome to the “team”, I’m sure you will love to call yourself a linux freak in the near future. xD

I see other ppl have touched on this, but let me nerd down an explanation for you.
The physical sector mentioned here is where a block is ending and a new is starting. A sector contains x amount of blocks, blocks contain x amount of bytes (block size).

The tricky part with this is that the boot partition is not only in another partition format (MBR, GPT for ext4 and newer filesystems), the block size is different. On fat32 it is 512 and on ext4 it is 4k (4096). But that does not actually matter, because both of them are a binary “even number”. Let me explain:

These numbers are all in 8 bit integers, ie an even number in binary.
That is the reason you always see these numbers increase the way they do on computers, 8, 16, 32, 64 etc. Also the reason why one byte = 8 bits.
8 = 1000 in binary
16 = 10 000
32 = 100 000
etc etc.

So why is this relevant?

Well, this means that if you break a partition in the middle of a block, the filesystem will have to share one block on 2 partitions, that won’t work. Today most linux distros will handle this and just throw a warning and ignore that particular block/sector (you will not be able to store things here) and still work, but SOME things, like you noticed might break so you should obviously aim to not create this situation.

A really simple trick to see if the partitions are aligned is just to divide the number by 8, in this case on sda3:
3875690045/8=484461255,625 (not an even a whole number)

But if we check sda2:
618496/8=77312 (an even a whole number)

There are multiple ways to fix this, but there are already people helping out and do not need more “chefs”, but thought this could be helpful in general to know. :smiley: