Sudo mount -o uid=1000 /dev/sdb1 /media/andrew/temp Unmount it, and make it writeable sudo umount /dev/sdb1Ĭreate a new mount point and mount it there (my userID from /etc/passwd is 1000) sudo mkdir /media/andrew/temp Ubuntu mounted it automatically on /media/andrew/6AB0-1FD91, and dmesg showed the partition to be /dev/sdb1.
Plug in the card (mine is an SD card with a manual write-protect switch on it, but the switch is off and it is writable on a Windows machine). It's working great to this day!Īngel's answer is good, but the actual commands weren't so easy for me. I opened the case, shaved some of the plastic casing away to give the PCB some wiggle room and then reflowed the NAND chip to repair the broken solder joints. Rather than doing yet another RMA, I took matters into my own hands.
But for this particular model, it seems to have had weak solder joints that the pressure from the sliding action exacerbated - leading to oxidation in the cracked joint and eventual failure. Ordinarily, this wouldn't have caused an issue in the normal life span of the device. The sliding mechanism seems to put a small amount of pressure on the PCB. The problem actually turned out to be mechanical.
Update 2: Regarding that Corsair Flash Voyager, I sent mine in for an RMA, only to have my second one fail on me in the same fashion. Since this is one of my more popular answers and this also falls into the category of "failing flash drives," I figured I'd include it here for reference. This was a result of the drive having accrued a large amount of bad sectors and dropping into diagnostic/programming mode. While it didn't show the symptoms noted here, it occasionally would not mount and showed up as a "Silicon Power" device.
In my case, this was a Corsair Flash Voyager 128GB that started slowing down pretty drastically on me. I hate to break the bad news to you =\ but it appears you're out of luck in this situation as everything I've read points to hardware failure.Įdit : I experienced an issue personally with a flash drive flaking out on me recently. If you still have this drive and it's still in warranty I'd return it and get a replacement. People had tried opening them and jumping two leads (maybe from a flaky switch?) to no avail. Mkfs -t vfat /dev/sdb1 mkfs.vfat 3.0.9 ()Īfter researching your question it appears that this is a not-too-uncommon problem with certain brands of USB flash drives (some older Samsung, a Kingston model) that would essentially just "crap out" for no known reason. There are differences between boot sector and its backup.įree cluster summary wrong (968250 vs.
Used Google and have seen about 10,000 discussions about this problem but they were never solvedįsck -n /dev/sdb1 fsck from util-linux 2.19.1.Tried to fix this with several tools from Ubuntu software center.Tried to format it on windows and on Linux (via terminal too).Checked if it has a hardware switch - no.sd 7:0:0:0: Attached SCSI removable disk sd 7:0:0:0: Assuming drive cache: write through sd 7:0:0:0: No Caching mode page present Dmesg | tail sd 7:0:0:0: Write Protect is on