Sponsored Content
Operating Systems Linux Red Hat Linux bad superblock on /dev/mapper/VolGroup-lv_root Post 303005972 by MadeInGermany on Wednesday 25th of October 2017 10:34:15 AM
Old 10-25-2017
So it's the partion 2, in Linux accessable as /dev/sda2,
but under lvm control, so you should try to repair it from a resuce system with lvm.
Stop the boot process with a few key strokes, so you get a grub menu that offers a rescue system.

If there is none, you can try to edit the normal linux system, and add rd.break to the kernel parameters, then continue the boot. It then spawns a rescue shell.

In the rescue system or in the rescue shell you must try to access the disk
The lsblk command should list a tree.
You can try to mount a part of it, probably /dev/mapper/VolGroup-lv_root,
(create an empty directory for example with mkdir -p /mnt)
so the command is
Code:
mount /dev/mapper/VolGroup-lv_root /mnt

If the mount fails with "bad superblock", then run fsck on it.

Pardon if my knowledge is rather theoretical.
 

8 More Discussions You Might Find Interesting

1. Linux

I screwed up linux really bad...

Hey, I definately screwed up my libraries, but I am not sure how. I get this error: /bin/sh: relocation error: /usr/local/lib/libdl.so.2 symbol _rtld_global_ro, version GLIBC_PRIVATE not defined in file ld-linux.so.2 with link time reference when I try to even login. I cannot even get to a... (1 Reply)
Discussion started by: farhan00
1 Replies

2. UNIX for Dummies Questions & Answers

Warning: HTFS: bad dir inode 62730 on HTFS dev hd (1/42)

Hello all. I am receiving this message on the console of a SCO Openserver 5.0.7 server. The hardware is IBM, running mirrored SCSI drives with a hot-swap spare off of an IBM Serveraid controller. I suspect that some permutation of fsck can help me resolve whatever is causing the error, but I am... (0 Replies)
Discussion started by: DoublePanic
0 Replies

3. UNIX for Advanced & Expert Users

Bad magic number on /dev/md0

Hello All, (RHEL4) Few weeks ago I had posted a message in this forum about the problem I had when I replaced my two scsi disks and tried rebuild raid1 array. I somehow managed to up the system with working raid1 array. But the main problem persisted.. i.e when I reboot the system, mounting... (0 Replies)
Discussion started by: ravinandan
0 Replies

4. Solaris

What is /dev/tty /dev/null and /dev/console

Hi, Anyone can help My solaris 8 system has the following /dev/null , /dev/tty and /dev/console All permission are lrwxrwxrwx Can this be change to a non-world write ?? any impact ?? (12 Replies)
Discussion started by: civic2005
12 Replies

5. AIX

Can't mount showing 0506-342 The superblock on /dev/fslv00 is dirty

Dear All Last day in Aix 5.2 server by executing # df –g I found following: Filesystem GB blocks Free %Used Iused %Iused Mounted on . . /dev/fslv00 58.00 136.70 -135% 212103 1% /sprod After shutting down by following command # shutdown –h And when... (1 Reply)
Discussion started by: xa52000
1 Replies

6. UNIX for Advanced & Expert Users

Linux EXT3 superblock recovery

Is there a way to recover or rebuild the superblock of an ext3 filesystem with out loosing data? Thanks (5 Replies)
Discussion started by: lochraven
5 Replies

7. UNIX for Dummies Questions & Answers

What is /dev/mapper used for?

I see a folder named "mapper" in /dev. This folder "mapper" has some soft link to other folders. What is mapper folder used for? (2 Replies)
Discussion started by: rupeshkp728
2 Replies

8. Solaris

File System Error: BAD SUPERBLOCK AT BLOCK 16: NUMBER OF DIRECTORIES OUT OF RANGE

Hi All, we are having a file system error in one of our servers. The server failed to boot in usual user mode. Instead boot with single user mode and requesting to run a FSCK manually to repair the corrupted. see the below output. Netra T2000, No Keyboard Copyright 2008 Sun Microsystems,... (5 Replies)
Discussion started by: Buddhike G
5 Replies
RESCUE(8)						    BSD System Manager's Manual 						 RESCUE(8)

NAME
rescue -- rescue utilities in /rescue DESCRIPTION
The /rescue directory contains a collection of common utilities intended for use in recovering a badly damaged system. With the transition to a dynamically-linked root beginning with NetBSD 2.0, there is a real possibility that the standard tools in /bin and /sbin may become non- functional due to a failed upgrade or a disk error. The tools in /rescue are statically linked and should therefore be more resistant to damage. However, being statically linked, the tools in /rescue are also less functional than the standard utilities. In particular, they do not have full use of the locale, pam(3), and nsswitch libraries. If your system fails to boot, and it shows an error message similar to: init: not found try booting the system with the boot flag ``-a'' and supplying /rescue/init, which is the rescue init(8), as the init path. If your system fails to boot, and it shows a prompt similar to: Enter full pathname of shell or RETURN for /bin/sh: the first thing to try running is the standard shell, /bin/sh. If that fails, try running /rescue/sh, which is the rescue shell. To repair the system, the root partition must first be remounted read-write. This can be done with the following mount(8) command: /rescue/mount -uw / The next step is to double-check the contents of /bin, /lib, /libexec, and /sbin, possibly mounting a NetBSD installation CD-ROM and copying files from there. Once it is possible to successfully run /bin/sh, /bin/ls, and other standard utilities, try rebooting back into the stan- dard system. The /rescue tools are compiled using crunchgen(1), which makes them considerably more compact than the standard utilities. FILES
/rescue Root of the rescue hierarchy. SEE ALSO
crunchgen(1) HISTORY
The rescue utilities first appeared in NetBSD 2.0. AUTHORS
The rescue system was written by Luke Mewburn <lukem@NetBSD.org>. This manual page was written by Simon L. Nielsen <simon@FreeBSD.org>, based on text by Tim Kientzle <kientzle@FreeBSD.org>. BUGS
Most of the rescue tools work even in a fairly crippled system. The most egregious exception is the rescue version of vi(1), which currently requires that /usr be mounted so that it can access the termcap(5) files. Hopefully, a failsafe termcap(3) entry will eventually be added into the curses(3) library, so that /rescue/vi can be used even in a system where /usr cannot immediately be mounted. In the meantime, the rescue version of the ed(1) editor can be used from /rescue/ed if you need to edit files, but cannot mount /usr. BSD
January 20, 2009 BSD
All times are GMT -4. The time now is 02:00 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy