[SOLVED] Strange Mount Behavior After Unexpected Shutdown Mid File Transfer

bdjnk · 08-06-2010, 02:44 AM

Hardware: HP Pavilion tx1000
Distribution: PCLinuxOS 2010.1 (fully updated)
DE: KDE SC 4.4.5

I had a UMS device (my new Samsung Vibrant) hooked up and was transferring files from my computer to the device. Suddenly my computer had a hardware malfunction (which I later tracked to a faulty RAM module) and proceeded to shutdown swiftly. Not a straight power down, I couldn't tell what was happening because the screen fuzzed over and started glitching, but it was faster than normal.

Upon correcting the hardware issue, rebooting, and reconnecting the device (to reattempt the transfer) I discovered that the name of the device had become "_PNG []" (with [] representing the symbol which indicates that the desired charter is unknown) according to KDE.

Additionally a device "_PNG []" appears in the Device Manager plasmoid all the time now and attempts to mount it result in the message "Cannot mount the disc." In the /Media directory a folder named "_PNG []-2" exists and cannot be deleted, even from the command line using rm -rf as root, the rm informing me that it "cannot remove directory `_PNG\r\n\032-2': Device or resource busy".

Lastly, each time the device is mounted a new folder is created in the /media directory, starting with "_PNG []", then "_PNG []-3", "_PNG []-4", and so on. These can be deleted once the device is unmounted.

An Image of the Issue

This is really bothering me and I have searched high and low to no avail. Any help is tremendously appreciated.

bdjnk · 08-06-2010, 03:06 PM

Searching various portions of my system for files containing "_PNG" took a long time and turned up more results then expected but it did lead me partway to a solution.

The contents of /Media/.hal-mtab were as follows:

Code:

/dev/sdc	500	0	vfat	nosuid,nodev,uhelper=hal,uid=500,utf8,shortname=mixed,flush	/media/_PNG

/dev/sdc	500	0	vfat	nosuid,nodev,uhelper=hal,uid=500,utf8,shortname=mixed,flush	/media/_PNG
-1
/dev/sdc	500	0	vfat	nosuid,nodev,uhelper=hal,uid=500,utf8,shortname=mixed,flush	/media/_PNG
-2
/dev/sdc	500	0	vfat	nosuid,nodev,uhelper=hal,uid=500,utf8,shortname=mixed,flush	/media/_PNG
-3
/dev/sdc	500	0	vfat	nosuid,nodev,uhelper=hal,uid=500,utf8,shortname=mixed,flush	/media/_PNG
-4
/dev/sdc	500	0	vfat	nosuid,nodev,uhelper=hal,uid=500,utf8,shortname=mixed,flush	/media/_PNG
-5
/dev/sdc	500	0	vfat	nosuid,nodev,uhelper=hal,uid=500,utf8,shortname=mixed,flush	/media/_PNG
-6
/dev/sdc	500	0	vfat	nosuid,nodev,uhelper=hal,uid=500,utf8,shortname=mixed,flush	/media/_PNG
-7
/dev/sdc	500	0	vfat	nosuid,nodev,uhelper=hal,uid=500,utf8,shortname=mixed,flush	/media/_PNG

/dev/sdc	500	0	vfat	nosuid,nodev,uhelper=hal,uid=500,utf8,shortname=mixed,flush	/media/_PNG
-1
/dev/sdc	500	0	vfat	nosuid,nodev,uhelper=hal,uid=500,utf8,shortname=mixed,flush	/media/_PNG
-2
/dev/sdd	500	0	vfat	nosuid,nodev,uhelper=hal,uid=500,utf8,shortname=mixed,flush	/media/_PNG

/dev/sdd	500	0	vfat	nosuid,nodev,uhelper=hal,uid=500,utf8,shortname=mixed,flush	/media/_PNG
-1
/dev/sdd	500	0	vfat	nosuid,nodev,uhelper=hal,uid=500,utf8,shortname=mixed,flush	/media/_PNG

/dev/sdd	500	0	vfat	nosuid,nodev,uhelper=hal,uid=500,utf8,shortname=mixed,flush	/media/_PNG
-1
/dev/sdd	500	0	vfat	nosuid,nodev,uhelper=hal,uid=500,utf8,shortname=mixed,flush	/media/_PNG
-3
/dev/sdd	500	0	vfat	nosuid,nodev,uhelper=hal,uid=500,utf8,shortname=mixed,flush	/media/_PNG

Which didn't seem right to me, so I renamed it and rebooted, and sure enough the second and third issues were corrected.

This just leaves the problem of my device name being seen as "_PNG []" by KDE.

bdjnk · 08-06-2010, 04:05 PM

Thanks to the information in this Ubuntu forum post I have managed to correct the name of the device! And while this may not be a proper 'root of the problem has been dealt with' type solution, it is plenty good enough for me.