MandrivaThis Forum is for the discussion of Mandriva (Mandrake) Linux.
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.
I reinstalled my system again, and this time decided to install 10.1 instead of 10.0. All went well, except for one problem. My USB Hard Drive is having problems. In 10.0 I could just turn it on when I wanted to use it and a nice icon popped up on my desktop and when I was done I could just turn it off and the icon would be removed. I use this drive to transfer large amounts of data between different systems and for some backup stuff.
On 10.1 however, the system doesn't seem to recognize it at all (no /dev entry or /mnt entry) unless I turn the drive on right after (within a couple of seconds) of getting to my desktop for the first time (after a reboot). If I reboot and turn the drive on, sometimes I will have an icon waiting on my desktop, and it will disappear if I turn the drive off, and if I turn it back on fairly quickly it will re-spawn, but if I wait very long it will not do anything all all, and I can't find any entries for it under /dev or /mnt in this case (when it is working correctly I can find an entry under /dev/removeable). One time when I tried the reboot trick, though, my computer froze up at the "USB filesystems" prompt and after about 10 minutes of hanging I restarted the system and turned off the drive and it started up without any problems (not even a question about checking the files systems since they were uncleanly unmounted) . Is this a known issue with 10.1? I can't seem to find any other people talking about this particular problem anywhere.
I'm not sure if this is a known issue, but did you see any errors in /var/log/messages or /var/log/boot.log?
Also, are the "hotplug", "harddrake" and "haldaemon" services running at boot time? (MCC->System->Services)? I'm not really sure if they're absolutely required, but it might be worth a shot....(I THINK HAL exists on 10.1, I don't remember).
Wow, maybe it is something with my install. I had a tough time getting the MCC to start (it was bringing up the splash screen, and I could see it trying to start in the taskbar, and then the taskbar isonb would go away but the splash screen was still hanging around. I had to reboot just to get MCC to properly start, and in doing so they system was hanging just trying to stop alsa, so I had to do a hard reset. Then I got into MCC and saw hotplug was not set to start "on boot" and was not running, so I clicked "on boot" and then pressed the button to start the service, and the mouse cursor got stuck, but the system was still running, I just couldn't move the mouse cursor. I think I'm going to go back to 10.0 and see if things work alright. 10.0 was ok, I just figured I'd check out the changes since 10.1 came out, and for some reason it is not going well for me. Thanks for the help.
Wow that is weird, I had problems with 10.1 but nothing that dramatic. You did a full partition overwrite when installing 10.1 over 10.0? If so I don't know what to say. If not, maybe give that a shot before moving back to 10.0? Anyway, good luck!
I had some similar problems with 10.1, particularly with MCC not starting, and general problems with stability... I ended up going back to 10.0 on that machine..
I think 10.1 does use HAL, and with the benefit of hindsight and having tried other distro's that also use it (SuSE 9.2; Ubuntu; FC3), the problem appears to lie with HAL, and in particular its rather poor tolerance of flaky hardware... In my case, I've found that the Pioneer DVD-ROM fitted to this particular machine (DVD-120S) tends to hang up during polling by the HAL daemon, and in the process, completely hangs HAL, requiring a re-boot (HAL daemon goes into 'uninterruptible sleep') - this could be what's happening with you.
It may well be worth checking your system logs. Also check the status of the HAL daemon when things go wrong trying to access your USB drive..
Yeah, when I did this install I did a full format. Actually, I wanted to try ReiserFS, too, so I ended up doing it twice, as I chose the "automatic" option first, and then redid it to "Custom formating" to use ReiserFS. I've always used Ext3 before.
I think the problem may be with HAL now that Kevin mentions it.
This is some entries from /var/log/messages that seem to show the connection to the drive, and then at the end perhaps where it is complaining about a "Dead device"? I don't see anything useful in the boot.log file.
Apr 29 15:59:08 Linuxbox kernel: usb 5-1: new high speed USB device using address 2
Apr 29 15:59:09 Linuxbox kernel: SCSI subsystem initialized
Apr 29 15:59:09 Linuxbox kernel: Initializing USB Mass Storage driver...
Apr 29 15:59:09 Linuxbox kernel: scsi0 : SCSI emulation for USB Mass Storage devices
Apr 29 15:59:14 Linuxbox kernel: Vendor: WDC WD30 Model: 0BB-00AUA1 Rev: 0 0
Apr 29 15:59:14 Linuxbox kernel: Type: Direct-Access ANSI SCSI revision: 02
Apr 29 15:59:14 Linuxbox kernel: usbcore: registered new driver usb-storage
Apr 29 15:59:14 Linuxbox kernel: USB Mass Storage support registered.
Apr 29 15:59:15 Linuxbox scsi.agent: disk at /devices/pci0000:00/0000:00:0b.2/usb5/5-1/5-1:1.0/host0/0:0:0:0
Apr 29 15:59:15 Linuxbox kernel: SCSI device sda: 58633344 512-byte hdwr sectors (30020 MB)
Apr 29 15:59:15 Linuxbox kernel: sda: assuming drive cache: write through
Apr 29 15:59:15 Linuxbox kernel: /dev/scsi/host0/bus0/target0/lun0: p1
Apr 29 15:59:15 Linuxbox kernel: Attached scsi disk sda at scsi0, channel 0, id 0, lun 0
Apr 29 15:59:15 Linuxbox perl: drakupdate_fstab called with --auto --add /dev/sda1
Apr 29 15:59:52 Linuxbox kernel: usb 5-1: USB disconnect, address 2
Apr 29 15:59:52 Linuxbox perl: drakupdate_fstab called with --auto --del /dev/sda1
Apr 29 16:00:02 Linuxbox kernel: usb 5-1: new high speed USB device using address 3
Apr 29 16:00:03 Linuxbox kernel: scsi1 : SCSI emulation for USB Mass Storage devices
Apr 29 16:00:08 Linuxbox kernel: Vendor: WDC WD30 Model: 0BB-00AUA1 Rev: 0 0
Apr 29 16:00:08 Linuxbox kernel: Type: Direct-Access ANSI SCSI revision: 02
Apr 29 16:00:08 Linuxbox kernel: SCSI device sda: 58633344 512-byte hdwr sectors (30020 MB)
Apr 29 16:00:08 Linuxbox kernel: sda: assuming drive cache: write through
Apr 29 16:00:08 Linuxbox kernel: /dev/scsi/host1/bus0/target0/lun0: p1
Apr 29 16:00:08 Linuxbox kernel: Attached scsi disk sda at scsi1, channel 0, id 0, lun 0
Apr 29 16:00:09 Linuxbox scsi.agent: disk at /devices/pci0000:00/0000:00:0b.2/usb5/5-1/5-1:1.0/host1/1:0:0:0
Apr 29 16:00:10 Linuxbox perl: drakupdate_fstab called with --auto --add /dev/sda1
Apr 29 16:00:28 Linuxbox kernel: usb 5-1: USB disconnect, address 3
Apr 29 16:00:29 Linuxbox perl: drakupdate_fstab called with --auto --del /dev/sda1
Apr 29 16:00:29 Linuxbox kernel: scsi1 (0:0): rejecting I/O to dead device
Apr 29 16:00:29 Linuxbox kernel: FAT bread failed in fat_clusters_flush