Skip navigation.
Home
Now Shipping Version 7.0

udev-problem ? in 3.4-3.RC1

Ko Bros's picture

Posts: 690

Mepis 3.4-3.RC1:

CDROM (/dev/hdc) and DVDRW (/dev/hdd) and floppy drive (/dev/fd0) are recognized, but they cannot be mounted using Kdiskfree. In fact they do not show up at all there.
A quick check learned that the entries are missing in /etc/fstab. The old trick to manually edit /etc/fstab doesn't work anymore (the drives will show up in kdiskfree, but still cannot be mounted). Only partitions on hda and sda (usb-stick) can be mounted.

Does anyone know the 'new' (after udev got in) trick to solve this......Smiling ?

Another observation [that may or may not be related]: there are NO device-icons at all (like hd-partitions, cdrom, dvdrw, floppydrive or usb-stick) on my desktop - NO MATTER how I change KDE-CC Desktop Behavior FileIcons settings.

Regards, Ko

Not Ready for prime time

I somehow appear to have avoided the ext3 problems others are experiencing, but I can see the apparent udev issues. Nothing mounted or mountable except the harddrive partitions (no floppy or CD). No desktop Icons. Problems with parallel port printing but no problems printing to network devices.

In addition to the udev

In addition to the udev issues I also get a FATAL error message on boot that complains of being unable to find the EXT3 module. It then mounts and boots 2 ext3 partitions.

Ko Bros's picture

Re: In addition to the udev

rshol wrote:
In addition to the udev issues I also get a FATAL error message on boot that complains of being unable to find the EXT3 module. It then mounts and boots 2 ext3 partitions.

I got that FATAL error message too, early on boot, about not being able to find/load (?) the Reiser module (I use reiserFS for all debian-based distros), but all my hd-partitions showed up.

Regards, Ko

kerry's picture

hmmm

When you add a entry in fstab, you also have to create the folder for it in /mnt, just right click a blank area and create new folder, then name it the same as the device cdrom, cdrom1,floppy,etc.....

Thanks Kerry

I should have known. All problems now solved, for me at least, with CD's and Floppy.

Add the following to /etc/fstab

/dev/cdrom /mnt/cdrom udf,iso9660 noauto,users,dev,ro 0 0
/dev/fd /mnt/fd vfat,ext2,hfsplus noauto,users,dev 0 0

Then:

mkdir /mnt/cdrom
mkdir /mnt/fd

Those lines were included in the fstab created by 3.4-2rc1 but not by the current release.

Now, if I can cure my problems with printing to a parallel printer, I'm good to go.

Darn, spoke too soon again.

Darn, spoke too soon again. The above works beautifully for the cdrom, but fd is apparently not a block device that the system can mount (/dev/fd is actually a folder). Any hints? Thanks.

kerry's picture

even easier

change /media to /media~, then create a new folder /media(so it's empty), no fstab or /mnt modifications needed. For the floppy i'm still working on that one, mine's not even being detected. Apparently floppys are mounted under /proc, i've tried following it but am having no luck in getting it to work.

Ko Bros's picture

3.4-3.RC1 = DISASTER (for me)

All this mucking around with missing devices finally resulted in my system failing to boot from hda (my only harddisk). "Non-system disk or disk error". Installing grub from LiveCD 3.4-3.RC1 made it worse as hda seemed to be completely gone the next time I booted from the LiveCD... (I only had my usb-stick left,,,,,,)
The LiveCD from 3.4-2.RC1 could not solve this either either, although it was stated that grub was successfully instaled in the MBR.

Wrong. The disk remained unbootable.

I tried another LiveCD and its Gparted showed that all my partitions were still existing. But I cannot get the disk to boot !!

How can I (from the LiveCD commandline) install grub into the MBR of my hda-disk ??

note: I am posting this from a livecd.

Regards, KO

Ko Bros

Ko Bros's picture

Re: 3.4-3.RC1 = DISASTER (for me)

Ko Bros wrote:
All this mucking around with missing devices finally resulted in my system failing to boot from hda (my only harddisk). "Non-system disk or disk error". Installing grub from LiveCD 3.4-3.RC1 made it worse as hda seemed to be completely gone the next time I booted from the LiveCD... (I only had my usb-stick left,,,,,,)
The LiveCD from 3.4-2.RC1 could not solve this either either, although it was stated that grub was successfully instaled in the MBR.

Wrong. The disk remained unbootable.

I tried another LiveCD and its Gparted showed that all my partitions were still existing. But I cannot get the disk to boot !!

How can I (from the LiveCD commandline) install grub into the MBR of my hda-disk ??

note: I am posting this from a livecd.

Regards, KO

Ko Bros

Grub was not properly installed into MBR by Mepis. The Mepis LiveCD's could not fix this either as they did not see /dev/hda. There I was with an [seemingly] unbootable 120 GB harddisk It's been solved by using another livecd (not mepis) to write grub into mbr.

I have re-installed Mepis 3.4-2.RC1 and thrown out 3.4-3.RC1 (although I liked its speed, I consider it more of a beta than a RC. I will wait to see what this new 3.4-3.RC2 brings.

Regards, Ko

udev cdrom hal

After installing Mepis 3.4-3 many people experience loss of cdrom access. I solved my problem by installing the program "hal" using synaptic. After doing this, when you insert a cd, a dialog box will pop up. From this box you must choose to "open in new folder". Also check the check box to do this each time you insert a disk. You must then make an entry in the static section of fstab something like this.

/dev/hdc /media/hdc auto noauto,users,dev,ro 0 0

fstab is a file in the folder etc/ which can be opened with kwrite. The static section is anywhere above the line:

# Dynamic entries below, identified by 'users' option

Do this for each cd and you will be able to use KDiskFree to unmount or mount. This is important to make the disk removable.

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.