Hello,
after my box crashed and when I booted the machine agai I got the message:
...
ext3 No journal on filesystem on ide0(3, 4)
mount: wrong fs type, bad option, bad superblock on /dev2/root2, or
too many mounted file system.
however fsck said that '/dev/hda4' is clean and I can use
On Wed, 22 Jan 2003, John Schmidt <[EMAIL PROTECTED]> wrote:
>
> I am copying & pasting their post:
>
>
> I've written a doc on how to install a Debian with root file system over
> LVM and RAID.
>
> If it's of any interest it can be found at this URL:
> http://www.midhgard.it/docs/index_en.htm
On Tuesday 21 January 2003 11:31 pm, Michael Kahle wrote:
> > I am trying to install a Debian testing box with root on RAID
> > 1 following the instructions given at
> > http://karaolides.com/computing/HOWTO/lvmraid/
>
> I am working on setting up a system with this configuration. I
> decided to w
> When I ran vgcreate it seamed to work fine. However it lists
> the MAX LV Size as being 255.99GB. This does not make sense
> with my configuration. I have 5 SCSI disk partitions in a
> RAID5 array. Each partition is 36446.22mb. My math shows I
> should have a MAX LV size of being 145784.8
> I am trying to install a Debian testing box with root on RAID
> 1 following the instructions given at
> http://karaolides.com/computing/HOWTO/lvmraid/
I am working on setting up a system with this configuration. I decided to
work step by step with this howto to get my system running. Thanks
clue! :-( ):
kernel: EXT2-fs error (device md(9,1)): ext2_check_page: bad entry in directory
#487195: rec_len is smaller than minimal - offset=0, inode=0, rec_len=0, name_len=0
No need to say, after that the system goes berzek and most of the
commands stop working. However, if I reboot, the pro
I found the following in /var/log/kern.log:
kernel: EXT2-fs error (device ide0(3,4)): ext2_readdir: bad entry in directory
#198657: rec_len is too small for name_len - offset=868, inode=198683,
rec_len=32, name_len=56
kernel: EXT2-fs error (device ide0(3,4)): ext2_readdir: bad entry in
On Tue, May 18, 1999 at 04:23:41PM +1000, Rob wrote:
> Have you run fsck on the partition? Its probably the best place to start
> with disk problems.
Yes, that was one of the first things I did. The partition came up clean.
> I'm running a full Potato system (2.2.9 kernel). Tonight, for the first
> time, I got an error I've never seen before in the 4 years I've been running
> Linux full-time. I'm hoping this is bug in Potato and not something more
> serious with my system.
[snip]
> 3,69 is the /dev/hdb5 partition
d up when Debian was doing it's nightly housekeeping
in /etc/cron.daily ...
EXT2-fs error (device ide0(3,69)): ext2_readdir: directory #4148 contains a
hole at offset 1024
EXT2-fs error (device ide0(3,69)): ext2_readdir: directory #4148 contains a
hole at offset 2048
EXT2-fs error (device
and load
the data from my backup tape. But I got these error messages:
EXT-fs error (device 03:41) ext2_readdir: bad entry in directory
EXT2-fs error (device 03:02): ext2_find_entry: bad entry in directory
#4179: rec_len is smaller than minimal - offset=616, inode=0, rec_len=0,
name_len=0
EXT2-fs
11 matches
Mail list logo