Mount: You Must Specify the filesystem type

[zmeuka]

Hello ...
The problem of such standing Fedora 12-i686, with all the latest updates, the next time (do not remember what he's updated), restarted the computer ...
after as soon as he began to load line (Grub boot norms) wrote many times that the Mount: You Must specify the filesystem type

from the LiveCD tried all said that there was no public Linux systems, tried a single mode w that crusty file system ...

tell me how best to restore the data from the HDD ...

Sorry for my English

[gid99]

Hi,

Have you ever dealt with using a linux rescue disk?
http://www.redhat.com/docs/manuals/l...escuemode.html
while the instructions in the URL above are for redhat, don't let that turn you away, it ought to be somewhat similar to Fedora.

Follow the instructions there, again, it may not be 100% verbatim

It seems from what I can make of your post, your grub line attempts to pass off control to your system to mount the drives in RW (read write), however, your fstab or drive may have an issue. Start with least invasive. Since you have a new install, the /etc/fstab is not likely, but may be good to rule out if there is any chance someone altered it. Otherwise, your drive may have some problem, especially if it is ext2 (ext2 is not a journal file system)
/etc/fstab
may have an issue (not likely unless someone tampered with it)
or worse
your drive may have superblock issues or some sort of drive corruption.

If the drive in question is corrupted and you happened to have used LVM instead of non-LVM, that incurs another round of complications.

ALTERNATIVELY - may be easier...
Boot from a live CD (one example, a live edition cd of fedora)
Download a live edition fedora disk, or a knoppix linux disk and boot your system live.

Then become root and attempt to find (use fdisk -l) and mount the drive that has your /etc/fstab

Then verify one by one your /etc/fstab entries (IMPORTANT - but do not mount to the locations your fstab states, make a directory like /testing/root for "/" mount, and make other directories as needed for each)

Narrow down through this process of checking entries in your /etc/fstab to find the drive that is not mounting properly. If you are lucky, it is a typo (you are probably not lucky since it is a new install). If you are not lucky, the drive or partition may have an issue. If you don't care about the data on that drive or partition, then reformat it. There could be a physical issue with the disk in the worse case.

After verifying your mounts - (since you did a clean installation, I suspect from your post), check with fsck against the drives.

Repost here - not sure if I'll be available with my odd schedule.
Good luck

By the way, you can translate the above (hopefully) by
http://www.google.com/language_tools?hl=en
and follow the instructions there for translation

[zmeuka]

Thx, for help...
LiveCD - "Not found the Linux filesystems".

But now i in new clean Fedora 12 (with all updates)...
fdisk -l

Диск /dev/sda: 750.2 ГБ, 750156374016 байт
255 heads, 63 sectors/track, 91201 cylinders
Units = цилиндры of 16065 * 512 = 8225280 bytes
Disk identifier: 0x2ecf75a4

Устр-во Загр     Начало       Конец       Блоки   Id  Система
/dev/sda1   *           1          26      204800   83  Linux
Раздел 1 не заканчивается на границе цилиндра.
/dev/sda2              26       91201   732367201   8e  Linux LVM 

Диск /dev/sdb: 1000.2 ГБ, 1000204886016 байт
255 heads, 63 sectors/track, 121601 cylinders
Units = цилиндры of 16065 * 512 = 8225280 bytes
Disk identifier: 0x592a8100

Устр-во Загр     Начало       Конец       Блоки   Id  Система
/dev/sdb1   *           1          26      204800   83  Linux
Раздел 1 не заканчивается на границе цилиндра.
/dev/sdb2              26      121601   976555201   8e  Linux LVM

Диск /dev/dm-0: 995.8 ГБ, 995761324032 байт
255 heads, 63 sectors/track, 121061 cylinders
Units = цилиндры of 16065 * 512 = 8225280 bytes
Disk identifier: 0x00000000

На диске /dev/dm-0 отсутствует верная таблица разделов

Диск /dev/dm-1: 4227 МБ, 4227858432 байт
255 heads, 63 sectors/track, 514 cylinders
Units = цилиндры of 16065 * 512 = 8225280 bytes
Disk identifier: 0x00000000

На диске /dev/dm-1 отсутствует верная таблица разделов

/dev/sda2 -- it's old Fedora 12

Now i try http://forums.fedoraforum.org/showthread.php?t=165808 (Howto mount a logical volume)

But so far without success

[gid99]

Thx, for help...
LiveCD - "Not found the Linux filesystems".

But now i in new clean Fedora 12 (with all updates)...
fdisk -l

Диск /dev/sda: 750.2 ГБ, 750156374016 байт
255 heads, 63 sectors/track, 91201 cylinders
Units = цилиндры of 16065 * 512 = 8225280 bytes
Disk identifier: 0x2ecf75a4

Устр-во Загр     Начало       Конец       Блоки   Id  Система
/dev/sda1   *           1          26      204800   83  Linux
Раздел 1 не заканчивается на границе цилиндра.
/dev/sda2              26       91201   732367201   8e  Linux LVM

Диск /dev/sdb: 1000.2 ГБ, 1000204886016 байт
255 heads, 63 sectors/track, 121601 cylinders
Units = цилиндры of 16065 * 512 = 8225280 bytes
Disk identifier: 0x592a8100

Устр-во Загр     Начало       Конец       Блоки   Id  Система
/dev/sdb1   *           1          26      204800   83  Linux
Раздел 1 не заканчивается на границе цилиндра.
/dev/sdb2              26      121601   976555201   8e  Linux LVM

Диск /dev/dm-0: 995.8 ГБ, 995761324032 байт
255 heads, 63 sectors/track, 121061 cylinders
Units = цилиндры of 16065 * 512 = 8225280 bytes
Disk identifier: 0x00000000

На диске /dev/dm-0 отсутствует верная таблица разделов

Диск /dev/dm-1: 4227 МБ, 4227858432 байт
255 heads, 63 sectors/track, 514 cylinders
Units = цилиндры of 16065 * 512 = 8225280 bytes
Disk identifier: 0x00000000

На диске /dev/dm-1 отсутствует верная таблица разделов

Now i try http://forums.fedoraforum.org/showthread.php?t=165808 (Howto mount a logical volume)

But so far without success

You may not be actually booting first from your physical CDROM device. You may need to change the BOOT ORDER in your BIOS so your CDROM is first in the boot order, not your hard drive.

Go to your BIOS and see if you can switch the BOOT ORDER - so your CDROM boots first!!

Also, some BIOS will allow a "boot menu" at BIOS LOAD -- so you can select "boot from cd" AT BIOS.

Good luck

---------- Post added at 09:49 AM CDT ---------- Previous post was at 09:44 AM CDT ----------

The dates in your fdisk output show the year 1926

1) how old is your computer?
2) Is the BIOS battery exhausted

NOTE - this is a side or separate issue to your original problem you posted.

But you may want to consider checking the BIOS battery on your computer.
The battery looks like a coin on your motherboard.

So if you change your BIOS settings so your CDROM is first, it may not sustain a reboot, depending on your system.

---------- Post added at 09:51 AM CDT ---------- Previous post was at 09:49 AM CDT ----------

http://translate.google.com/translat...u&hl=&ie=UTF-8

[COLOR="Silver"]

---------- Post added at 09:55 AM CDT ---------- Previous post was at 09:54 AM CDT ----------

I do not read my private messages, please post here instead in case I'm not available (most likely) and so others (the Fedora Community) can answer or see the progress of this problem.

Thanks and good luck

[zmeuka]

I buy my computer in this year,

Since BIOS is also normal all
With batteries too good ... and time shows in 2010 inyun
Now I'm on a new hard drive installed a new Fedora 12

Characteristics of the computer:
CPU : Intel Core2Duo E7300
VIDEO: NVIDIA 8600GT
RAM: 2GB
MOTHERBoard: ASUS P5B
HDD 1 TB

---------- Post added at 10:04 AM CDT ---------- Previous post was at 09:58 AM CDT ----------

i know how boot from CD,
But I have already tried to boot, and restores the system, but the disc does not poluchaetsya .. because he does not want to define this section as a Linux system,
When you try to boot into the system, he wrote that is not a valid file system and all this

---------- Post added at 10:10 AM CDT ---------- Previous post was at 10:04 AM CDT ----------

I need to restore data from the old system, but I can not connect either the volume or boot ... I just need to copy data from the HDD,
Help me please (((

[gid99]

I buy my computer in this year,

Since BIOS is also normal all
With batteries too good ... and time shows in 2010 inyun
Now I'm on a new hard drive installed a new Fedora 12

Characteristics of the computer:
CPU : Intel Core2Duo E7300
VIDEO: NVIDIA 8600GT
RAM: 2GB
MOTHERBoard: ASUS P5B
HDD 1 TB

---------- Post added at 10:04 AM CDT ---------- Previous post was at 09:58 AM CDT ----------

i know how boot from CD,
But I have already tried to boot, and restores the system, but the disc does not poluchaetsya .. because he does not want to define this section as a Linux system,
When you try to boot into the system, he wrote that is not a valid file system and all this

---------- Post added at 10:10 AM CDT ---------- Previous post was at 10:04 AM CDT ----------

I need to restore data from the old system, but I can not connect either the volume or boot ... I just need to copy data from the HDD,
Help me please (((

Great - you can boot from the cd

1) Have you attempted to mount each of the devices from the output of "fdisk -l" to an empty folder, to rule out and find which device is bad? Or specifically, which device complains of "must specify the filesystem type"?
-- If so - please post which device /dev/THEBADpartition

1a) Do you know what specific linux format your disk is in? ext2, ext3, riserfs (not likely riserfs), ext4 perhaps?
2) Does the disk use LVM?
3) Is the disk part of a RAID configuration?

Perhaps fsck would be good on the disk
fsck /dev/corruptedpartition
(the above is just an example, it will require a real device location), and will require a live cd that you have access to fsck

Good luck, and I welcome others to post here with suggestions - it seems the poor gentleman who started this may have a corrupted disk or partition.

[zmeuka]

1) /dev/sda2 --- LVM2
1a) EXT3
2) Yes
3) No

I tried FSCK, but wrote error ((

[gid99]

1) /dev/sda2 --- LVM2
1a) EXT3
2) Yes
3) No

I tried FSCK, but wrote error ((

Zmueka,

You may be experiencing issues with corruption on either LVM (in your case, LVM2), or the ext3 file system itself, or if you are really not lucky, both. You may be experiencing physical drive issues as well.

What error did you receive with fsck?

---------- Post added at 12:38 PM CDT ---------- Previous post was at 12:12 PM CDT ----------

I see from your fdisk output previously, that your /dev/sda drive is probably 750 GB (provided google translate website translated properly, I suspect it did).

It seems that formatted, your /dev/sda is roughly 726GB

anyway,

Find the intended mount point of the logical volume.

Also, please post the result of
fsck
and
e2fsck
In general, fsck or e2fsck should be done without the drive mounted (umount the drive first), I don't think your drive is mounted... if it is, unmount it.


Carefully read the following

http://forums.fedoraforum.org/showthread.php?t=208303
http://fedoraforum.org/forum/showthread.php?t=184210 (for fedora 8 and 9, but read anyway)
http://anthonydawson.thelasis.com/LVRecovery/index.htm
http://www.kernelhardware.org/how-sh...x-file-system/


Good luck

---------- Post added at 12:39 PM CDT ---------- Previous post was at 12:38 PM CDT ----------

updated - see above

---------- Post added at 12:57 PM CDT ---------- Previous post was at 12:39 PM CDT ----------

http://forums.fedoraforum.org/showthread.php?t=246851

---------- Post added at 12:57 PM CDT ---------- Previous post was at 12:57 PM CDT ----------

and see my other recent replies too

[stoat]

Okay. You have two Fedora systems. One works. One is busted. They both use Logical Volume Management. You want files from the busted one.

Hello zmeuka,

I have no idea what is wrong with the busted system. But I recommend that you try again to do the traditional steps to mount its root logical volume.

su
vgchange -a y
vgs
lvs

Use that information to figure out which logical volume you're interested in and try to mount it...

su
mkdir /mnt/temp
mount /dev/vg-name-here/lv-name-here /mnt/temp

Next, open your file manager and look at /mnt/temp. If something didn't work, then take a moment to copy the output of all that stuff from your terminal to here.

P.S.:

The dates in your fdisk output show the year 1926

Where does it say that? Just curious.

[zmeuka]

To: stoat
I tried

vgchange -a y
vgs
lvs

vgs:

  WARNING: Duplicate VG name VolGroup: Existing eaqSjZ-bIMf-1XAO-g0t4-xzGn-y0mP-VkW5WU (created here) takes precedence over hu00Rz-lT3o-h4LT-5bha-FIxl-NyjM-poUSZP
  WARNING: Duplicate VG name VolGroup: Existing eaqSjZ-bIMf-1XAO-g0t4-xzGn-y0mP-VkW5WU (created here) takes precedence over hu00Rz-lT3o-h4LT-5bha-FIxl-NyjM-poUSZP
  WARNING: Duplicate VG name VolGroup: Existing hu00Rz-lT3o-h4LT-5bha-FIxl-NyjM-poUSZP (created here) takes precedence over eaqSjZ-bIMf-1XAO-g0t4-xzGn-y0mP-VkW5WU
  WARNING: Duplicate VG name VolGroup: Existing eaqSjZ-bIMf-1XAO-g0t4-xzGn-y0mP-VkW5WU (created here) takes precedence over hu00Rz-lT3o-h4LT-5bha-FIxl-NyjM-poUSZP
  VG       #PV #LV #SN Attr   VSize   VFree
  VolGroup   1   2   0 wz--n- 698,44G    0 
  VolGroup   1   2   0 wz--n- 931,31G    0

LVS:

 
WARNING: Duplicate VG name VolGroup: Existing eaqSjZ-bIMf-1XAO-g0t4-xzGn-y0mP-VkW5WU (created here) takes precedence over hu00Rz-lT3o-h4LT-5bha-FIxl-NyjM-poUSZP
  WARNING: Duplicate VG name VolGroup: Existing hu00Rz-lT3o-h4LT-5bha-FIxl-NyjM-poUSZP (created here) takes precedence over eaqSjZ-bIMf-1XAO-g0t4-xzGn-y0mP-VkW5WU
  WARNING: Duplicate VG name VolGroup: Existing eaqSjZ-bIMf-1XAO-g0t4-xzGn-y0mP-VkW5WU (created here) takes precedence over hu00Rz-lT3o-h4LT-5bha-FIxl-NyjM-poUSZP
  LV      VG       Attr   LSize   Origin Snap%  Move Log Copy%  Convert
  lv_root VolGroup -wi-ao 694,50G                                      
  lv_swap VolGroup -wi-ao   3,94G

(((

[gid99]

Okay. You have two Fedora systems. One works. One is busted. They both use Logical Volume Management. You want files from the busted one.

Hello zmeuka,

I have no idea what is wrong with the busted system. But I recommend that you try again to do the traditional steps to mount its root logical volume.

su
vgchange -a y
vgs
lvs

Use that information to figure out which logical volume you're interested in and try to mount it...

su
mkdir /mnt/temp
mount /dev/vg-name-here/lv-name-here /mnt/temp

Next, open your file manager and look at /mnt/temp. If something didn't work, then take a moment to copy the output of all that stuff from your terminal to here.

P.S.:Where does it say that? Just curious.

I took his Russian output of 'fsck -l' and translated it via google translation, and there the 1926 came apparent. I did mention someplace (I think) that if google translate did it's job in reference to the Russian text.

He replied later that the machine was a year old, so I'm leaning against his bios battery being bad. It could be a google-translation anomoly with the 1926 bit.

---------- Post added at 10:58 PM CDT ---------- Previous post was at 10:55 PM CDT ----------

Stoat - thanks for assisting zmeuka, I don't deal with LVM a lot - I kinda loathe LVM and prefer straight ext3 or ext4, I like to avoid the metadata of LVM, even if recommended by redhat or by extensive use. Of course mounting the lvm as you mentioned is proper.

[stoat]

If you rename the old volume group, then you might be able to mount its root logical volume. No promises.

su
vgdisplay

If that shows both volume groups, and if both of them have that "VolGroup" name, then copy the UUID of the busted one (it should be the smaller sized one according to you). Paste the UUID into this...

su
vgrename UUID-GOES-HERE VolGroupOld

Try to activate and mount again.

su
vgchange -a y
mkdir /mnt/temp
mount /dev/VolGroupOld/lv_root /mnt/temp

Try to get files from /mnt/temp.

[stoat]

I'm leaning against his bios battery being bad. It could be a google-translation anomoly with the 1926 bit.

Yeah, I think so. I tried what you did with that Google translator thingy. It translated this...

Устр-во   Загр     Начало       Конец       Блоки   Id  Система
/dev/sda1   *           1          26      204800   83  Linux
Раздел 1 не заканчивается на границе цилиндра.
/dev/sda2              26       91201   732367201   8e  Linux LVM

To this...

Devices   Boot      Start         End       Blocks  Id  System
/ Dev/sda1  *     January        1926       204800  83  Linux
Section 1 does not end at the boundary of the cylinder.
/ Dev/sda2             26       91201    732367201  8e  Linux LVM

It mistakenly interpreted the starting and ending cylinders of /dev/sda1 (1 and 26 respectively) as a date. There is no date in the output of fdisk -l. The CMOS battery idea was a red herring this time.

[zmeuka]

Thanks all for the help All works well