fsck unexpected inconsistency, unreadable blocks, short read -Pls Help
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.
You need to restart your machine and boot it off of a "live CD"/RHEL build disk/etc. Then run fsck on the disk/partition in question.
That's what I'm doing right now. I used the RHEL build disc to boot in Rescue Mode. Filesystem was mounted to /mnt/sysimage so I'm trying to unmount to run fsck. You know what? I'll just reboot and run the Rescue Mode again but this time I'll skip the mounting and just fsck /dev/VolGroup00/LogVol00
Distribution: Currently: OpenMandriva. Previously: openSUSE, PCLinuxOS, CentOS, among others over the years.
Posts: 3,881
Rep:
Quote:
Originally Posted by SomeITguy
That's what I'm doing right now. I used the RHEL build disc to boot in Rescue Mode. Filesystem was mounted to /mnt/sysimage so I'm trying to unmount to run fsck. You know what? I'll just reboot and run the Rescue Mode again but this time I'll skip the mounting and just fsck /dev/VolGroup00/LogVol00
Sound good?
Sounds really good.
That was your mistake... mounting it. Let fsck do it's work before mounting it.
Distribution: Currently: OpenMandriva. Previously: openSUSE, PCLinuxOS, CentOS, among others over the years.
Posts: 3,881
Rep:
Quote:
Originally Posted by SomeITguy
Well, that didn't go as I hoped for. Looks like if I skip the "find and mount your filesystem" part then there is no /dev/VolGroup00/LogVol00
It looks like it creates another device node for your RAID volume, when you mount it. I was afraid of something like that.
So now we need to work out WHICH device node is for the disk/partition in question. Can you describe the RAID setup you have, eg. how many disks, partitions, which RAID level, etc?
Also run the following command and post the output:
It looks like it creates another device node for your RAID volume, when you mount it. I was afraid of something like that.
So now we need to work out WHICH device node is for the disk/partition in question. Can you describe the RAID setup you have, eg. how many disks, partitions, which RAID level, etc?
Also run the following command and post the output:
Code:
ls -la /dev/md*
Beforing checking for replies I tried this:
Code:
#lvm lvchange -a y /dev/VolGroup00/LogVol00
After that I could confirm with lvm lvscan that /dev/VolGroup00/LogVol00 was now active, but then this happened when I tried to fsck:
Code:
#fsck /dev/VolGroup00/LogVol00
#fsck: WARNING: couldn't open /etc/fstab: no such file or directory
#/dev/VolGroup00/LogVol00: clean, 106094/518356992 files, 65944159/51834060 ks
Last edited by SomeITguy; 02-11-2018 at 10:49 AM.
Reason: typo
From below it looks like it's saying your file system is clean.
That's what I thought at first, but how can that be possible? It didn't do or scan anything, it didn't even take a second after I pressed ENTER and that was the output.
Last edited by SomeITguy; 02-11-2018 at 11:14 AM.
Reason: typo
Distribution: Currently: OpenMandriva. Previously: openSUSE, PCLinuxOS, CentOS, among others over the years.
Posts: 3,881
Rep:
Quote:
Originally Posted by SomeITguy
That's what I thought at first, but how can that be possible? It didn't do or scan anything, it didn't even take a second after I pressed ENTER and that was the output.
It may have cleared it's journal the last time you mounted it. As you have found, Linux systems generally do a file system check when you start the system and it goes to mount the disk/partition.
You can also run the command I mentioned in my last post, but I would un-mount the drive first beforehand.
Distribution: Currently: OpenMandriva. Previously: openSUSE, PCLinuxOS, CentOS, among others over the years.
Posts: 3,881
Rep:
Quote:
Originally Posted by SomeITguy
They just tried and still nothing.
As soon as I finish lunch I'll try fsck -fy as suggedted.
Well, good luck with it.
If you type in the command below, you should be able to find out which device node is for the partition in question.
Code:
fdisk -l
For your LVM volumes it should look something like this:
Code:
/dev/sda5 660611072 1709187071 524288000 8e Linux LVM
Some of the numbers will be a little different, that's all. The important bit your looking for is in bold. That's the device node your after - the one at the start of the line (/dev/XXX).
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
