Re: usb marked as read-only

2023-01-16 Thread Michael via PLUG-discuss 
maybe that is why it ran out of space?


On Mon, Jan 16, 2023 at 12:06 PM Michael  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~(-:
>


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

Re: usb marked as read-only

2023-01-16 Thread Rusty Carruth via PLUG-discuss 
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  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

Re: usb marked as read-only

2023-01-16 Thread Michael via PLUG-discuss 
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  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
>


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

Re: usb marked as read-only

2023-01-16 Thread Stephen Partington via PLUG-discuss 
I know some USB devices when they reach a critical fault level will go
read-only when there are no longer any write cycles that can be safely
applied. like SSD's But I haven ever run into it to verify.

On Mon, Jan 16, 2023 at 2:23 PM Michael via PLUG-discuss <
plug-discuss@lists.phxlinux.org> 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  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
>>
>
>
> --
> :-)~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
>


-- 
A mouse trap, placed on top of your alarm clock, will prevent you from
rolling over and going back to sleep after you hit the snooze button.

Stephen
---
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

Re: usb marked as read-only

2023-01-16 Thread Michael via PLUG-discuss 
Ok, thanks. Funny thing is when I unmount it it keeps flashing. It even
keeps flashing after I eject it..

On Mon, Jan 16, 2023 at 2:24 PM Stephen Partington 
wrote:

> I know some USB devices when they reach a critical fault level will go
> read-only when there are no longer any write cycles that can be safely
> applied. like SSD's But I haven ever run into it to verify.
>
> On Mon, Jan 16, 2023 at 2:23 PM Michael via PLUG-discuss <
> plug-discuss@lists.phxlinux.org> 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  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
>>>
>>
>>
>> --
>> :-)~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
>>
>
>
> --
> A mouse trap, placed on top of your alarm clock, will prevent you from
> rolling over and going back to sleep after you hit the snooze button.
>
> Stephen
>
>

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

Re: usb marked as read-only

2023-01-16 Thread Rusty Carruth via PLUG-discuss 

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  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

Re: usb marked as read-only

2023-01-16 Thread Michael via PLUG-discuss 
yea.. 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/sdb112G   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 BootStart  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
>128Shared-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  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.
>

Re: usb marked as read-only

2023-01-16 Thread Michael via PLUG-discuss 
sorry forgot to prove it:
   usb=/dev/sdb
   sudo fsck -r $usb
   [sudo] password for michael:
   fsck from util-linux 2.37.2

On Mon, Jan 16, 2023 at 2:47 PM Michael  wrote:

> yea.. 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/sdb112G   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 BootStart  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
>>128Shared-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  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

Re: usb marked as read-only

2023-01-16 Thread Eric Oyen via PLUG-discuss 
I had one of those a few years back. I had many of the same issues and it 
turned out that it had failed because there were no left over sectors that 
could be written after marking bad and choosing spare. Also, the flashing light 
after eject is an indication that the firmware has suffered a fatal error, 
resulting in a read only system on the device. However, this is not the only 
cause of the condition you describe.

Possible conditions:
1. USB drive infected with malware that attempted to overwrite firmware
2. Damaged USB port (try a new port?)
3. Old/outdated or corrupted USB driver/module
4. USB firmware failure resulting in read only FS access
5. Max write cycles reached (usually caused by bad memory locations on board.

Now, depending on the size, speed and other particulars of your USB device, it 
might just be easier to purchase a new one from amazon, Best Buy or other 
retail outlet. For most things, I use USB sticks in a write once, read many 
configuration scenario. Things like photos, documents and even a media library 
can be stored on these. So long as I don’t need to write very many times, the 
stick will perform very well over it’s useful life. I have a few of the older 
sub 4GB sticks around here that are at least 10 years old and still work 
nicely. Of course, I wrote my media collection to them and then only use them 
for playing my music or listening to my legally downloaded videos. :)

-Eric
From the Central Offices of the Technomage Guild, Media Services Dept.


> On Jan 16, 2023, at 12:34 PM, Michael via PLUG-discuss 
>  wrote:
> 
> Ok, thanks. Funny thing is when I unmount it it keeps flashing. It even keeps 
> flashing after I eject it..
> 
> On Mon, Jan 16, 2023 at 2:24 PM Stephen Partington  > wrote:
> I know some USB devices when they reach a critical fault level will go 
> read-only when there are no longer any write cycles that can be safely 
> applied. like SSD's But I haven ever run into it to verify.
> 
> On Mon, Jan 16, 2023 at 2:23 PM Michael via PLUG-discuss 
> mailto:plug-discuss@lists.phxlinux.org>> 
> 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 
> mailto: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  > > 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~(-:
> >>
> >
> >
> > ---

Re: usb marked as read-only

2023-01-16 Thread Steve Litt via PLUG-discuss 
Eric Oyen via PLUG-discuss said on Mon, 16 Jan 2023 16:38:57 -0700

>For most things, I use USB sticks in
>a write once, read many configuration scenario.

Another thing I've found anecdotally that helps lengthen the USB stick
life, whether write once or write a bunch, is to format it as Ext4. I
don't think I ever had one go bad as Ext4, but I have with the windows
format they're shipped with. Of course, if you have to interact with
windows computers or devices expecting windows formated USB sticks, my
trick becomes useless.

SteveT

Steve Litt 
Autumn 2022 featured book: Thriving in Tough Times
http://www.troubleshooters.com/bookstore/thrive.htm
---
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

Re: usb marked as read-only

2023-01-16 Thread Michael via PLUG-discuss 
lovely, my 32gb ultra is toast. I started gparted to see if I could format
it and the square showing the partitions and usage is gray (as well as the
file system icon).

On Mon, Jan 16, 2023 at 7:16 PM Steve Litt via PLUG-discuss <
plug-discuss@lists.phxlinux.org> wrote:

> Eric Oyen via PLUG-discuss said on Mon, 16 Jan 2023 16:38:57 -0700
>
> >For most things, I use USB sticks in
> >a write once, read many configuration scenario.
>
> Another thing I've found anecdotally that helps lengthen the USB stick
> life, whether write once or write a bunch, is to format it as Ext4. I
> don't think I ever had one go bad as Ext4, but I have with the windows
> format they're shipped with. Of course, if you have to interact with
> windows computers or devices expecting windows formated USB sticks, my
> trick becomes useless.
>
> SteveT
>
> Steve Litt
> Autumn 2022 featured book: Thriving in Tough Times
> http://www.troubleshooters.com/bookstore/thrive.htm
> ---
> 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~(-:
---
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

Re: usb marked as read-only

2023-01-16 Thread Michael via PLUG-discuss 
any advice before I toss it? I suppose I could buy a chain and wear it
around my neck!

On Mon, Jan 16, 2023 at 7:53 PM Michael  wrote:

> lovely, my 32gb ultra is toast. I started gparted to see if I could format
> it and the square showing the partitions and usage is gray (as well as the
> file system icon).
>
> On Mon, Jan 16, 2023 at 7:16 PM Steve Litt via PLUG-discuss <
> plug-discuss@lists.phxlinux.org> wrote:
>
>> Eric Oyen via PLUG-discuss said on Mon, 16 Jan 2023 16:38:57 -0700
>>
>> >For most things, I use USB sticks in
>> >a write once, read many configuration scenario.
>>
>> Another thing I've found anecdotally that helps lengthen the USB stick
>> life, whether write once or write a bunch, is to format it as Ext4. I
>> don't think I ever had one go bad as Ext4, but I have with the windows
>> format they're shipped with. Of course, if you have to interact with
>> windows computers or devices expecting windows formated USB sticks, my
>> trick becomes useless.
>>
>> SteveT
>>
>> Steve Litt
>> Autumn 2022 featured book: Thriving in Tough Times
>> http://www.troubleshooters.com/bookstore/thrive.htm
>> ---
>> 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~(-:
>


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

Re: usb marked as read-only

2023-01-16 Thread Michael via PLUG-discuss 
yeah. I think all is loast. I finally got around to looking at the gparted
report:


Device: /dev/sdd
Model: SanDisk Ultra
Serial:
Sector size: 512
Total sectors: 60063744

Heads: 255
Sectors/track: 2
Cylinders: 117772

Partition table: none

PartitionTypeStartEndFlagsPartition NameFile SystemLabelMount Point
/dev/sdd Unpartitioned 0 60063743 iso9660 Kali Live


*Format /dev/sdd as ext4*  00:00:17( ERROR )

calibrate /dev/sdd  00:00:00( SUCCESS )




*path: /dev/sdd (device)start: 0end: 60063743size: 60063744 (28.64 GiB)*
clear old file system signatures in /dev/sdd  00:00:17( ERROR )

write 512.00 KiB of zeros at byte offset 0  00:00:17( ERROR )

libparted messages( ERROR )

*Unable to open /dev/sdd read-write (Read-only file system). /dev/sdd has
been opened read-only.*
*Can't write to /dev/sdd, because it is opened read-only.*
*Can't write to /dev/sdd, because it is opened read-only.*

On Mon, Jan 16, 2023 at 7:55 PM Michael  wrote:

> any advice before I toss it? I suppose I could buy a chain and wear it
> around my neck!
>
> On Mon, Jan 16, 2023 at 7:53 PM Michael  wrote:
>
>> lovely, my 32gb ultra is toast. I started gparted to see if I could
>> format it and the square showing the partitions and usage is gray (as
>> well as the file system icon).
>>
>> On Mon, Jan 16, 2023 at 7:16 PM Steve Litt via PLUG-discuss <
>> plug-discuss@lists.phxlinux.org> wrote:
>>
>>> Eric Oyen via PLUG-discuss said on Mon, 16 Jan 2023 16:38:57 -0700
>>>
>>> >For most things, I use USB sticks in
>>> >a write once, read many configuration scenario.
>>>
>>> Another thing I've found anecdotally that helps lengthen the USB stick
>>> life, whether write once or write a bunch, is to format it as Ext4. I
>>> don't think I ever had one go bad as Ext4, but I have with the windows
>>> format they're shipped with. Of course, if you have to interact with
>>> windows computers or devices expecting windows formated USB sticks, my
>>> trick becomes useless.
>>>
>>> SteveT
>>>
>>> Steve Litt
>>> Autumn 2022 featured book: Thriving in Tough Times
>>> http://www.troubleshooters.com/bookstore/thrive.htm
>>> ---
>>> 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~(-:
>>
>
>
> --
> :-)~MIKE~(-:
>


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

Re: usb marked as read-only

2023-01-16 Thread Eric Oyen via PLUG-discuss 
There is one thing you can try before absolutely tossing it. Run dd as root 
with the following code: sudo dd if=/dev/zero of=/dev/sdb
And let her run. That should erase everything on that stick, including 
partition info, boot sector and the like.

If there is a problem, dd will very quickly quit with an error.

-Eric
From the Central Offices of the Technomage Guild, Hardware dispositions Dept.


> On Jan 16, 2023, at 7:23 PM, Michael via PLUG-discuss 
>  wrote:
> 
> yeah. I think all is loast. I finally got around to looking at the gparted 
> report:
> 
> 
> 
> Device:   /dev/sdd
> Model:SanDisk Ultra
> Serial:   
> Sector size:  512
> Total sectors:60063744
>  
> Heads:255
> Sectors/track:2
> Cylinders:117772
>  
> Partition table:  none
>  
> Partition TypeStart   End Flags   Partition Name  File System 
> Label   Mount Point
> /dev/sdd  Unpartitioned   0   60063743iso9660 
> Kali Live   
> 
> 
> Format /dev/sdd as ext4  00:00:17( ERROR )
>   
> calibrate /dev/sdd  00:00:00( SUCCESS )
>   
> path: /dev/sdd (device)
> start: 0
> end: 60063743
> size: 60063744 (28.64 GiB)
> clear old file system signatures in /dev/sdd  00:00:17( ERROR )
>   
> write 512.00 KiB of zeros at byte offset 0  00:00:17( ERROR )
>   
> libparted messages( ERROR )
>   
> Unable to open /dev/sdd read-write (Read-only file system). /dev/sdd has been 
> opened read-only.
> Can't write to /dev/sdd, because it is opened read-only.
> Can't write to /dev/sdd, because it is opened read-only.
> 
> On Mon, Jan 16, 2023 at 7:55 PM Michael  > wrote:
> any advice before I toss it? I suppose I could buy a chain and wear it around 
> my neck!
> 
> On Mon, Jan 16, 2023 at 7:53 PM Michael  > wrote:
> lovely, my 32gb ultra is toast. I started gparted to see if I could format it 
> and the square showing the partitions and usage is gray (as well as the file 
> system icon).
> 
> On Mon, Jan 16, 2023 at 7:16 PM Steve Litt via PLUG-discuss 
> mailto:plug-discuss@lists.phxlinux.org>> 
> wrote:
> Eric Oyen via PLUG-discuss said on Mon, 16 Jan 2023 16:38:57 -0700
> 
> >For most things, I use USB sticks in
> >a write once, read many configuration scenario.
> 
> Another thing I've found anecdotally that helps lengthen the USB stick
> life, whether write once or write a bunch, is to format it as Ext4. I
> don't think I ever had one go bad as Ext4, but I have with the windows
> format they're shipped with. Of course, if you have to interact with
> windows computers or devices expecting windows formated USB sticks, my
> trick becomes useless.
> 
> SteveT
> 
> Steve Litt 
> Autumn 2022 featured book: Thriving in Tough Times
> http://www.troubleshooters.com/bookstore/thrive.htm 
> 
> ---
> 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~(-:
> 
> 
> -- 
> :-)~MIKE~(-:
> 
> 
> -- 
> :-)~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

Re: usb marked as read-only

2023-01-17 Thread Michael via PLUG-discuss 
I tried 'wipe' on it last night. But got the same error message:
sudo dd if=/dev/zero of=/dev/sdb
[sudo] password for michael:
dd: failed to open '/dev/sdb': Read-only file system

On Tue, Jan 17, 2023 at 12:03 AM Eric Oyen via PLUG-discuss <
plug-discuss@lists.phxlinux.org> wrote:

> There is one thing you can try before absolutely tossing it. Run dd as
> root with the following code: sudo dd if=/dev/zero of=/dev/sdb
> And let her run. That should erase everything on that stick, including
> partition info, boot sector and the like.
>
> If there is a problem, dd will very quickly quit with an error.
>
> -Eric
> From the Central Offices of the Technomage Guild, Hardware dispositions
> Dept.
>
>
> On Jan 16, 2023, at 7:23 PM, Michael via PLUG-discuss <
> plug-discuss@lists.phxlinux.org> wrote:
>
> yeah. I think all is loast. I finally got around to looking at the gparted
> report:
>
> 
> Device: /dev/sdd
> Model: SanDisk Ultra
> Serial:
> Sector size: 512
> Total sectors: 60063744
>
> Heads: 255
> Sectors/track: 2
> Cylinders: 117772
>
> Partition table: none
>
> PartitionTypeStartEndFlagsPartition NameFile SystemLabelMount Point
> /dev/sdd Unpartitioned 0 60063743 iso9660 Kali Live
>
> 
> *Format /dev/sdd as ext4*  00:00:17( ERROR )
>
> calibrate /dev/sdd  00:00:00( SUCCESS )
>
>
>
>
> *path: /dev/sdd (device)start: 0end: 60063743size: 60063744 (28.64 GiB)*
> clear old file system signatures in /dev/sdd  00:00:17( ERROR )
>
> write 512.00 KiB of zeros at byte offset 0  00:00:17( ERROR )
>
> libparted messages( ERROR )
>
> *Unable to open /dev/sdd read-write (Read-only file system). /dev/sdd has
> been opened read-only.*
> *Can't write to /dev/sdd, because it is opened read-only.*
> *Can't write to /dev/sdd, because it is opened read-only.*
>
> On Mon, Jan 16, 2023 at 7:55 PM Michael  wrote:
>
>> any advice before I toss it? I suppose I could buy a chain and wear it
>> around my neck!
>>
>> On Mon, Jan 16, 2023 at 7:53 PM Michael  wrote:
>>
>>> lovely, my 32gb ultra is toast. I started gparted to see if I could
>>> format it and the square showing the partitions and usage is gray (as
>>> well as the file system icon).
>>>
>>> On Mon, Jan 16, 2023 at 7:16 PM Steve Litt via PLUG-discuss <
>>> plug-discuss@lists.phxlinux.org> wrote:
>>>
 Eric Oyen via PLUG-discuss said on Mon, 16 Jan 2023 16:38:57 -0700

 >For most things, I use USB sticks in
 >a write once, read many configuration scenario.

 Another thing I've found anecdotally that helps lengthen the USB stick
 life, whether write once or write a bunch, is to format it as Ext4. I
 don't think I ever had one go bad as Ext4, but I have with the windows
 format they're shipped with. Of course, if you have to interact with
 windows computers or devices expecting windows formated USB sticks, my
 trick becomes useless.

 SteveT

 Steve Litt
 Autumn 2022 featured book: Thriving in Tough Times
 http://www.troubleshooters.com/bookstore/thrive.htm
 ---
 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~(-:
>>>
>>
>>
>> --
>> :-)~MIKE~(-:
>>
>
>
> --
> :-)~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
>


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

Re: usb marked as read-only

2023-01-17 Thread Rusty Carruth via PLUG-discuss 
are you running that command while booted on the stick you are trying to 
erase?


While that SHOULD work, you are writing over the device you are booted 
on, not usually considered best practice ;-)  And this 
'read-only-filesystem' message is interesting to me, I'd love to have 
that stick to play with just to see, but it probably isn't worth it.



Anyway:


I've wanted to come back and say that from what I've seen before the 
whole 'drive is toast' path was that the partition  you have been trying 
to make on the stick appears to have been correctly created and 
formatted.  This implies you just need to start at that step in the how-to.


But if you are convinced the stick is dead, the cost of time dealing 
with it is more than the cost of a new stick, go get a new stick and 
start over.


On 1/17/23 06:52, Michael via PLUG-discuss wrote:

I tried 'wipe' on it last night. But got the same error message:
sudo dd if=/dev/zero of=/dev/sdb
[sudo] password for michael:
dd: failed to open '/dev/sdb': Read-only file system

On Tue, Jan 17, 2023 at 12:03 AM Eric Oyen via PLUG-discuss <
plug-discuss@lists.phxlinux.org> wrote:


There is one thing you can try before absolutely tossing it. Run dd as
root with the following code: sudo dd if=/dev/zero of=/dev/sdb
And let her run. That should erase everything on that stick, including
partition info, boot sector and the like.

If there is a problem, dd will very quickly quit with an error.

-Eric
 From the Central Offices of the Technomage Guild, Hardware dispositions
Dept.


On Jan 16, 2023, at 7:23 PM, Michael via PLUG-discuss <
plug-discuss@lists.phxlinux.org> wrote:

yeah. I think all is loast. I finally got around to looking at the gparted
report:


Device: /dev/sdd
Model: SanDisk Ultra
Serial:
Sector size: 512
Total sectors: 60063744

Heads: 255
Sectors/track: 2
Cylinders: 117772

Partition table: none

PartitionTypeStartEndFlagsPartition NameFile SystemLabelMount Point
/dev/sdd Unpartitioned 0 60063743 iso9660 Kali Live


*Format /dev/sdd as ext4*  00:00:17( ERROR )

calibrate /dev/sdd  00:00:00( SUCCESS )




*path: /dev/sdd (device)start: 0end: 60063743size: 60063744 (28.64 GiB)*
clear old file system signatures in /dev/sdd  00:00:17( ERROR )

write 512.00 KiB of zeros at byte offset 0  00:00:17( ERROR )

libparted messages( ERROR )

*Unable to open /dev/sdd read-write (Read-only file system). /dev/sdd has
been opened read-only.*
*Can't write to /dev/sdd, because it is opened read-only.*
*Can't write to /dev/sdd, because it is opened read-only.*

On Mon, Jan 16, 2023 at 7:55 PM Michael  wrote:


any advice before I toss it? I suppose I could buy a chain and wear it
around my neck!

On Mon, Jan 16, 2023 at 7:53 PM Michael  wrote:


lovely, my 32gb ultra is toast. I started gparted to see if I could
format it and the square showing the partitions and usage is gray (as
well as the file system icon).

On Mon, Jan 16, 2023 at 7:16 PM Steve Litt via PLUG-discuss <
plug-discuss@lists.phxlinux.org> wrote:


Eric Oyen via PLUG-discuss said on Mon, 16 Jan 2023 16:38:57 -0700


For most things, I use USB sticks in
a write once, read many configuration scenario.

Another thing I've found anecdotally that helps lengthen the USB stick
life, whether write once or write a bunch, is to format it as Ext4. I
don't think I ever had one go bad as Ext4, but I have with the windows
format they're shipped with. Of course, if you have to interact with
windows computers or devices expecting windows formated USB sticks, my
trick becomes useless.

SteveT

Steve Litt
Autumn 2022 featured book: Thriving in Tough Times
http://www.troubleshooters.com/bookstore/thrive.htm
---
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~(-:



--
:-)~MIKE~(-:



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

Re: usb marked as read-only

2023-01-17 Thread Michael via PLUG-discuss 
On Tue, Jan 17, 2023 at 1:05 PM Rusty Carruth via PLUG-discuss <
plug-discuss@lists.phxlinux.org> wrote:

> are you running that command while booted on the stick you are trying to
> erase?
>
>
Of course not. Always unmount the device.
I threw it away before I got this message so
But the other drive look at the other thread.


> While that SHOULD work, you are writing over the device you are booted
> on, not usually considered best practice ;-)  And this
> 'read-only-filesystem' message is interesting to me, I'd love to have
> that stick to play with just to see, but it probably isn't worth it.
>
>
> Anyway:
>
>
> I've wanted to come back and say that from what I've seen before the
> whole 'drive is toast' path was that the partition  you have been trying
> to make on the stick appears to have been correctly created and
> formatted.  This implies you just need to start at that step in the how-to.
>
> But if you are convinced the stick is dead, the cost of time dealing
> with it is more than the cost of a new stick, go get a new stick and
> start over.
>
> On 1/17/23 06:52, Michael via PLUG-discuss wrote:
> > I tried 'wipe' on it last night. But got the same error message:
> > sudo dd if=/dev/zero of=/dev/sdb
> > [sudo] password for michael:
> > dd: failed to open '/dev/sdb': Read-only file system
> >
> > On Tue, Jan 17, 2023 at 12:03 AM Eric Oyen via PLUG-discuss <
> > plug-discuss@lists.phxlinux.org> wrote:
> >
> >> There is one thing you can try before absolutely tossing it. Run dd as
> >> root with the following code: sudo dd if=/dev/zero of=/dev/sdb
> >> And let her run. That should erase everything on that stick, including
> >> partition info, boot sector and the like.
> >>
> >> If there is a problem, dd will very quickly quit with an error.
> >>
> >> -Eric
> >>  From the Central Offices of the Technomage Guild, Hardware dispositions
> >> Dept.
> >>
> >>
> >> On Jan 16, 2023, at 7:23 PM, Michael via PLUG-discuss <
> >> plug-discuss@lists.phxlinux.org> wrote:
> >>
> >> yeah. I think all is loast. I finally got around to looking at the
> gparted
> >> report:
> >>
> >> 
> >> Device: /dev/sdd
> >> Model: SanDisk Ultra
> >> Serial:
> >> Sector size: 512
> >> Total sectors: 60063744
> >>
> >> Heads: 255
> >> Sectors/track: 2
> >> Cylinders: 117772
> >>
> >> Partition table: none
> >>
> >> PartitionTypeStartEndFlagsPartition NameFile SystemLabelMount Point
> >> /dev/sdd Unpartitioned 0 60063743 iso9660 Kali Live
> >>
> >> 
> >> *Format /dev/sdd as ext4*  00:00:17( ERROR )
> >>
> >> calibrate /dev/sdd  00:00:00( SUCCESS )
> >>
> >>
> >>
> >>
> >> *path: /dev/sdd (device)start: 0end: 60063743size: 60063744 (28.64 GiB)*
> >> clear old file system signatures in /dev/sdd  00:00:17( ERROR )
> >>
> >> write 512.00 KiB of zeros at byte offset 0  00:00:17( ERROR )
> >>
> >> libparted messages( ERROR )
> >>
> >> *Unable to open /dev/sdd read-write (Read-only file system). /dev/sdd
> has
> >> been opened read-only.*
> >> *Can't write to /dev/sdd, because it is opened read-only.*
> >> *Can't write to /dev/sdd, because it is opened read-only.*
> >>
> >> On Mon, Jan 16, 2023 at 7:55 PM Michael  wrote:
> >>
> >>> any advice before I toss it? I suppose I could buy a chain and wear it
> >>> around my neck!
> >>>
> >>> On Mon, Jan 16, 2023 at 7:53 PM Michael  wrote:
> >>>
>  lovely, my 32gb ultra is toast. I started gparted to see if I could
>  format it and the square showing the partitions and usage is gray (as
>  well as the file system icon).
> 
>  On Mon, Jan 16, 2023 at 7:16 PM Steve Litt via PLUG-discuss <
>  plug-discuss@lists.phxlinux.org> wrote:
> 
> > Eric Oyen via PLUG-discuss said on Mon, 16 Jan 2023 16:38:57 -0700
> >
> >> For most things, I use USB sticks in
> >> a write once, read many configuration scenario.
> > Another thing I've found anecdotally that helps lengthen the USB
> stick
> > life, whether write once or write a bunch, is to format it as Ext4. I
> > don't think I ever had one go bad as Ext4, but I have with the
> windows
> > format they're shipped with. Of course, if you have to interact with
> > windows computers or devices expecting windows formated USB sticks,
> my
> > trick becomes useless.
> >
> > SteveT
> >
> > Steve Litt
> > Autumn 2022 featured book: Thriving in Tough Times
> > http://www.troubleshooters.com/bookstore/thrive.htm
> > ---
> > 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~(-:
> 
> >>>
> >>> --
> >>> :-)~MIKE~(-:
> >>>
> >>
> >> --
> >> :-)~MIKE~(-:
> >> ---
> >> PLUG-discuss mailing list: PL

Re: usb marked as read-only

2023-01-18 Thread Michael via PLUG-discuss 
I fixed the drive I didn't throw away! I put the msdos partition table back
on it and format it ntfs and it is happily accepting files again. How did
you format it ext4? Did you change the partition table?

On Tue, Jan 17, 2023 at 7:26 PM Michael  wrote:

> On Tue, Jan 17, 2023 at 1:05 PM Rusty Carruth via PLUG-discuss <
> plug-discuss@lists.phxlinux.org> wrote:
>
>> are you running that command while booted on the stick you are trying to
>> erase?
>>
>>
> Of course not. Always unmount the device.
> I threw it away before I got this message so
> But the other drive look at the other thread.
>
>
>> While that SHOULD work, you are writing over the device you are booted
>> on, not usually considered best practice ;-)  And this
>> 'read-only-filesystem' message is interesting to me, I'd love to have
>> that stick to play with just to see, but it probably isn't worth it.
>>
>>
>> Anyway:
>>
>>
>> I've wanted to come back and say that from what I've seen before the
>> whole 'drive is toast' path was that the partition  you have been trying
>> to make on the stick appears to have been correctly created and
>> formatted.  This implies you just need to start at that step in the
>> how-to.
>>
>> But if you are convinced the stick is dead, the cost of time dealing
>> with it is more than the cost of a new stick, go get a new stick and
>> start over.
>>
>> On 1/17/23 06:52, Michael via PLUG-discuss wrote:
>> > I tried 'wipe' on it last night. But got the same error message:
>> > sudo dd if=/dev/zero of=/dev/sdb
>> > [sudo] password for michael:
>> > dd: failed to open '/dev/sdb': Read-only file system
>> >
>> > On Tue, Jan 17, 2023 at 12:03 AM Eric Oyen via PLUG-discuss <
>> > plug-discuss@lists.phxlinux.org> wrote:
>> >
>> >> There is one thing you can try before absolutely tossing it. Run dd as
>> >> root with the following code: sudo dd if=/dev/zero of=/dev/sdb
>> >> And let her run. That should erase everything on that stick, including
>> >> partition info, boot sector and the like.
>> >>
>> >> If there is a problem, dd will very quickly quit with an error.
>> >>
>> >> -Eric
>> >>  From the Central Offices of the Technomage Guild, Hardware
>> dispositions
>> >> Dept.
>> >>
>> >>
>> >> On Jan 16, 2023, at 7:23 PM, Michael via PLUG-discuss <
>> >> plug-discuss@lists.phxlinux.org> wrote:
>> >>
>> >> yeah. I think all is loast. I finally got around to looking at the
>> gparted
>> >> report:
>> >>
>> >> 
>> >> Device: /dev/sdd
>> >> Model: SanDisk Ultra
>> >> Serial:
>> >> Sector size: 512
>> >> Total sectors: 60063744
>> >>
>> >> Heads: 255
>> >> Sectors/track: 2
>> >> Cylinders: 117772
>> >>
>> >> Partition table: none
>> >>
>> >> PartitionTypeStartEndFlagsPartition NameFile SystemLabelMount Point
>> >> /dev/sdd Unpartitioned 0 60063743 iso9660 Kali Live
>> >>
>> >> 
>> >> *Format /dev/sdd as ext4*  00:00:17( ERROR )
>> >>
>> >> calibrate /dev/sdd  00:00:00( SUCCESS )
>> >>
>> >>
>> >>
>> >>
>> >> *path: /dev/sdd (device)start: 0end: 60063743size: 60063744 (28.64
>> GiB)*
>> >> clear old file system signatures in /dev/sdd  00:00:17( ERROR )
>> >>
>> >> write 512.00 KiB of zeros at byte offset 0  00:00:17( ERROR )
>> >>
>> >> libparted messages( ERROR )
>> >>
>> >> *Unable to open /dev/sdd read-write (Read-only file system). /dev/sdd
>> has
>> >> been opened read-only.*
>> >> *Can't write to /dev/sdd, because it is opened read-only.*
>> >> *Can't write to /dev/sdd, because it is opened read-only.*
>> >>
>> >> On Mon, Jan 16, 2023 at 7:55 PM Michael  wrote:
>> >>
>> >>> any advice before I toss it? I suppose I could buy a chain and wear it
>> >>> around my neck!
>> >>>
>> >>> On Mon, Jan 16, 2023 at 7:53 PM Michael  wrote:
>> >>>
>>  lovely, my 32gb ultra is toast. I started gparted to see if I could
>>  format it and the square showing the partitions and usage is gray (as
>>  well as the file system icon).
>> 
>>  On Mon, Jan 16, 2023 at 7:16 PM Steve Litt via PLUG-discuss <
>>  plug-discuss@lists.phxlinux.org> wrote:
>> 
>> > Eric Oyen via PLUG-discuss said on Mon, 16 Jan 2023 16:38:57 -0700
>> >
>> >> For most things, I use USB sticks in
>> >> a write once, read many configuration scenario.
>> > Another thing I've found anecdotally that helps lengthen the USB
>> stick
>> > life, whether write once or write a bunch, is to format it as Ext4.
>> I
>> > don't think I ever had one go bad as Ext4, but I have with the
>> windows
>> > format they're shipped with. Of course, if you have to interact with
>> > windows computers or devices expecting windows formated USB sticks,
>> my
>> > trick becomes useless.
>> >
>> > SteveT
>> >
>> > Steve Litt
>> > Autumn 2022 featured book: Thriving in Tough Times
>> > http://www.troubleshooters.com/bookstore/thrive.htm
>> > ---
>> > PLU