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.
Distribution: Debian /Jessie/Stretch/Sid, Linux Mint DE
Posts: 5,195
Rep:
as root run: mkdir /mnt/hda2
and retry the mount.
If you get an error complaining that the superblock is invalid, make sure the disk is formatted ext3.
You can also try to mount without the -t ext3 and let mount discover the file system.
If you are sure there is no file system and you have no data on the partition you could create ext3: WARNING THIS DESTROYS YOUR DATA mkfs -t ext3 /dev/hda2
This was created when my system failed due to bad battery in my UPS and power failure. I SCP data from old drive to new drive in rescue mode but my new OS was RedHat and only had a 40 GB hda drive. Since then I have installed a new 1 TB sda with CentOS. I would like to access the hda2 which has the data on ext3 file system but when try to mount I get the error.
mount -t ext3 /dev/hda2 /mnt/old
mount: wrong fs type, bad option, bad superblock on /dev/hda2,
missing codepage or other error
In some cases useful info is found in syslog - try
dmesg | tail or so
-------------
fdisk -l
Disk /dev/hda: 40.0 GB, 40020664320 bytes
255 heads, 63 sectors/track, 4865 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/hda1 * 1 13 104391 83 Linux
/dev/hda2 14 4865 38973690 8e Linux LVM
Disk /dev/sda: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/sda1 * 1 13 104391 83 Linux
/dev/sda2 14 121601 976655610 8e Linux LVM
Distribution: Debian /Jessie/Stretch/Sid, Linux Mint DE
Posts: 5,195
Rep:
Quote:
Originally Posted by mikebigado
Device Boot Start End Blocks Id System
/dev/hda1 * 1 13 104391 83 Linux /dev/hda2 14 4865 38973690 8e Linux LVM
This says that /dev/hda2 is a LVM. If this is true, there is no chance that you can mount it as ext3. Unfortunately I have no experience with LVM, can't help you any further here.
This was created when my system failed due to bad battery in my UPS and power failure. I SCP data from old drive to new drive in rescue mode but my new OS was RedHat and only had a 40 GB hda drive. Since then I have installed a new 1 TB sda with CentOS. I would like to access the hda2 which has the data on ext3 file system but when try to mount I get the error.
mount -t ext3 /dev/hda2 /mnt/old
mount: wrong fs type, bad option, bad superblock on /dev/hda2,
missing codepage or other error
In some cases useful info is found in syslog - try
dmesg | tail or so
-------------
fdisk -l
Disk /dev/hda: 40.0 GB, 40020664320 bytes
255 heads, 63 sectors/track, 4865 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/hda1 * 1 13 104391 83 Linux
/dev/hda2 14 4865 38973690 8e Linux LVM
Disk /dev/sda: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/sda1 * 1 13 104391 83 Linux
/dev/sda2 14 121601 976655610 8e Linux LVM
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.