Re: usb marked as read-only

> michael@desktop1:~$ df -h
> Filesystem      Size  Used Avail Use% Mounted on
> tmpfs           779M  1.5M  777M   1% /run
> /dev/sda2       234G  151G   72G  68% /
> tmpfs           3.8G   84M  3.8G   3% /dev/shm
> tmpfs           5.0M  4.0K  5.0M   1% /run/lock
> /dev/sda1       511M  5.3M  506M   2% /boot/efi
> tmpfs           779M   92K  779M   1% /run/user/1000
> /dev/sdb1        12G   12G     0 100% /media/michael/Kali Live
> /dev/sdb2       876K  868K  8.0K 100% /media/michael/6383-98E2
> michael@desktop1:~$

> Device     Boot    Start      End  Sectors  Size Id Type
> /dev/sdb1  *          64 24395943 24395880 11.6G 17 Hidden HPFS/NTFS
> /dev/sdb2       24395944 24397735     1792  896K  1 FAT12

>>         The exit code returned by fsck is the sum of the following
>> conditions:

>>                0      No errors
>>                1      Filesystem errors corrected
>>                2      System should be rebooted
>>                4      Filesystem errors left uncorrected
>>                8      Operational error
>>                16     Usage or syntax error
>>                32     Checking canceled by user request
>>                128    Shared-library error

>> On 1/16/23 12:22, Michael via PLUG-discuss wrote:
>> > creating persistence means I want to use the drive as if it were the
>> main
>> > drive.
>> > The verbose flag is a big v? I tried the little v!
>> >      sudo fsck -V $usb
>> >     [sudo] password for michael:
>> >     fsck from util-linux 2.37.2
>> > Same thing.
>> >     sudo fsck -Vf /dev/sdb ; echo $?
>> >     fsck from util-linux 2.37.2
>> >     0
>> > I think the zero means there is nothing wrong with the drive.

>> >>>> HI. On my Kali Live USB drive I am trying to create persistence. I
>> did
>> >> it
>> >>>> once but then something happened (it ran out of space when I tried to
>> >>>> install snort) so I started over. But when I tried tpo create
>> >> persistence I
>> >>>> got the read-only error. YOu know in my search to get it out of
>> >> read-only I
>> >>>> discovered that it might mean my file system is corrupted.. But when
>> I
>> >> ran
>> >>>>      $ sudo fsck -f /dev/sdb
>> >>>> it just responded
>> >>>>      fsck from util-linux 2.37.2
>> >>>> then when I attempted to follow the directions (that worked before:
>> >>>>      sudo fdisk $usb <<< $(printf "n\np\n\n\n\nw")
>> >>>>      Welcome to fdisk (util-linux 2.37.2).
>> >>>>      Changes will remain in memory only, until you decide to write
>> them.
>> >>>>      Be careful before using the write command.
>> >>>>      fdisk: cannot open /dev/sdb: Read-only file system
>> >>>> I'm thinking I need a new drive. Anything the gurus know that would
>> be
>> >>>> beneficial before I spend the money on a new drive??
>> >>>> --
>> >>>> :-)~MIKE~(-: