LinuxQuestions.org
Welcome to the most active Linux Forum on the web.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Newbie
User Name
Password
Linux - Newbie This 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


Reply
  Search this Thread
Old 05-02-2013, 04:53 AM   #1
Celzo
LQ Newbie
 
Registered: May 2013
Posts: 2

Rep: Reputation: Disabled
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
and here is the blkid output

Quote:
ubuntu@ubuntu:~$ sudo blkid
/dev/loop0: TYPE="squashfs"
/dev/sda1: LABEL="Igre" UUID="1E2CFD042CFCD82B" TYPE="ntfs"
/dev/sda2: LABEL="Storage" UUID="B84C13C44C137BF6" TYPE="ntfs"
/dev/sdb1: UUID="5826e790-9944-4817-9e9c-3b14bf502149" TYPE="ext2"
/dev/sdb5: UUID="2cgDDQ-CkWY-hAY9-ST3i-Su5m-bA1u-TDgWbf" TYPE="LVM2_member"
/dev/sr0: LABEL="Ubuntu 13.04 i386" TYPE="iso9660"
/dev/mapper/Voyager-root: UUID="c94261b0-82c6-4f2c-80c7-b53ba7c56680" TYPE="ext4"
/dev/mapper/Voyager-swap_1: UUID="96870738-8c2f-4e37-a751-d30bd1212c15" TYPE="swap"
Although I never touched fstab file. From googling around, I saw that almost everyone fixed it with running fsck but for some reason it doesn't work for me. Here are some images from disk utility on live cd.
http://www.pohrani.com/f/2o/Sv/Hh7Pc...m-2013-05-.png
http://www.pohrani.com/f/3m/vu/1C8mR...m-2013-05-.png
http://www.pohrani.com/f/47/5Y/3lUGj...m-2013-05-.png
http://www.pohrani.com/f/2G/KL/n8sVH...m-2013-05-.png

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

7 0 775440 loop0
11 0 813056 sr0
8 0 156290904 sda
8 1 50178996 sda1
8 2 106109325 sda2
8 16 78150744 sdb
8 17 248832 sdb1
8 18 1 sdb2
8 21 77899776 sdb5
252 0 74752000 dm-0
252 1 3145728 dm-1

Last edited by Celzo; 05-02-2013 at 12:33 PM.
 
Old 05-02-2013, 09:57 PM   #2
chrism01
LQ Guru
 
Registered: Aug 2004
Location: Sydney
Distribution: Centos 6.9, Centos 7.3
Posts: 17,417

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

Last edited by chrism01; 05-02-2013 at 10:01 PM.
 
Old 05-03-2013, 02:43 AM   #3
Celzo
LQ Newbie
 
Registered: May 2013
Posts: 2

Original Poster
Rep: Reputation: Disabled
Since I needed my PC very badly, I simply reinstalled my OS
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

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
fsck failed for at least one filesystem (not /)... linux_2007_ Linux - General 2 01-25-2010 01:57 AM
Mount dirty ext3 filesystem as read only during fsck. Is it possible ? t0x Linux - General 2 05-06-2009 09:18 AM
fsck check failed odeimi_t'zaune Ubuntu 5 01-06-2008 12:42 AM
Failed to check filesystem jonmarco Linux - General 2 07-18-2005 06:12 AM
fsck fails to mount filesystem GoatKing Linux - Software 6 01-26-2004 10:41 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Newbie

All times are GMT -5. The time now is 10:22 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
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration