Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Device Boot Start End Blocks Id System
/dev/sda1 * 1 64 512000 83 Linux
Partition 1 does not end on cylinder boundary.
/dev/sda2 64 243202 1953001472 8e Linux LVM
Disk /dev/sdc: 320.1 GB, 320072933376 bytes------->This is the HD from i take to copy some data
255 heads, 63 sectors/track, 38913 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000080
Device Boot Start End Blocks Id System
/dev/sdc1 * 1 13 104391 83 Linux
/dev/sdc2 14 38913 312464250 8e Linux LVM
[root@localhost ~]# mount -t ext3 /dev/mapper/VolGroup00-LogVol01 /home/Tiger
mount: wrong fs type, bad option, bad superblock on /dev/mapper/VolGroup00-LogVol01,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so
Checking with fsck, giving the following error..
[root@localhost ~]# fsck /dev/mapper/VolGroup00-LogVol01
fsck from util-linux-ng 2.17.2
fsck: fsck.swap: not found
fsck: Error 2 while executing fsck.swap for /dev/mapper/VolGroup00-LogVol01
can any trace out how to resolve this issue to make life easier.
Its have very critical data and need to copy some config file from here.
Thanks In Advance
Last edited by boby.kumar; 10-25-2013 at 07:45 AM.
[root@localhost ~]# mount -t ext3 /dev/mapper/VolGroup00-LogVol01 /home/Tiger
mount: wrong fs type, bad option, bad superblock on /dev/mapper/VolGroup00-LogVol01,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so
Checking with fsck, giving the following error..
[root@localhost ~]# fsck /dev/mapper/VolGroup00-LogVol01
fsck from util-linux-ng 2.17.2 fsck: fsck.swap: not found
fsck: Error 2 while executing fsck.swap for /dev/mapper/VolGroup00-LogVol01
have a look at the parts I've highlighted. You are trying to mount a swap partition which is not ext3 formated.
You have 2 partitons assigned to swap space, /dev/mapper/VolGroup-lv_swap and /dev/mapper/VolGroup00-LogVol01.
Maybe that wasn't what you expected?
2TB of swap should definitely be enough for most applications
If your running system also uses LVM and if the volume groups have the same name, you'd probably find it easier to mount the recovery disk from a live linux CD. I use fedora 19 live CD for this, just boo the live cd, enter a root terminal, issue "vgchange -a y" to activate your lvm on the recovery disk, and then mount the desired lvm volume group.
I usually just copy off what I need to an external usb disk temporarily, then disconnect the recovery disk, reboot to the normal system, hook up the external usb disk and copy what you need.
Once I attempted to activate two volume groups with the same name (trying to recover some fedora system data), but that didn't go well at all. lvm got "confused" when both vg's had a name conflict.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.