USB Flash Disk Won't Format (Read Only)

[bedna]

sudo umount /dev/sdb1 (or whatever number is mounted, if anything)

[cscs]

I think there might be some confusion here.

When changing permissions or doing things your user does not have rights for … you will need to use something like sudo.

But … regardless of all that … lets help you clean/format the device …

Maybe fdisk would be friendly to use;
First make sure the thing is unmounted:

sudo umount /dev/sdb1

Then you can start fdisk in interactive mode

sudo fdisk /dev/sdb

From there you can hit d for delete and select the partition.
Then hit g to create a new GPT partition table or o for MBR table - as yours seems broken.
Then hit n to create a new partition.
To write/exit hit w.

[alefe]

@megavolt

sudo wipefs --all --force /dev/sdb

not working

``
sudo fdisk /dev/sdb

Welcome to fdisk (util-linux 2.38.1).
Changes will only remain in memory until you decide to save them.
Be careful before using the write command.

fdisk: could not open /dev/sdb: Read-only file system
``

[alefe]

sudo fdisk /dev/sdb

Welcome to fdisk (util-linux 2.38.1).
Changes will only remain in memory until you decide to save them.
Be careful before using the write command.

fdisk: could not open /dev/sdb: Read-only file system

[bedna]

That might be a sign of faulty hardware tbh.
Doesn’t linux automatically put anything in read only mode if it detects hardware irregularities?
Edit. I cross my fingers I am wrong.

[cscs]

@alefe

fdisk: could not open /dev/sdb: Read-only file system

OK … try this:

sudo hdparm -r0 /dev/sdb

(then try mounting or interacting with it again - fdisk, i suppose)

Also please verify your device does not have some sort of hard switch - for example many SD cards may have a little toggle for ‘locking’ which can force this read-only situation.

[megavolt]

@alefe

fdisk: could not open /dev/sdb: Read-only file system

Could be then only:

A) Flash Disk reaches its lifetime, no more write cycles possible, therefore it is readonly.
B) A physical switch let it be locked as read only.

[alefe]

@cscs

(then try mounting or interacting with it again - fdisk, i suppose)

Also please verify your device does not have some sort of hard switch - for example many SD cards may have a little toggle for ‘locking’ which can force this read-only situation.

sudo hdparm -r0 /dev/sdb

/dev/sdb:
 setting readonly to 0 (off)
 readonly      =  1 (on)

Nothing bruh

[alefe]

Right, alternative B would not be possible, because I don’t have a physical switch on this device.
But, considering alternative A, how do you know if it really has reached the end of its useful life?

[megavolt]

@alefe

But, considering alternative A, how do you know if it really has reached the end of its useful life?

Look, every Flash Drive has a Controller and a Flash Memory. The controller controls how much data can be written and how in simple words. There is a hard limit of write cycles, like on any SSD. On dump USB Flash Drives, you can only detect it when you cannot write data on it (create, modify, delete), but still you can read everything.

[alefe]

Got it, from that, I believe that’s the problem then, because everything we tried went down the drain.

[bedna]

You could try installing gsmartcontrol and maybe you might find some info there if you are curious.

pamac install gsmartcontrol

Edit. I revoke that, I tried with a usb stick and it shows nothing, guess it’s not S.M.A.R.T capable. xD
My “ssd” usb stick gave me info though.

[megavolt]

Just an alternative you don’t have a Flash Drive… wrote that myself and I use it on all of my Manjaro systems:

@megavolt

I have a backup OS, which is just a customized Manjaro ISO and I don’t use a flash drive for this.

1. Make some space on sdc and create a 10GB vfat partition and flag it with boot,esp and name the partition and file system “RECOVERY” ( important ).
2. Mount it and install grub on it:

sudo mount --mkdir --label RECOVERY /mnt/recovery
sudo grub-install --target=x86_64-efi --recheck --removable --efi-directory=/mnt/recovery --boot-directory=/mnt/recovery/boot --verbose --force

3. Create an efi entry in your UEFI/BIOS:

 sudo efibootmgr --create --disk /dev/sdX --part <number> --label "Recovery" --loader '\EFI\BOOT\BOOTX64.EFI'

4. Copy a Manjaro ISO to that partition:

sudo cp -f /path/to/manjaro.iso /mnt/recovery/manjaro.iso

5. This script has to be in /mnt/recovery/boot/grub/grub.cfg (create it):

function load_video {
  if [ x$feature_all_video_module = xy ]; then
    insmod all_video
  else
    insmod efi_gop
    insmod efi_uga
    insmod ieee1275_fb
    insmod vbe
    insmod vga
    insmod video_bochs
    insmod video_cirrus
  fi
}

if loadfont $prefix/fonts/unicode.pf2 ; then
  # Set Video
  set gfxmode=auto
  load_video
  insmod gfxterm
  # Set Langauge for grub
  set locale_dir="$prefix/locale"
  set lang="de"
  insmod gettext
fi

# Set keyboard language for grub
#insmod keylayouts
#keymap $prefix/lang.gkb

terminal_input console
terminal_output gfxterm

insmod part_gpt
insmod part_msdos
insmod fat
set label="RECOVERY"
search --no-floppy --label --set=root $label
insmod png

set timeout_style="menu"
set timeout="10"

menuentry "Manjaro ISO"  {
    # Setup grub
    load_video
    set gfxpayload=keep
    insmod part_gpt
    insmod part_msdos
    insmod fat

    ## Set Parameters for the ISO
    # Set the free or nonfree drivers
    set dri="free"
    # Set the language of the Desktop (localectl list-locales)
    set lang="de_DE"
    # Set keyboard language (localectl list-keymaps)
    set keyboard="de"
    # Set the timezone (timedatectl list-timezones)
    set timezone="Europe/Berlin"
    # Copy to RAM (needs at least 8GB RAM)
    #set c2r="copy2ram"

    # Set Params searching the ISO
    # Label of the partition where it searches for the iso file
    set label="RECOVERY"
    # Search for the partition label and switch to the root directory of it
    search --no-floppy --label --set=root $label
    # Set the device where the ISO is located
    set device="/dev/disk/by-label/$label"
    # Set the Path to the ISO
    set file="/manjaro.iso"

    loopback loop $file
    linux  (loop)/boot/vmlinuz-x86_64  img_dev=$dev img_loop=$file driver=$dri tz=$timezone lang=$lang keytable=$keyboard $cr2
    initrd (loop)/boot/intel_ucode.img (loop)/boot/initramfs-x86_64.img
}

6. And now you are done. You can now reboot, type F12 and choose “Recovery” from the Bootmenu. This little installation is fully dedicated and even work when your main installation is non-functional. You can also do a full installation form here.

You need to adjust the parameter in menu to your language. Parameters are mostly explained. If you have an amd CPU, then replace intel_ucode.img with amd_ucode.img.

[alefe]

I’ll try this another time. Thanks!

[bedna]

@megavolt Wow, I’m def bookmarking that for playing around with, I have played around with mounting isos directly in my standard grub, this is a very nice reference! Thank you!

To use nvidia do I only have to change set dri="free" to nonfree, or does this still bring up the grub menu (I see a timeout) and this is just the menu chooser will be at default?

[megavolt]

@bedna

To use nvidia do I only have to change set dri="free" to nonfree, or does this still bring up the grub menu (I see a timeout) and this is just the menu chooser will be at default?

You see the Grub Menu, where you can choose to boot the ISO. The grub menu of the ISO will be skipped, since all parameters are already set.

[bedna]

Ah, I see, thank you very much for this, I will def play around with it!

[jrichard326]

Would this work to zero the critical initial sectors when normal formatting tools don’t work?

dd if=/dev/zero of=/dev/sdY bs=4k count=1 status=progress

where “Y” in sdY is the actual USB drive.

[linux-aarhus]

@bedna

I have played around with mounting isos directly in my standard grub

It has been around for a long time in Tutorials section

• [HowTo] Boot Manjaro ISO directly with GRUB

@alefe

sudo chown -R $USER /dev/sdb

You cannot do that - the command may return OK but it won’t work.

In the Tutorials section is a utility script to handle the task

• [root tip] [Utility script] Repartition and format your USB stick

If @cscs suggestion in #10 is failing - it is likely end of life - it happens more often than you think.

[JohnML]

Simple alternative is install package
grml-rescueboot

See also explanation for Debian
http://wiki.grml.org/doku.php?id=rescueboot

Now its as simple as copy your *.iso to
/boot/grml/
then update-grub and you have aditional boot entry for your *.iso