LinuxQuestions.org

LinuxQuestions.org (http://www.linuxquestions.org/questions/index.php)
-   Linux - Hardware (http://www.linuxquestions.org/questions/forumdisplay.php?f=18)
-   -   "Error mounting: mount: File too large" Centos 6.4 with Raptor 34Gb HDD (http://www.linuxquestions.org/questions/showthread.php?t=4175468935)

soohyun2222 07-08-2013 08:09 PM

"Error mounting: mount: File too large" Centos 6.4 with Raptor 34Gb HDD
 
Hello everyone, I am in need of your help. I am trying to mount my hard disk which was working fine just few days ago. So the error message that I get is the following: "Error mounting: mount: File too large"
This message appears when I pass GRUB screen.
I tried mounting the same hard disk by booting through other hard disk and then mount that hard disk. I still get the same error.
I think that what might have caused the problem is hard disk space over usage. Not only it has small disk space from the beginning, I installed League of Legends last time when it was working.
However, also note that I have a overclocking going on in that computer and first symptom that I got was that unresponsive log-on screen. I kept dropping FSB since and finally got to this error message.
Thanks for the help in advance.
Soohyun

GlennsPref 07-08-2013 08:18 PM

A nice tool I use during Over clocking is memtest86+

I say this because of the size factor.

soohyun2222 07-10-2013 03:03 PM

Quote:

Originally Posted by GlennsPref (Post 4986630)
A nice tool I use during Over clocking is memtest86+

I say this because of the size factor.

Thanks for the reply.
Currently, I am on my stock clock. I am running Pentium4 800FSB 2.8Ghz CPU.
As far as the CPU operation, it seems to be fine. Right now it is summer in the US and I sometimes see "CPU overheated and throttled" message on my Centos screen but I assume that CPU should be on my last concern because I am now underclocking.

What is the size factor by the way?

GlennsPref 07-10-2013 05:55 PM

Memtest86+ is a ram test, not cpu.

The size factor maybe the size of the file compared to the size of the ram.

soohyun2222 07-11-2013 02:05 AM

Quote:

Originally Posted by GlennsPref (Post 4988025)
Memtest86+ is a ram test, not cpu.

The size factor maybe the size of the file compared to the size of the ram.

Thanks.
So the mounting is not happening because the file size of what is larger than RAM?
My RAM is 1.5Gb. Even though when I last used the hard drive I ran it in 512Mb. Then I added an extra 1Gb to the computer.
Could this be the problem???

jefro 07-11-2013 03:15 PM

I'd think the drive has some errors on it. Grub is booting and the complaint is the file or files it is looking at are too large.

Boot to live cd and use file system check tools.

It can't hurt to test memory. Can't hurt to run hard drive diags.

GlennsPref 07-12-2013 08:44 PM

Quote:

Originally Posted by soohyun2222 (Post 4988230)
Thanks.
So the mounting is not happening because the file size of what is larger than RAM?
My RAM is 1.5Gb. Even though when I last used the hard drive I ran it in 512Mb. Then I added an extra 1Gb to the computer.
Could this be the problem???

I may be off target, I thought the file may be too large to be held in memory, swap and ram.

Sorry for the mis-direction.

selfprogrammed 07-26-2013 03:47 PM

You don't usually mount a drive, so I assume you are mounting a partition of a drive.
You are specifying a partition device name, and not the whole drive, aren't you?
Because there is no reason to assume the MBR got written, let us assume the partition table has the partition location and size right. If unsure then check with fdisk.
>> man fdisk

Linux can handle files larger than the memory, it does not bring them in whole, it uses a drive cache.
This partition should be checked by a fsck, which is done unmounted anywhay.
>> man fsck
>> ls /sbin/*fsck*

Interesting that it is mount that is giving the error, not a filesystem driver.
Check dmesg for filesystem messages and mount messages. They are more explicit.
Check /var/log/ files for recent mount messages (use tail <filename>).

Overclocking while writing to the drive may have written some corrupted information,
such as recording a file as larger than the physical size of the drive.
Self checks at mount may be detecting this.


All times are GMT -5. The time now is 09:57 PM.