Error Mounting Dev Root On Sysroot As Ext4
Common F23 Bugs Common F24 Bugs Communicate with Fedora The Documents Bug Reports Fedora Update System (Bodhi) Fedora Build System (Koji) Official Spins FedoraForum.org > Fedora 23/24 > Using Fedora mount error - error mounting /dev/root on sysroot as ext3 : invalid argument FedoraForum Search User Name Remember Me? Password Forgot Password? Join Us! Register All Albums FAQ Today's Posts Search Using Fedora General support for current versions. Ask questions about Fedora that do not belong in any other forum. Google™ Search FedoraForum Search Red Hat Bugzilla Search Search Forums Show Threads Show Posts Tag Search Advanced Search Go to Page... Thread Tools Search this Thread Display Modes #1 1st January 2009, 02:17 AM marko Offline Registered User Join Date: Jun 2004 Location: Laurel, MD USA Posts: 6,942 mount error - error mounting /dev/root on sysroot as ext3 : invalid argument After updating to the current 2.6.27.9-159.fc10.x86_64 kernel I can't boot it due to getting a mount error: Quote: mount: error mounting /dev/root on sysroot as ext3 : invalid argument Note this PC is not using LVM and I'm using AHCI I've tried several things I've found on google but none worked: 1) make a file /etc/sysconfig/mkinitrd containing: Code: MODULES="scsi_wait_scan" and run Code: mkinitrd -v -f /boot/initrd-2.6.27.9-159.fc10.x86_64.img 2.6.27.9-159.fc10.x86_64 2) added to the grub boot line: mod_scsi.scan=sync 3) finally I noticed after trying "2" that I could see a error about the mount argument "norelatime" being invalid, but the mount man page says that's still supported ? I want norelatime to reduce file system writes when I just look at files. Last edited by marko; 1st January 2009 at 02:27 AM. marko View Public Profile Find all posts by marko #2 1st January 2009, 02:41 AM leigh123linux Guest Posts: n/a I think you have the wrong option , it should be relatime Code: # # /etc/fstab # Created by anaconda
Marques Johansson on 2008-12-19 22 This bug affects 3 people Affects Status Importance Assigned to Milestone klibc (Ubuntu) Edit Fix Released Undecided Unassigned Edit You need to log in to change this bug's status. Affecting: klibc (Ubuntu) Filed here by: Marques Johansson When: 2008-12-19 Confirmed: 2008-12-29 Started work: 2009-01-08 Completed: 2009-01-08 Target Distribution Baltix BOSS Juju Charms Collection Elbuntu Guadalinex Guadalinex Edu Kiwi Linux nUbuntu PLD Linux Tilix tuXlab Ubuntu Ubuntu Linaro Evaluation Build Ubuntu RTM Package (Find…) Project (Find…) Status Importance Fix Released Undecided Assigned to http://forums.fedoraforum.org/showthread.php?t=209411 Nobody Me Comment on this change (optional) Email me about changes to this bug report Nominated for Jaunty by Marques Johansson Also affects project (?) Also affects distribution/package Nominate for series Bug Description Binary package hint: initramfs-tools The init scripts in initramfs do not mount an ext4 root partition, this leaves the user stuck at an (initram) prompt at a point that https://bugs.launchpad.net/bugs/309762 is too late for the user to correct matters. There are a few TODO notes in the local script that mention that there is not error handling when the FSTYPE detection or root mount fails. This should be addressed. When dropped to the (initram) I was able to "modprobe ext4; mount /dev/sda1 /root", but attempting to run "exec init", resulted in a Kernel Panic. The init local script had continued running past the root mount failure, so commands like these: mount -n --bind /root/dev /dev/.static/dev mount -n --move /dev /root/dev mount -n --move /proc /root/proc mount -n --move /sys /root/sys had already been attempted before I could intervene and manually mount root. Running them myself, and trying to finish off the local script (which ends with something like "exec run-init .... /root/dev/console ... " resulted in a kernel panic that /root/dev/console could not be found. I don't know why the ext4 mount was not successfully mounted, but I was able to work around this by adding a /etc/initramfs-tools/scripts/local-bottom/custom_mount_ext4 script: #! /bin/sh modprobe ext4 mount /dev/sda1 /root mount /dev/disk/by-uuid/..... /root I als
panic - not syncing: Attempted to kill init! after installation of Driver Diskette for enabling Onboard RAID Controller Chipset Next message: [CentOS] autofs problem on CentOS6 Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] Kaushal Shriyan https://lists.centos.org/pipermail/centos/2011-July/114777.html wrote: > On Mon, Jul 18, 2011 at 6:59 PM, Kaushal Shriyan >
Help » Laptop Hardware » Can't boot « previous next » Print Pages: [1] Go Down Author Topic: Can't boot (Read 1369 times) balduro Guest Can't boot « on: June 24, 2013, 08:43:50 AM » Hello, I can't boot the system. Yesterday everything worked fine, but today does not boot.In normal mode shows: EXT4-fs error comm java: unable write itable.In safe mode: EXT4-fs (sda1): error loading journal. And mount: error mounting /dev/root on /sysroot as ext4: invalid argument.No new updates o installations were done.Any help? Logged balduro Guest Re: Can't boot « Reply #1 on: June 24, 2013, 09:43:49 AM » Quote from: balduro on June 24, 2013, 08:43:50 AMHello, I can't boot the system. Yesterday everything worked fine, but today does not boot.In normal mode shows: EXT4-fs error comm java: unable write itable.In safe mode: EXT4-fs (sda1): error loading journal. And mount: error mounting /dev/root on /sysroot as ext4: invalid argument.No new updates o installations were done.Any help? More info. when I run from LiveCD can't access to sda1 and the error reported is similar to some forum post.I have read related post like:http://www.pclinuxos.com/forum/index.php?topic=81444.0http://www.pclinuxos.com/forum/index.php?topic=89500.0So I wonder if can I use the same solution, and which option of fcsk is correct? I have read fcsk -f option also. First I'd like to recovery some files, and it was neccesary to reinstall the system, but I shouldn't like to break anything. And the http://www.sysresccd.org/ tools could work ?Thanks in advance. Logged agmg PCLinuxOS Tester Hero Member Posts: 2784 Certified Windows Hater Re: Can't boot « Reply #2 on: June 24, 2013, 09:47:03 AM » Why don't you start with fsck -f? Logged Toshiba Satellite L505-12QIntel Core2Duo T6600 2.2Ghz ATI Mobility Radeon HD4650 1GB4GB DDR3OCZ Vertex 4 128Gb SATAII balduro Guest Re: Can't boot « Reply #3 on: June 24, 2013, 10:33:20 AM » Thanks for reply agmg.I ran it without -f and revealed a lot of errors. At the moment I'm doing a backup of some important files, and when finish I'll reboot. I'm not sure if should I have answered "yes" in all questions .It was better with -f option? Logged agmg PCLinuxOS Tester Hero Member Posts: 2784 Certified Windows Hater Re: Can't boot « Reply #4 on: June 24, 2013, 02:07:59 PM » Normal use of fsck doesn't really require a switch.For example it should be fsck /dev/sda1The filesystem will be checked as it should.The -f switch tells fsck to force examination