LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Newbie (https://www.linuxquestions.org/questions/linux-newbie-8/)
-   -   computer asks me to run a FSCK Manually, but won't : says can't run on mounted (https://www.linuxquestions.org/questions/linux-newbie-8/computer-asks-me-to-run-a-fsck-manually-but-wont-says-cant-run-on-mounted-631402/)

lightwave 03-28-2008 10:42 PM

computer asks me to run a FSCK Manually, but won't : says can't run on mounted
 
Disk drive .

fsck says I can't run on a disk that it is failing.
dev/sda2 am stuck without it.

Does anyone know how to deal with this issue? Or has anyone else seen this and fixed it?

thanks

blackhole54 03-29-2008 12:14 AM

If the disk is actually failing (about to die), you probably want to recover what you can off of it immediately and not worry about fsck. (Unless you already have a current backup -- good for you! -- in which case you can then just throw the disk away.)

If you meant the disk is just showing an error with the message to run fsck, the simplest thing might be to boot from a live CD and run fsck from there. Almost any live CD will work, including KNOPPIX, or perhaps the live CD you installed from (if that was how you installed.) There are other options depending on whether this is your root partition and perhaps the distro you are running.

If you need to post back, please let us know what distro you are using.

STARHARVEST 03-29-2008 11:31 AM

why actually disk is failing? maybe that was just emergency power off?

onebuck 03-29-2008 11:52 AM

Hi,

Hopefully you already have a backup.

You should run 'fsck' in single user mode. Just pass the 'single' option at the boot of your distro. Once you are booted then run the 'fsck' on the device. You could use a Livecd to perform the same as the device could be 'umount' to perform maintenance on it.

I would suggest that you get the drive manufactures diagnostics and run the the diagnostics on the device in question.

Another good tool would be the 'SystemRescueCD' this link is in the 'Tools, Recovery, Diagnostic, Emergency' section of 'Slackware-Links' . You will find other useful tools and links in the wiki.

lightwave 03-29-2008 12:57 PM

computer asks me to run a FSCK Manually, but won't : says can't run on mounted Reply
 
I am running OpenSuse 10.2,
This is not happening to the "root" partition.
It happening on dev/sda2 (2nd part on 1st sata drive) Not raided, btw.

I think I had caused this myself by trying to delete a persons folder as root? not sure. But it was just a personal folder with pictures on a shared drive for someone not using this machine anylonger.

I don't believe anything may be wrong with the disk though (is that possible?)

will ruinning fsck from intall disk run? If so I will try to do that.

thanks

onebuck 03-29-2008 08:24 PM

Hi,

You should still run the fsck on the drive as single user.

blackhole54 03-29-2008 11:55 PM

Quote:

Originally Posted by lightwave (Post 3104252)
I don't believe anything may be wrong with the disk though (is that possible?)

If you don't think anything is wrong with the disk, then I wouldn't worry about it. Your wording was unclear in your original post.

Quote:

will ruinning fsck from intall disk run? If so I will try to do that.
If the installation disk is a live CD or has a rescue mode then your can run fsck from there if it has a copy of fsck (it probably does). Make sure the partition is not mounted.

lightwave 03-30-2008 05:37 PM

computer asks me to run a FSCK Manually
 
Ok the exact verbage from the problem is stating THE FOLLOWING:

the problem occurred looks like a hardware problem. If you have bad blocks ....

bread: Cannot read the block (58261504) (input/output error)

Warning ... fsck.reiserfs for device /dev/hdc1 exited with signal 6.
fsck.reiserfs /dev/hdc failed (status 0x8). Run manually!
blogd: no message logging because /var filesystem is not accessible

[usb init stuff]
then...

fsck failed for at least one filesystem (not /).
Please repair manually and reboot.
The root filesytem is already mounted read/write.

Attention: Only CONTROL-D WILL REBOOT the system in this maintenance mode. shutdown or reboot will not work.

give root pw for login:


then I go to run fsck and get the following:

Will readonly check consistency of fs on dev/sda2
it complains about write permissions and fsck fails.

btmiller 03-30-2008 05:47 PM

It looks like /dev/hdc1 is the problem ... how are you running fsck? If you just type "fsck" with no arguments I believe it will try to fsck the root partition which is no good, because it's mounted. You need to do:

umount /dev/hdc1

to unmount it in case it's mounted, and then

fsck /dev/hdc1

To fsck it. Note that if you're getting block read errors, that probably means that the disk is on its way out ... I'd suggest taking a backup ASAP. Deleting someone's folder as root should not cause filesystem errors.

onebuck 03-30-2008 07:16 PM

Hi,

If this is a system with just one user then run the 'fsck' on the unmounted filesystem. I just like to run as single to insure no activity is allowed to others when in this mode. That way you are insured no problem will arise.

lightwave 03-30-2008 07:55 PM

computer asks me to run a FSCK Manually
 
Will running fsk change the file structure at all? That is does it have the possibility to Render it unusable or unbootable? I have many users on this machine and a lot of important data (backed up), to make sure they remain having the availability if at all possible for their data.


One thing should be noted, I am also exporting the file system on this drive. BUt, that just has to do with mounting...

thanks

onebuck 03-30-2008 08:35 PM

Hi,

If the problem is within the data of the filesystem then of course the possibility exists.

lightwave 04-02-2008 12:25 AM

SUSE 10.2 , computer asks me to run a FSCK
 
Quote:

Originally Posted by btmiller (Post 3105301)
It looks like /dev/hdc1 is the problem ... how are you running fsck? If you just type "fsck" with no arguments I believe it will try to fsck the root partition which is no good, because it's mounted. You need to do:

umount /dev/hdc1

to unmount it in case it's mounted, and then

fsck /dev/hdc1

To fsck it. Note that if you're getting block read errors, that probably means that the disk is on its way out ... I'd suggest taking a backup ASAP. Deleting someone's folder as root should not cause filesystem errors.


This, is at the least of what I know the issue is it seems. I did not believe the drive was going out because the os complained about 2 other drives going out as well, during different boots. (I still questions this but I must accept becuase we have reformated with rieserfs AND ext3 filesystems with multiple errors being reported during each format.
Thanks, I at least have this episode over with and now boot into init level 5 again.

One more thing, if any one can lend another outlook. During bootup I often get the "falling back to UDP" protocol from TCP. But, the drives all seem to mount fine eventually even the exported mounts.
What could be the cause?

thanks again...


All times are GMT -5. The time now is 09:06 AM.