Opened 4 years ago

Closed 17 months ago

Last modified 17 months ago

#16791 closed bug (fixed)

My SanDisk 1tb ssd shows up twice in DriveSetup under different names

Reported by: WildKeccak Owned by: nobody
Priority: normal Milestone: R1/beta5
Component: Drivers/Disk/USB Version: R1/Development
Keywords: Cc:
Blocked By: Blocking:
Platform: x86-64

Description

Walter (hrev54950) x86_64

Intel Core i5-7200U

Model is SDSSDE60-1T00

Attachments (5)

33CF72B8-0EB8-413A-BFAA-BD88AF5C9FB6.jpeg (2.9 MB ) - added by WildKeccak 4 years ago.
This shows the drive basically being listed twice
syslog (284.0 KB ) - added by WildKeccak 4 years ago.
The syslog, which I presume is good, but I did restart the desktop that failed to start.
output.txt (28.0 KB ) - added by WildKeccak 4 years ago.
The output of listusb -v
dmesg.txt (69.1 KB ) - added by WildKeccak 4 years ago.
dmesg from MX Linux, running
apparently_fixed.png (98.2 KB ) - added by WildKeccak 17 months ago.

Change History (15)

by WildKeccak, 4 years ago

This shows the drive basically being listed twice

by WildKeccak, 4 years ago

Attachment: syslog added

The syslog, which I presume is good, but I did restart the desktop that failed to start.

comment:1 by miqlas, 4 years ago

It looks completely correct to me, it seems your SSD report itself as 2 device. Maybe it supports some kind of hardware-encryption or a security card unlock option? I tried to research the “Sandisk SES Device” but nothing found, except it works strange in linux too: https://ubuntuforums.org/showthread.php?t=2453248

comment:2 by pulkomandy, 4 years ago

Component: - GeneralDrivers/Disk/USB
Keywords: USB SSD removed

The output of listusb -v for the device may be useful

comment:3 by madmax, 4 years ago

https://ubuntuforums.org/showthread.php?t=2453248

The dmesg there shows the same two device names. It would seem 'SES Device' is the enclosure device for SCSI enclosure services and 'Extreme SSD' the direct access to the disk?

Last edited 4 years ago by madmax (previous) (diff)

by WildKeccak, 4 years ago

Attachment: output.txt added

The output of listusb -v

comment:4 by WildKeccak, 4 years ago

Seems to work, although I can't do anything with said device, such as partitioning, setting up partitioning schemes, etc. I'll check it out further.

comment:5 by WildKeccak, 4 years ago

There are things on the drive, namely MX Linux. But that's another bug

by WildKeccak, 4 years ago

Attachment: dmesg.txt added

dmesg from MX Linux, running

comment:6 by WildKeccak, 4 years ago

I attach the drive and restart the computer
I boot
I receive a light blue screen with no icons
I restart the desktop
I start drive setup
This happens again

Last edited 4 years ago by WildKeccak (previous) (diff)

comment:7 by waddlesplash, 18 months ago

Please retest after hrev57051.

by WildKeccak, 17 months ago

Attachment: apparently_fixed.png added

comment:8 by WildKeccak, 17 months ago

Seems to work now

comment:9 by waddlesplash, 17 months ago

Milestone: UnscheduledR1/beta5
Resolution: fixed
Status: newclosed

Excellent, thanks for testing!

comment:10 by khallebal, 17 months ago

The first drive is published as

/dev/disk/usb/0/0/raw

the sec should be set to

/dev/disk/usb/1/0/raw

and not

/dev/disk/usb/2/0/raw
Note: See TracTickets for help on using tickets.