@
magostinelli
I agree with the observations of both @
Nutul and @
GioF_71.
Basically, this isn't a moOde code issue*. It is an issue with your specific hardware setup and all we can do is toss suggestions your way.
I had done some tests last night with the first external SSD drive I could find near at hand, which is a 1TB Samsung m.2 NVMe SSD module in an SSK USB adapter. I plugged it into a Pi 3B running moOde 9.0.3 and powered by a Canakit 5v/2.5a powerpack.
From lsblk I get the drive's device assignment, partitioning, formatting, and mountpoints.
Code:
rho@red:~ $ lsblk -fm
NAME FSTYPE FSVER LABEL UUID FSAVAIL FSUSE% MOUNTPOINTS SIZE OWNER GROUP MODE
sda 931.5G root disk brw-rw----
└─sda1 exfat 1.0 Data 677C-FA64 930.8G 0% /media/Data 931.5G root disk brw-rw----
mmcblk0 14.8G root disk brw-rw----
├─mmcblk0p1 vfat FAT32 bootfs AF49-3217 446.9M 12% /boot/firmware 512M root disk brw-rw----
└─mmcblk0p2 ext4 1.0 rootfs ef4e2b66-9674-4ed8-a66d-326796522901 10G 23% / 14.3G root disk brw-rw----
From dmesg (or journalctl) I get perfectly normal messages related to drive sda
Code:
rho@red:~ $ dmesg|grep sda
[ 6.290502] sd 0:0:0:0: [sda] 1953525168 512-byte logical blocks: (1.00 TB/932 GiB)
[ 6.302722] sd 0:0:0:0: [sda] Write Protect is off
[ 6.305073] sd 0:0:0:0: [sda] Mode Sense: 37 00 00 08
[ 6.310044] sd 0:0:0:0: [sda] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
[ 6.344864] sda: sda1
[ 6.354993] sd 0:0:0:0: [sda] Attached SCSI disk
As it happens, I ran vcgencmd last night while scanning this drive and see no undervolt or throttling flags
Code:
rho@red:~ $ vcgencmd get_throttled
throttled=0x0
Following @
GioF_71's suggestion, I ran lsusb this morning so you see what the output looks like
Code:
rho@red:~ $ lsusb
Bus 001 Device 009: ID 0bda:9210 Realtek Semiconductor Corp. RTL9210 M.2 NVME Adapter
Bus 001 Device 004: ID 041e:3125 Creative Technology, Ltd Creative Bluetooth Audio W2
Bus 001 Device 003: ID 0424:ec00 Microchip Technology, Inc. (formerly SMSC) SMSC9512/9514 Fast Ethernet Adapter
Bus 001 Device 002: ID 0424:9514 Microchip Technology, Inc. (formerly SMSC) SMC9514 Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
As you can see, in my case, the controller in question is a Realtek.
Finally, to test the idea that the power supply might be close to being max'ed out, I also plugged in a 1TB Western Digital Passport HD which has a USB interface. This drive is announced by lsusb as
Code:
Bus 001 Device 008: ID 1058:25e1 Western Digital Technologies, Inc. My Passport (WD20NMVW)
No drama here. Now I have both drive sda and drive sdb running with no undervolt or throttling codes and no error messages in dmesg. So, although a USB hub/dock certainly can handle a more power-consuming set of USB devices, I don't seem to need it in my test case. Normal operation all around.
IMHO if you continue to have problems you might be better served to post them on the Raspberry Pi Forums where far more people with far more varieties of hardware can respond. They will need lots of details about all your hardware.
Good hunting.
Regards,
Kent
*The one curiosity is your observation that you didn't see this disappearing act with an older release of moOde, but as far as the drive interface is concerned this means an older release of Raspberry Pi OS Lite.
