Displaying 20 results from an estimated 6000 matches similar to: "Ext3 problem - lost files/directorys"
2002 Nov 10
2
Harddisk gone bad
Hi all,
I know this is the EXT3 list, and my problem is with an EXT2 filesys, but I cannot seem to find a more suitable list on this server, and I have seen a lot of knowledge go by on this list and in the archives, so I thought I'd give it a try anyway...
Here goes nothing:
I am in a terrible problem: My data disk on my Linux server has gone bad, with approx 18 GB of data on it, and I
2006 Nov 01
1
e2fsck: Bad magic number in super-block
I posted this to the Fedora-list, but thought I might get some
additional information here as well.
I have a HD that refuses to mount with a 'bad magic number in
super-block'. I'm running FedoraCore 6 x86_64.
[root at moe ~]# fdisk -l /dev/hdc
Disk /dev/hdc: 250.0 GB, 250059350016 bytes
255 heads, 63 sectors/track, 30401 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
2006 Jun 24
3
recover data from linear raid
Hello,
I had a scientific linux 3.0.4 system (rhel compatible), with 3
ide disks, one for / and two others in linear raid (250 gb and 300 gb
each).
This system was obsoleted so i move the raid disks to a new
scientific linux 3.0.7 installation. However, the raid array was not
detected ( I put the disks on the same channels and same master/lsave
setup as in the previous setup). In fact
2007 Sep 20
8
How are alternate superblocks repaired?
Hi,
Using dumpe2fs I have been able to determine that all of my alternate ext3 superblocks are corrupted (not clean), and only the primary superblock is valid, i.e. mount works and the ordered journal is applied. When the primary superblock gets flakey, i.e. the ext_attr Filesystem feature goes missing - not sure why this occurs. At this point, the mount does not apply the journal using the
2006 Apr 21
1
problem with e2fsck not knowing xfs
Hi!
I had problem yesterday with e2fsck.
It reported a bad superblock.
I then tried to use one of the other superblocks.
To no avail.
Then later I remembered that I had switched the fs type to xfs.
Maybe e2fsck could recognize other common fs types,
and report this instead?
best regards
keld
2004 Jul 22
2
Ext3 filesystem aborting journal at random times (Maxtor 300GB disk)
Hi,
Sorry if this is an old and fixed issue but I can't really seem to find
a definitive explanation/fix to this in the mail lists. Ever since I
upgraded to FC2 my server randomly decides that it can no longer access
the disk and "aborts" the ext3 journal leaving it read-only as
expected. I've seen the same errors on other mail list, explained away
as disk or disk cable
2006 Jan 17
1
Mounting problem
Hi folks,
For unknown cause I encounter following mounting problem;
# /mnt/hda8
mount: wrong fs type, bad option, bad superblock on /dev/hda8,
missing codepage or other error
In some cases useful info is found in syslog - try
dmesg | tail or so
# dmesg | tail
via82cxxx: timeout while reading AC97 codec (0x9A0000)
via82cxxx: timeout while reading AC97 codec (0x9A0000)
2020 May 28
2
Recover from an fsck failure
This is CentOS-6x.
I have cloned the HDD of a CentOS-6 system. I booted a host with that drive
and received the following error:
checking filesystems
/dev/mapper/vg_voinet01-lv_root: clean, 128491/4096000 files, 1554114/16304000
blocks
/dev/sda1: clean, 47/120016 files, 80115/512000 blocks
/dev/mapper/vg_voinet01-lv_home: clean, 7429/204800 files, 90039/819200 blocks
2001 Mar 22
1
get root inode failed
Erm, sheez having alot of problems :(
I have just been reading all the archives on the mailing list for the past few hours and
decided to try make the journal with:
tune2fs -j -J10 /dev/hdc1
[root@tkw /]# tune2fs -j -J10 /dev/hdc1
tune2fs 1.20-WIP, 17-Jan-2001 for EXT2 FS 0.5b, 95/08/09
Creating journal inode: done
[root@tkw /]# cat /etc/fstab
/dev/hdc1 /usr/local ext3
2003 Aug 18
2
another seriously corrupt ext3 -- pesky journal
Hi Ted and all,
I have a couple of questions near the end of this message, but first I have
to describe my problem in some detail.
The power failure on Thursday did something evil to my ext3 file system (box
running RH9+patches, ext3, /dev/md0, raid5 driver, 400GB f/s using 3x200GB
IDE drives and one hot-spare). The f/s got corrupt badly and the symptoms
are very similar to what Eddy described
2001 May 11
1
ext3 filesystem lost.
Hello.
We have, over the last few months, lost ext3 filesystems three times.
The whole filesystem left unusable.
nfs-server:~# mount /dev/rd/c0d1p1 /mnt -t ext3
mount: wrong fs type, bad option, bad superblock on /dev/rd/c0d1p1,
or too many mounted file systems
(in dmesg)
EXT3-fs: journal inode is deleted.
EXT3-fs: get root inode failed
nfs-server:~# fsck /dev/rd/c0d1p1
Parallelizing
2004 Jul 06
1
Overwriting ext2 Partition with ext3
Hi,
Suppose you have an ext2 Partition at 14GB which is 80-90% full.
Most files are smaller than 1 MB (there are just 20 or so which are
over 100MB where 800MB is the biggest one).
Block size etc - everything is default.
Now you do this:
mke2fs -j /device
Important is the "-j" switch.
What happens without the "-j" switch? All superblocks and inodes
are overwritten. Is this
2007 Mar 01
1
whoops, corrupted my filesystem
Hi all-
I corrupted my filesystem by not doing a RTFM first... I got an automated
email that the process monitoring the SMART data from my hard drive detected
a bad sector. Not thinking (or RTFMing), I did a fsck on my partition-
which is the main partition. Now it appears that I've ruined the
superblock.
I am running Fedora Core 6. I am booting off the Fedora Core 6 Rescue CD in
2009 Dec 08
3
botched RAID, now e2fsck or what?
Hi all,
Somehow I managed to mess with a RAID array containing an ext3 partition.
Parenthesis, if it matters: I disconnected physically a drive while
the array was online. Next thing, I lost the right order of the drives
in the array. While trying to re-create it, I overwrote the raid
superblocks. Luckily, the array was RAID5 degraded, so whenever I
re-created it, it didn't go into sync;
2007 Mar 12
1
Error mounting
Hi all,
i'm new in the list so i'm sorry if this i'm posting is off-topic or it was
already answered before.
I'm having this problem; i've got an ext3 8GB partition and it doesn't
mount, the cause of this: a user (yes me!) running fsck.ext3 with the
filesystem mounted, ups! (snif, forgive me!!, totally newbie and mad)
errors while booting:
EXT3_fs error (device hda4):
2005 Oct 31
2
ext3 + fs > 2Tbyte
Hi list
this is actually a problem on a debian system but I thought you might
be interested to hear of it and perhaps can offer some help.
I have a woody box (dell pe750, dual cpu) running a kernel from
backports.org (debian 'testing' packages built on a 'stable' box).
The kernel version is 2.6.7-1.backports.org.1.
This host is hooked up to an Apple Xserve RAID with a 2.3Tbyte
2002 Apr 02
7
ext3 crash
Hi,
One of my shared volumes crashed the other day on a RH-7.2, 2.4.9-31 system.
These are the first errors in the log:
kernel: EXT3-fs error (device ide0(3,9)): ext3_readdir: bad entry in
directory #2424833: rec_len is smaller than minimal - offset=0,
inode=2553887680, rec_len=0, name_len=0
kernel: EXT3-fs error (device ide0(3,9)): ext3_readdir: bad entry in
directory #2424833: rec_len is
2003 Nov 09
1
EXT3 Superblock Recovery
hello.
had a bad day yesterday: accidentally, the first 0.5% to 1% of my ext3 partition got overwritten, can't gauge it more exactly. Geography of the partition is:
size ~100 GB.
block size should be 4096.
=> deleted are averages to 500mb - 1gb still.
I don't think it is relevant, but the device itself is /dev/loop0, because there is a cryptoloop layer between the device and the
2004 Apr 02
2
Strange Fedora Booting problem: can not mount "LABEL=*" partitions
Hi,
Just got Fedora FC1 vanilla 2.4.25kernel+libata8patch booting problems, FC1 complains that it can not automatically find&found partitions specified with "LABEL=" in /etc/fstab, and then falls me into repair mode. In the repair mode I can mount it manually without any problems. More interesting are: 1) I have several partitions specified with "LABEL=*" in
2014 Sep 21
1
Re: Possible bug in mkfs.ext3
On 09/20/2014 12:07 AM, Andreas Dilger wrote:
> On Sep 19, 2014, at 7:56 PM, jd1008 <jd1008@gmail.com> wrote:
>> I am reporting this on the advice of the Fedora Users Mailing List Member.
>>
>> This the mailing list exchange outlining the problem with specifying -S to mkfs, and it's subsequent consequences when fsck is run.
>>
>> I am reporting this per