mount: fs type adfs not supported by kernel
 

Hi

I have 2 hds, hda and hdb. Hda was my windows drive and was one big partition. hdb had two windows partitions and linux on it. for reasons unknown, after reinstalling windows a few days ago, it killed grub. So i linux rescued my linux boot and now i can't boot back into windows. (see my other thread if you have ideas on that- need help BADLY!) Anways, since I've reinstalled windows, which booted and worked fine when i could boot into it, i can no longer mount that drive. I get this cracked out error:

mount /dev/hda1
mount: fs type adfs not supported by kernel

What the hell is an adfs file system and how to i make linux see it?

Can you boot into Linux at the moment ? - if so can you post /etc/fstab and fdisk

open a terminal - su to root user and type

cat /etc/fstab ; fdisk -l

(-l = small L)

post the results

I have two hd's (win98-hda RH9-hdb)...I use the following commands and it works...but first
step 1....mkdir /mnt/windows
setp 2...mount -t vfat /dev/hda1 /mnt/windows

I created a HD link for my RH9 desktop (right click desktop choose Create/Hard Disc) under the Execute tab type in step 2...when you double-click on the icon it automatically mounts the hda drv...then you can view your hda via the File Manager...makes it easy to move files this way...hope this helps.

Hi!

Ok so that's my FSTAB :

LABEL=/ / ext3 defaults 1 1
none /dev/pts devpts gid=5,mode=620 0 0
none /proc proc defaults 0 0
none /dev/shm tmpfs defaults 0 0
LABEL=/usr /usr ext3 defaults 1 2
/dev/hdb6 swap swap defaults 0 0
/dev/cdrom /mnt/cdrom udf,iso9660 noauto,owner,kudzu,ro 0 0
/dev/cdrom1 /mnt/cdrom1 udf,iso9660 noauto,owner,kudzu,ro 0 0
/dev/fd0 /mnt/floppy auto noauto,owner,kudzu 0 0
/dev/hda1 /mnt/win_c auto defaults
/dev/hdb1 /mnt/win_d auto defaults
/dev/hdb8 /mnt/win_e auto defaults
/dev/sda1 /mnt/flash auto noauto,owner,kudzu 0 0

and this is my fdisk:
Disk /dev/hda: 40.0 GB, 40027029504 bytes
255 heads, 63 sectors/track, 4866 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/hda1 * 1 4866 39086113+ c Win95 FAT32 (LBA)

Disk /dev/hdb: 80.0 GB, 80054059008 bytes
255 heads, 63 sectors/track, 9732 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/hdb1 * 1 1964 15775798+ c Win95 FAT32 (LBA)
/dev/hdb2 1965 9731 62388427+ f Win95 Ext'd (LBA)
/dev/hdb5 1965 2728 6136798+ 83 Linux
/dev/hdb6 2729 2791 506016 82 Linux swap
/dev/hdb7 2792 3824 8297541 83 Linux
/dev/hdb8 3825 9731 47447946 b Win95 FAT32

hope that helps!

Jim

So hey I tried that vfat mount and it worked! Although I still can't boot into that partition, at least I can get my files and such through linux! Now, why was it that when i used default mount it was picking it up as a adfs file system that it didn't like, and when you say vfat (virtaul fat) it liked it?

Jim

You don't as such boot into vfat partitions from Linux - the idea is simply to mount the vfat filesystem to an appropriate place in your Linux filesystem..that's why you create a mount point - I'm not sure about this "adfs" , but using the correct syntax to mount with helps.

for windows xp you can make a boot disk by copying these files on the root directory onto floppy
boot.ini
NTDETECT
ntlrd

if you have access to these files you can make a boot disk. Depending on your version of windows it might be a little different

Why don't you try installing lilo, it might work for you

Well, again, i wrekced my grub by reinstalling xp. Then i linux rescued my linux boot and wrecked my boot.ini (i guess) because i can't boot into xp. I know that the mount is just to view nad use the files, what i was saying was that i tried to tell grub it was vfat and it still didn't work!

Thanks agin!

Jim

Jim - are you using XP alongside Red Hat ? - if so, are you using NTFS or VFAT as your XP filesystems ?

ADFS = Apple Dos File System???

There is also an ADFS associated with some RISC system known as "FileCore". I know nothing about it.

If you get a message like that, it makes me think your partition table is chucked, farley. This wouldn't surprise me, given what you describe you have done.

I can take you through the repair procedure, but it is involved and dangerous. You should obtain and carefully review this document:

http://www.cs.mtsu.edu/~alex/operati.../multiboot.pdf

After you have done so, I need to know if you know your way around any hex editors, and if you have the guts to manually edit your partition table.

Basically, Windows overwrote the grub boot record in the Master Boot record with its own boot record (the "standard" boot record) which is why you lost the capability to boot linux. Your Linux rescue left you with a corrupted boot table and master partition table. You are still running, but you may be progressively corrupting your system and may be on your way to a real mess.

Please obtain all of the following tools:

1. A DOS boot floppy with fdisk on it.
2 MBR-Rescue, which you can get from here:
http://www.diydatarecovery.nl/~tkuurstra/mbrresc.htm

3. Linux Disk Editor - lde (you should already have this).
4. A Windows boot floppy that you have verified will boot your Windows system
5. A Linux boot floppy that you have verified will boot your Linux system.
6. PartEd, which you can get from here:
http://www.gnu.org/software/parted/
7. GPart, which you can obtain from here:
http://public.www.planetmirror.com/pub/gpart/

8. You didn't specify which version of Windows you are running, but if it is NT/2000/XP you should also get DiskProbe from here:
http://www.dynawell.com/support/ResK....asp#DiskTools

You may not need all these tools, but it is best to be prepared. You will also need a handful of floppies.

Don't attempt to use any high level tools on the hard drive (any formatting tools, for instance) until you have been able to do some low level work on it manually to make sure you are not totally f*cked.

You will not fix this problem with any automatic tools; you will have to get "down and dirty" with some manual tools to straighten it out.

It may take awhile, and if you make any critical mistakes along the way you will render your system unbootable. If you are willing to undertake it, I'll show you the way. It will lead to a long thread and will take awhile.

Just keep in mind that the damage to your system may very well be far more serious than it presently appears. You may have a situation where you have overlapping partitions as a result of what has happened; should this be the case you will find yourself low-level formatting and reinstalling everything after awhile, unless you do the manual repair.

I suspect this level of trouble with your system because of the reported presence of ADFS; this clearly states your partition table is hosed.

Well, I guess my first few questions are this:
1) how to i do a damage check and see how badly my system is/could be damaged?
2) If its an option, could i simply attempt to format the hda, reinstall xp and then go about fixing the bootloader to load linux?

I don't know about grub (I use lilo) but is your windows partition defined in you grub.conf file (or whatever it's called under grub)? Also you may need to change your fstab file to say "vfat" instead of "auto" under filesystem type for the windows partition.

Well, I guess my first few questions are this:
1) how to i do a damage check and see how badly my system is/could be damaged?

That is why I am asking you to pull these tools together. The first step will be to read out the master partition table, and to scan the disk looking for partitions, then compare the results. It could be as simple as changing the file system code in the partition table, or it could be much more complicated than that.

2) If its an option, could i simply attempt to format the hda, reinstall xp and then go about fixing the bootloader to load linux?

No. This will not work. You have XP? OK. NTFS file system?

I re-read your original post and I see that your windows is on one drive and linux is on another.

In this event, yes you could reformat hda and reinstall windows, and bypass all the potential nastiness that I was planning for you.