Sponsored Content
Top Forums UNIX for Advanced & Expert Users Linux EXT3 superblock recovery Post 302230073 by lochraven on Thursday 28th of August 2008 02:40:48 PM
Old 08-28-2008
I let the fsck continue, answering 'y' to everything.
When it was finished I was able to mount the filesystem as ext2 and all data was still there.
 

9 More Discussions You Might Find Interesting

1. Linux

Help! Boot failure - corrupt superblock

Hi everyone, OK, I've made a monumental fsck-up of my linux installation AND I did not backup my data properly (idiot!), so I'm really up the proverbial without a paddle here. Basically the problem is I re-sized my /home partition (hda13) using Partition Magic 8.0, after doing so my mandrake... (0 Replies)
Discussion started by: alarmcall
0 Replies

2. Solaris

How to corrupt a superblock?

I need to corrupt a superblock of a mounted device in a soalris m/c and check recovery from an alternate superblock. How can this be done? (2 Replies)
Discussion started by: sujathan
2 Replies

3. Red Hat

superblock error

can anybody help me to recovermy superblock , the recent power crash has done some stuff on my linux redhat 9 box . when i startup the machine iam getting the following error: The superblock could not be read or does not describe a correct ext2 filesystem. If the device is valid and it... (2 Replies)
Discussion started by: ppass
2 Replies

4. Filesystems, Disks and Memory

Linux HDD Recovery

Hello, I have my backup disks here because my server got hacked and we didn't like how liquidweb made the things. So we ask them to ship us the disk. They ran photorec and they got lots of .gz files from it. All accounts I would say. But 50% of them the .tar.gz files came corrupt. And is lefting... (2 Replies)
Discussion started by: asturmas
2 Replies

5. UNIX for Advanced & Expert Users

linux system recovery after overriding connect() by "ld.so.preload"

dear fellows; i have used ld.so.preload file to override connect() function, dynamic library overriding, it did worked really fine ...... but i went on to struck in a situation ... within the overrided connect() i have used printf once to see IP and Port to whom the connect request is being... (1 Reply)
Discussion started by: mzeeshan
1 Replies

6. Filesystems, Disks and Memory

Recovery of formatted ext3 partition

Hi! I have a really big problem right now. I (accidently) formatted a ext3 partition with "mkfs.ext3 /dev/sda1". The problem is that I REALLY need some files from there. The partition had a size of about 4GB, after accidently formatting it, I accidently rewrote Grub on it :wall: I hope I didn't... (3 Replies)
Discussion started by: al0x
3 Replies

7. Linux

CentOS Error: Superblock

Hi Guys, I really don't know where to put my query about this. And as a newbie, I think CentOS is closest to Ubuntu. Anyway, here's my dilemma. I have installed a VMWare - ESX 3.5 and installed CentOS 6 and cloned the CentOS 6. The first CentOS was working fine, when i cloned it, and the cloning... (2 Replies)
Discussion started by: init6_
2 Replies

8. UNIX for Advanced & Expert Users

Superblock marked dirty

Good morning! I met a problem on a FS with AIX 5.3 It's not possible to mount the FS because of a dirty superblock. I tried few things without success. I need your help to solve my problem guys. Do you have any idea please? Thanks a lot drp01,/home/root # mount /GSPRES/data Replaying... (9 Replies)
Discussion started by: Castelior
9 Replies

9. Red Hat

Linux bad superblock on /dev/mapper/VolGroup-lv_root

Hi Friends . my linux try to start very slowly after give it this error: mount: wrong fs type, bad option, bad superblock on /dev/mapper/VolGroup-lv_root, missing codepage or helper program, or other error in some cases useful info is found in syslog - try dmesg : tail or so Kernel panic... (3 Replies)
Discussion started by: blackjuan
3 Replies
FSCK(8) 						       System Administration							   FSCK(8)

NAME
fsck.minix - check consistency of Minix filesystem SYNOPSIS
fsck.minix [-larvsmf] device DESCRIPTION
fsck.minix performs a consistency check for the Linux MINIX filesystem. The current version supports the 14 character and 30 character filename options. The program assumes the filesystem is quiescent. fsck.minix should not be used on a mounted device unless you can be sure nobody is writ- ing to it (and remember that the kernel can write to it when it searches for files). The device name will usually have the following form: /dev/hda[1-63] (IDE disk 1) /dev/hdb[1-63] (IDE disk 2) /dev/sda[1-15] (SCSI disk 1) /dev/sdb[1-15] (SCSI disk 2) If the filesystem was changed (i.e., repaired), then fsck.minix will print "FILE SYSTEM HAS CHANGED" and will sync(2) three times before exiting. Since Linux does not currently have raw devices, there is no need to reboot at this time. WARNING
fsck.minix should not be used on a mounted filesystem. Using fsck.minix on a mounted filesystem is very dangerous, due to the possibility that deleted files are still in use, and can seriously damage a perfectly good filesystem! If you absolutely have to run fsck.minix on a mounted filesystem (i.e., the root filesystem), make sure nothing is writing to the disk, and that no files are "zombies" waiting for dele- tion. OPTIONS
-l List all filenames. -r Perform interactive repairs. -a Perform automatic repairs. (This option implies -r and serves to answer all of the questions asked with the default.) Note that this can be extremely dangerous in the case of extensive filesystem damage. -v Be verbose. -s Output super-block information. -m Activate MINIX-like "mode not cleared" warnings. -f Force a filesystem check even if the filesystem was marked as valid (this marking is done by the kernel when the filesystem is unmounted). SEE ALSO
fsck(8), fsck.ext2(8), mkfs(8), mkfs.minix(8), mkfs.ext2(8), reboot(8) DIAGNOSTICS
There are numerous diagnostic messages. The ones mentioned here are the most commonly seen in normal usage. If the device does not exist, fsck.minix will print "unable to read super block". If the device exists, but is not a MINIX filesystem, fsck.minix will print "bad magic number in super-block". EXIT CODES
The exit code returned by fsck.minix is the sum of the following: 0 No errors 3 Filesystem errors corrected, system should be rebooted if filesystem was mounted 4 Filesystem errors left uncorrected 7 Combination of exit codes 3 and 4 8 Operational error 16 Usage or syntax error In point of fact, only 0, 3, 4, 7, 8, and 16 can ever be returned. AUTHOR
Linus Torvalds (torvalds@cs.helsinki.fi) Error code values by Rik Faith (faith@cs.unc.edu) Added support for filesystem valid flag: Dr. Wettstein (greg%wind.uucp@plains.nodak.edu) Check to prevent fsck of mounted filesystem added by Daniel Quinlan (quinlan@yggdrasil.com) Minix v2 fs support by Andreas Schwab (schwab@issan.informatik.uni-dortmund.de), updated by Nicolai Langfeldt (janl@math.uio.no) Portability patch by Russell King (rmk@ecs.soton.ac.uk). AVAILABILITY
The fsck.minix command is part of the util-linux package and is available from ftp://ftp.kernel.org/pub/linux/utils/util-linux/. util-linux July 1996 FSCK(8)
All times are GMT -4. The time now is 04:11 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy