Displaying 20 results from an estimated 9000 matches similar to: "How are alternate superblocks repaired?"
2008 Aug 15
1
Hard disk, format, filesystem
Ok, I give up... I have to ask. This is CentOS 5.
I switched one of my raid1 disks, and I already thought I had succeeded. But
now it seems that something is very wrong with the first partition on the
new disk. Luckily my system is fully bootable with the other disk.
Here's some info. The new disk is sdb.
// I removed all partitions with parted, and created the first one again.
// parted
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
2005 Oct 21
2
Recover original superblock on corrupted filesystem?
I've been trying to use fsck to recover a corrupted filesystem.
It appears the original superblock is corrupted too, as it has an inode
count of 0. When I start fsck with -b 32760, it uses the alternate
superblock and proceeds. However, it restarts from the beginning a
couple of times and after the second restart it doesn't use the
alternate superblock, stopping instead as it can't
2004 Mar 03
2
Ext3 problem - lost files/directorys
Hi
I work on this harddrive for 3 days now ...
I had noticed errors in kernel while working on a harddrive (120 gigas) but
all continue to work fine (archives/directory)..
So i have unmounted the driver and try e2fsck... bad !
e2fsck 1.34 (25-Jul-2003)
e2fsck: Attempt to read block from filesystem resulted in short read while
trying to open /dev/hdc1
So i have tried to create 1 image of this
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
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
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 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
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)
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
2014 Sep 20
0
Re: Possible bug in mkfs.ext3
On Sep 19, 2014, at 7:56 PM, jd1008 <jd1008 at 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 suggestions made to me on the Fedora Users Mailing List.
I would
2001 Dec 11
1
More external journal woes.
I have been playing with external journals some more and thought I
should share some experiences.
I am running 2.4.16 with the ext3 patches from Andrew Morton
and e2fsprogs 1.25
I have an ext3fs filesystem on an 8 drive RAID5 array and place the
journal on a partition of the mirrored pair that I boot off (all
drives SCSI).
I have tried pulling the power cable and seeing what happens. I
finally
2006 Nov 16
2
ext3 corrupted
Hi there,
For years I've been using the ext3 file system without to think that it can ever gets broken so bad.
This was until last week when a box that I have running Linux from a SanDisk CF went down.
Since then I am struggling with this CF trying to understand what is happening.
The CF is SanDisk ultra II 1GB.
On this I have 4 partitions all of them with ext3:
boot
/
swap
2014 Sep 20
4
Possible bug in mkfs.ext3
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 suggestions made to me on the Fedora Users
Mailing List.
The following is the mailing list exchange:
On 09/18/2014 07:01 PM, Robert Nichols wrote:
> On
2007 Jan 10
3
Can't mount /home anymore
Hi!
I'm new to the list. I have a problem with mounting my home directory since
my PC crashed. I hope that I can get some help on this list as I don't know
much of ext3 myself.
The mount command for my /home gives me the following output:
# mount /dev/sda6 /mnt/tmp/
mount: wrong fs type, bad option, bad superblock on /dev/sda6,
missing codepage or other error
In some cases useful info
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
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
2005 Dec 16
1
Ghost 8.0 Clone Filesystem with ext3 (remove resize_inode and ext_attr features)
I've Found a page with interesing discussion about images backup
http://forums.fedoraforum.org/archive/index.php/t-28255.html
This give a "dirty" solucion for remove special thing of ext3 (Selinux
remove resize_inode and ext_attr features) witch cause the error in ghost.
I hope somebody help with the problem of norton ghost and clone centos 4.
:)
-----------
sfabkk
2005-07-11,
2011 Mar 08
3
[Newbie] Reclaiming /boot space
When trying to do a yum update, I am told I need more space in
/boot. When I check the contents of /boot (ls -l /boot), there
are no files.
If I do a df -h, there is no available space yet it shows that it
has a lot of used space.
The fstab shows the following:
# This file is edited by fstab-sync - see 'man fstab-sync' for
details
/dev/VolGroup00/LogVol00 /
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