Filesystem check or mount failed. fsck not helping
Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
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.
Filesystem check or mount failed. fsck not helping
Hi,
For some reason, yesterday skype crashed with some I/O error and said to reinstall it. I did that and then my PC restarted showing following error at start
Quote:
Filesystem check or mount failed.
A maintenance shell will now be started.
CONTROL-D will terminate this shell and continue booting after re-trying filesystems. Any further errors will be ignored.
I ran fsck -f and it found few errors and fixed them. I tried hitting CONTROL-D then but everything I get immediately is the same message.
I then tried reboot and shutdown commands but PC would just hang at "shutting down processes" or something like that. If I reboot my PC over restart button I get the same message again.
I booted from Live cd now and I can normally see my partitions and hard drivers.
Here is the fdisk -l output.
Quote:
ubuntu@ubuntu:~$ sudo fdisk -l
Disk /dev/sda: 160.0 GB, 160041885696 bytes
255 heads, 63 sectors/track, 19457 cylinders, total 312581808 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 identifier: 0x077de6f1
Device Boot Start End Blocks Id System
/dev/sda1 * 63 100358054 50178996 7 HPFS/NTFS/exFAT
/dev/sda2 100358055 312576704 106109325 7 HPFS/NTFS/exFAT
Disk /dev/sdb: 80.0 GB, 80026361856 bytes
255 heads, 63 sectors/track, 9729 cylinders, total 156301488 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 identifier: 0x000402ca
Device Boot Start End Blocks Id System
/dev/sdb1 * 2048 499711 248832 83 Linux
/dev/sdb2 501758 156301311 77899777 5 Extended
/dev/sdb5 501760 156301311 77899776 8e Linux LVM
Disk /dev/mapper/Voyager-root: 76.5 GB, 76546048000 bytes
255 heads, 63 sectors/track, 9306 cylinders, total 149504000 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 identifier: 0x00000000
Disk /dev/mapper/Voyager-root doesn't contain a valid partition table
Disk /dev/mapper/Voyager-swap_1: 3221 MB, 3221225472 bytes
255 heads, 63 sectors/track, 391 cylinders, total 6291456 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 identifier: 0x00000000
Disk /dev/mapper/Voyager-swap_1 doesn't contain a valid partition table
Here is the fstab output
Quote:
# /etc/fstab: static file system information.
#
# Use 'blkid -o value -s UUID' 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>
proc /proc proc nodev,noexec,nosuid 0 0
/dev/mapper/Voyager-root / ext4 errors=remount-ro 0 1
# /boot was on /dev/sda1 during installation
UUID=5826e790-9944-4817-9e9c-3b14bf502149 /boot ext2 defaults 0 2
/dev/mapper/Voyager-swap_1 none swap sw 0 0
/dev/fd0 /media/floppy0 auto rw,user,noauto,exec,utf8 0 0
Also, everything is read only wwheter I boot from live cd or try recovery console.
I really don't understand what went wrong here. I never ever had problems like this... but it seems there's a first time for everything. And right at the wrong moment since I have exam tomorrow and I need my PC today :/
p.s.
I'm using latest version of kubuntu
edit:
some LVM info
Quote:
lvm> pvscan
PV /dev/sdb5 VG Voyager lvm2 [74,29 GiB / 0 free]
Total: 1 [74,29 GiB] / in use: 1 [74,29 GiB] / in no VG: 0 [0 ]
Quote:
lvm> vgscan
Reading all physical volumes. This may take a while...
Found volume group "Voyager" using metadata type lvm2
lvm> lvscan
ACTIVE '/dev/Voyager/root' [71,29 GiB] inherit
ACTIVE '/dev/Voyager/swap_1' [3,00 GiB] inherit
Quote:
lvm> lvdisplay
--- Logical volume ---
LV Path /dev/Voyager/root
LV Name root
VG Name Voyager
LV UUID qq1qtw-VwQn-5Uwf-AF7O-HFa2-9sSO-PI469L
LV Write Access read/write
LV Creation host, time ,
LV Status available
# open 1
LV Size 71,29 GiB
Current LE 18250
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 252:0
--- Logical volume ---
LV Path /dev/Voyager/swap_1
LV Name swap_1
VG Name Voyager
LV UUID bjB2Ym-Zxbn-dbpB-G2ql-FQVD-G2XE-Tk1gAJ
LV Write Access read/write
LV Creation host, time ,
LV Status available
# open 0
LV Size 3,00 GiB
Current LE 768
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 252:1
lvm>
/proc/partitions
Quote:
ubuntu@ubuntu:~$ cat /proc/partitions
major minor #blocks name
If fsck only found a few errors, and you can see ALL your disks from the rescue disk, it could be the 2nd option 'or mount failed.'
Have a look at /var/log/dmesg, /var/log/boot.log and see if its having problems with mounting, rather than corruption.
Possibilities include a slightly loose cxn. Cable connectors can work loose over time, due to heating and cooling during use/non-use.
Try reseating all connectors firmly.
Might(?) be a disk going bad, but seems unlikely if fsck didn't find much.
You could run some diagnostics http://linux.die.net/man/8/smartctl and also see the manufacturers website for more specific tools.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.