Rocksolid Light

Welcome to novaBBS (click a section below)

mail  files  register  newsreader  groups  login

Message-ID:  

Memories of you remind me of you. -- Karl Lehenbauer


computers / alt.os.linux.mint / Re: Problem with USB drive

SubjectAuthor
* Problem with USB driveRobH
+* Re: Problem with USB driveEnno Borgsteede
|`* Re: Problem with USB driveRobH
| `- Re: Problem with USB driveEnno Borgsteede
+* Re: Problem with USB drivePaul
|`* Re: Problem with USB driveRobH
| `* Re: Problem with USB driveMark Bourne
|  `- Re: Problem with USB driveRobH
+- Re: Problem with USB driveNic
+* Re: Problem with USB drivepinnerite
|`* Re: Problem with USB driveRobH
| `- Re: Problem with USB drivePaul
`* Re: Problem with USB driveJack Strangio
 +* Re: Problem with USB drivePaul
 |`- Re: Problem with USB driveRobH
 `* Re: Problem with USB driveRobH
  `- Re: Problem with USB drivePaul

1
Problem with USB drive

<kvieedF92pfU1@mid.individual.net>

 copy mid

https://www.novabbs.com/computers/article-flat.php?id=7346&group=alt.os.linux.mint#7346

 copy link   Newsgroups: alt.os.linux.mint
Path: i2pn2.org!i2pn.org!weretis.net!feeder8.news.weretis.net!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail
From: rob...@nospam.com (RobH)
Newsgroups: alt.os.linux.mint
Subject: Problem with USB drive
Date: Tue, 2 Jan 2024 12:38:37 +0000
Lines: 18
Message-ID: <kvieedF92pfU1@mid.individual.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Trace: individual.net nARtXXPwQJ/ExEonH+RWoQs5LtHUqEggdryL9+zvuMg7bMGi8U
Cancel-Lock: sha1:7mIswY1YLN9StnBFhz2veME0hjk= sha256:I5n9ZPEQG/Rznfj7g/FFUpxSAyIBsoXiZSAz0SWih5s=
User-Agent: Mozilla Thunderbird
Content-Language: en-US
 by: RobH - Tue, 2 Jan 2024 12:38 UTC

I have a 64Gb Innostor USD drive that I cannot read,as LM21.1 only sees
it as /dev/sdc using lsblk:

ob@rob-Z97-HD3:~$ sudo lsblk
sdc 8:32 1 0B 0 disk

When I try sudo fdisk, it is not found

In
rob@rob-Z97-HD3:~$ lsusb
Bus 007 Device 004: ID 1f75:0903 Innostor Technology Corporation PenDrive

Using Disks, the USB stick is showing but there are no options to do
anything with it, as they are all greyed out in the context

Is there anything else I can try to get it working again.

Re: Problem with USB drive

<un125l$2n606$1@dont-email.me>

 copy mid

https://www.novabbs.com/computers/article-flat.php?id=7347&group=alt.os.linux.mint#7347

 copy link   Newsgroups: alt.os.linux.mint
Path: i2pn2.org!i2pn.org!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: ennob...@gmail.com (Enno Borgsteede)
Newsgroups: alt.os.linux.mint
Subject: Re: Problem with USB drive
Date: Tue, 2 Jan 2024 14:13:25 +0100
Organization: A noiseless patient Spider
Lines: 21
Message-ID: <un125l$2n606$1@dont-email.me>
References: <kvieedF92pfU1@mid.individual.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Injection-Date: Tue, 2 Jan 2024 13:13:25 -0000 (UTC)
Injection-Info: dont-email.me; posting-host="0614e3adf59ef50d43dfa61010724afe";
logging-data="2856966"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1/h5l8R4acDYovBQHEr+fr5TOar+Gj7KpY="
User-Agent: Mozilla Thunderbird
Cancel-Lock: sha1:vVboZ5Gxeeb7Yh5X+7/MgkGjisg=
In-Reply-To: <kvieedF92pfU1@mid.individual.net>
Content-Language: en-US
 by: Enno Borgsteede - Tue, 2 Jan 2024 13:13 UTC

Op 02-01-2024 om 13:38 schreef RobH:
> I have a 64Gb Innostor USD drive that I cannot read,as LM21.1 only sees
> it as /dev/sdc using lsblk:
>
> ob@rob-Z97-HD3:~$ sudo lsblk
> sdc      8:32   1     0B  0 disk
>
>
> When I try sudo fdisk, it is not found
>
> In
> rob@rob-Z97-HD3:~$ lsusb
> Bus 007 Device 004: ID 1f75:0903 Innostor Technology Corporation PenDrive
>
> Using Disks, the USB stick is showing but there are no options to do
> anything with it, as they are all greyed out in the context
>
> Is there anything else I can try to get it working again.
>
Gparted?

Re: Problem with USB drive

<kvihdcF9ngiU1@mid.individual.net>

 copy mid

https://www.novabbs.com/computers/article-flat.php?id=7348&group=alt.os.linux.mint#7348

 copy link   Newsgroups: alt.os.linux.mint
Path: i2pn2.org!i2pn.org!weretis.net!feeder8.news.weretis.net!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail
From: rob...@nospam.com (RobH)
Newsgroups: alt.os.linux.mint
Subject: Re: Problem with USB drive
Date: Tue, 2 Jan 2024 13:29:16 +0000
Lines: 23
Message-ID: <kvihdcF9ngiU1@mid.individual.net>
References: <kvieedF92pfU1@mid.individual.net> <un125l$2n606$1@dont-email.me>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
X-Trace: individual.net 76KgZVIH/9g4HQRFoMfRHAHQ+HjztWzcXZNNCql6KXFxuMk3SV
Cancel-Lock: sha1:py2wHUaKq4CAiqgr33ivR7e1sxw= sha256:mJCUQkiERgNVO/wU6PgUNd+UEBZlzH2V7tPGpbQkhNk=
User-Agent: Mozilla Thunderbird
Content-Language: en-US
In-Reply-To: <un125l$2n606$1@dont-email.me>
 by: RobH - Tue, 2 Jan 2024 13:29 UTC

On 02/01/2024 13:13, Enno Borgsteede wrote:
> Op 02-01-2024 om 13:38 schreef RobH:
>> I have a 64Gb Innostor USD drive that I cannot read,as LM21.1 only
>> sees it as /dev/sdc using lsblk:
>>
>> ob@rob-Z97-HD3:~$ sudo lsblk
>> sdc      8:32   1     0B  0 disk
>>
>>
>> When I try sudo fdisk, it is not found
>>
>> In
>> rob@rob-Z97-HD3:~$ lsusb
>> Bus 007 Device 004: ID 1f75:0903 Innostor Technology Corporation PenDrive
>>
>> Using Disks, the USB stick is showing but there are no options to do
>> anything with it, as they are all greyed out in the context
>>
>> Is there anything else I can try to get it working again.
>>
> Gparted?
>
I forgot about that, but no the USB drive is not seen in gparted

Re: Problem with USB drive

<un13ib$2n605$1@dont-email.me>

 copy mid

https://www.novabbs.com/computers/article-flat.php?id=7349&group=alt.os.linux.mint#7349

 copy link   Newsgroups: alt.os.linux.mint
Path: i2pn2.org!i2pn.org!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: ennob...@gmail.com (Enno Borgsteede)
Newsgroups: alt.os.linux.mint
Subject: Re: Problem with USB drive
Date: Tue, 2 Jan 2024 14:37:15 +0100
Organization: A noiseless patient Spider
Lines: 12
Message-ID: <un13ib$2n605$1@dont-email.me>
References: <kvieedF92pfU1@mid.individual.net> <un125l$2n606$1@dont-email.me>
<kvihdcF9ngiU1@mid.individual.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Injection-Date: Tue, 2 Jan 2024 13:37:15 -0000 (UTC)
Injection-Info: dont-email.me; posting-host="0614e3adf59ef50d43dfa61010724afe";
logging-data="2856965"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1/mx7Wdzg/2OLZxlrwRc1ReYJysAYYROdE="
User-Agent: Mozilla Thunderbird
Cancel-Lock: sha1:j8fEBhMne72Nx/HC33rIz1czRCI=
Content-Language: en-US
In-Reply-To: <kvihdcF9ngiU1@mid.individual.net>
 by: Enno Borgsteede - Tue, 2 Jan 2024 13:37 UTC

Op 02-01-2024 om 14:29 schreef RobH:

> I forgot about that, but no the USB drive is not seen in gparted

Weird. Not even when you insert it into another port?

I have two machines with dual boot Mint and Windows 10 and 11, so in a
case like this, I try it on all, including Windows disk management in
the process.

And if you have Windows somewhere, the Recuva program may also help.

Re: Problem with USB drive

<un1585$2njqs$1@dont-email.me>

 copy mid

https://www.novabbs.com/computers/article-flat.php?id=7350&group=alt.os.linux.mint#7350

 copy link   Newsgroups: alt.os.linux.mint
Path: i2pn2.org!i2pn.org!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: nos...@needed.invalid (Paul)
Newsgroups: alt.os.linux.mint
Subject: Re: Problem with USB drive
Date: Tue, 2 Jan 2024 09:05:58 -0500
Organization: A noiseless patient Spider
Lines: 49
Message-ID: <un1585$2njqs$1@dont-email.me>
References: <kvieedF92pfU1@mid.individual.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
Injection-Date: Tue, 2 Jan 2024 14:05:57 -0000 (UTC)
Injection-Info: dont-email.me; posting-host="4420a0c9dcd4767f44af0561aa6e21e8";
logging-data="2871132"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX19y5kvrdvE0NbMF7C8n8MNYpPgeRCWLEP0="
User-Agent: Ratcatcher/2.0.0.25 (Windows/20130802)
Cancel-Lock: sha1:sD3solFnCY6ybDItk4E8fiTIVpk=
In-Reply-To: <kvieedF92pfU1@mid.individual.net>
Content-Language: en-US
 by: Paul - Tue, 2 Jan 2024 14:05 UTC

On 1/2/2024 7:38 AM, RobH wrote:
> I have a 64Gb Innostor USD drive that I cannot read,as LM21.1 only sees it as /dev/sdc using lsblk:
>
> ob@rob-Z97-HD3:~$ sudo lsblk
> sdc      8:32   1     0B  0 disk
>
>
> When I try sudo fdisk, it is not found
>
> In
> rob@rob-Z97-HD3:~$ lsusb
> Bus 007 Device 004: ID 1f75:0903 Innostor Technology Corporation PenDrive
>
> Using Disks, the USB stick is showing but there are no options to do anything with it, as they are all greyed out in the context
>
> Is there anything else I can try to get it working again.
>

Maybe the device has gone read-only ?

sudo apt install disktype
sudo disktype /dev/sdc

You know that so far, the device has successfully had endpoints
made to it. The device would not respond at all, if the NAND was
totally inaccessible. It was able to read that a NAND was present.
But more than that, we cannot be sure what it is doing.

Disktype will try some read operations. It does not need to see
partitions, to do reads. It will read the MBR. It will take the
partition offset value and read the file system header sector at
that offset, then parse it and tell you what file system is there.

You can try a read-only mount after that, and "see if it takes".
The command will need to be issued manually. If the automounter is
set up to do RW mounts, and the device "does not support writing",
I would expect the mount attempt to fail with a message.

sudo mkdir /mnt/ntfs # Make a mount point for manual mount. Remove much later.
sudo mount -o ro -t ntfs /dev/sdxY /mnt/ntfs # Need details from disktype or ls /dev to work out the sdxY value

You can also try "dmesg" or "sudo dmesg" and see if there
are any messages waiting for you in there. There are other log
files of course.

But since you got part-way into the device, I'm going to
hypothesize it is read-only for some reason.

Paul

Re: Problem with USB drive

<vhWkN.22590$taff.5556@fx41.iad>

 copy mid

https://www.novabbs.com/computers/article-flat.php?id=7351&group=alt.os.linux.mint#7351

 copy link   Newsgroups: alt.os.linux.mint
Path: i2pn2.org!i2pn.org!weretis.net!feeder6.news.weretis.net!panix!usenet.blueworldhosting.com!diablo1.usenet.blueworldhosting.com!peer03.iad!feed-me.highwinds-media.com!news.highwinds-media.com!fx41.iad.POSTED!not-for-mail
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101
Thunderbird/102.13.0
Reply-To: Nic@none.net
Subject: Re: Problem with USB drive
Newsgroups: alt.os.linux.mint
References: <kvieedF92pfU1@mid.individual.net>
Content-Language: en-US
From: Nic...@none.net (Nic)
Organization: Arm Chair Observer
In-Reply-To: <kvieedF92pfU1@mid.individual.net>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Lines: 20
Message-ID: <vhWkN.22590$taff.5556@fx41.iad>
X-Complaints-To: abuse(at)newshosting.com
NNTP-Posting-Date: Tue, 02 Jan 2024 15:50:51 UTC
Date: Tue, 2 Jan 2024 10:50:51 -0500
X-Received-Bytes: 1325
 by: Nic - Tue, 2 Jan 2024 15:50 UTC

On 1/2/24 7:38 AM, RobH wrote:
> I have a 64Gb Innostor USD drive that I cannot read,as LM21.1 only
> sees it as /dev/sdc using lsblk:
>
> ob@rob-Z97-HD3:~$ sudo lsblk
> sdc      8:32   1     0B  0 disk
>
>
> When I try sudo fdisk, it is not found
>
> In
> rob@rob-Z97-HD3:~$ lsusb
> Bus 007 Device 004: ID 1f75:0903 Innostor Technology Corporation PenDrive
>
> Using Disks, the USB stick is showing but there are no options to do
> anything with it, as they are all greyed out in the context
>
> Is there anything else I can try to get it working again.
>
Try M$ Checkdisk

Re: Problem with USB drive

<kvislbFbjenU1@mid.individual.net>

 copy mid

https://www.novabbs.com/computers/article-flat.php?id=7352&group=alt.os.linux.mint#7352

 copy link   Newsgroups: alt.os.linux.mint
Path: i2pn2.org!i2pn.org!weretis.net!feeder8.news.weretis.net!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail
From: rob...@nospam.com (RobH)
Newsgroups: alt.os.linux.mint
Subject: Re: Problem with USB drive
Date: Tue, 2 Jan 2024 16:41:15 +0000
Lines: 106
Message-ID: <kvislbFbjenU1@mid.individual.net>
References: <kvieedF92pfU1@mid.individual.net> <un1585$2njqs$1@dont-email.me>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
X-Trace: individual.net yZSsFIX1BNcswdScpvOn1A9Rjw3S4/DSWNY+dH76QkWDDnl6wj
Cancel-Lock: sha1:ioB+f8CJwOIlt5LQ47fsJxzOv14= sha256:HrGMF/XbrAOXUW1CG5I2bgwxS9qaJK1Sf8oKq/i38yQ=
User-Agent: Mozilla Thunderbird
Content-Language: en-US
In-Reply-To: <un1585$2njqs$1@dont-email.me>
 by: RobH - Tue, 2 Jan 2024 16:41 UTC

On 02/01/2024 14:05, Paul wrote:
> On 1/2/2024 7:38 AM, RobH wrote:
>> I have a 64Gb Innostor USD drive that I cannot read,as LM21.1 only sees it as /dev/sdc using lsblk:
>>
>> ob@rob-Z97-HD3:~$ sudo lsblk
>> sdc      8:32   1     0B  0 disk
>>
>>
>> When I try sudo fdisk, it is not found
>>
>> In
>> rob@rob-Z97-HD3:~$ lsusb
>> Bus 007 Device 004: ID 1f75:0903 Innostor Technology Corporation PenDrive
>>
>> Using Disks, the USB stick is showing but there are no options to do anything with it, as they are all greyed out in the context
>>
>> Is there anything else I can try to get it working again.
>>
>
> Maybe the device has gone read-only ?
>
> sudo apt install disktype
> sudo disktype /dev/sdc
>
> You know that so far, the device has successfully had endpoints
> made to it. The device would not respond at all, if the NAND was
> totally inaccessible. It was able to read that a NAND was present.
> But more than that, we cannot be sure what it is doing.
>
> Disktype will try some read operations. It does not need to see
> partitions, to do reads. It will read the MBR. It will take the
> partition offset value and read the file system header sector at
> that offset, then parse it and tell you what file system is there.
>
> You can try a read-only mount after that, and "see if it takes".
> The command will need to be issued manually. If the automounter is
> set up to do RW mounts, and the device "does not support writing",
> I would expect the mount attempt to fail with a message.
>
> sudo mkdir /mnt/ntfs # Make a mount point for manual mount. Remove much later.
> sudo mount -o ro -t ntfs /dev/sdxY /mnt/ntfs # Need details from disktype or ls /dev to work out the sdxY value
>
> You can also try "dmesg" or "sudo dmesg" and see if there
> are any messages waiting for you in there. There are other log
> files of course.
>
> But since you got part-way into the device, I'm going to
> hypothesize it is read-only for some reason.
>
> Paul

Thanks Paul, but:
After I installed disktype:

rob@rob-Z97-HD3:~$ sudo disktype /dev/sdc

--- /dev/sdc
disktype: Can't open /dev/sdc: No medium found

rob@rob-Z97-HD3:~$ lsblk
sdc 8:32 1 0B 0 disk

rob@rob-Z97-HD3:~$ sudo mkdir /mnt/ntfs

rob@rob-Z97-HD3:~$ sudo mount -o ro -t ntfs /dev/sdc /mnt/ntfs
Error opening '/dev/sdc': No medium found
Failed to mount '/dev/sdc': No medium found

This is from part of
sudo dmesg:

cdDevice= 0.01
[ 3122.449323] usb 7-4.4: New USB device strings: Mfr=1, Product=2,
SerialNumber=3
[ 3122.449325] usb 7-4.4: Product: PenDrive
[ 3122.449326] usb 7-4.4: Manufacturer: Innostor
[ 3122.449327] usb 7-4.4: SerialNumber: 000000000000000336
[ 3122.457891] usb-storage 7-4.4:1.0: USB Mass Storage device detected
[ 3122.458125] scsi host6: usb-storage 7-4.4:1.0
[ 3122.458224] usbcore: registered new interface driver usb-storage
[ 3122.460106] usbcore: registered new interface driver uas
[ 3123.465255] scsi 6:0:0:0: Direct-Access Innostor NAND Flash
1.00 PQ: 0 ANSI: 6
[ 3123.465438] sd 6:0:0:0: Attached scsi generic sg3 type 0
[ 3123.465661] sd 6:0:0:0: [sdc] Media removed, stopped polling
[ 3123.466063] sd 6:0:0:0: [sdc] Attached SCSI removable disk
[ 3185.764117] usb 7-4.4: Disable of device-initiated U1 failed.
[ 3185.767816] usb 7-4.4: Disable of device-initiated U2 failed.
[ 3186.451442] usb 7-4.4: USB disconnect, device number 3
[ 3216.534482] usb 7-4.4: new SuperSpeed USB device number 4 using xhci_hcd
[ 3216.554884] usb 7-4.4: New USB device found, idVendor=1f75,
idProduct=0903, bcdDevice= 0.01
[ 3216.554888] usb 7-4.4: New USB device strings: Mfr=1, Product=2,
SerialNumber=3
[ 3216.554890] usb 7-4.4: Product: PenDrive
[ 3216.554890] usb 7-4.4: Manufacturer: Innostor
[ 3216.554891] usb 7-4.4: SerialNumber: 000000000000000336
[ 3216.556208] usb-storage 7-4.4:1.0: USB Mass Storage device detected
[ 3216.556364] scsi host6: usb-storage 7-4.4:1.0
[ 3217.578772] scsi 6:0:0:0: Direct-Access Innostor NAND Flash
1.00 PQ: 0 ANSI: 6

I also tried the usb stick in both another usb port and on another linux
pc, without any luck.

Thanks

Re: Problem with USB drive

<20240102165037.6bb7ee783a6675a40ce1342d@gmail.com>

 copy mid

https://www.novabbs.com/computers/article-flat.php?id=7354&group=alt.os.linux.mint#7354

 copy link   Newsgroups: alt.os.linux.mint
Path: i2pn2.org!i2pn.org!news.niel.me!pasdenom.info!paganini.bofh.team!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: pinner...@gmail.com (pinnerite)
Newsgroups: alt.os.linux.mint
Subject: Re: Problem with USB drive
Date: Tue, 2 Jan 2024 16:50:37 +0000
Organization: A noiseless patient Spider
Lines: 39
Message-ID: <20240102165037.6bb7ee783a6675a40ce1342d@gmail.com>
References: <kvieedF92pfU1@mid.individual.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Injection-Info: dont-email.me; posting-host="404dd1bbb62253ad815baeb648e6785a";
logging-data="2917752"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1+9D+y39yLP/9VV2LWOJakQHEx/DP905Ew="
Cancel-Lock: sha1:pen9sEhMDxHJfcmzx/VYbdW4HO8=
X-Newsreader: Sylpheed 3.7.0 (GTK+ 2.24.33; x86_64-pc-linux-gnu)
 by: pinnerite - Tue, 2 Jan 2024 16:50 UTC

On Tue, 2 Jan 2024 12:38:37 +0000
RobH <rob@nospam.com> wrote:

> I have a 64Gb Innostor USD drive that I cannot read,as LM21.1 only sees
> it as /dev/sdc using lsblk:
>
> ob@rob-Z97-HD3:~$ sudo lsblk
> sdc 8:32 1 0B 0 disk
>
>
> When I try sudo fdisk, it is not found
>
> In
> rob@rob-Z97-HD3:~$ lsusb
> Bus 007 Device 004: ID 1f75:0903 Innostor Technology Corporation PenDrive
>
> Using Disks, the USB stick is showing but there are no options to do
> anything with it, as they are all greyed out in the context
>
> Is there anything else I can try to get it working again.
>

I found this on the www:

1) run sudo -i (so that you won't type your password all the time)
2) run df -Th (to see where your USB stick is mounted)
3) unmount your USB stick.
4) run dosfsck on the device you saw from your previous command.
Example: dosfsck /dev/sdc1.
5) remove and reattach your USB stick.

I haven't tried it myself. :)

Regards, Alan

--
Linux Mint 21.1 kernel version 5.15.0-91-generic Cinnamon 5.6.8
AMD Phenom II x4 955 CPU 16Gb Dram 2TB Barracuda

Re: Problem with USB drive

<kviu6pFc000U1@mid.individual.net>

 copy mid

https://www.novabbs.com/computers/article-flat.php?id=7355&group=alt.os.linux.mint#7355

 copy link   Newsgroups: alt.os.linux.mint
Path: i2pn2.org!i2pn.org!weretis.net!feeder8.news.weretis.net!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail
From: rob...@nospam.com (RobH)
Newsgroups: alt.os.linux.mint
Subject: Re: Problem with USB drive
Date: Tue, 2 Jan 2024 17:07:37 +0000
Lines: 53
Message-ID: <kviu6pFc000U1@mid.individual.net>
References: <kvieedF92pfU1@mid.individual.net>
<20240102165037.6bb7ee783a6675a40ce1342d@gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Trace: individual.net pzWWfTxtIn5/sqILjGiffg1bY89vgRoK9TJZ/l3VTNxGSniAtR
Cancel-Lock: sha1:kbjPex2EazdEJ2QzkiOmv8NpJ/8= sha256:/N72jg645NEzrkMoSs82YCTBZP7vdCmPqjKZTcrT8lE=
User-Agent: Mozilla Thunderbird
Content-Language: en-US
In-Reply-To: <20240102165037.6bb7ee783a6675a40ce1342d@gmail.com>
 by: RobH - Tue, 2 Jan 2024 17:07 UTC

On 02/01/2024 16:50, pinnerite wrote:
> On Tue, 2 Jan 2024 12:38:37 +0000
> RobH <rob@nospam.com> wrote:
>
>> I have a 64Gb Innostor USD drive that I cannot read,as LM21.1 only sees
>> it as /dev/sdc using lsblk:
>>
>> ob@rob-Z97-HD3:~$ sudo lsblk
>> sdc 8:32 1 0B 0 disk
>>
>>
>> When I try sudo fdisk, it is not found
>>
>> In
>> rob@rob-Z97-HD3:~$ lsusb
>> Bus 007 Device 004: ID 1f75:0903 Innostor Technology Corporation PenDrive
>>
>> Using Disks, the USB stick is showing but there are no options to do
>> anything with it, as they are all greyed out in the context
>>
>> Is there anything else I can try to get it working again.
>>
>
> I found this on the www:
>
> 1) run sudo -i (so that you won't type your password all the time)
> 2) run df -Th (to see where your USB stick is mounted)
> 3) unmount your USB stick.
> 4) run dosfsck on the device you saw from your previous command.
> Example: dosfsck /dev/sdc1.
> 5) remove and reattach your USB stick.
>
> I haven't tried it myself. :)
>
> Regards, Alan
>
>

Thanks for the above but that didn't work either:

root@rob-Z97-HD3:~# df -Th
results in the usb stick not listed , ie dev/sdc

root@rob-Z97-HD3:~# dosfsck /dev/sdc
fsck.fat 4.2 (2021-01-31)
open: No medium found

root@rob-Z97-HD3:~# lsblk
sdc 8:32 1 0B 0 disk

Re: Problem with USB drive

<un1r6o$2qthp$1@dont-email.me>

 copy mid

https://www.novabbs.com/computers/article-flat.php?id=7356&group=alt.os.linux.mint#7356

 copy link   Newsgroups: alt.os.linux.mint
Path: i2pn2.org!i2pn.org!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: nos...@needed.invalid (Paul)
Newsgroups: alt.os.linux.mint
Subject: Re: Problem with USB drive
Date: Tue, 2 Jan 2024 15:20:41 -0500
Organization: A noiseless patient Spider
Lines: 79
Message-ID: <un1r6o$2qthp$1@dont-email.me>
References: <kvieedF92pfU1@mid.individual.net>
<20240102165037.6bb7ee783a6675a40ce1342d@gmail.com>
<kviu6pFc000U1@mid.individual.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
Injection-Date: Tue, 2 Jan 2024 20:20:40 -0000 (UTC)
Injection-Info: dont-email.me; posting-host="4420a0c9dcd4767f44af0561aa6e21e8";
logging-data="2979385"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX192jRTdb13VC8YxZaSCQavhdsijrdq3iJw="
User-Agent: Ratcatcher/2.0.0.25 (Windows/20130802)
Cancel-Lock: sha1:trCzL+kQlHie1MyHslTDQ9VVYPo=
In-Reply-To: <kviu6pFc000U1@mid.individual.net>
Content-Language: en-US
 by: Paul - Tue, 2 Jan 2024 20:20 UTC

On 1/2/2024 12:07 PM, RobH wrote:
> On 02/01/2024 16:50, pinnerite wrote:
>> On Tue, 2 Jan 2024 12:38:37 +0000
>> RobH <rob@nospam.com> wrote:
>>
>>> I have a 64Gb Innostor USD drive that I cannot read,as LM21.1 only sees
>>> it as /dev/sdc using lsblk:
>>>
>>> ob@rob-Z97-HD3:~$ sudo lsblk
>>> sdc      8:32   1     0B  0 disk
>>>
>>>
>>> When I try sudo fdisk, it is not found
>>>
>>> In
>>> rob@rob-Z97-HD3:~$ lsusb
>>> Bus 007 Device 004: ID 1f75:0903 Innostor Technology Corporation PenDrive
>>>
>>> Using Disks, the USB stick is showing but there are no options to do
>>> anything with it, as they are all greyed out in the context
>>>
>>> Is there anything else I can try to get it working again.
>>>
>>
>> I found this on the www:
>>
>> 1)  run sudo -i (so that you won't type your password all the time)
>> 2)  run df -Th (to see where your USB stick is mounted)
>> 3)  unmount your USB stick.
>> 4)  run dosfsck on the device you saw from your previous command.
>>      Example: dosfsck /dev/sdc1.
>> 5)  remove and reattach your USB stick.
>>
>> I haven't tried it myself. :)
>>
>> Regards, Alan
>>
>>
>
> Thanks for the above  but that didn't work either:
>
> root@rob-Z97-HD3:~# df -Th
> results in the usb stick not listed , ie dev/sdc
>
> root@rob-Z97-HD3:~# dosfsck /dev/sdc
> fsck.fat 4.2 (2021-01-31)
> open: No medium found
>
> root@rob-Z97-HD3:~# lsblk
> sdc      8:32   1     0B  0 disk

I don't know what to make of what you're seeing,
but it does look cooked.

I'm just surprised it is talking to us, while being
unable to commission the storage. It's unusual for
storage standards to talk if the medium (NAND flash chip)
is apparently not working. It is not read-only, it's
neither read nor write by the looks of it.

On a hard drive, if the heads cannot load from the platter,
then the drive will refuse to ID itself. It won't say
"WD Black 1TB" and give its model number, if asked. Only
if a certain amount of the bring-up completes, is a
hard drive ready to open shop.

Your USB stick talked to us, while "the shop is still closed".
Which is interesting and all, but it isn't bringing back
your data. No amount of ddrescue, or prayer rituals, will
get the files back now.

I tried some web searches, but nothing interesting is
coming back. Unfortunately. I tried CoPilot and the results
of queries there, are no better than Google really. It's
just a different kind of rubbish.

Paul

Re: Problem with USB drive

<un1vsu$2rim9$1@dont-email.me>

 copy mid

https://www.novabbs.com/computers/article-flat.php?id=7358&group=alt.os.linux.mint#7358

 copy link   Newsgroups: alt.os.linux.mint
Path: i2pn2.org!i2pn.org!news.neodome.net!news.mixmin.net!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: nntp.mbo...@spamgourmet.com (Mark Bourne)
Newsgroups: alt.os.linux.mint
Subject: Re: Problem with USB drive
Date: Tue, 2 Jan 2024 21:40:45 +0000
Organization: A noiseless patient Spider
Lines: 141
Message-ID: <un1vsu$2rim9$1@dont-email.me>
References: <kvieedF92pfU1@mid.individual.net> <un1585$2njqs$1@dont-email.me>
<kvislbFbjenU1@mid.individual.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Injection-Date: Tue, 2 Jan 2024 21:40:46 -0000 (UTC)
Injection-Info: dont-email.me; posting-host="b7a0f3dace094b657ae672f9011d38d9";
logging-data="3001033"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX19y/eCJX0uABuGjtjRwKsXI"
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101
SeaMonkey/2.53.18
Cancel-Lock: sha1:OYUsgdM5gVHzwAe3HsjV7M7T/Rc=
In-Reply-To: <kvislbFbjenU1@mid.individual.net>
 by: Mark Bourne - Tue, 2 Jan 2024 21:40 UTC

RobH wrote:
> On 02/01/2024 14:05, Paul wrote:
>> On 1/2/2024 7:38 AM, RobH wrote:
>>> I have a 64Gb Innostor USD drive that I cannot read,as LM21.1 only
>>> sees it as /dev/sdc using lsblk:
>>>
>>> ob@rob-Z97-HD3:~$ sudo lsblk
>>> sdc      8:32   1     0B  0 disk
>>>
>>>
>>> When I try sudo fdisk, it is not found
>>>
>>> In
>>> rob@rob-Z97-HD3:~$ lsusb
>>> Bus 007 Device 004: ID 1f75:0903 Innostor Technology Corporation
>>> PenDrive
>>>
>>> Using Disks, the USB stick is showing but there are no options to do
>>> anything with it, as they are all greyed out in the context
>>>
>>> Is there anything else I can try to get it working again.
>>>
>>
>> Maybe the device has gone read-only ?
>>
>>     sudo apt install disktype
>>     sudo disktype /dev/sdc
>>
>> You know that so far, the device has successfully had endpoints
>> made to it. The device would not respond at all, if the NAND was
>> totally inaccessible. It was able to read that a NAND was present.
>> But more than that, we cannot be sure what it is doing.
>>
>> Disktype will try some read operations. It does not need to see
>> partitions, to do reads. It will read the MBR. It will take the
>> partition offset value and read the file system header sector at
>> that offset, then parse it and tell you what file system is there.
>>
>> You can try a read-only mount after that, and "see if it takes".
>> The command will need to be issued manually. If the automounter is
>> set up to do RW mounts, and the device "does not support writing",
>> I would expect the mount attempt to fail with a message.
>>
>>     sudo mkdir /mnt/ntfs                          # Make a mount point
>> for manual mount. Remove much later.
>>     sudo mount -o ro -t ntfs /dev/sdxY /mnt/ntfs  # Need details from
>> disktype or ls /dev to work out the sdxY value
>>
>> You can also try "dmesg" or "sudo dmesg" and see if there
>> are any messages waiting for you in there. There are other log
>> files of course.
>>
>> But since you got part-way into the device, I'm going to
>> hypothesize it is read-only for some reason.
>>
>>     Paul
>
> Thanks Paul, but:
> After I installed disktype:
>
> rob@rob-Z97-HD3:~$ sudo disktype /dev/sdc
>
> --- /dev/sdc
> disktype: Can't open /dev/sdc: No medium found
>
> rob@rob-Z97-HD3:~$ lsblk
> sdc      8:32   1     0B  0 disk
>
> rob@rob-Z97-HD3:~$ sudo mkdir /mnt/ntfs
>
> rob@rob-Z97-HD3:~$ sudo mount -o ro -t ntfs /dev/sdc /mnt/ntfs
> Error opening '/dev/sdc': No medium found
> Failed to mount '/dev/sdc': No medium found
>
> This is from part of
> sudo dmesg:
>
> cdDevice= 0.01
> [ 3122.449323] usb 7-4.4: New USB device strings: Mfr=1, Product=2,
> SerialNumber=3
> [ 3122.449325] usb 7-4.4: Product: PenDrive
> [ 3122.449326] usb 7-4.4: Manufacturer: Innostor
> [ 3122.449327] usb 7-4.4: SerialNumber: 000000000000000336
> [ 3122.457891] usb-storage 7-4.4:1.0: USB Mass Storage device detected
> [ 3122.458125] scsi host6: usb-storage 7-4.4:1.0
> [ 3122.458224] usbcore: registered new interface driver usb-storage
> [ 3122.460106] usbcore: registered new interface driver uas
> [ 3123.465255] scsi 6:0:0:0: Direct-Access     Innostor NAND Flash 1.00
> PQ: 0 ANSI: 6
> [ 3123.465438] sd 6:0:0:0: Attached scsi generic sg3 type 0
> [ 3123.465661] sd 6:0:0:0: [sdc] Media removed, stopped polling

I'm not sure what problem it might indicate, but the "Media removed"
line above looks suspicious. It doesn't look like you unplugged the
drive at this point, since that's the "USB disconnect" line further
down. It looks almost as if the USB-SATA interface in the USB stick is
working, but there's no storage media attached to it.

At this point after connecting a USB drive, I get several lines
indicating the block size of the device, whether it's write protected,
mode sense, caching, and the partitions, followed by the "Attached SCSI
removable disk" line that you get below.

If I connect a USB-SATA adapter with no disk attached to the SATA
interface, I don't get anything at all from dmesg - which fits with what
Paul describes about the drive controller not enumerating if there's no
storage media attached. Perhaps the USB-SATA controller built into USB
sticks doesn't always have that handling, assuming that the storage will
always be there.

> [ 3123.466063] sd 6:0:0:0: [sdc] Attached SCSI removable disk
> [ 3185.764117] usb 7-4.4: Disable of device-initiated U1 failed.
> [ 3185.767816] usb 7-4.4: Disable of device-initiated U2 failed.
> [ 3186.451442] usb 7-4.4: USB disconnect, device number 3
> [ 3216.534482] usb 7-4.4: new SuperSpeed USB device number 4 using xhci_hcd
> [ 3216.554884] usb 7-4.4: New USB device found, idVendor=1f75,
> idProduct=0903, bcdDevice= 0.01
> [ 3216.554888] usb 7-4.4: New USB device strings: Mfr=1, Product=2,
> SerialNumber=3
> [ 3216.554890] usb 7-4.4: Product: PenDrive
> [ 3216.554890] usb 7-4.4: Manufacturer: Innostor
> [ 3216.554891] usb 7-4.4: SerialNumber: 000000000000000336
> [ 3216.556208] usb-storage 7-4.4:1.0: USB Mass Storage device detected
> [ 3216.556364] scsi host6: usb-storage 7-4.4:1.0
> [ 3217.578772] scsi 6:0:0:0: Direct-Access     Innostor NAND Flash 1.00
> PQ: 0 ANSI: 6

Is this the end of the dmesg output, or were you just copying a
relevant-looking chunk from the middle? If this is the end, it might be
relevant that the "Attached scsi generic", "Media removed" and "Attached
SCSI removable disk" lines don't appear again here, indicating that it
doesn't behave consistently.

> I also tried the usb stick in both another usb port and on another linux
> pc, without any luck.

It does look like the USB stick has gone faulty. If possible, it might
be worth seeing what another OS (Windows or Mac) makes of it.

--
Mark.

Re: Problem with USB drive

<s6o6C7.A1Mw@yahoo.com>

 copy mid

https://www.novabbs.com/computers/article-flat.php?id=7359&group=alt.os.linux.mint#7359

 copy link   Newsgroups: alt.os.linux.mint
Path: i2pn2.org!i2pn.org!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: jackstra...@yahoo.com (Jack Strangio)
Newsgroups: alt.os.linux.mint
Subject: Re: Problem with USB drive
Date: Wed, 3 Jan 2024 05:10:51 -0000 (UTC)
Organization: North Star Horizon Builders Club
Lines: 23
Message-ID: <s6o6C7.A1Mw@yahoo.com>
References: <kvieedF92pfU1@mid.individual.net>
Injection-Date: Wed, 3 Jan 2024 05:10:51 -0000 (UTC)
Injection-Info: dont-email.me; posting-host="2e90a9b7879d58899a78026dd618db9a";
logging-data="3267479"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX18w6e2VcYyZKbbs4TbXWRMjUsddVbP0eMQ="
Cancel-Lock: sha1:o2ACbG5HR9ubLqfneqjI77ZtPqE=
X-Newsreader: TASS News Reader 3.7.2 jvs [linux]
 by: Jack Strangio - Wed, 3 Jan 2024 05:10 UTC

RobH <rob@nospam.com> writes:
> I have a 64Gb Innostor USD drive that I cannot read,as LM21.1 only sees
> it as /dev/sdc using lsblk:
>
Try zeroing out some (maybe the first few megabytes or so) or even all
of the storage using the raw device and /dev/zero

as in

dd if=/dev/zero of=/dev/sdc bs=1M count=10

or maybe

dd if=/dev/zero of=/dev/sdc bs=1M

and then use gparted or similar to replace the filesystem.

Jack
--
I could tell you a joke about UDP.
But you might not get it.

Re: Problem with USB drive

<un2qna$33nln$1@dont-email.me>

 copy mid

https://www.novabbs.com/computers/article-flat.php?id=7360&group=alt.os.linux.mint#7360

 copy link   Newsgroups: alt.os.linux.mint
Path: i2pn2.org!i2pn.org!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: nos...@needed.invalid (Paul)
Newsgroups: alt.os.linux.mint
Subject: Re: Problem with USB drive
Date: Wed, 3 Jan 2024 00:18:36 -0500
Organization: A noiseless patient Spider
Lines: 27
Message-ID: <un2qna$33nln$1@dont-email.me>
References: <kvieedF92pfU1@mid.individual.net> <s6o6C7.A1Mw@yahoo.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Injection-Date: Wed, 3 Jan 2024 05:18:34 -0000 (UTC)
Injection-Info: dont-email.me; posting-host="4d3ac6c9e604833e65f7870be25c9563";
logging-data="3268279"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1+akKTTKop09eV8SV+6PuXdaWXpsgwN/BM="
User-Agent: Ratcatcher/2.0.0.25 (Windows/20130802)
Cancel-Lock: sha1:qGdE8jq+ks9sGpHEgjWFOCF5qbY=
In-Reply-To: <s6o6C7.A1Mw@yahoo.com>
Content-Language: en-US
 by: Paul - Wed, 3 Jan 2024 05:18 UTC

On 1/3/2024 12:10 AM, Jack Strangio wrote:
> RobH <rob@nospam.com> writes:
>> I have a 64Gb Innostor USD drive that I cannot read,as LM21.1 only sees
>> it as /dev/sdc using lsblk:
>>
> Try zeroing out some (maybe the first few megabytes or so) or even all
> of the storage using the raw device and /dev/zero
>
> as in
>
> dd if=/dev/zero of=/dev/sdc bs=1M count=10
>
> or maybe
>
> dd if=/dev/zero of=/dev/sdc bs=1M
>
>
> and then use gparted or similar to replace the filesystem.
>
>
> Jack
>

The controller chip is claiming it has no NAND flash chip. No media.

Paul

Re: Problem with USB drive

<kvkl1pFlg6tU1@mid.individual.net>

 copy mid

https://www.novabbs.com/computers/article-flat.php?id=7361&group=alt.os.linux.mint#7361

 copy link   Newsgroups: alt.os.linux.mint
Path: i2pn2.org!i2pn.org!weretis.net!feeder8.news.weretis.net!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail
From: rob...@nospam.com (RobH)
Newsgroups: alt.os.linux.mint
Subject: Re: Problem with USB drive
Date: Wed, 3 Jan 2024 08:43:37 +0000
Lines: 31
Message-ID: <kvkl1pFlg6tU1@mid.individual.net>
References: <kvieedF92pfU1@mid.individual.net> <s6o6C7.A1Mw@yahoo.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Trace: individual.net 3sO5A+AIZS00ri6WyYISnQ0k+IHA8k/BJlUZUQWw4SzbkrR111
Cancel-Lock: sha1:JEOO/jmG6orDoDbObLWgn6d9qKw= sha256:f+yMA3qTU+32xRtbXB6pvivWvzpnkv27YPztWtpNdkc=
User-Agent: Mozilla Thunderbird
Content-Language: en-US
In-Reply-To: <s6o6C7.A1Mw@yahoo.com>
 by: RobH - Wed, 3 Jan 2024 08:43 UTC

On 03/01/2024 05:10, Jack Strangio wrote:
> RobH <rob@nospam.com> writes:
>> I have a 64Gb Innostor USD drive that I cannot read,as LM21.1 only sees
>> it as /dev/sdc using lsblk:
>>
> Try zeroing out some (maybe the first few megabytes or so) or even all
> of the storage using the raw device and /dev/zero
>
> as in
>
> dd if=/dev/zero of=/dev/sdc bs=1M count=10
>
> or maybe
>
> dd if=/dev/zero of=/dev/sdc bs=1M
>
>
> and then use gparted or similar to replace the filesystem.
>
>
> Jack
Thamks but this i what I get:

dd if=/dev/zero of=/dev/sdc bs=1M count=10
dd: failed to open '/dev/sdc': No medium found

Then:

root@rob-Z97-HD3:~# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
sdc 8:32 1 0B 0 disk

Re: Problem with USB drive

<kvklb3Flg6tU2@mid.individual.net>

 copy mid

https://www.novabbs.com/computers/article-flat.php?id=7362&group=alt.os.linux.mint#7362

 copy link   Newsgroups: alt.os.linux.mint
Path: i2pn2.org!i2pn.org!weretis.net!feeder8.news.weretis.net!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail
From: rob...@nospam.com (RobH)
Newsgroups: alt.os.linux.mint
Subject: Re: Problem with USB drive
Date: Wed, 3 Jan 2024 08:48:34 +0000
Lines: 155
Message-ID: <kvklb3Flg6tU2@mid.individual.net>
References: <kvieedF92pfU1@mid.individual.net> <un1585$2njqs$1@dont-email.me>
<kvislbFbjenU1@mid.individual.net> <un1vsu$2rim9$1@dont-email.me>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
X-Trace: individual.net CBKbyyYYHIVyglIhrIRFcQ9s8k8LYkUaRYpeKh9H1q+CLS62Kx
Cancel-Lock: sha1:Bnz47P66aHRdJQcXm/krd/879PQ= sha256:E4hT9bhiUcZPab8KSOYnOVDy0KKqXuu8DmRiVa29H5Q=
User-Agent: Mozilla Thunderbird
Content-Language: en-US
In-Reply-To: <un1vsu$2rim9$1@dont-email.me>
 by: RobH - Wed, 3 Jan 2024 08:48 UTC

On 02/01/2024 21:40, Mark Bourne wrote:
> RobH wrote:
>> On 02/01/2024 14:05, Paul wrote:
>>> On 1/2/2024 7:38 AM, RobH wrote:
>>>> I have a 64Gb Innostor USD drive that I cannot read,as LM21.1 only
>>>> sees it as /dev/sdc using lsblk:
>>>>
>>>> ob@rob-Z97-HD3:~$ sudo lsblk
>>>> sdc      8:32   1     0B  0 disk
>>>>
>>>>
>>>> When I try sudo fdisk, it is not found
>>>>
>>>> In
>>>> rob@rob-Z97-HD3:~$ lsusb
>>>> Bus 007 Device 004: ID 1f75:0903 Innostor Technology Corporation
>>>> PenDrive
>>>>
>>>> Using Disks, the USB stick is showing but there are no options to do
>>>> anything with it, as they are all greyed out in the context
>>>>
>>>> Is there anything else I can try to get it working again.
>>>>
>>>
>>> Maybe the device has gone read-only ?
>>>
>>>     sudo apt install disktype
>>>     sudo disktype /dev/sdc
>>>
>>> You know that so far, the device has successfully had endpoints
>>> made to it. The device would not respond at all, if the NAND was
>>> totally inaccessible. It was able to read that a NAND was present.
>>> But more than that, we cannot be sure what it is doing.
>>>
>>> Disktype will try some read operations. It does not need to see
>>> partitions, to do reads. It will read the MBR. It will take the
>>> partition offset value and read the file system header sector at
>>> that offset, then parse it and tell you what file system is there.
>>>
>>> You can try a read-only mount after that, and "see if it takes".
>>> The command will need to be issued manually. If the automounter is
>>> set up to do RW mounts, and the device "does not support writing",
>>> I would expect the mount attempt to fail with a message.
>>>
>>>     sudo mkdir /mnt/ntfs                          # Make a mount
>>> point for manual mount. Remove much later.
>>>     sudo mount -o ro -t ntfs /dev/sdxY /mnt/ntfs  # Need details from
>>> disktype or ls /dev to work out the sdxY value
>>>
>>> You can also try "dmesg" or "sudo dmesg" and see if there
>>> are any messages waiting for you in there. There are other log
>>> files of course.
>>>
>>> But since you got part-way into the device, I'm going to
>>> hypothesize it is read-only for some reason.
>>>
>>>     Paul
>>
>> Thanks Paul, but:
>> After I installed disktype:
>>
>> rob@rob-Z97-HD3:~$ sudo disktype /dev/sdc
>>
>> --- /dev/sdc
>> disktype: Can't open /dev/sdc: No medium found
>>
>> rob@rob-Z97-HD3:~$ lsblk
>> sdc      8:32   1     0B  0 disk
>>
>> rob@rob-Z97-HD3:~$ sudo mkdir /mnt/ntfs
>>
>> rob@rob-Z97-HD3:~$ sudo mount -o ro -t ntfs /dev/sdc /mnt/ntfs
>> Error opening '/dev/sdc': No medium found
>> Failed to mount '/dev/sdc': No medium found
>>
>> This is from part of
>> sudo dmesg:
>>
>> cdDevice= 0.01
>> [ 3122.449323] usb 7-4.4: New USB device strings: Mfr=1, Product=2,
>> SerialNumber=3
>> [ 3122.449325] usb 7-4.4: Product: PenDrive
>> [ 3122.449326] usb 7-4.4: Manufacturer: Innostor
>> [ 3122.449327] usb 7-4.4: SerialNumber: 000000000000000336
>> [ 3122.457891] usb-storage 7-4.4:1.0: USB Mass Storage device detected
>> [ 3122.458125] scsi host6: usb-storage 7-4.4:1.0
>> [ 3122.458224] usbcore: registered new interface driver usb-storage
>> [ 3122.460106] usbcore: registered new interface driver uas
>> [ 3123.465255] scsi 6:0:0:0: Direct-Access     Innostor NAND Flash
>> 1.00 PQ: 0 ANSI: 6
>> [ 3123.465438] sd 6:0:0:0: Attached scsi generic sg3 type 0
>> [ 3123.465661] sd 6:0:0:0: [sdc] Media removed, stopped polling
>
> I'm not sure what problem it might indicate, but the "Media removed"
> line above looks suspicious.  It doesn't look like you unplugged the
> drive at this point, since that's the "USB disconnect" line further
> down.  It looks almost as if the USB-SATA interface in the USB stick is
> working, but there's no storage media attached to it.
>
> At this point after connecting a USB drive, I get several lines
> indicating the block size of the device, whether it's write protected,
> mode sense, caching, and the partitions, followed by the "Attached SCSI
> removable disk" line that you get below.
>
> If I connect a USB-SATA adapter with no disk attached to the SATA
> interface, I don't get anything at all from dmesg - which fits with what
> Paul describes about the drive controller not enumerating if there's no
> storage media attached.  Perhaps the USB-SATA controller built into USB
> sticks doesn't always have that handling, assuming that the storage will
> always be there.
>
>> [ 3123.466063] sd 6:0:0:0: [sdc] Attached SCSI removable disk
>> [ 3185.764117] usb 7-4.4: Disable of device-initiated U1 failed.
>> [ 3185.767816] usb 7-4.4: Disable of device-initiated U2 failed.
>> [ 3186.451442] usb 7-4.4: USB disconnect, device number 3
>> [ 3216.534482] usb 7-4.4: new SuperSpeed USB device number 4 using
>> xhci_hcd
>> [ 3216.554884] usb 7-4.4: New USB device found, idVendor=1f75,
>> idProduct=0903, bcdDevice= 0.01
>> [ 3216.554888] usb 7-4.4: New USB device strings: Mfr=1, Product=2,
>> SerialNumber=3
>> [ 3216.554890] usb 7-4.4: Product: PenDrive
>> [ 3216.554890] usb 7-4.4: Manufacturer: Innostor
>> [ 3216.554891] usb 7-4.4: SerialNumber: 000000000000000336
>> [ 3216.556208] usb-storage 7-4.4:1.0: USB Mass Storage device detected
>> [ 3216.556364] scsi host6: usb-storage 7-4.4:1.0
>> [ 3217.578772] scsi 6:0:0:0: Direct-Access     Innostor NAND Flash
>> 1.00 PQ: 0 ANSI: 6
>
> Is this the end of the dmesg output, or were you just copying a
> relevant-looking chunk from the middle?  If this is the end, it might be
> relevant that the "Attached scsi generic", "Media removed" and "Attached
> SCSI removable disk" lines don't appear again here, indicating that it
> doesn't behave consistently.
>
>> I also tried the usb stick in both another usb port and on another
>> linux pc, without any luck.
>
> It does look like the USB stick has gone faulty.  If possible, it might
> be worth seeing what another OS (Windows or Mac) makes of it.
>

Yes I copied and pasted what I thought are the relevant lines but I
didn't look far enough down the page, doh!

[27693.539382] scsi 6:0:0:0: Direct-Access Innostor NAND Flash
1.00 PQ: 0 ANSI: 6

3 more lines below the last line posted here.

[27693.539571] sd 6:0:0:0: Attached scsi generic sg3 type 0
[27693.543842] sd 6:0:0:0: [sdc] Media removed, stopped polling
[27693.544305] sd 6:0:0:0: [sdc] Attached SCSI removable disk

Thanks

Re: Problem with USB drive

<kvkld1Flg6tU3@mid.individual.net>

 copy mid

https://www.novabbs.com/computers/article-flat.php?id=7363&group=alt.os.linux.mint#7363

 copy link   Newsgroups: alt.os.linux.mint
Path: i2pn2.org!i2pn.org!weretis.net!feeder8.news.weretis.net!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail
From: rob...@nospam.com (RobH)
Newsgroups: alt.os.linux.mint
Subject: Re: Problem with USB drive
Date: Wed, 3 Jan 2024 08:49:37 +0000
Lines: 29
Message-ID: <kvkld1Flg6tU3@mid.individual.net>
References: <kvieedF92pfU1@mid.individual.net> <s6o6C7.A1Mw@yahoo.com>
<un2qna$33nln$1@dont-email.me>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Trace: individual.net M2PCryY4Wo4s9KEry0tq5Q6rTqCF8Q+kqsouvjFmwOpCbSMUco
Cancel-Lock: sha1:0TQRCZyxiVttgxYylYN6DhNDIKk= sha256:CLbVt/NRsnevGyoQYraanW7haD/XE9kU6QCictAwHUk=
User-Agent: Mozilla Thunderbird
Content-Language: en-US
In-Reply-To: <un2qna$33nln$1@dont-email.me>
 by: RobH - Wed, 3 Jan 2024 08:49 UTC

On 03/01/2024 05:18, Paul wrote:
> On 1/3/2024 12:10 AM, Jack Strangio wrote:
>> RobH <rob@nospam.com> writes:
>>> I have a 64Gb Innostor USD drive that I cannot read,as LM21.1 only sees
>>> it as /dev/sdc using lsblk:
>>>
>> Try zeroing out some (maybe the first few megabytes or so) or even all
>> of the storage using the raw device and /dev/zero
>>
>> as in
>>
>> dd if=/dev/zero of=/dev/sdc bs=1M count=10
>>
>> or maybe
>>
>> dd if=/dev/zero of=/dev/sdc bs=1M
>>
>>
>> and then use gparted or similar to replace the filesystem.
>>
>>
>> Jack
>>
>
> The controller chip is claiming it has no NAND flash chip. No media.
>
> Paul
>
mmm, yes it may well be time to bin it now?

Re: Problem with USB drive

<un3sd3$382a7$1@dont-email.me>

 copy mid

https://www.novabbs.com/computers/article-flat.php?id=7364&group=alt.os.linux.mint#7364

 copy link   Newsgroups: alt.os.linux.mint
Path: i2pn2.org!i2pn.org!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: nos...@needed.invalid (Paul)
Newsgroups: alt.os.linux.mint
Subject: Re: Problem with USB drive
Date: Wed, 3 Jan 2024 09:53:24 -0500
Organization: A noiseless patient Spider
Lines: 60
Message-ID: <un3sd3$382a7$1@dont-email.me>
References: <kvieedF92pfU1@mid.individual.net> <s6o6C7.A1Mw@yahoo.com>
<kvkl1pFlg6tU1@mid.individual.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
Injection-Date: Wed, 3 Jan 2024 14:53:24 -0000 (UTC)
Injection-Info: dont-email.me; posting-host="4d3ac6c9e604833e65f7870be25c9563";
logging-data="3410247"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX194xMNxBtadz7vU/3eGY7Zw0A+K+dOCKe4="
User-Agent: Ratcatcher/2.0.0.25 (Windows/20130802)
Cancel-Lock: sha1:IA4DwPeeEDUkJZYQLykneAyIrxo=
In-Reply-To: <kvkl1pFlg6tU1@mid.individual.net>
Content-Language: en-US
 by: Paul - Wed, 3 Jan 2024 14:53 UTC

On 1/3/2024 3:43 AM, RobH wrote:
> On 03/01/2024 05:10, Jack Strangio wrote:
>> RobH <rob@nospam.com> writes:
>>> I have a 64Gb Innostor USD drive that I cannot read,as LM21.1 only sees
>>> it as /dev/sdc using lsblk:
>>>
>> Try zeroing out some (maybe the first few megabytes or so) or even all
>> of the storage using the raw device and /dev/zero
>>
>> as in
>>
>>        dd if=/dev/zero of=/dev/sdc bs=1M count=10
>>
>> or maybe
>>
>>       dd if=/dev/zero of=/dev/sdc bs=1M
>>
>>
>> and then use gparted or similar to replace the filesystem.
>>
>>
>> Jack
> Thamks but this i what I get:
>
> dd if=/dev/zero of=/dev/sdc bs=1M count=10
> dd: failed to open '/dev/sdc': No medium found
>
> Then:
>
> root@rob-Z97-HD3:~# lsblk
> NAME   MAJ:MIN RM   SIZE RO TYPE MOUNTPOINTS
> sdc      8:32   1     0B  0 disk

I would mentally bin it, but don't throw it away,
as a little more research may dig up a similar event
in Google. It's just, you can't depend on Google for
a result these days, and it can take a while (and the
right keywords), to find an answer.

Of course there is the odd utility that talks to *some*
controllers. But it never seems to be the broken controller
you own.

I don't think that message means what it says. It means
it did read the device. It did cycles on it. But some
critical data is corrupt. That's my wild guess at what
it is telling us. And you can't carry out a read on the
device, unless the critical data is loaded into the
controller chip, off the NAND. The device has effectively,
come "half-way-up". That is why it can spit out that message.
The firmware seems to be loaded and running, but the NAND
map is unavailable. The sectors are not in linear order
(need a map). At least, on some USB flash stick designs.

In my years on a computer, I've only seen a storage device
come "Half-way-up", one other time. It does not happen very often.
Usually they die, silently.

Paul

1
server_pubkey.txt

rocksolid light 0.9.7
clearnet tor