I never had this problem before: after pluging a USB device, I get error in Konqueror: mount: wrong fs type, bad option, bad superblock... try dmesg | tail or...

So I tried dmesg | tail and the related output was:

Post your /etc/fstab file, please.

Well, I never had a /dev/sda entry in /etc/fstab and everithing worked fine...

so there is no entry in /etc/fstab? if not, then it seems the automounting program (udev or hal, i forget which) is giving an option that it shouldn't be...very odd. might be a bug...

I'd create an /etc/fstab entry it might help fix your problem. I had permission problems with disks attached by USB, etc, and so I created an fstab entry to get around it.

Thanks everyone, I solved it by creating a /etc/fstab entry. Still, I consider to be a workaround. I guess that's called "Living with Cooker"

It's most likely something to do with udev/hal or whatever is mounting it, I'm not sure exactly. Otherwise you're looking at editing udev rules, or something with hal. And for me, it's easier just creating the fstab entry

In which case, I'll move this to the Cooker forum. Please let us know what you're using next time.

Hey folks, can you tell me what the proper FSTAB entry for SDA would be?

I have a 2006 install upgraded to 2007 that I then accidentally got some Cooker stuff in, then upgraded to 2007.1, and I have this problem. I gather that the problem is solved by moving from the 2.6.17.13 to 2.6.17.14 kernel (I have 2.6.17.13-mm-desktop-3mdv), but this has been a really rocky upgrade and I've just now got most of the problems solved and would like to not introduce any new quirks, if possible, or again accidentally wind up on the Cooker track.
http://archives.mandrivalinux.com/cooker/2...02/msg02858.php

The proper entry is none.
If you cannot mount your external harddidk by any other means, then something is broken @ your system.
Are you sure you have HAL daemon running?

Well I know something is broken. But HAL seems to be running:

Seems to be running:

Well, I finally figured out how to fix the USB mounting problem from a post over at the Mandriva Club Forum.
Mount of USB removable devices keeps failing in 2007.1

Apparently at least some of us folks who upgraded from 2007 (or 2006 in my case, with some elements of 2007) didn't get the latest kernel patch that was necessary to properly mount removable media and need to upgrade their kernel. Here is the command:



After a reboot I saw some verbiage saying the kernel didn't know which of two Nvidia packages to use and dumped me in to a 'init 3' command prompt. Joy. I edited my xorg.conf to use nv instead of nvidia and was able to install the proper Nvidia packages after a bit of fumbling around. The 'drakx11' command from a root terminal sorted things out, after the Software Management applet of MCC (rpmdrake, I believe it is called) left me at runlevel 3 after rebooting.

This is the third major hassle I've had upgrading from 2006 to 2007.1. Most of the reviews of 2007.1 have been positive, but they have generally been clean installs. I enjoy Mandriva when it is working properly, but the free product is only supported for about a year and a half and the upgrade process is just too bumpy. I really like Mandriva and want it to survive, but I'd have a hard time recommending it over Debian or Ubuntu just because upgrading is so problematic (not that upgrades of those distros are always painless, either). I may give CentOS 5 a try; it is supposed to be supported until 2014 (by which time I'll be well sick of it and ready for a fresh install).

I am using cooker right now and when the nvidia driver install fails mandriva nowautomatically switches to nv. Kernel never used to be updated but since 2007.0 there are these kernel-latest packages (which now also automatically install the source package) which make upgrading a lot easier.

btw: installed upgraded my system like this 10.2rc2->2006->cooker->2007.0->cooker-2007.1->cooker, i know just a little bit about linux, an avarage user and the upgrade had been pretty smooth, all in all, well I did have some X problems like your but not so anymore recently, since it switches to nv....

2006 to 2007 Spring is a three-release upgrade, which is always dicey. So much infrastructure changes in a Linux distro over a year and a half (the period in question) that it's very hard to ensure a clean upgrade. One-release upgrades (2006 -> 2007, 2007 -> 2007 Spring) tend to work better. I've heard a lot of successful reports of 2007 to 2007 Spring upgrades (though they do run into the kernel-not-updated problem, which is a shame, and should be fixed in future).

In general I'd advise only doing one-release upgrades. In fact, for a regular system, I'd probably advise storing /home on a separate partition and doing a fresh install while preserving /home, rather than an update install. That has the highest success rate.