I have an external 1TB 2.5" SSD in a USB cassette used as an archive. It became inaccessible despite appearing in the file table. Its underlying file format is FAT and the disk is readable on a Windows system. I have had the disk for a number of years and it has been problem free.
I have a new 1TB m.2 SSD that in a USB cassette that I am planning to use with a native Linux file system to provide a duplicate archive. It doesn’t appear in the file table.
A 16GB USB stick (thumb drive) appears and works as normal.
I’m a bit clued out and would be grateful for any advice.
That is a very vague conclusion. You better give computer based evidence on what does not work as expected.
BTW, seeing that you switch this to be used by a Windows system, be sure it is safely removed there. And taking it from a shutdown Windows system is only OK when you do not use fastboot in Windows.
gerry@Unknown-18-c0-4d-6a-ed-f9:~> sudo journalctl -f
Oct 08 13:49:48 Unknown-18-c0-4d-6a-ed-f9 dolphin[2402]: kf.solid.backends.udisks2: Error getting props: "org.freedesktop.DBus.Error.UnknownMethod" "Object does not exist at path “/org/freedesktop/UDisks2/drives/Samsung_SSD_860_EVO_1TB_S3Z9NB0M303017Y”" for "/org/freedesktop/UDisks2/drives/Samsung_SSD_860_EVO_1TB_S3Z9NB0M303017Y"
Oct 08 13:49:48 Unknown-18-c0-4d-6a-ed-f9 dolphin[2429]: kf.solid.backends.udisks2: Error getting props: "org.freedesktop.DBus.Error.UnknownMethod" "Object does not exist at path “/org/freedesktop/UDisks2/drives/Samsung_SSD_860_EVO_1TB_S3Z9NB0M303017Y”" for "/org/freedesktop/UDisks2/drives/Samsung_SSD_860_EVO_1TB_S3Z9NB0M303017Y"
Oct 08 13:49:48 Unknown-18-c0-4d-6a-ed-f9 plasmashell[2006]: kf.solid.backends.udisks2: Error getting props: "org.freedesktop.DBus.Error.UnknownMethod" "Object does not exist at path “/org/freedesktop/UDisks2/drives/Samsung_SSD_860_EVO_1TB_S3Z9NB0M303017Y”" for "/org/freedesktop/UDisks2/drives/Samsung_SSD_860_EVO_1TB_S3Z9NB0M303017Y"
Oct 08 13:49:48 Unknown-18-c0-4d-6a-ed-f9 kernel: sd 6:0:0:0: [sda] Synchronizing SCSI cache
Oct 08 13:49:48 Unknown-18-c0-4d-6a-ed-f9 kernel: sd 6:0:0:0: [sda] Synchronize Cache(10) failed: Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
Oct 08 13:50:10 Unknown-18-c0-4d-6a-ed-f9 sudo[3592]: gerry : TTY=pts/1 ; PWD=/home/gerry ; USER=root ; COMMAND=/usr/bin/journalctl -f
Oct 08 13:50:10 Unknown-18-c0-4d-6a-ed-f9 sudo[3592]: pam_kwallet5(sudo:setcred): pam_kwallet5: pam_sm_setcred
Oct 08 13:50:10 Unknown-18-c0-4d-6a-ed-f9 sudo[3592]: pam_unix(sudo:session): session opened for user root(uid=0) by gerry(uid=1000)
Oct 08 13:50:10 Unknown-18-c0-4d-6a-ed-f9 sudo[3592]: pam_kwallet5(sudo:session): pam_kwallet5: pam_sm_open_session
Oct 08 13:50:10 Unknown-18-c0-4d-6a-ed-f9 sudo[3592]: pam_kwallet5(sudo:session): pam_kwallet5: not a graphical session, skipping. Use force_run parameter to ignore this.
So, no lines were added when you connected the device? Because what we see here is the last few lines before you entered the command. (we see you change to root).
The KDE device notifier works like a charm since a long time. You may post the journal as follows.
erlangen:~ # journalctl -f
...
# Plugin of USB Drive
...
Oct 09 12:42:14 erlangen kernel: usb 2-3: new SuperSpeed USB device number 8 using xhci_hcd
Oct 09 12:42:14 erlangen kernel: usb 2-3: New USB device found, idVendor=090c, idProduct=2000, bcdDevice=11.00
Oct 09 12:42:14 erlangen kernel: usb 2-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Oct 09 12:42:14 erlangen kernel: usb 2-3: Product: Intenso Ultra Line
Oct 09 12:42:14 erlangen kernel: usb 2-3: Manufacturer: SMI
Oct 09 12:42:14 erlangen kernel: usb 2-3: SerialNumber: CCYYMMDDHHmmSSVZ
Oct 09 12:42:14 erlangen kernel: usb-storage 2-3:1.0: USB Mass Storage device detected
Oct 09 12:42:14 erlangen kernel: usb-storage 2-3:1.0: Quirks match for vid 090c pid 2000: 800000
Oct 09 12:42:14 erlangen kernel: scsi host12: usb-storage 2-3:1.0
Oct 09 12:42:14 erlangen mtp-probe[1381]: checking bus 2, device 8: "/sys/devices/pci0000:00/0000:00:02.1/0000:01:00.0/usb2/2-3"
Oct 09 12:42:14 erlangen mtp-probe[1381]: bus: 2, device: 8 was not an MTP device
Oct 09 12:42:14 erlangen mtp-probe[1382]: checking bus 2, device 8: "/sys/devices/pci0000:00/0000:00:02.1/0000:01:00.0/usb2/2-3"
Oct 09 12:42:14 erlangen mtp-probe[1382]: bus: 2, device: 8 was not an MTP device
Oct 09 12:42:15 erlangen kernel: scsi 12:0:0:0: Direct-Access Intenso Ultra Line 1100 PQ: 0 ANSI: 6
Oct 09 12:42:15 erlangen kernel: sd 12:0:0:0: Attached scsi generic sg2 type 0
Oct 09 12:42:15 erlangen kernel: sd 12:0:0:0: [sdb] 62545920 512-byte logical blocks: (32.0 GB/29.8 GiB)
Oct 09 12:42:15 erlangen kernel: sd 12:0:0:0: [sdb] Write Protect is off
Oct 09 12:42:15 erlangen kernel: sd 12:0:0:0: [sdb] Mode Sense: 43 00 00 00
Oct 09 12:42:15 erlangen kernel: sd 12:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Oct 09 12:42:15 erlangen kernel: sdb: sdb1 sdb2
Oct 09 12:42:15 erlangen kernel: sd 12:0:0:0: [sdb] Attached SCSI removable disk
Oct 09 12:42:15 erlangen dbus-daemon[1090]: [system] Activating service name='org.kde.kded.smart' requested by ':1.812' (uid=1000 pid=20557 comm="/usr/bin/kded5") (using servicehelper)
Oct 09 12:42:15 erlangen dbus-daemon[1090]: [system] Successfully activated service 'org.kde.kded.smart'
Oct 09 12:42:15 erlangen plasmashell[20601]: file:///usr/share/plasma/plasmoids/org.kde.plasma.devicenotifier/contents/ui/DeviceItem.qml:36:5: Unable to assign [undefined] to bool
Oct 09 12:42:15 erlangen plasmashell[20601]: file:///usr/share/plasma/plasmoids/org.kde.plasma.devicenotifier/contents/ui/DeviceItem.qml:35:5: Unable to assign [undefined] to bool