rohitsz Posted July 1, 2006 Report Share Posted July 1, 2006 (edited) Greetings there, Well i have been facing this problem for long. I use a kingston 256M data traveller, whose discovery is automatic since mdk 10.1 . Since i have upgraded to mdk 2006,the discovery part is perfect,but when it comes to working with big or small files, the operation is stalled for too long. If a small file is being moved, the mounted part shows the files,but on unmounting the drive and mounting it on a different system or same system, the files are not visible. This is too painful as i have to mail my stuff from linux and then access it on an xp notebook at home. Has anyone else faced any similar problem?How to solve it? thanks, rohit. Edited July 5, 2006 by rohitsz Quote Link to comment Share on other sites More sharing options...
scarecrow Posted July 1, 2006 Report Share Posted July 1, 2006 I assume its formatted as vfat/ FAT32? Can you pass an lsmod with the pendrive already mounted? Quote Link to comment Share on other sites More sharing options...
rohitsz Posted July 1, 2006 Author Report Share Posted July 1, 2006 (edited) Hello there, sorry for the late reply... I assume its formatted as vfat/ FAT32?Can you pass an lsmod with the pendrive already mounted? Yes it is FAT32 formatted.. here's the output: [root@localhost rsz]# lsmod Module Size Used by sd_mod 16240 2 usb_storage 82020 2 scsi_mod 121064 2 sd_mod,usb_storage af_packet 16392 0 radeon 76672 1 drm 60404 2 radeon md5 3584 1 ipv6 234016 8 raw 6592 0 i810_audio 33556 1 ac97_codec 18156 1 i810_audio soundcore 7008 2 i810_audio ipt_IFWLOG 2788 1 ipt_psd 43428 1 ip_set_iptree 5544 2 ipt_REJECT 4256 4 ipt_LOG 6272 7 8139too 21760 0 mii 4704 1 8139too ipt_state 1312 13 ipt_pkttype 1184 4 ipt_set 1920 2 ipt_CONNMARK 1696 0 ipt_MARK 1984 0 ipt_ROUTE 4260 0 ipt_connmark 1216 0 ipt_owner 2432 0 ipt_recent 9292 0 ipt_iprange 1312 0 ipt_physdev 1744 0 ipt_multiport 2112 0 ipt_conntrack 1792 0 iptable_mangle 2016 0 ip_set_portmap 3840 0 ip_set_macipmap 3780 0 ip_set_ipmap 3872 0 ip_set_iphash 5924 0 ip_set 18876 11 ip_set_iptree,ipt_set,ip_set_portmap,ip_set_macipmap,ip_set_ipmap,ip_set_iphash ip_nat_irc 1824 0 ip_nat_tftp 1216 0 ip_nat_ftp 2560 0 iptable_nat 20212 3 ip_nat_irc,ip_nat_tftp,ip_nat_ftp ip_conntrack_irc 70352 1 ip_nat_irc ip_conntrack_tftp 3088 1 ip_nat_tftp ip_conntrack_ftp 71408 1 ip_nat_ftp ip_conntrack 40824 9 ipt_state,ipt_conntrack,ip_nat_irc,ip_nat_tftp,ip_nat_ftp,iptable_nat,ip_conntra ck_irc,ip_conntrack_tftp,ip_conntrack_ftp iptable_filter 2080 1 ip_tables 20416 20 ipt_IFWLOG,ipt_psd,ipt_REJECT,ipt_LOG,ipt_state,ipt_pkttype,ipt_set,ipt_CONNMARK ,ipt_MARK,ipt_ROUTE,ipt_connmark,ipt_owner,ipt_recent,ipt_iprange,ipt_physdev,ip t _multiport,ipt_conntrack,iptable_mangle,iptable_nat,iptable_filter ide_cd 37988 0 loop 14504 0 nls_iso8859_1 3680 8 nls_cp850 4480 8 supermount 31956 1 vfat 10592 8 fat 45980 1 vfat intel_agp 20636 1 agpgart 29032 2 drm,intel_agp hw_random 4244 0 tsdev 5984 0 uhci_hcd 29136 0 usbcore 108348 3 usb_storage,uhci_hcd evdev 7648 0 ext3 124744 4 jbd 48568 1 ext3 [root@localhost rsz]# rohit. Edited July 1, 2006 by rohitsz Quote Link to comment Share on other sites More sharing options...
scarecrow Posted July 1, 2006 Report Share Posted July 1, 2006 All needed modules are loaded, so there shouldn't be a real problem. Please try in a root console: urpmi dosfstools and then mounting the pendrive again, and performing I/O operations. Linux does need the above package to perform several tasks on vfat volumes. Quote Link to comment Share on other sites More sharing options...
rohitsz Posted July 1, 2006 Author Report Share Posted July 1, 2006 Hello Again, All needed modules are loaded, so there shouldn't be a real problem.Please try in a root console: urpmi dosfstools and then mounting the pendrive again, and performing I/O operations. Linux does need the above package to perform several tasks on vfat volumes. i did try what you said. i have this package installed... but i still face the same problem. Also my drive mounts read only thru GUI. is there a way that i can make it mount in read-write mode when i double click /dev/sda1 in Devices? thanks, rohit. Quote Link to comment Share on other sites More sharing options...
ianw1974 Posted July 3, 2006 Report Share Posted July 3, 2006 I've had similar problems that you have. I used to have Windows on an NTFS partition, and when I attempted to copy large files from the NTFS partition into Linux, they would stall and fail. No matter what I tried, I never got it to work. I ended up using a machine as an ftp server, and ftp'd the files to the server, and then back down to my machine once I'd rebooted. I'd never experienced it with vfat though, and my USB disk is vfat currently. You can make your disk mount read/write by editing the entry in /etc/fstab and making sure that you have umask=0. My example for my NTFS partition, but you can see from where umask exists where to add it in your fstab. /dev/hda1 /mnt/windows ntfs umask=0,nls=iso8859-15,ro 0 0 so after where it says vfat in your fstab, put umask=0 on the options line. If there are other options, make sure a comma is placed to separate them like my example above. Quote Link to comment Share on other sites More sharing options...
rohitsz Posted July 4, 2006 Author Report Share Posted July 4, 2006 Hi ian, /dev/hda1 /mnt/windows ntfs umask=0,nls=iso8859-15,ro 0 0 so after where it says vfat in your fstab, put umask=0 on the options line. If there are other options, make sure a comma is placed to separate them like my example above. The entry for my usb(vfat) is as follows: /dev/sda1 /mnt/ROHIT vfat rw,noauto,exec,user,quiet,iocharset=iso8859-1,codepage=850 0 0 Is there anything wrong/missing anything in this?(except umask=0). I know where to add umask.. but what is umask? regards, rohit. Quote Link to comment Share on other sites More sharing options...
ianw1974 Posted July 4, 2006 Report Share Posted July 4, 2006 Umask (I think) is a way of placing permissions. Therefore, umask=0 gives you full access to get around the read-only problem you were having. Quote Link to comment Share on other sites More sharing options...
pmpatrick Posted July 4, 2006 Report Share Posted July 4, 2006 Remove the drive and comment out the line for sda1 in fstab by putting # in front of it. Then try reinserting the drive and see if it automounts. mdv 2006 uses udev and hal to automatically generate the appropriate fstab entry on the fly for removable media and removes that entry from fstab when the device is removed. The fstab entry generated by hal will have the word "pamconsole" in it. If you have a permanent entry in fstab for sda1 like you have, this will overide hal and be used instead on any removable device designated sda1. I'm hoping that the autogenerated fstab entry from hal will work better for you. Quote Link to comment Share on other sites More sharing options...
scarecrow Posted July 4, 2006 Report Share Posted July 4, 2006 Indeed, no fstab entry is needed. Mandriva 2006 uses the completely deprecated fstab-sync method of mounting removable media, and the needed entries are autocreated (and anyway the current automounting methods do not modify fstab themseleves, but do not need any fstab entry, either). Just get sure that the Hardware Abstraction Layer (hal) daemon is running. Quote Link to comment Share on other sites More sharing options...
rohitsz Posted July 5, 2006 Author Report Share Posted July 5, 2006 Thanks a lot for solving my usb problem! i commented out the /dev/sda1 entry in /etc/fstab and the drive now works better. i have nothing to say except thank you again! :-) regards, rohit. 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.