Sounds like it might be some bad blocks, but about doing the fscks..

fsck let's you do fscks on a mounted partition, in fact, according 
to the manpage it let's you even fsck a mountpoint ie 'fsck /'.

You can boot into single user mode, make sure no read-write/write 
files are open, and type 'mount -o remount,ro /'  that will remount 
your root filesystem read-only.  Not sure if it will work or not 
though, cause you might run into problems with open files that you 
can't really close, but give it a shot and tell us how it goes. 
This is similar to what happens when you boot up, your / filesystem 
is originally mounted read-only, then after checking the filesystems 
it does a 'mount -o remount,rw /'.

You could also boot from one of those single-floppy linuxes, or from 
an installer cd, and do what you want with the filesystems from there.


J. Rafael S�nchez a �crit:
> Hi all,
> 
> Thanks in advance for any attention you lend to this request for help.
> How do you file-system-check the root partition (/) when it appears that
> it's always mounted even in single-mode?
> 
> The reason I'm asking this question is that a day and a half ago, I replaced
> the power supply on one of my servers. I had a master and a slave ide disks
> (and other scsi ones). I removed the slave one because it was not even
> mounted. Twelve hours later, it starting acting kind of funny. I discovered
> that noone could login to the system because /etc/exports was there but the
> system was not exporting any file systems.
> 
> When I looked at the /etc/exports file, there was a bunch or junk at the
> end, like @ signs and stuff. Luckily I had a backup of it to replace it.
> There was another configuration file which showed the same behaviour, namely
> /etc/printcap. Again I had a backup copy to use.
> 
> Things seem to be normal on the surface, except that I'm getting some error
> messages.Here's some of them from dmesg:
> ================start==========
> 
>>dev 03:01 blksize=1024 blocknr=1701999988 sector=-890967320 size=1024
> 
> count=1
> EXT2-fs error (device ide0(3,1)): ext2_readdir: directory #48219 contains a
> hole at offset 1768684544
> attempt to access beyond end of device
> 03:01: rw=0, want=1701999989, limit=265041
> dev 03:01 blksize=1024 blocknr=1701999988 sector=-890967320 size=1024
> count=1
> EXT2-fs error (device ide0(3,1)): ext2_readdir: directory #48219 contains a
> hole at offset 1768685568
> attempt to access beyond end of device
> 03:01: rw=0, want=1701999989, limit=265041
> dev 03:01 blksize=1024 blocknr=1701999988 sector=-890967320 size=1024
> count=1
> EXT2-fs error (device ide0(3,1)): ext2_readdir: directory #48219 contains a
> hole at offset 1768686592
> attempt to access beyond end of device
> 03:01: rw=0, want=1701999989, limit=265041
> dev 03:01 blksize=1024 blocknr=1701999988 sector=-890967320 size=1024
> count=1
> EXT2-fs error (device ide0(3,1)): ext2_readdir: directory #48219 contains a
> hole at offset 1768687616
> attempt to access beyond end of device
> 03:01: rw=0, want=1701999989, limit=265041
> dev 03:01 blksize=1024 blocknr=1701999988 sector=-890967320 size=1024
> count=1
> EXT2-fs error (device ide0(3,1)): ext2_readdir: directory #48219 contains a
> hole at offset 1768688640
> attempt to access beyond end of device
> 03:01: rw=0, want=1701999989, limit=265041
> dev 03:01 blksize=1024 blocknr=1701999988 sector=-890967320 size=1024
> count=1
> EXT2-fs error (device ide0(3,1)): ext2_readdir: directory #48219 contains a
> hole at offset 1768689664
> attempt to access beyond end of device
> 03:01: rw=0, want=1701999989, limit=265041
> dev 03:01 blksize=1024 blocknr=1701999988 sector=-890967320 size=1024
> count=1
> EXT2-fs error (device ide0(3,1)): ext2_readdir: directory #48219 contains a
> hole at offset 1768690688
> attempt to access beyond end of device
> 03:01: rw=0, want=1701999989, limit=265041
> dev 03:01 blksize=1024 blocknr=1701999988 sector=-890967320 size=1024
> count=1
> EXT2-fs error (device ide0(3,1)): ext2_readdir: directory #48219 contains a
> hole at offset 1768691712
> attempt to access beyond end of device
> 03:01: rw=0, want=1701999989, limit=265041
> dev 03:01 blksize=1024 blocknr=1701999988 sector=-890967320 size=1024
> count=1
> EXT2-fs error (device ide0(3,1)): ext2_readdir: directory #48219 contains a
> hole at offset 1768692736
> attempt to access beyond end of device
> 03:01: rw=0, want=1701999989, limit=265041
> dev 03:01 blksize=1024 blocknr=1701999988 sector=-890967320 size=1024
> count=1
> EXT2-fs error (device ide0(3,1)): ext2_readdir: directory #48219 contains a
> hole at offset 1768693760
> attempt to access beyond end of device
> 03:01: rw=0, want=1701999989, limit=265041
> dev 03:01 blksize=1024 blocknr=1701999988 sector=-890967320 size=1024
> count=1
> EXT2-fs error (device ide0(3,1)): ext2_readdir: directory #48219 contains a
> hole at offset 1768694784
> attempt to access beyond end of device
> 03:01: rw=0, want=1701999989, limit=265041
> dev 03:01 blksize=1024 blocknr=1701999988 sector=-890967320 size=1024
> count=1
> EXT2-fs error (device ide0(3,1)): ext2_readdir: directory #48219 contains a
> hole at offset 1768695808
> attempt to access beyond end of device
> 03:01: rw=0, want=1701999989, limit=265041
> dev 03:01 blksize=1024 blocknr=1701999988 sector=-890967320 size=1024
> count=1
> EXT2-fs error (device ide0(3,1)): ext2_readdir: directory #48219 contains a
> hole at offset 1768696832
> attempt to access beyond end of device
> 03:01: rw=0, want=1701999989, limit=265041
> dev 03:01 blksize=1024 blocknr=1701999988 sector=-890967320 size=1024
> count=1
> EXT2-fs error (device ide0(3,1)): ext2_readdir: directory #48219 contains a
> hole at offset 1768697856
> attempt to access beyond end of device
> 03:01: rw=0, want=1701999989, limit=265041
> dev 03:01 blksize=1024 blocknr=1701999988 sector=-890967320 size=1024
> count=1
> EXT2-fs error (device ide0(3,1)): ext2_readdir: directory #48219 contains a
> hole at offset 1768698880
> attempt to access beyond end of device
> 03:01: rw=0, want=1701999989, limit=265041
> dev 03:01 blksize=1024 blocknr=1701999988 sector=-890967320 size=1024
> count=1
> EXT2-fs error (device ide0(3,1)): ext2_readdir: directory #48219 contains a
> hole at offset 1768699904
> attempt to access beyond end of device
> 03:01: rw=0, want=1701999989, limit=265041
> dev 03:01 blksize=1024 blocknr=1701999988 sector=-890967320 size=1024
> count=1
> EXT2-fs error (device ide0(3,1)): ext2_readdir: directory #48219 contains a
> hole at offset 1768700928
> attempt to access beyond end of device
> 03:01: rw=0, want=1701999989, limit=265041
> dev 03:01 blksize=1024 blocknr=1701999988 sector=-890967320 size=1024
> count=1
> EXT2-fs error (device ide0(3,1)): ext2_readdir: directory #48219 contains a
> hole at offset 1768701952
> attempt to access beyond end of device
> 03:01: rw=0, want=1701999989, limit=265041
> dev 03:01 blksize=1024 blocknr=1701999988 sector=-890967320 size=1024
> count=1
> EXT2-fs error (device ide0(3,1)): ext2_readdir: directory #48219 contains a
> hole at offset 1768702976
> attempt to access beyond end of device
> 03:01: rw=0, want=1701999989, limit=265041
> dev 03:01 blksize=1024 blocknr=1701999988 sector=-890967320 size=1024
> count=1
> EXT2-fs error (device ide0(3,1)): ext2_readdir: directory #48219 contains a
> hole at offset 1768704000
> attempt to access beyond end of device
> 03:01: rw=0, want=1701999989, limit=265041
> dev 03:01 blksize=1024 blocknr=1701999988 sector=-890967320 size=1024
> count=1
> EXT2-fs error (device ide0(3,1)): ext2_readdir: directory #48219 contains a
> hole at offset 1768705024
> attempt to access beyond end of device
> 03:01: rw=0, want=1701999989, limit=265041
> dev 03:01 blksize=1024 blocknr=1701999988 sector=-890967320 size=1024
> count=1
> EXT2-fs error (device ide0(3,1)): ext2_readdir: directory #48219 contains a
> hole at offset 1768706048
> attempt to access beyond end of device
> 03:01: rw=0, want=1701999989, limit=265041
> dev 03:01 blksize=1024 blocknr=1701999988 sector=-890967320 size=1024
> count=1
> EXT2-fs error (device ide0(3,1)): ext2_readdir: directory #48219 contains a
> hole at offset 1768707072
> attempt to access beyond end of device
> 03:01: rw=0, want=1701999989, limit=265041
> dev 03:01 blksize=1024 blocknr=1701999988 sector=-890967320 size=1024
> count=1
> EXT2-fs error (device ide0(3,1)): ext2_readdir: directory #48219 contains a
> hole at offset 1768708096
> attempt to access beyond end of device
> 03:01: rw=0, want=1701999989, limit=265041
> dev 03:01 blksize=1024 blocknr=1701999988 sector=-890967320 size=1024
> count=1
> EXT2-fs error (device ide0(3,1)): ext2_readdir: directory #48219 contains a
> hole at offset 1768709120
> attempt to access beyond end of device
> 03:01: rw=0, want=1701999989, limit=265041
> dev 03:01 blksize=1024 blocknr=1701999988 sector=-890967320 size=1024
> count=1
> EXT2-fs error (device ide0(3,1)): ext2_readdir: directory #48219 contains a
> hole at offset 1768710144
> attempt to access beyond end of device
> 03:01: rw=0, want=1701999989, limit=265041
> dev 03:01 blksize=1024 blocknr=1701999988 sector=-890967320 size=1024
> count=1
> EXT2-fs error (device ide0(3,1)): ext2_readdir: directory #48219 contains a
> hole at offset 1768711168
> EXT2-fs error (device ide0(3,1)): ext2_readdir: bad entry in directory
> #56306: rec_len % 4 != 0 - offset=0, inode=606087727, rec_len=25673,
> name_len=58
> EXT2-fs error (device ide0(3,1)): ext2_readdir: bad entry in directory
> #56308: directory entry across blocks - offset=0, inode=1699881006,
> rec_len=26980, name_len=115
> EXT2-fs error (device ide0(3,1)): ext2_readdir: bad entry in directory
> #56310: rec_len % 4 != 0 - offset=0, inode=1701409364, rec_len=8307,
> name_len=116
> EXT2-fs error (device ide0(3,1)): ext2_readdir: bad entry in directory
> #56311: rec_len % 4 != 0 - offset=0, inode=1700754537, rec_len=28781,
> name_len=116
> EXT2-fs error (device ide0(3,5)): ext2_readdir: bad entry in directory
> #38162: rec_len % 4 != 0 - offset=0, inode=673212009, rec_len=26401,
> name_len=101
> EXT2-fs warning (device ide0(3,5)): ext2_free_blocks: bit already cleared
> for block 254658
> 
> ================ end ==========
> 
> You problably don't need it all, but here you have it.
> 
> At first look I thought that I maybe switched hard drives on myself, in the
> exitement of the moment, but I double check jumpers, as well as data that
> I'd added just recently to some httpd folders and this is the right master
> drive.
> 
> I can also tell that it's talking about /dev/hda1 and /dev/hda5 partitions
> (slash and /tmp mount points respectively)
> 
> Is there anything you can make out of this?
> 
> Much appreciated in advance.
> 
> 
> 
> +=+=+=+=+=+=+=+=+=+=+=+=+
> j.rafael.s�nchez
> Systems Administrator
> +=+=+=+=+=+=+=+=+=+=+=+=+
> Itres Research Limited
> www.itres.com
> Phone: 403.250.9944
> Fax:   403.250.9916
> +=+=+=+=+=+=+=+=+=+=+=+=+



Reply via email to