On 2022-04-22 00:03, Per Inge Oestmoen wrote:
Hello.
I use openSUSE Leap 15.3. Trouble is, when I attach USB sticks from 16-128 GB there are no problems. They are mounted and read immediately upon being attached.
When I attach large external USB disks, there is a different story. The disks most often do not show up. Sometimes they do, but most times I must read the disks (formatted with EXT4, FAT32 and EXFAT) on a Mac laptop in order to access them. Which, admittedly, makes me ashamed.
The question is why this happens.
To elucidate the problem, I have typed fdisk -l and dmesg, and the results are in the links below. I shall be extremely thankful if you can have a look at these outputs and see if you can spot the source of my problem. If these files do not provide a clue, please tell me what commands I should try next.
In both cases, an external disk was attached. However, the system failed to see it.
The fdisk -l output:
http://www.coldsiberia.net/technics/fdisk_l_21042022.txt
The dmesg output:
As you can see in your outputs, the disks are recognized. I see sdb with one partition, and sda, with 4. [ 2.428846] usb 1-2: New USB device found, idVendor=0b05, idProduct=190e, bcdDevice= 2.00 [ 2.428852] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 2.428855] usb 1-2: Product: ASUS USB-BT500 [ 2.428857] usb 1-2: Manufacturer: Realtek [ 2.428860] usb 1-2: SerialNumber: 00E04C239987 [ 2.444976] scsi 2:0:0:0: Direct-Access ATA WDC WD30EFRX-68E 0A82 PQ: 0 ANSI: 5 [ 2.446060] scsi 3:0:0:0: Direct-Access ATA Samsung SSD 860 2B6Q PQ: 0 ANSI: 5 [ 2.461082] sd 2:0:0:0: [sda] 5860533168 512-byte logical blocks: (3.00 TB/2.73 TiB) [ 2.461083] sd 2:0:0:0: [sda] 4096-byte physical blocks [ 2.461087] sd 2:0:0:0: [sda] Write Protect is off [ 2.461087] sd 2:0:0:0: [sda] Mode Sense: 00 3a 00 00 [ 2.461092] sd 2:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA It is your desktop that doesn't open or offer to open them automatically, but you do not even say what desktop you are using. You can probably find the entries in the file browser of your desktop, and click to open them. The technique to investigate these things is not to send the entire dmesg log. Open a terminal, su to root if necessary, then issue one of these commands: tail -f /var/log/messages dmesg --follow journalctl --follow (and hit enter twice or more) THEN, plug in the external media. What is interesting are only the new lines that appear in the window. -- Cheers / Saludos, Carlos E. R. (from 15.3 x86_64 at Telcontar)