Is it safe to connect and disconnect USB Memory sticks with the power on?
usually yes. its safe The risk is to remove during a write cycle, that can be really bad. Its best to unmount the device first and then you can connect and disconnect with power on safely. The power issue will not damage the device as its made for that, but the mount issue can corrupt data. Judy & Lindsay Roberts wrote:
Is it safe to connect and disconnect USB Memory sticks with the power on?
_______________________________________________ wlug mailing list | wlug(a)list.waikato.ac.nz Unsubscribe: http://list.waikato.ac.nz/mailman/listinfo/wlug
-- "Engineering is the art of modeling materials we do not wholly understand, into shapes we cannot precisely analyse so as to withstand forces we cannot properly assess in such a way that the public has no reason to suspect the extent of our ignorance." Dr A R Dykes.
Also it should be noted that FC3 have improved their handling they claim. Often it gets confused whether it is mounted or not it is claimed in FC2. You can always run the mount command from a prompt but supposedly in FC2 it will allow you to graphically mount just once before it complains about locks On Tue, 21 Dec 2004 18:28:04 +1300, Gavin Denby <redhat(a)ihug.co.nz> wrote:
usually yes. its safe
The risk is to remove during a write cycle, that can be really bad.
Its best to unmount the device first and then you can connect and disconnect with power on safely.
The power issue will not damage the device as its made for that, but the mount issue can corrupt data.
Judy & Lindsay Roberts wrote:
Is it safe to connect and disconnect USB Memory sticks with the power on?
_______________________________________________ wlug mailing list | wlug(a)list.waikato.ac.nz Unsubscribe: http://list.waikato.ac.nz/mailman/listinfo/wlug
--
"Engineering is the art of modeling materials we do not wholly understand, into shapes we cannot precisely analyse so as to withstand forces we cannot properly assess in such a way that the public has no reason to suspect the extent of our ignorance." Dr A R Dykes.
_______________________________________________ wlug mailing list | wlug(a)list.waikato.ac.nz Unsubscribe: http://list.waikato.ac.nz/mailman/listinfo/wlug
So, does this mean, that if it is plugged in after Linux has loaded, it will be unmounted and need to be mounted so that data can be saved to it? Ian McDonald wrote:
Also it should be noted that FC3 have improved their handling they claim.
Often it gets confused whether it is mounted or not it is claimed in FC2.
You can always run the mount command from a prompt but supposedly in FC2 it will allow you to graphically mount just once before it complains about locks
On Tue, 21 Dec 2004 18:28:04 +1300, Gavin Denby <redhat(a)ihug.co.nz> wrote:
usually yes. its safe
The risk is to remove during a write cycle, that can be really bad.
Its best to unmount the device first and then you can connect and disconnect with power on safely.
The power issue will not damage the device as its made for that, but the mount issue can corrupt data.
Judy & Lindsay Roberts wrote:
Is it safe to connect and disconnect USB Memory sticks with the power on?
_______________________________________________ wlug mailing list | wlug(a)list.waikato.ac.nz Unsubscribe: http://list.waikato.ac.nz/mailman/listinfo/wlug
--
"Engineering is the art of modeling materials we do not wholly understand, into shapes we cannot precisely analyse so as to withstand forces we cannot properly assess in such a way that the public has no reason to suspect the extent of our ignorance." Dr A R Dykes.
_______________________________________________ wlug mailing list | wlug(a)list.waikato.ac.nz Unsubscribe: http://list.waikato.ac.nz/mailman/listinfo/wlug
_______________________________________________ wlug mailing list | wlug(a)list.waikato.ac.nz Unsubscribe: http://list.waikato.ac.nz/mailman/listinfo/wlug
On Tue, 21 Dec 2004, Judy & Lindsay Roberts wrote:
So, does this mean, that if it is plugged in after Linux has loaded, it will be unmounted and need to be mounted so that data can be saved to it?
No, you have it around the wrong way. When you want to access a new disk (such as a CD, or USB key) you have to mount the new drive. This is often automatically done by many new distributions when you plug in a USB key or insert a CD. When you have finished with a device, you need to unmount it before removing it. This is kinda equlivent to "Start Stop Hardware" that you get in Windows. Again, some modern distro's are setup in such a way as to protect you if you remove a drive before unmounting it. Unfortunatly this is all very distribution dependent, so you should probably tell us what you are using, then someone who also runs that can give you specific help. Cheers, Jamie
In the case of a CD, Linux will actually disable the eject button on the CDROM drive so you can not eject the disk without unmounting it first. With devices that rely on plug friction to remain attached (ie, USB and Firewire devices) you can just yank their plugs out. This can cause problems with your OS or the data stored on those devices if you do not tell the OS to stop/unmount/eject them before yanking. This is only relevant to USB storage devices. Other USB devices like printers and scanners can generally be plugged and unplugged at will as long as they are not "in use". Ie, don't yank the cable out while scanning an image or printing a photo. Doing so could cause weirdness. Regards On Tue, 2004-12-21 at 18:52 +1300, Jamie Curtis wrote:
On Tue, 21 Dec 2004, Judy & Lindsay Roberts wrote:
So, does this mean, that if it is plugged in after Linux has loaded, it will be unmounted and need to be mounted so that data can be saved to it?
No, you have it around the wrong way. When you want to access a new disk (such as a CD, or USB key) you have to mount the new drive. This is often automatically done by many new distributions when you plug in a USB key or insert a CD.
When you have finished with a device, you need to unmount it before removing it. This is kinda equlivent to "Start Stop Hardware" that you get in Windows. Again, some modern distro's are setup in such a way as to protect you if you remove a drive before unmounting it. Unfortunatly this is all very distribution dependent, so you should probably tell us what you are using, then someone who also runs that can give you specific help.
Cheers,
Jamie
_______________________________________________ wlug mailing list | wlug(a)list.waikato.ac.nz Unsubscribe: http://list.waikato.ac.nz/mailman/listinfo/wlug
I am using Mandrake Move (Live CD version) with no access to HDD. Jamie Curtis wrote:
On Tue, 21 Dec 2004, Judy & Lindsay Roberts wrote:
So, does this mean, that if it is plugged in after Linux has loaded, it will be unmounted and need to be mounted so that data can be saved to it?
No, you have it around the wrong way. When you want to access a new disk (such as a CD, or USB key) you have to mount the new drive. This is often automatically done by many new distributions when you plug in a USB key or insert a CD.
When you have finished with a device, you need to unmount it before removing it. This is kinda equlivent to "Start Stop Hardware" that you get in Windows. Again, some modern distro's are setup in such a way as to protect you if you remove a drive before unmounting it. Unfortunatly this is all very distribution dependent, so you should probably tell us what you are using, then someone who also runs that can give you specific help.
Cheers,
Jamie
_______________________________________________ wlug mailing list | wlug(a)list.waikato.ac.nz Unsubscribe: http://list.waikato.ac.nz/mailman/listinfo/wlug
Yes. However as noted by another poster you need to ensure the "drive" has been unmounted. On my Fedora Core 3 powered laptop I presently have both my camera and external HDD connected via USB. Both are treated as USB Storage devices as a USB memory stick would be. When I connect them they are automatically mounted by hotplug and the hal/d-bus is told about them so Nautilus shows nice little icons on the Gnome desktop. Before I remove the devices I right click on them and select "Unmount Volume". You can do the same with an "unmount /mnt/usbdisk" or "unmount /media/usbdisk" from the command line. It is important to make sure you unmount removable media before unplugging or else you may cause file system corruption and loose data. In Windows it is the same. You should right click on USB or Flash devices in Explorer and select "Eject" before removing the device. However windows can sometimes not recognise USB devices as "ejectable" media and doesn't provide the Eject choice. In that case it is safest to use the stop removable device control panel applet. Though I have noticed windows sometimes refusing to stop devices because it thinks they are in use for inexplicable reasons. Regards On Tue, 2004-12-21 at 18:06 +1300, Judy & Lindsay Roberts wrote:
Is it safe to connect and disconnect USB Memory sticks with the power on?
_______________________________________________ wlug mailing list | wlug(a)list.waikato.ac.nz Unsubscribe: http://list.waikato.ac.nz/mailman/listinfo/wlug
Oliver Jones wrote:
Yes. However as noted by another poster you need to ensure the "drive" has been unmounted.
On my Fedora Core 3 powered laptop I presently have both my camera and external HDD connected via USB. Both are treated as USB Storage devices as a USB memory stick would be. When I connect them they are automatically mounted by hotplug and the hal/d-bus is told about them so Nautilus shows nice little icons on the Gnome desktop. Before I remove the devices I right click on them and select "Unmount Volume".
You can do the same with an "unmount /mnt/usbdisk" or "unmount /media/usbdisk" from the command line.
It is important to make sure you unmount removable media before unplugging or else you may cause file system corruption and loose data.
In Windows it is the same. You should right click on USB or Flash devices in Explorer and select "Eject" before removing the device. However windows can sometimes not recognise USB devices as "ejectable" media and doesn't provide the Eject choice. In that case it is safest to use the stop removable device control panel applet. Though I have noticed windows sometimes refusing to stop devices because it thinks they are in use for inexplicable reasons.
Regards
On Tue, 2004-12-21 at 18:06 +1300, Judy & Lindsay Roberts wrote:
Is it safe to connect and disconnect USB Memory sticks with the power on?
_______________________________________________ wlug mailing list | wlug(a)list.waikato.ac.nz Unsubscribe: http://list.waikato.ac.nz/mailman/listinfo/wlug
_______________________________________________ wlug mailing list | wlug(a)list.waikato.ac.nz Unsubscribe: http://list.waikato.ac.nz/mailman/listinfo/wlug
And to keep this subject alive and helpful may I ask...... How do you re-mount another mass_storage device? eg. I boot my system with a memstick inserted and the system sees it AOK. I then issue: # umount /mnt/removable And then remove the device. I now wish to insert my camera card reader - and this is where at present I come unstuck as I have yet to successfully do this without 'emptying' the data ( read photos ) from the device. I have also tried remounting the previously removed memstick and lost the data on that also. Er... did I mention that I'm running mandrake 10 Official with hotplug installed. I have tried: # mount -t usbfs /dev/sda1 /mnt/removable # mount -t vfat /dev/sda1 /mnt/removable # mount -t ext2 /dev/removable # mount -t ext2,vfat /dev/removable I understood that the first one should have worked whereas the other three would only work if I had formatted the drive to one or both of those file systems. And booting into WinXP I didn't have any problems provided I did as suggested previously - was able to put some data onto the memstick and retry my Linux side in an attempt to get this thing to work. This is important because at work I am getting more and more clients arriving with their dxf files on mem/flash sticks and it is a pain that I cannot reliable use Linux to read them. It is embarrassing to have to boot into Windows just to download the data and then back into Windows later to update their sticks. As to the CD issue mentioned earlier - if in doubt then as su issue: # eject Remove the CD and then: # eject -t The 'eject' command ought to unmount the device for you. [Note: if you have more than one CD/DVD onboard then you will have to specify the device. eg: # eject cdrom1 -- Regards SnapafunFrank Big or small, a challenge requires the same commitment to resolve. Registered Linux User # 324213
On Tue, 2004-12-21 at 22:16 +1300, SnapafunFrank wrote:
And to keep this subject alive and helpful may I ask...... How do you re-mount another mass_storage device?
eg. I boot my system with a memstick inserted and the system sees it AOK.
I then issue:
# umount /mnt/removable
And then remove the device.
I now wish to insert my camera card reader - and this is where at present I come unstuck as I have yet to successfully do this without 'emptying' the data ( read photos ) from the device. Chances are, the device has been registered as /dev/sdb, so you should be able to mount it using /dev/sdb1 as the partition.
Running 'dmesg' after pluggin in the dives will show you technical information including what the device is, and the file in /dev that it has been linked to.
I have also tried remounting the previously removed memstick and lost the data on that also.
Er... did I mention that I'm running mandrake 10 Official with hotplug installed.
I have tried:
# mount -t usbfs /dev/sda1 /mnt/removable # mount -t vfat /dev/sda1 /mnt/removable # mount -t ext2 /dev/removable # mount -t ext2,vfat /dev/removable If it's a standard drive that works in windows, you will want to use -t vfat
I understood that the first one should have worked whereas the other three would only work if I had formatted the drive to one or both of those file systems.
And booting into WinXP I didn't have any problems provided I did as suggested previously - was able to put some data onto the memstick and retry my Linux side in an attempt to get this thing to work. This is important because at work I am getting more and more clients arriving with their dxf files on mem/flash sticks and it is a pain that I cannot reliable use Linux to read them. It is embarrassing to have to boot into Windows just to download the data and then back into Windows later to update their sticks.
As to the CD issue mentioned earlier - if in doubt then as su issue:
# eject
Remove the CD and then:
# eject -t
The 'eject' command ought to unmount the device for you. [Note: if you have more than one CD/DVD onboard then you will have to specify the device. eg:
# eject cdrom1
-- (o< - A l a s t a i r P o r t e r //\ V_/_ alastair(a)linuxexperience.com
Alastair Porter wrote:
On Tue, 2004-12-21 at 22:16 +1300, SnapafunFrank wrote:
And to keep this subject alive and helpful may I ask...... How do you re-mount another mass_storage device?
eg. I boot my system with a memstick inserted and the system sees it AOK.
I then issue:
# umount /mnt/removable
And then remove the device.
I now wish to insert my camera card reader - and this is where at present I come unstuck as I have yet to successfully do this without 'emptying' the data ( read photos ) from the device.
Chances are, the device has been registered as /dev/sdb, so you should be able to mount it using /dev/sdb1 as the partition.
Running 'dmesg' after pluggin in the dives will show you technical information including what the device is, and the file in /dev that it has been linked to.
I have also tried remounting the previously removed memstick and lost the data on that also.
Er... did I mention that I'm running mandrake 10 Official with hotplug installed.
I have tried:
# mount -t usbfs /dev/sda1 /mnt/removable # mount -t vfat /dev/sda1 /mnt/removable # mount -t ext2 /dev/removable # mount -t ext2,vfat /dev/removable
If it's a standard drive that works in windows, you will want to use -t vfat
I understood that the first one should have worked whereas the other three would only work if I had formatted the drive to one or both of those file systems.
And booting into WinXP I didn't have any problems provided I did as suggested previously - was able to put some data onto the memstick and retry my Linux side in an attempt to get this thing to work. This is important because at work I am getting more and more clients arriving with their dxf files on mem/flash sticks and it is a pain that I cannot reliable use Linux to read them. It is embarrassing to have to boot into Windows just to download the data and then back into Windows later to update their sticks.
As to the CD issue mentioned earlier - if in doubt then as su issue:
# eject
Remove the CD and then:
# eject -t
The 'eject' command ought to unmount the device for you. [Note: if you have more than one CD/DVD onboard then you will have to specify the device. eg:
# eject cdrom1
------------------------------------------------------------------------
_______________________________________________ wlug mailing list | wlug(a)list.waikato.ac.nz Unsubscribe: http://list.waikato.ac.nz/mailman/listinfo/wlug
So OK, I had that much correct anyway. Thanks for confirmation.
To follow your advise I removed the memstick: and replaced having first issued [root(a)Snapafun mnt]# umount removable/ umount: removable/: not mounted { removed it here } { then re-installed it } [root(a)Snapafun mnt]# dmesg usb 2-3: USB disconnect, address 5 usb 2-3: new full speed USB device using address 6 scsi1 : SCSI emulation for USB Mass Storage devices Vendor: M-Sys. Model: Storage Media Rev: 1.05 Type: Direct-Access ANSI SCSI revision: 02 SCSI device sda: 32000 512-byte hdwr sectors (16 MB) sda: assuming Write Enabled sda: assuming drive cache: write through /dev/scsi/host1/bus0/target0/lun0: p1 Attached scsi removable disk sda at scsi1, channel 0, id 0, lun 0 Attached scsi generic sg0 at scsi1, channel 0, id 0, lun 0, type 0 WARNING: USB Mass Storage data integrity not assured USB Mass Storage device found at 6 So...... care to fill in the missing bits? # mount -t vfat /dev/...... /mnt/removable Surely with automount running there ought to be an easier way? -- Regards SnapafunFrank Big or small, a challenge requires the same commitment to resolve. Registered Linux User # 324213
On Tue, 2004-12-21 at 23:51 +1300, SnapafunFrank wrote:
Alastair Porter wrote:
On Tue, 2004-12-21 at 22:16 +1300, SnapafunFrank wrote:
And to keep this subject alive and helpful may I ask...... How do you re-mount another mass_storage device?
eg. I boot my system with a memstick inserted and the system sees it AOK.
I then issue:
# umount /mnt/removable
And then remove the device.
I now wish to insert my camera card reader - and this is where at present I come unstuck as I have yet to successfully do this without 'emptying' the data ( read photos ) from the device.
Chances are, the device has been registered as /dev/sdb, so you should be able to mount it using /dev/sdb1 as the partition.
Running 'dmesg' after pluggin in the dives will show you technical information including what the device is, and the file in /dev that it has been linked to.
So OK, I had that much correct anyway. Thanks for confirmation.
To follow your advise I removed the memstick: and replaced having first issued
[root(a)Snapafun mnt]# umount removable/ umount: removable/: not mounted This is saying that you haven't actually unmounted the device. Try umount /mnt/removable
{ removed it here } Because you didn't really unmount it, this will probably have bed concequences - ie, the loss of data you were talking about
{ then re-installed it } Since you are plugging the same device in, it will have the same allocation in /dev
[root(a)Snapafun mnt]# dmesg usb 2-3: USB disconnect, address 5 usb 2-3: new full speed USB device using address 6 scsi1 : SCSI emulation for USB Mass Storage devices Vendor: M-Sys. Model: Storage Media Rev: 1.05 Type: Direct-Access ANSI SCSI revision: 02 SCSI device sda: 32000 512-byte hdwr sectors (16 MB) sda: assuming Write Enabled Here you can see it's been re-allocated sda sda: assuming drive cache: write through /dev/scsi/host1/bus0/target0/lun0: p1 Attached scsi removable disk sda at scsi1, channel 0, id 0, lun 0 Attached scsi generic sg0 at scsi1, channel 0, id 0, lun 0, type 0 WARNING: USB Mass Storage data integrity not assured USB Mass Storage device found at 6
So...... care to fill in the missing bits?
# mount -t vfat /dev/...... /mnt/removable # mount -t vfat /dev/sda1 /mnt/removable
Surely with automount running there ought to be an easier way? You said you were running Mandrake. Does an icon appear on the desktop when you plug the drive in? If so, then there is probably an 'Unmount'
<snip> option in the menu when you right click on it. This would be a much wasier way to use it. Alastair -- (o< - A l a s t a i r P o r t e r //\ V_/_ alastair(a)linuxexperience.com
[root(a)Snapafun mnt]# umount removable/ umount: removable/: not mounted This is saying that you haven't actually unmounted the device. Try umount /mnt/removable
Indeed (u)mount can be finicky about mount points. Relative mount mounts like "mount removable" will only work if you are in the parent directory of the mount point. In this case /mnt. Note that mount reads the file /etc/fstab. If you have predefined mount points for devices there you can issue shortcut commands like: mount /mnt/removable mount /mnt/cdrom etc without specifying devices or partition types. These are taken from /etc/fstab. Also note that FC3 which follows (some of) the new Linux Filesystem Standard mounts removable media in the new /media directory.
{ then re-installed it } Since you are plugging the same device in, it will have the same allocation in /dev
On new 2.6 based distros this isn't guaranteed. FC3 uses udev to assign device names. My wireless card kept getting given random device names until I tweaked the udev config. You shouldn't have a problem with USB storage devices though.
# mount -t vfat /dev/...... /mnt/removable # mount -t vfat /dev/sda1 /mnt/removable
Note that some devices may not be partitioned or have odd partition layouts (rare in the case of USB storage, but still possible). Check the devices partition table with: fdisk -l /dev/sda This will list all the partitions on the device.
Surely with automount running there ought to be an easier way? You said you were running Mandrake. Does an icon appear on the desktop when you plug the drive in? If so, then there is probably an 'Unmount' option in the menu when you right click on it. This would be a much wasier way to use it.
Modern distros should just mount usb storage devices automatically out of the box. Fedora Core 3 certainly does. -- Oliver Jones <oliver(a)deeper.co.nz> Deeper Design Limited
Oliver Jones wrote:
[root(a)Snapafun mnt]# umount removable/ umount: removable/: not mounted
This is saying that you haven't actually unmounted the device. Try umount /mnt/removable
Indeed (u)mount can be finicky about mount points. Relative mount mounts like "mount removable" will only work if you are in the parent directory of the mount point. In this case /mnt.
Note that mount reads the file /etc/fstab. If you have predefined mount points for devices there you can issue shortcut commands like:
mount /mnt/removable mount /mnt/cdrom
etc without specifying devices or partition types. These are taken from /etc/fstab.
Also note that FC3 which follows (some of) the new Linux Filesystem Standard mounts removable media in the new /media directory.
{ then re-installed it }
Since you are plugging the same device in, it will have the same allocation in /dev
On new 2.6 based distros this isn't guaranteed. FC3 uses udev to assign device names. My wireless card kept getting given random device names until I tweaked the udev config. You shouldn't have a problem with USB storage devices though.
# mount -t vfat /dev/...... /mnt/removable
# mount -t vfat /dev/sda1 /mnt/removable
Note that some devices may not be partitioned or have odd partition layouts (rare in the case of USB storage, but still possible). Check the devices partition table with:
fdisk -l /dev/sda
This will list all the partitions on the device.
Surely with automount running there ought to be an easier way?
You said you were running Mandrake. Does an icon appear on the desktop when you plug the drive in? If so, then there is probably an 'Unmount' option in the menu when you right click on it. This would be a much wasier way to use it.
Modern distros should just mount usb storage devices automatically out of the box. Fedora Core 3 certainly does.
So does knoppix (since we're dealing with a live CD here. Apples, etc..) [sda1] appears on the desktop when I plug my camera in. Right-click menu for the icon has the mount/unmount option. I would expect any kde-desktop linux to be fairly similar but I'm not familiar with mandrake..
I think I'm nearly there - but not being there could mean I have miles to go. Thanks to all the advise this thread has made available, I've learnt heaps. Sad fact is I am unable to read my flash sticks / camera card yet. So I went looking and discovered /udev. Some good HOWTOs out there and I got it all up to actually seeing the devices. eg. [ I called this one 64MB and have made all the entries the HOWTOs have suggested as can be seen here.] [root(a)Snapafun mnt]# fdisk /udev/64MB Command (m for help): p Disk /udev/64MB: 65 MB, 65536000 bytes 16 heads, 32 sectors/track, 250 cylinders Units = cylinders of 512 * 512 = 262144 bytes Device Boot Start End Blocks Id System /udev/64MB1 * 1 249 63728 6 FAT16 Command (m for help): q [root(a)Snapafun mnt]# mount /udev/64MB -t vfat 64MB mount: wrong fs type, bad option, bad superblock on /udev/64MB, or too many mounted file systems Of the three devices I have one shows " FAT12 " - another shows " FAT16 " and the last shows " FAT16<32M " Any suggestions anyone? I have the latest rpms installed for all the stuff needed according to the HOWTO. http://www.tldp.org/HOWTO/Flash-Memory-HOWTO/linux-2.6.html And all the files/folders to check for are present. I'm not sure if the devices once plugged in are suppose to show up in /mnt but they don't at present. One more thing, once I have made changes to /etc/fstab do I need to do anything extra to invoke the changes? [ Like we need to do with lilo eg. ] Things seem OK: [root(a)Snapafun mnt]# ls /udev 64MB 64MB0 64MB1 But I thought I had better be sure. Merry xmas all. -- Regards SnapafunFrank Big or small, a challenge requires the same commitment to resolve. Registered Linux User # 324213
Device Boot Start End Blocks Id System /udev/64MB1 * 1 249 63728 6 FAT16
This output from fdisk shows a single partition inside your device. Note, that the partition is /udev/64MB1. A device can contain many (non-overlapping) partitions, each of which can be used and formatted independantly
Command (m for help): q
[root(a)Snapafun mnt]# mount /udev/64MB -t vfat 64MB mount: wrong fs type, bad option, bad superblock on /udev/64MB, or too many mounted file systems
When you mount something, you have to mount a partition. So instead of mounting the device /udev/64MB, you should be mounting /udev/64MB1 Also, the partition needs to have been formatted first. I assume you can read this correctly under windows - if that's the case, then it's been formatted. So, if: * the device is called /udev/64MB * you want to mount the first partition in /udev/64MB - ie, /udev/64MB1 * it has been correclty formatted as fat * the mountpount /mnt/64MB exists (mkdir -p /mnt/64MB as root) you can run: mount /udev/64MB1 -t vfat /mnt/64MB And it should work.
One more thing, once I have made changes to /etc/fstab do I need to do anything extra to invoke the changes? [ Like we need to do with lilo eg. ]
No.
Daniel Lawson wrote:
Device Boot Start End Blocks Id System /udev/64MB1 * 1 249 63728 6 FAT16
This output from fdisk shows a single partition inside your device. Note, that the partition is /udev/64MB1. A device can contain many (non-overlapping) partitions, each of which can be used and formatted independantly
Command (m for help): q
[root(a)Snapafun mnt]# mount /udev/64MB -t vfat 64MB mount: wrong fs type, bad option, bad superblock on /udev/64MB, or too many mounted file systems
When you mount something, you have to mount a partition. So instead of mounting the device /udev/64MB, you should be mounting /udev/64MB1
Also, the partition needs to have been formatted first. I assume you can read this correctly under windows - if that's the case, then it's been formatted.
So, if: * the device is called /udev/64MB * you want to mount the first partition in /udev/64MB - ie, /udev/64MB1 * it has been correclty formatted as fat * the mountpount /mnt/64MB exists (mkdir -p /mnt/64MB as root) you can run:
mount /udev/64MB1 -t vfat /mnt/64MB
And it should work.
And it does. Thanks for that. Still have one problem though. Can not access the device as user. Before mounting: [root(a)Snapafun mnt]# ls -al total 127 drwxr-xr-x 16 root root 4096 Dec 24 01:26 ./ drwxr-xr-x 24 root root 4096 Dec 23 19:53 ../ drwxr-xr-x 2 frank frank 4096 Dec 24 01:22 16MB/ drwxr-xr-x 2 frank frank 4096 Dec 24 01:22 64MB/ drwxr-xr-x 2 frank frank 4096 Dec 24 01:22 Camera/ <SNIP> After mounting: [root(a)Snapafun mnt]# mount /udev/16MB1 -t vfat /mnt/16MB [root(a)Snapafun mnt]# ls -al total 139 drwxr-xr-x 16 root root 4096 Dec 24 01:26 ./ drwxr-xr-x 24 root root 4096 Dec 23 19:53 ../ drwxr--r-- 2 root root 16384 Jan 1 1970 16MB/ drwxr-xr-x 2 frank frank 4096 Dec 24 01:22 64MB/ drwxr-xr-x 2 frank frank 4096 Dec 24 01:22 Camera/ <SNIP> As you can see, the owner is changed by the system and though I am happy to chmod for other than owner [ being USER ] I do not know how to handle this problem. So right now I need to be able to mount the partition as user. Any ideas? Summary: So I am missing one more step at least - my aim is to be able to mount and read write to the device as user. ( I'm thinking something like : # chmod 600 /mnt/16MB - etc.) Once I have got it sorted, albeit relying on your capable assistance, it is my intention to repeat the exercise so as to post a step by step command howto on my site and anywhere else that asks. I believe we are nearly there so await your reply with patience as it is indeed the xmas season. [ And there will be heaps of photos to process - always windows TILL NOW! - I hope. ] Thanks again. -- Regards SnapafunFrank Big or small, a challenge requires the same commitment to resolve. Registered Linux User # 324213
SnapafunFrank wrote:
Daniel Lawson wrote:
Device Boot Start End Blocks Id System /udev/64MB1 * 1 249 63728 6 FAT16
This output from fdisk shows a single partition inside your device. Note, that the partition is /udev/64MB1. A device can contain many (non-overlapping) partitions, each of which can be used and formatted independantly
Command (m for help): q
[root(a)Snapafun mnt]# mount /udev/64MB -t vfat 64MB mount: wrong fs type, bad option, bad superblock on /udev/64MB, or too many mounted file systems
When you mount something, you have to mount a partition. So instead of mounting the device /udev/64MB, you should be mounting /udev/64MB1
Also, the partition needs to have been formatted first. I assume you can read this correctly under windows - if that's the case, then it's been formatted.
So, if: * the device is called /udev/64MB * you want to mount the first partition in /udev/64MB - ie, /udev/64MB1 * it has been correclty formatted as fat * the mountpount /mnt/64MB exists (mkdir -p /mnt/64MB as root) you can run:
mount /udev/64MB1 -t vfat /mnt/64MB
And it should work.
And it does. Thanks for that. Still have one problem though. Can not access the device as user.
Before mounting:
[root(a)Snapafun mnt]# ls -al total 127 drwxr-xr-x 16 root root 4096 Dec 24 01:26 ./ drwxr-xr-x 24 root root 4096 Dec 23 19:53 ../ drwxr-xr-x 2 frank frank 4096 Dec 24 01:22 16MB/ drwxr-xr-x 2 frank frank 4096 Dec 24 01:22 64MB/ drwxr-xr-x 2 frank frank 4096 Dec 24 01:22 Camera/ <SNIP>
After mounting:
[root(a)Snapafun mnt]# mount /udev/16MB1 -t vfat /mnt/16MB [root(a)Snapafun mnt]# ls -al total 139 drwxr-xr-x 16 root root 4096 Dec 24 01:26 ./ drwxr-xr-x 24 root root 4096 Dec 23 19:53 ../ drwxr--r-- 2 root root 16384 Jan 1 1970 16MB/ drwxr-xr-x 2 frank frank 4096 Dec 24 01:22 64MB/ drwxr-xr-x 2 frank frank 4096 Dec 24 01:22 Camera/ <SNIP>
As you can see, the owner is changed by the system and though I am happy to chmod for other than owner [ being USER ] I do not know how to handle this problem.
So right now I need to be able to mount the partition as user. Any ideas?
Summary:
So I am missing one more step at least - my aim is to be able to mount and read write to the device as user. ( I'm thinking something like : # chmod 600 /mnt/16MB - etc.)
Once I have got it sorted, albeit relying on your capable assistance, it is my intention to repeat the exercise so as to post a step by step command howto on my site and anywhere else that asks.
I believe we are nearly there so await your reply with patience as it is indeed the xmas season. [ And there will be heaps of photos to process - always windows TILL NOW! - I hope. ]
Thanks again.
Darn.... a problem to solve before I can continue. I just had to reboot the system as I suspected a power outage was on the way. When up and running again I issued: # ls /udev Expecting to see my storage device, instead I got a whole page full of devices - the whole system is listed by the looks. Any ideas anyone? (Mandrake10 Official) -- Regards SnapafunFrank Big or small, a challenge requires the same commitment to resolve. Registered Linux User # 324213
participants (9)
-
Alastair Porter -
Daniel Lawson -
Gavin Denby -
Ian McDonald -
Jamie Curtis -
Judy & Lindsay Roberts -
Oliver Jones -
SnapafunFrank -
zcat