Your root file system has an error and needs to have fsck run on it. When you
get that prompt for the root password that is shown in the picture, enter it and
then run the command
fsck -y /dev/sda1
These errors do not happen very often, but I have had a couple of them since I
switched to ext4.
> (I do not know why it prints an error on Ext2 filesystem when the disk
> is formatted Ext4…)
The underlying file system for ext2, ext3, and ext4 are so similar that the
fixing is all handled by the ext2 program. That is why it was mentioned here.
Also, you may use since Ext3 data=writeback without any problems, but this does not imply that writeback is a safe/good option, even most file systems developers will advise you not to use it, unless you’re a speed freak and don’t value much what’s on your partition. If you want to end up with garbage during unsafe shutdowns, sudden power outages, etc, then please do. Heck, throw away Ext4/Ext3 and go use Ext2 instead, which will give you better performance than data=writeback since there’s no journal overhead involved as Ext2 doesn’t have one
I’m not certain what can cause such things… You may have better luck by using the good old device names instead of device IDs/paths…
This will involve changing all in /etc/fstab to /dev/sdXX (where XX corresponds to the correct disk and partition on it) and it will also involve changing to device names in /boot/grub/menu.lst and /etc/sysconfig/bootloader (the resume= part)
To microchip8:
I have changed device names in fstab and menu.lst, but in /etc/sysconfig/bootloader is no record of device names:
## Path: System/Bootloader
## Description: Bootloader configuration
## Type: list(grub,lilo,none)
## Default: grub
#
# Type of bootloader in use.
# For making the change effect run bootloader configuration tool
# and configure newly selected bootloader
#
#
LOADER_TYPE="grub"
## Path: System/Bootloader
## Description: Bootloader configuration
## Type: list(floppy,mbr,root,boot,custom,none)
## Default: mbr
#
# Location of boot loader.
# For making the change effect run bootloader configuration tool
#
#
LOADER_LOCATION=""
DEFAULT_APPEND="splash=silent quiet showopts"
DEFAULT_VGA="0x346"
FAILSAFE_APPEND="showopts apm=off noresume edd=off powersaved=off nohz=off highres=off processor.max_cstate=1 x11failsafe"
FAILSAFE_VGA="0x346"
XEN_KERNEL_APPEND="splash=silent quiet showopts"
XEN_APPEND=""
XEN_VGA="0x346"
## Path: System/Bootloader
## Description: Bootloader configuration
## Type: yesno
## Default: no
#
# Should the boot cycle detection be used to
# avoid unconditional reboot cycles of not
# supervised system.
#
CYCLE_DETECTION="no"
## Type: integer(0:)
## Default: 1
#
# The number of the entry in grub's menu.lst
# which should be used on the next reboot cycle.
# Note that the first entry has the number 0.
#
CYCLE_NEXT_ENTRY="1"
I think what is being suggested is to replace the disk ID info in fstab with /dev info
If you do fdisk -l from a terminal in Parted Magic it will list them that way then replace like this:
This is just showing one example which I think is correct:
Looking at your image it looks like your root fs is ok
the problem is with your data disk first the obvious if its an external disk is it plugged in.
run fsck -f on that disk no -y
expect to spend some time because when it happened to me it took a while.
It looked like my disk was defraging
boot fail when system mounted sda1 partition, but when i do restart, boot run also fine (or not)…
These errors do not occur each time, but only sometimes…
To dale14846:
Yes, problem is sometimes with data disc (sdb device - classic sata HDD), but sometimes also with root partition (sda1) screen two.
fsck -f ended good on all partition…(see post 8 - Boot fail, when is Ext4 partition mounting - openSUSE 11.2 - openSUSE Forums)
If I delete from the fstab data disc mount point, error number 1 is gone, bun no 2. It is logical
These errors do not occur each time, but only sometimes!
>
>To caf4926:
>Problem is described in the first post. OpenSUSE boot sometimes end
>with these errors:
>
>http://www.djscore.org/tmp/boot_fail_1.jpg
>- boot fail when system mounted sdb1 partition, but when i do restart,
>boot run fine (or not)…
>
>http://www.djscore.org/tmp/boot_fail_2.jpg
>- boot fail when system mounted sda1 partition, but when i do restart,
>boot run also fine (or not)…
>
>These errors do not occur each time, but only sometimes…
>
>To dale14846:
>Yes, problem is sometimes with data disc (sdb device - classic sata
>HDD), but sometimes also with root partition (sda1) screen two.
>fsck -f ended good on all partition…(see post 8 - ‘Boot fail, when is
>Ext4 partition mounting - openSUSE 11.2 - openSUSE Forums’
>(http://tinyurl.com/y8qg3pb))
>If I delete from the fstab data disc mount point, error number 1 is
>gone, bun no 2. It is logical
>These errors do not occur each time, but only sometimes!
An intermittent error strongly suggests marginal HW or cabling in the system.
Try replacing the disk cables (or even just remove&reinstall the ones youhave).
The cause could be that the partition in question is not avaiable (e.g. it is on an external HD that is not connected), the partition has wrong parameters or the wrong file system listed in /etc/fstab, or that there’s something wrong with the partition.
The /etc/fstab entry looks ok (if it wasn’t, it would always give the error), so if the partition is always avaiable, that can only mean there’s something wrong with the partition.
Run the following from a root console:
fsck -y /dev/sda2
That one means it couldn’t mount your root partition:
