Tymestream Posted December 14, 2004 Report Share Posted December 14, 2004 I have been having some trouble with mounting a usb drive in mandrake 10.1 - as I have read this is not uncommon. My question is : Why does Mandrake delete lines that I place into my fstab? I set up my usb device and it works fine, I then remove the device, and when I go to use it the next time it says there is no entry in fstab or mtab for it?? It is a line that I manually entered and not one that MCC entered on my behalf - this seems very arbitrary to me. This would be like Mandrake not finding a CD in your cdrom drive and then removing that line from your fstab file. Very frusrating indeed. Any ideas? Quote Link to comment Share on other sites More sharing options...
kmc77 Posted December 14, 2004 Report Share Posted December 14, 2004 Check your BIOS setup. I had to turn off the option allowing BIOS to detect accessories (USB) and turn on the option allowing OS to detect accessories. Untill I did that, the same thing kept happening to me. Quote Link to comment Share on other sites More sharing options...
Tymestream Posted December 14, 2004 Author Report Share Posted December 14, 2004 Check your BIOS setup. I had to turn off the option allowing BIOS to detect accessories (USB) and turn on the option allowing OS to detect accessories. Untill I did that, the same thing kept happening to me. <{POST_SNAPBACK}> That is interesting because I had heard the opposite - that setting the bios to detect devices made it easier for mandrake to see them. I will turn it off and see what happens. Thanks. Quote Link to comment Share on other sites More sharing options...
crazyspongebob Posted December 15, 2004 Report Share Posted December 15, 2004 I think it is part of usb thing. When you plug in you usb drive Mandrake tries to detect and mount the drive automagically for you like in Window$. So you don't have to enter a line for usb drives in fstab and mtab. In mdk 10.0 and 10.1 CE, the auto-detection and auto-mounting work fine in my case. But in 10.1, I am having a little headache. Even though mdk 10.1 harddrake detects the drive as sda, but it does not auto-mount the drive. I have to run the configure tool to mount, but it does not work after a reboot. I have turned on hotplug for usb and firewire devices, but it still doesn't work properly. J.T. Quote Link to comment Share on other sites More sharing options...
pmpatrick Posted December 15, 2004 Report Share Posted December 15, 2004 In mdk10.1-OE I turned off hotplug and harddrake in mcc>system>services and my manual usb entries in fstab are now staying put. Quote Link to comment Share on other sites More sharing options...
aRTee Posted December 15, 2004 Report Share Posted December 15, 2004 Check /var/log/messages to see what happens. What exact line did you add? If it looks too much like what Mdk would add itself, it will get deleted by the drakupdatefstab --del command. BTW why do you need to use your own command - if the deleting works, the creating (--add) should also work... no? Quote Link to comment Share on other sites More sharing options...
Tymestream Posted December 16, 2004 Author Report Share Posted December 16, 2004 I think it is part of usb thing. When you plug in you usb drive Mandrake tries to detect and mount the drive automagically for you like in Window$. So you don't have to enter a line for usb drives in fstab and mtab. In mdk 10.0 and 10.1 CE, the auto-detection and auto-mounting work fine in my case. But in 10.1, I am having a little headache. Even though mdk 10.1 harddrake detects the drive as sda, but it does not auto-mount the drive. I have to run the configure tool to mount, but it does not work after a reboot. I have turned on hotplug for usb and firewire devices, but it still doesn't work properly. J.T. <{POST_SNAPBACK}> I will try that as well, though I fear that it is a ongoing problem with 10.1 OE. Quote Link to comment Share on other sites More sharing options...
Tymestream Posted December 16, 2004 Author Report Share Posted December 16, 2004 Okay I have tried all the suggestions above and it seems that everything is working okay. Device mounts and unmounts at my request and fstab lines are not being deleted anymore. Final issue, I hope, the device seems to hang on large file transfers (100MB +) and my var/log/messages file is filled with this: Dec 16 09:21:17 primarycore kernel: FAT: bread(block 359) in fat_access failed Dec 16 09:21:17 primarycore kernel: scsi2 (0:0): rejecting I/O to offline device Dec 16 09:21:17 primarycore kernel: FAT: bread(block 359) in fat_access failed Dec 16 09:21:17 primarycore kernel: scsi2 (0:0): rejecting I/O to offline device Dec 16 09:21:17 primarycore kernel: FAT: bread(block 359) in fat_access failed Dec 16 09:21:17 primarycore kernel: scsi2 (0:0): rejecting I/O to offline device Dec 16 09:21:17 primarycore kernel: FAT: bread(block 359) in fat_access failed Dec 16 09:21:17 primarycore kernel: scsi2 (0:0): rejecting I/O to offline device Dec 16 09:21:17 primarycore kernel: FAT: bread(block 359) in fat_access failed Dec 16 09:21:17 primarycore kernel: scsi2 (0:0): rejecting I/O to offline device Dec 16 09:21:17 primarycore kernel: Buffer I/O error on device sdb1, logical block 1360212 Dec 16 09:21:17 primarycore kernel: Buffer I/O error on device sdb1, logical block 1360213 Dec 16 09:21:17 primarycore kernel: Buffer I/O error on device sdb1, logical block 1360214 Dec 16 09:21:17 primarycore kernel: Buffer I/O error on device sdb1, logical block 1360215 Dec 16 09:21:17 primarycore kernel: Buffer I/O error on device sdb1, logical block 1360216 Dec 16 09:21:17 primarycore kernel: Buffer I/O error on device sdb1, logical block 1360217 Dec 16 09:21:17 primarycore kernel: Buffer I/O error on device sdb1, logical block 1360218 Dec 16 09:21:17 primarycore kernel: Buffer I/O error on device sdb1, logical block 1360219 Dec 16 09:21:17 primarycore kernel: scsi2 (0:0): rejecting I/O to offline device Dec 16 09:21:17 primarycore kernel: Buffer I/O error on device sdb1, logical block 1374356 Dec 16 09:21:17 primarycore kernel: Buffer I/O error on device sdb1, logical block 1374357 Dec 16 09:21:17 primarycore kernel: Buffer I/O error on device sdb1, logical block 1374358 Dec 16 09:21:17 primarycore kernel: Buffer I/O error on device sdb1, logical block 1374359 Dec 16 09:21:17 primarycore kernel: Buffer I/O error on device sdb1, logical block 1374360 Dec 16 09:21:17 primarycore kernel: Buffer I/O error on device sdb1, logical block 1374361 Dec 16 09:21:17 primarycore kernel: Buffer I/O error on device sdb1, logical block 1374362 Dec 16 09:21:17 primarycore kernel: Buffer I/O error on device sdb1, logical block 1374363 Dec 16 09:21:17 primarycore kernel: Buffer I/O error on device sdb1, logical block 1374364 Dec 16 09:21:17 primarycore kernel: Buffer I/O error on device sdb1, logical block 1374365 Dec 16 09:21:17 primarycore kernel: Buffer I/O error on device sdb1, logical block 1374366 Dec 16 09:21:17 primarycore kernel: Buffer I/O error on device sdb1, logical block 1374367 Dec 16 09:21:17 primarycore kernel: Buffer I/O error on device sdb1, logical block 1374368 Dec 16 09:21:17 primarycore kernel: Buffer I/O error on device sdb1, logical block 1374369 Dec 16 09:21:17 primarycore kernel: Buffer I/O error on device sdb1, logical block 1374370 Dec 16 09:21:17 primarycore kernel: Buffer I/O error on device sdb1, logical block 1374371 Dec 16 09:21:17 primarycore kernel: Buffer I/O error on device sdb1, logical block 1374372 Dec 16 09:21:17 primarycore kernel: Buffer I/O error on device sdb1, logical block 1374373 Dec 16 09:21:17 primarycore kernel: Buffer I/O error on device sdb1, logical block 1374374 Dec 16 09:21:17 primarycore kernel: Buffer I/O error on device sdb1, logical block 1374375 Dec 16 09:21:17 primarycore kernel: Buffer I/O error on device sdb1, logical block 1374376 The files transfer simply stalls and gives a I/O error. Any ideas. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.