LinuxQuestions.org
Help answer threads with 0 replies.
Home Forums Tutorials Articles Register
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Software > Linux - Kernel
User Name
Password
Linux - Kernel This forum is for all discussion relating to the Linux kernel.

Notices


Reply
  Search this Thread
Old 11-06-2014, 12:15 AM   #1
Prime08
LQ Newbie
 
Registered: Nov 2014
Posts: 6

Rep: Reputation: Disabled
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.

Please help.

Paul
 
Old 11-06-2014, 02:19 AM   #2
ondoho
LQ Addict
 
Registered: Dec 2013
Posts: 19,872
Blog Entries: 12

Rep: Reputation: 6053Reputation: 6053Reputation: 6053Reputation: 6053Reputation: 6053Reputation: 6053Reputation: 6053Reputation: 6053Reputation: 6053Reputation: 6053Reputation: 6053
Quote:
Originally Posted by Prime08 View Post
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.

Last edited by ondoho; 11-06-2014 at 02:20 AM.
 
Old 11-06-2014, 05:09 AM   #3
Prime08
LQ Newbie
 
Registered: Nov 2014
Posts: 6

Original Poster
Rep: Reputation: Disabled
Thanks for the reply Ondoho.

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.

What do i do?
 
Old 11-06-2014, 09:15 AM   #4
RockDoctor
Senior Member
 
Registered: Nov 2003
Location: Minnesota, US
Distribution: Fedora, Ubuntu, Manjaro
Posts: 1,791

Rep: Reputation: 427Reputation: 427Reputation: 427Reputation: 427Reputation: 427
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.
 
Old 11-06-2014, 09:26 AM   #5
Prime08
LQ Newbie
 
Registered: Nov 2014
Posts: 6

Original Poster
Rep: Reputation: Disabled
I ran fsck and this is the output
Code:
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.
 
Old 11-06-2014, 09:35 AM   #6
RockDoctor
Senior Member
 
Registered: Nov 2003
Location: Minnesota, US
Distribution: Fedora, Ubuntu, Manjaro
Posts: 1,791

Rep: Reputation: 427Reputation: 427Reputation: 427Reputation: 427Reputation: 427
In that case, I'd do the read-only check first. If that looks good, I'd try the remount option.
Code:
 mount -o remount,rw /dev/sda1 <mountpoint>
 
Old 11-06-2014, 10:02 AM   #7
Prime08
LQ Newbie
 
Registered: Nov 2014
Posts: 6

Original Poster
Rep: Reputation: Disabled
okay. how do i specify the filesystem type?

Code:
root@ubuntu:~# fsck -n /dev/sda1
fsck from util-linux 2.20.1
e2fsck 1.42.9 (4-Feb-2014)
Warning: skipping journal recovery because doing a read-only filesystem check.
/dev/sda1: clean, 256277/848640 files, 3146660/3393792 blocks
root@ubuntu:~# mount -o remount,rw /dev/sda1 /mnt
mount: you must specify the filesystem type
root@ubuntu:~#
 
Old 11-06-2014, 10:10 AM   #8
RockDoctor
Senior Member
 
Registered: Nov 2003
Location: Minnesota, US
Distribution: Fedora, Ubuntu, Manjaro
Posts: 1,791

Rep: Reputation: 427Reputation: 427Reputation: 427Reputation: 427Reputation: 427
Code:
man fsck
is your friend. If it's an ext4 filesystem, you can use fsck -t <filesystem-type> or fsck.ext4
 
Old 11-06-2014, 11:18 AM   #9
Prime08
LQ Newbie
 
Registered: Nov 2014
Posts: 6

Original Poster
Rep: Reputation: Disabled
Still not working.
Code:
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:~#
 
Old 11-06-2014, 12:52 PM   #10
ondoho
LQ Addict
 
Registered: Dec 2013
Posts: 19,872
Blog Entries: 12

Rep: Reputation: 6053Reputation: 6053Reputation: 6053Reputation: 6053Reputation: 6053Reputation: 6053Reputation: 6053Reputation: 6053Reputation: 6053Reputation: 6053Reputation: 6053
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.
 
Old 11-06-2014, 01:42 PM   #11
Prime08
LQ Newbie
 
Registered: Nov 2014
Posts: 6

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by ondoho View Post
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.
 
Old 11-07-2014, 08:48 AM   #12
RockDoctor
Senior Member
 
Registered: Nov 2003
Location: Minnesota, US
Distribution: Fedora, Ubuntu, Manjaro
Posts: 1,791

Rep: Reputation: 427Reputation: 427Reputation: 427Reputation: 427Reputation: 427
Quote:
Originally Posted by Prime08 View Post
Still not working.
Code:
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?
Code:
fsck -n -t ext4 /dev/sdb1
 
  


Reply



Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
boot message: mount: mounting /dev/sda1 on /mnt failed: Invalid argument. stf92 Slackware 7 10-10-2014 03:51 PM
message sending failed : Error[22 ] invalid argument .....but each and every argument rakeshranjanjha Linux - Software 2 01-07-2008 11:22 PM
mount: Mounting /dev/sda2 on /mnt failed: Invalid argument dohpaz Slackware 7 05-25-2007 02:03 AM
cryptsetup error (Command failed: Invalid argument) SlackN00b Slackware 5 02-07-2007 12:59 PM
installation Error mounting sda1: Invalid Argument sadirmata Linux - Software 4 01-31-2002 10:37 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Software > Linux - Kernel

All times are GMT -5. The time now is 12:37 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration