yeahhhh.. I tried the r option yesterday. Got the same output.

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:~$

sudo fdisk -l /dev/sdb
[sudo] password for michael:          
Disk /dev/sdb: 28.64 GiB, 30752636928 bytes, 60063744 sectors
Disk model: Ultra          
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x43665e8c

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

On Mon, Jan 16, 2023 at 2:38 PM Rusty Carruth via PLUG-discuss <plug-discuss@lists.phxlinux.org> wrote:
man fsck says:

        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

so zero means no errors without our having to guess (however, it implies
that it did a check, but we're assuming that, so there is a guess there).

You could try the '-r' option to fsck and it will tell you the return
code and some other stuff, supposedly.

Anyway, it would REALLY HELP to know what 'df -h' says.  That would
answer (most of) the questions I still have at this moment.

Oh, how big is the USB stick?  How much room is left?

and what does 'sudo fdisk -l /dev/sdb' say?


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.
>
> "You don't say what you booted on - the USB drive?  And what device is
> that?"
> What do you mean? I'm trying to run thOS from the pen drive? THe device is
> /dev/sdb?
>
> On Mon, Jan 16, 2023 at 2:00 PM Rusty Carruth via PLUG-discuss <
> plug-discuss@lists.phxlinux.org> wrote:
>
>> I think it is probably too early to say if you need a new drive, and I
>> don't know what you mean by 'create persistence', but I'll stick my foot
>> in my mouth and ask a few questions.
>>
>> You don't say what you booted on - the USB drive?  And what device is that?
>>
>> When you run fsck, I suggest you use the -V option (verbose). Also, what
>> is the return code from fsck? that is:
>>
>> sudo fsck -Vf /dev/sdb ; echo $?
>>
>> what number is the last thing before your next prompt?
>>
>> Did you boot from device /dev/sda?  Is anything mounted from /dev/sdb?
>> (e.g. what does 'df -h' say (as one option))
>>
>> Finally, it is safer to do the fdisk commands manually and not use the
>> 'printf' trick.  This works for me on all my systems:
>>
>> echo $usb ; sudo fdisk $usb
>>
>> (then I enter the commands to fdisk to create a new partition, or whatever)
>>
>> Oh, the very first thing I should have asked is, what does 'ls -l
>> /dev/sdb' say?
>>
>> On 1/16/23 11:34, Michael via PLUG-discuss wrote:
>>> maybe that is why it ran out of space?
>>>
>>>
>>> On Mon, Jan 16, 2023 at 12:06 PM Michael <bmike1@gmail.com> wrote:
>>>
>>>> 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~(-:
>>>>
>>>
>>> ---------------------------------------------------
>>> PLUG-discuss mailing list: PLUG-discuss@lists.phxlinux.org
>>> To subscribe, unsubscribe, or to change your mail settings:
>>> https://lists.phxlinux.org/mailman/listinfo/plug-discuss
>> ---------------------------------------------------
>> PLUG-discuss mailing list: PLUG-discuss@lists.phxlinux.org
>> To subscribe, unsubscribe, or to change your mail settings:
>> https://lists.phxlinux.org/mailman/listinfo/plug-discuss
>>
>
>
> ---------------------------------------------------
> PLUG-discuss mailing list: PLUG-discuss@lists.phxlinux.org
> To subscribe, unsubscribe, or to change your mail settings:
> https://lists.phxlinux.org/mailman/listinfo/plug-discuss
---------------------------------------------------
PLUG-discuss mailing list: PLUG-discuss@lists.phxlinux.org
To subscribe, unsubscribe, or to change your mail settings:
https://lists.phxlinux.org/mailman/listinfo/plug-discuss


--
:-)~MIKE~(-: