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.
Hello.
I have a Flash drive with below information :
Code:
Bus 003 Device 004: ID 090c:1000 Silicon Motion, Inc. - Taiwan (formerly Feiya Technology Corp.) 64MB QDI U2 DISK
I did below commands on Linux and you can see their result :
Code:
sudo mkfs.ext2 /dev/sdc
mke2fs 1.42.5 (29-Jul-2012)
/dev/sdc is entire device, not just one partition!
Proceed anyway? (y,n) y
/dev/sdc: Read-only file system while setting up superblock
Code:
sudo fsck -fy /dev/sdc
fsck from util-linux 2.20.1
e2fsck 1.42.5 (29-Jul-2012)
fsck.ext2: Read-only file system while trying to open /dev/sdc
Disk write-protected; use the -n option to do a read-only
check of the device.
sudo dumpe2fs /dev/sdc
dumpe2fs 1.42.5 (29-Jul-2012)
dumpe2fs: Bad magic number in super-block while trying to open /dev/sdc
Couldn't find valid filesystem superblock.
Bad magic number in super-block while trying to open /dev/sdc
Couldn't find valid filesystem superblock.
One thing that might work is to find a Windows computer and reformat the drive with Windows. I've rescued a couple micro SD cards this way for sure, and I think I've rescued a USB thumbdrive or two in the past. Basically, I wanted to format the SD cards to ext2, but no matter how many times I tried, I'd get that error when trying to mount the card a second time. And gparted couldn't deal with it. But I could reformat it on a Windows 7 computer.
One thing that might work is to find a Windows computer and reformat the drive with Windows. I've rescued a couple micro SD cards this way for sure, and I think I've rescued a USB thumbdrive or two in the past. Basically, I wanted to format the SD cards to ext2, but no matter how many times I tried, I'd get that error when trying to mount the card a second time. And gparted couldn't deal with it. But I could reformat it on a Windows 7 computer.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.