Newer USB stick: scsi 10:0:0:0: Direct-Access SanDisk Cruzer Switch 1.26 PQ: 0 ANSI: 6 I then compared the dmesg output for the two sticks: Had I bought a bad USB stick? It formatted without issue and I could write to it and read from it without any errors. The script kept complaining that my new USB stick was not! I found an older SanDisk USB stick and with that one, my script ran without error. The script I was using to configure it had a check to make sure the disk target (e.g./dev/sdb) I was installing Linux onto was removable media. I had purchased a new SanDisk USB stick to boot Linux. Then you have to decide why.I came across something curious last week that failed the question:Ĭan I find a quick answer for this in Google? To restore it you have to hunt for the tool that can reset the controller, or the tools used on "certain websites" that are to be "trusted" running on your machine, both options results in the obliteration of the data already on the stick. So we end up having your public partition go read only for no known reason other than an actual failure or a bug. So yeah, all that fancy stuff we don't have. ![]() No more unetbootin or Rufus trying to create a bootable USB out of an ISO, just upload a bootable ISO and boom, bootable CDROM. Upload a ISO to this partition and bingo, plug the stick in and your public/private partitions appear alongside a read only usb CDROM drive! Alongside your public and private partition you can also have a CDROM partition. One killer feature is the CD ROM drive emulator. The controller could encrypt if they wanted it to. This wouldn't have been encrypted, just unmountable without the password. ![]() In fact many flash drives used to come with software that could activate and deactivate that feature. You can have a public and a password protected private partition. First, you can have a writable public partition then a read only public partition, or the whole flash drive can be one big read only public partition, which is what yours has turned into. If you create partitions, they are inside the public partition, like an onion the flash controller partition is a layer above. It is this space that you access when using the drive. As supplied from the store flash drives just have 1 partition, the public partition. ![]() It's a shame we (the public) didn't get these tools as it allows so many cool features of flash drives that are basically denied, such as the hardware enforcement of write protection.īy reading flash controller data sheets I recently learned that they can partition the flash chip. It is worth looking if SanDisk have a repair tool. Sometimes they release a tool that will simply restore the controller to factory default configuration.Įither way the data will be lost when doing this. Manufacturers annoyingly don't release these tools so they are typically found on "certain websites". The only way to bring it back is to use the MP (mass production) tools to reprogram the firmware. The firmware of the controller has put it into write protection mode because either there is something wrong with writing data or the firmware has a bug that tripped the feature. Just make sure to tag the post with the flair and give a little background info/context. On Fridays we'll allow posts that don't normally fit in the usual data-hoarding theme, including posts that would usually be removed by rule 4: “No memes or 'look at this '”
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |