USB Memorystick cylinder size / no of cylinders misreported
Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?
Notices
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.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
USB Memorystick cylinder size / no of cylinders misreported
Hi,
I'm experiencing some mayor issues with a USB memorystick. Something strange happend to it while plugged into a SuSE 10.0 box. In some way the originally 2.0 Gb stick is now reported as 1 Tb. It's not that I mind the extra capacity, if the result of this was not that I now can no longer use the disk at all.
I have a feeling that it's caused by the fact that the cylinder size of the stick is now reported as 7.84 Mb (which can be too big) or the fact that the number of cylinders is now set to 133673 (which seems a bit too many).
Does anybody have a suggestion on how to fix this?
This usually happens when the flash memory is uncleanly removed (not unmounted). These devices use FAT/VFAT filesystems, and they are trivially easy to damage. Remember how often you had to run chkdisk with FAT on DOS/Windows?
The solution is usually the same. Plug in the device, but don't mount it. Run:
dosfsck -a -w /dev/sdxy
(where /dev/sdxy is the device name)
Alternatively, plug it into a Windows machine and run chkdisk on it.
Thanks. However, in the mean time I managed to destroy the USB stick even furthter. (Don't know how I did that but I guess it has something to do with my attempt to change the number of cylinders on the device using fdisk).
As a result it's now completely useless (doesn't see any media anymore at all, I even plugged it in a Windows machine, which asks me to insert media into the drive).
Anyway, the vendor has kindly agreed to send me a new USB stick, so I guess that takes care of the problem.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.