BOOT ERROR: Mounting on /root failed: Invalid argument
Linux - KernelThis forum is for all discussion relating to the Linux kernel.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
BOOT ERROR: Mounting on /root failed: Invalid argument
Hi
Evrytime i try to boot my system i get an error message:
mount: mounting /dev/disk/by-uuid/a3c31122-6794-4fa6-a039-91d49dadfa8a on /root
failed: Invalid argument
mount: mounting /sys on /root/sys failed: No such file or directory
mount: mounting /dev on /root/dev failed: No such file or directory
mount: mounting /sys on /root/sys failed: No such file or directory
mount: mounting /proc on /root/proc failed: No such file or directory
Target filesystem doesn't have /sbin/init.
No init found. Try passing init = bootarg.
BusyBox v1.13.3 (Ubuntu 1:1.13.3-1ubuntu7) built-in shell (ash)
Enter 'help' for a lit of built in commands.
(initramfs)
I tried to boot using live disk but i can't mount the hdd.
Evrytime i try to boot my system i get an error message:
mount: mounting /dev/disk/by-uuid/a3c31122-6794-4fa6-a039-91d49dadfa8a on /root
failed: Invalid argument
the explanation is right there.
the uuid is a universal identifier for your hard drive, the one you installed your linux on.
mount cannot find it. the uuid is wrong.
it's hard to say more about this now, but i guess it's safe to say that something went wrong with your install.
Quote:
I tried to boot using live disk but i can't mount the hdd.
this doesn't make sense. booting a live medium, you don't need the hard drive.
It seems I was a bit unclear.
What i meant to say was i tried booting fron a Live CD but i cant seem to mount the boot partition or any other partitions on my device. Its write protected.
i was hoping to fix grub2 but i get an "access denied" response.
I'd unmount the hdd partition of interest, run fsck on it, then try remounting it. If that didn't allow you to mount the partition writably, and I was feeling brave (or is that foolish?) I'd try to forcibly mount it rw.
root@ubuntu:~# fsck /dev/sda1
fsck from util-linux 2.20.1
e2fsck 1.42.9 (4-Feb-2014)
fsck.ext4: Read-only file system while trying to open /dev/sda1
Disk write-protected; use the -n option to do a read-only
check of the device.
root@ubuntu:~# fsck.ext4 /dev/sdb1
e2fsck 1.42.9 (4-Feb-2014)
fsck.ext4: Read-only file system while trying to open /dev/sdb1
Disk write-protected; use the -n option to do a read-only
check of the device.
root@ubuntu:~# fsck -t ext4 /dev/sdb1
fsck from util-linux 2.20.1
e2fsck 1.42.9 (4-Feb-2014)
fsck.ext4: Read-only file system while trying to open /dev/sdb1
Disk write-protected; use the -n option to do a read-only
check of the device.
root@ubuntu:~#
the problem you are experiencing, is this on an installed version of ubuntu or while booting a live medium?
also, your filesystem magically moved from sda1 to sdb1, how's that happened?
and, i'll say it again, a live medium should just boot up to a graphical desktop, no matter what state your hard drive is in.
somehow i have the suspicion that you haven't even installed ubuntu yet and are trying to run a fsck on the live medium, which is by all rights read only.
the problem you are experiencing, is this on an installed version of ubuntu or while booting a live medium?
also, your filesystem magically moved from sda1 to sdb1, how's that happened?
and, i'll say it again, a live medium should just boot up to a graphical desktop, no matter what state your hard drive is in.
somehow i have the suspicion that you haven't even installed ubuntu yet and are trying to run a fsck on the live medium, which is by all rights read only.
Let me explain what happened.
I had installed ubuntu 14.04 lts a while back. whn i tried to boot yesterday i got the error. I then booted from a LiveCD so i can search online for a solution. After reading a few threads i learnt the solution would be to reinstall Grub2.
Now in order to reinstall grub2 i had to mount the boot partition.
Code:
root@ubuntu:~# mount /dev/sdb1 /mnt
mount: block device /dev/sdb1 is write-protected, mounting read-only
mount: wrong fs type, bad option, bad superblock on /dev/sdb1,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so
root@ubuntu:~#
And the reason why the device is now sdb from sda is simply because i turned the laptop off and left the house, and when i rebooted from LiveCD i had connected a flash drive wich was now sda.
root@ubuntu:~# fsck.ext4 /dev/sdb1
e2fsck 1.42.9 (4-Feb-2014)
fsck.ext4: Read-only file system while trying to open /dev/sdb1
Disk write-protected; use the -n option to do a read-only
check of the device.
root@ubuntu:~# fsck -t ext4 /dev/sdb1
fsck from util-linux 2.20.1
e2fsck 1.42.9 (4-Feb-2014)
fsck.ext4: Read-only file system while trying to open /dev/sdb1
Disk write-protected; use the -n option to do a read-only
check of the device.
root@ubuntu:~#
Have you tried running a check on your boot partition?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.