can mount C not D FAT: invalid media value (0x45) mount: wrong fs type, bad option
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: Mandriva mostly, vector 5.1, tried many.Suse gone from HD because bad Novell/Zinblows agreement
Posts: 1,606
Rep:
can mount C not D FAT: invalid media value (0x45) mount: wrong fs type, bad option
Hi,
Can mount win C drive but not D. Always using linux so never tried before.
Got the feeling it is bad partitioning / boundary or not LBA on 2d partition...
Any idea? cannot reformat evthg. Unusual error because googled for
FAT: invalid media value (0x45) found only 1 hit
#dmesg
VFS: Can't find a valid FAT filesystem on dev hdb5.
FAT: invalid media value (0x45)
# mount -t vfat -r /dev/hdb5 /mnt/win_D_drive
mount: wrong fs type, bad option, bad superblock on /dev/hdb5,
or too many mounted file system
# mount -t vfat -r /dev/hdb2 /mnt/win_D_drive
mount: wrong fs type, bad option, bad superblock on /dev/hdb2,
or too many mounted file systems
(aren't you trying to mount an extended partition
# mount
/dev/hdb1 on /mnt/windows type vfat (rw,nosuid,umask=0,user=blabla)
# fdisk -l
Disk /dev/hdb: 27.3 GB, 27329101824 bytes
255 heads, 63 sectors/track, 3322 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/hdb1 * 1 1274 10233373+ c W95 FAT32 (LBA)
/dev/hdb2 1275 3322 16450560 5 Extended
/dev/hdb5 1275 2421 9213246 b W95 FAT32
/dev/hdb6 2422 2547 1012063+ 83 Linux
/dev/hdb7 2548 2610 506016 82 Linux swap
/dev/hdb8 2611 3025 3333456 83 Linux
/dev/hdb9 3026 3322 2385621 83 Linux
Try using the defaults setting in fstab, I got that problem a LOT trying to mount my partitions, and almost every time I got that error, it was something I did wrong in fstab.
Distribution: Mandriva mostly, vector 5.1, tried many.Suse gone from HD because bad Novell/Zinblows agreement
Posts: 1,606
Original Poster
Rep:
Ta for the idea. It does not work though
I tried this before posting, but for the sake of completness here it is
#umount /mnt/windows (this is C, works ok, it umount C which was properly mounted)
#mount
does not list either C or D now
# kedit /etc/fstab &
comment out /dev/hdb1 /mnt/windows vfat umask=0,user,dev,exec 0 0
enable line /dev/hdb5 /mnt/win_D_drive vfat umask=0,user,dev,exec 0 0
save file
#mount -a
mount: wrong fs type, bad option, bad superblock on /dev/hdb5,
or too many mounted file system
#dmesg
VFS: Can't find a valid FAT filesystem on dev hdb5.
FAT: invalid media value (0x45)
# ls -l /mnt
drwxr-xr-x 2 root root 4096 Feb 10 2005 windows/
I have set win_D_drive as well as drwxr-xr-x 2 root root
Last edited by Emmanuel_uk; 11-18-2005 at 04:33 PM.
Distribution: Mandriva mostly, vector 5.1, tried many.Suse gone from HD because bad Novell/Zinblows agreement
Posts: 1,606
Original Poster
Rep:
bosewicht, you sound quite clued up from some of your posts I came across, any idea if I have a problem with hda5 not showing LBA?
Or the paritition being at the edge of a cluster (or sthg like that).
Or it is a M$ badly id'ed partition? The partition works ok under Zin98
I cannot remember for sure, but I think I created the partitions from scratch using mandrake 10.1, then I installed win98SE,
then put back grub. Maybe not.I put win 98SE first with 50% of the HD, with C and D created at the time, then I added mandy and grub and created the non fat partitions.
Cannot remember, 2d way more likely.
Anyway it is a PIII, and not my PC, so I never mount windows drive on it, but now that I had time to try it seems to be difficult
0b WIN95 OSR2 FAT32 Partitions up to 2047GB
0c WIN95 OSR2 FAT32, LBA-mapped Extended-INT13 equivalent of 0b.
What does WIN 98 show for the size of the d: drive. It appears that the partition is approx 9GB (if I did my math correctly) but the max filesystem size for type 0b is 2GB. There isn't any reason AFAIK that linux should not be able to mount a 0b filesystem using vfat. linux could be to smart or windows does not realize that something is wrong.
What happens when you check the d: drive for errors in windows?
Distribution: Mandriva mostly, vector 5.1, tried many.Suse gone from HD because bad Novell/Zinblows agreement
Posts: 1,606
Original Poster
Rep:
strace outputs
thanks for the suggestions
C is 10 465 607 680 bytes 9.77 GB
D is 9 425 141 670 bytes 8.77 GB according to Zindoze
did a dd of the 44, 512 and 1024 first bytes of hdb2 and 5 with linux (curiosity)
Copied fdisk -l to a file
Then went to windows, ran scandisk for D because that is all we have
It told me D "boot area damaged or invalid. This can make win to report
the free space incorrectly.
Asked Zin to fix it. It did. Log says "drive contained an error in its FSInfoSector"
error was corrected as specified above.
Did another scan: nor error this time.
Came back to Mandy, fdisk output unchanged
diff on dd obtained files no difference (but I need to do an hexa diff really, don't I?)
Still same error as before.
I straced the calls, I find this odd that they both use 0xc0ed0000, although
I do not know what this is for...
mount("/dev/hdb5", "/mnt/win_D_drive", "vfat", 0xc0ed0000, 0) = -1 EINVAL (Invalid argument)
mount("/dev/hdb1", "/mnt/windows/", "vfat", 0xc0ed0000, 0) = 0
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.