Hi, I'm having trouble using my USB drives on raspberry pi 5. You can read more about everything that happened before in this post viewtopic.php?t=368289. The thing is that I had to erase that memory and now the USB drives are not working again. I will indicate what I'm doing.
I'm making a fresh intall of the 2023-12-05-raspios-bookworm-arm64 version with Rpi Imager. I place the SD card on the raspberry pi (with nothing but power and HDMI connected) the first thing I connected was a 64 GB 3.0 USB Drive and it is mounted and I can even copy some files. I connect in another port a USB dongle for a mouse and keyboard, then I unmounted the drive and disconnect it. Afterwards I connected a 16 GB 2.0 drive and the same, it worked perfectly. The I mount again the 3.0 drive and let it connected on a USB 3.0 port. I disconnected the 2.0 drive, so, I only have pluged the 3.0 drive and the dongle.
Later, I plugged an ethernet cable in the port and then I opened the console and wrote sudo apt update and sudo apt upgrade. After it finished I can still use the drive. Then, I reboot the machine leaving both dongle and 3.0 drive plugged. After the reboot, The drive is never mounted and does not work even when I try to mount it (like in this cases viewtopic.php?t=127956&sid=34020b68d32d ... 4b4f248a5e viewtopic.php?t=53832)
In any case, this is the output from sudo fdisk -l after rebooting the machine:
from lsusb -t:
I will not paste the exit from dmesg but there are none errors. Now after I connect a USB drive and execute lsusb:
With sudo fdisk -l something change, this is the last part, the one with and error:
This appeared: The backup GPT table is corrupt, but the primary appears OK, so that will be used.
And now dmesg result this new lines:
Also, after I plug an USB drive the system can not be shutdown or rebooted normally, I must press the button to turn it off.
Oh, I was forgetting, this is the output from mount with the drive plugged:
And if I make mkdir /media/usbb and then sudo mount /dev/sda /media/usbb this is the output:
Hope someone can help me because I don't why this is happening after upgrading the system.
Thanks
I'm making a fresh intall of the 2023-12-05-raspios-bookworm-arm64 version with Rpi Imager. I place the SD card on the raspberry pi (with nothing but power and HDMI connected) the first thing I connected was a 64 GB 3.0 USB Drive and it is mounted and I can even copy some files. I connect in another port a USB dongle for a mouse and keyboard, then I unmounted the drive and disconnect it. Afterwards I connected a 16 GB 2.0 drive and the same, it worked perfectly. The I mount again the 3.0 drive and let it connected on a USB 3.0 port. I disconnected the 2.0 drive, so, I only have pluged the 3.0 drive and the dongle.
Later, I plugged an ethernet cable in the port and then I opened the console and wrote sudo apt update and sudo apt upgrade. After it finished I can still use the drive. Then, I reboot the machine leaving both dongle and 3.0 drive plugged. After the reboot, The drive is never mounted and does not work even when I try to mount it (like in this cases viewtopic.php?t=127956&sid=34020b68d32d ... 4b4f248a5e viewtopic.php?t=53832)
In any case, this is the output from sudo fdisk -l after rebooting the machine:
Code:
Disk /dev/ram0: 4 MiB, 4194304 bytes, 8192 sectorsUnits: sectors of 1 * 512 = 512 bytesSector size (logical/physical): 512 bytes / 16384 bytesI/O size (minimum/optimal): 16384 bytes / 16384 bytesDisk /dev/ram1: 4 MiB, 4194304 bytes, 8192 sectorsUnits: sectors of 1 * 512 = 512 bytesSector size (logical/physical): 512 bytes / 16384 bytesI/O size (minimum/optimal): 16384 bytes / 16384 bytesDisk /dev/ram2: 4 MiB, 4194304 bytes, 8192 sectorsUnits: sectors of 1 * 512 = 512 bytesSector size (logical/physical): 512 bytes / 16384 bytesI/O size (minimum/optimal): 16384 bytes / 16384 bytesDisk /dev/ram3: 4 MiB, 4194304 bytes, 8192 sectorsUnits: sectors of 1 * 512 = 512 bytesSector size (logical/physical): 512 bytes / 16384 bytesI/O size (minimum/optimal): 16384 bytes / 16384 bytesDisk /dev/ram4: 4 MiB, 4194304 bytes, 8192 sectorsUnits: sectors of 1 * 512 = 512 bytesSector size (logical/physical): 512 bytes / 16384 bytesI/O size (minimum/optimal): 16384 bytes / 16384 bytesDisk /dev/ram5: 4 MiB, 4194304 bytes, 8192 sectorsUnits: sectors of 1 * 512 = 512 bytesSector size (logical/physical): 512 bytes / 16384 bytesI/O size (minimum/optimal): 16384 bytes / 16384 bytesDisk /dev/ram6: 4 MiB, 4194304 bytes, 8192 sectorsUnits: sectors of 1 * 512 = 512 bytesSector size (logical/physical): 512 bytes / 16384 bytesI/O size (minimum/optimal): 16384 bytes / 16384 bytesDisk /dev/ram7: 4 MiB, 4194304 bytes, 8192 sectorsUnits: sectors of 1 * 512 = 512 bytesSector size (logical/physical): 512 bytes / 16384 bytesI/O size (minimum/optimal): 16384 bytes / 16384 bytesDisk /dev/ram8: 4 MiB, 4194304 bytes, 8192 sectorsUnits: sectors of 1 * 512 = 512 bytesSector size (logical/physical): 512 bytes / 16384 bytesI/O size (minimum/optimal): 16384 bytes / 16384 bytesDisk /dev/ram9: 4 MiB, 4194304 bytes, 8192 sectorsUnits: sectors of 1 * 512 = 512 bytesSector size (logical/physical): 512 bytes / 16384 bytesI/O size (minimum/optimal): 16384 bytes / 16384 bytesDisk /dev/ram10: 4 MiB, 4194304 bytes, 8192 sectorsUnits: sectors of 1 * 512 = 512 bytesSector size (logical/physical): 512 bytes / 16384 bytesI/O size (minimum/optimal): 16384 bytes / 16384 bytesDisk /dev/ram11: 4 MiB, 4194304 bytes, 8192 sectorsUnits: sectors of 1 * 512 = 512 bytesSector size (logical/physical): 512 bytes / 16384 bytesI/O size (minimum/optimal): 16384 bytes / 16384 bytesDisk /dev/ram12: 4 MiB, 4194304 bytes, 8192 sectorsUnits: sectors of 1 * 512 = 512 bytesSector size (logical/physical): 512 bytes / 16384 bytesI/O size (minimum/optimal): 16384 bytes / 16384 bytesDisk /dev/ram13: 4 MiB, 4194304 bytes, 8192 sectorsUnits: sectors of 1 * 512 = 512 bytesSector size (logical/physical): 512 bytes / 16384 bytesI/O size (minimum/optimal): 16384 bytes / 16384 bytesDisk /dev/ram14: 4 MiB, 4194304 bytes, 8192 sectorsUnits: sectors of 1 * 512 = 512 bytesSector size (logical/physical): 512 bytes / 16384 bytesI/O size (minimum/optimal): 16384 bytes / 16384 bytesDisk /dev/ram15: 4 MiB, 4194304 bytes, 8192 sectorsUnits: sectors of 1 * 512 = 512 bytesSector size (logical/physical): 512 bytes / 16384 bytesI/O size (minimum/optimal): 16384 bytes / 16384 bytesDisk /dev/mmcblk0: 57.95 GiB, 62226694144 bytes, 121536512 sectorsUnits: sectors of 1 * 512 = 512 bytesSector size (logical/physical): 512 bytes / 512 bytesI/O size (minimum/optimal): 512 bytes / 512 bytesDisklabel type: dosDisk identifier: 0x8e2fb681Device Boot Start End Sectors Size Id Type/dev/mmcblk0p1 8192 1056767 1048576 512M c W95 FAT32 (LBA)/dev/mmcblk0p2 1056768 121536511 120479744 57.4G 83 LinuxCode:
/: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 5000M/: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/2p, 480M/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 5000M/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/2p, 480M |__ Port 2: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M |__ Port 2: Dev 2, If 1, Class=Human Interface Device, Driver=usbhid, 12MI will not paste the exit from dmesg but there are none errors. Now after I connect a USB drive and execute lsusb:
Code:
/: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 5000M/: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/2p, 480M |__ Port 1: Dev 2, If 0, Class=Mass Storage, Driver=usb-storage, 480M/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 5000M/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/2p, 480M |__ Port 2: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M |__ Port 2: Dev 2, If 1, Class=Human Interface Device, Driver=usbhid, 12MCode:
Disk /dev/mmcblk0: 57.95 GiB, 62226694144 bytes, 121536512 sectorsUnits: sectors of 1 * 512 = 512 bytesSector size (logical/physical): 512 bytes / 512 bytesI/O size (minimum/optimal): 512 bytes / 512 bytesDisklabel type: dosDisk identifier: 0x8e2fb681Device Boot Start End Sectors Size Id Type/dev/mmcblk0p1 8192 1056767 1048576 512M c W95 FAT32 (LBA)/dev/mmcblk0p2 1056768 121536511 120479744 57.4G 83 LinuxThe backup GPT table is corrupt, but the primary appears OK, so that will be used.Disk /dev/sda: 14.48 GiB, 15545139200 bytes, 30361600 sectorsDisk model: DataTraveler 2.0Units: sectors of 1 * 512 = 512 bytesSector size (logical/physical): 512 bytes / 512 bytesI/O size (minimum/optimal): 512 bytes / 512 bytesDisklabel type: gptDisk identifier: 83696C2D-FAC7-4C03-B8BB-53267169C31EDevice Start End Sectors Size Type/dev/sda1 2048 30359551 30357504 14.5G Microsoft basic dataAnd now dmesg result this new lines:
Code:
[ 486.522335] usb 3-1: new high-speed USB device number 2 using xhci-hcd[ 486.671747] usb 3-1: New USB device found, idVendor=0951, idProduct=1665, bcdDevice=11.00[ 486.671755] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3[ 486.671758] usb 3-1: Product: DataTraveler 2.0[ 486.671761] usb 3-1: Manufacturer: Kingston[ 486.671763] usb 3-1: SerialNumber: 50E54951351BDD8000000119[ 486.672459] usb-storage 3-1:1.0: USB Mass Storage device detected[ 486.672620] scsi host0: usb-storage 3-1:1.0[ 488.336627] scsi 0:0:0:0: Direct-Access Kingston DataTraveler 2.0 1100 PQ: 0 ANSI: 4[ 488.337740] sd 0:0:0:0: [sda] 30361600 512-byte logical blocks: (15.5 GB/14.5 GiB)[ 488.338234] sd 0:0:0:0: [sda] Write Protect is off[ 488.338241] sd 0:0:0:0: [sda] Mode Sense: 43 00 00 00[ 488.339525] sd 0:0:0:0: [sda] No Caching mode page found[ 488.339530] sd 0:0:0:0: [sda] Assuming drive cache: write through[ 488.346004] sd 0:0:0:0: Attached scsi generic sg0 type 0[ 488.351792] Alternate GPT is invalid, using primary GPT.[ 488.351806] sda: sda1[ 488.352041] sd 0:0:0:0: [sda] Attached SCSI removable disk[ 488.673920] ntfs3: Max link count 4000[ 488.678760] Unable to handle kernel paging request at virtual address ffff800200d00ff0[ 488.686756] Mem abort info:[ 488.689711] ESR = 0x0000000096000006[ 488.693804] EC = 0x25: DABT (current EL), IL = 32 bits[ 488.699172] SET = 0, FnV = 0[ 488.702383] EA = 0, S1PTW = 0[ 488.705561] FSC = 0x06: level 2 translation fault[ 488.710520] Data abort info:[ 488.713451] ISV = 0, ISS = 0x00000006, ISS2 = 0x00000000[ 488.719203] CM = 0, WnR = 0, TnD = 0, TagAccess = 0[ 488.724294] GCS = 0, Overlay = 0, DirtyBit = 0, Xs = 0[ 488.729629] swapper pgtable: 16k pages, 47-bit VAs, pgdp=0000000001370000[ 488.736454] [ffff800200d00ff0] pgd=18000001ffff4003, p4d=18000001ffff4003, pud=18000001ffff4003, pmd=0000000000000000[ 488.747396] Internal error: Oops: 0000000096000006 [#1] PREEMPT SMP[ 488.753687] Modules linked in: ntfs3 sg rfcomm snd_seq_dummy snd_hrtimer snd_seq snd_seq_device algif_hash algif_skcipher af_alg bnep binfmt_misc brcmfmac_wcc aes_ce_blk aes_ce_cipher ghash_ce hci_uart gf128mul btbcm sha2_ce bluetooth sha256_arm64 sha1_ce rpivid_hevc(C) pisp_be v4l2_mem2mem videobuf2_dma_contig raspberrypi_hwmon videobuf2_memops videobuf2_v4l2 brcmfmac ecdh_generic videodev brcmutil ecc cfg80211 libaes joydev videobuf2_common rfkill mc nvmem_rmem raspberrypi_gpiomem rp1_adc uio_pdrv_genirq uio i2c_dev fuse dm_mod ip_tables x_tables ipv6 spidev vc4 snd_soc_hdmi_codec drm_display_helper cec drm_dma_helper drm_kms_helper i2c_brcmstb snd_soc_core spi_bcm2835 v3d gpu_sched drm_shmem_helper snd_compress drm drm_panel_orientation_quirks gpio_keys snd_pcm_dmaengine snd_pcm snd_timer snd backlight[ 488.825406] CPU: 3 PID: 2099 Comm: pool-udisksd Tainted: G C 6.6.20+rpt-rpi-2712 #1 Debian 1:6.6.20-1+rpt1[ 488.836583] Hardware name: Raspberry Pi 5 Model B Rev 1.0 (DT)[ 488.842433] pstate: 80400009 (Nzcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)[ 488.849420] pc : __memcpy+0x1a0/0x250[ 488.853092] lr : read_log_page+0xb8/0x188 [ntfs3][ 488.857819] sp : ffffc0008015b940[ 488.861138] x29: ffffc0008015b940 x28: ffff8001019e5d00 x27: 0000000000000000[ 488.868300] x26: ffff800103738950 x25: ffff800100d00000 x24: ffff800105f5f000[ 488.875461] x23: 0000000000001000 x22: ffffc0008015ba97 x21: 0000000000003000[ 488.882623] x20: ffffc0008015bad0 x19: 0000000000000000 x18: 0000000000000000[ 488.889784] x17: 0000000000000000 x16: ffffd00084ccdff0 x15: 0000000000000000[ 488.896945] x14: 000000000525c000 x13: 0000000000000000 x12: 0000000000000000[ 488.904106] x11: 0034000000000000 x10: 0000000000000000 x9 : ffffd00045558624[ 488.911267] x8 : 0000000000000000 x7 : 00000000fffffdd5 x6 : 0000000000000034[ 488.918428] x5 : ffff800205f5d000 x4 : ffff800200d01000 x3 : ffff800100d011fe[ 488.925589] x2 : 00000000ffffe000 x1 : ffff800100d03000 x0 : ffff800105f5f000[ 488.932750] Call trace:[ 488.935197] __memcpy+0x1a0/0x250[ 488.938517] log_replay+0x990/0x3430 [ntfs3][ 488.942804] ntfs_loadlog_and_replay+0x180/0x1b0 [ntfs3][ 488.948138] ntfs_fill_super+0x8d0/0x1570 [ntfs3][ 488.952860] get_tree_bdev+0x150/0x1f8[ 488.956619] ntfs_fs_get_tree+0x20/0x38 [ntfs3][ 488.961167] vfs_get_tree+0x30/0xf8[ 488.964662] path_mount+0x408/0xa88[ 488.968157] __arm64_sys_mount+0x1dc/0x2c0[ 488.972263] invoke_syscall+0x50/0x128[ 488.976021] el0_svc_common.constprop.0+0x48/0xf0[ 488.980739] do_el0_svc+0x24/0x38[ 488.984059] el0_svc+0x40/0xe8[ 488.987118] el0t_64_sync_handler+0x100/0x130[ 488.991486] el0t_64_sync+0x190/0x198[ 488.995157] Code: a93e24a8 a93f2caa d65f03c0 d503201f (a97f348c) [ 489.001272] ---[ end trace 0000000000000000 ]---Oh, I was forgetting, this is the output from mount with the drive plugged:
Code:
sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)proc on /proc type proc (rw,relatime)udev on /dev type devtmpfs (rw,nosuid,relatime,size=3946080k,nr_inodes=246630,mode=755)devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)tmpfs on /run type tmpfs (rw,nosuid,nodev,noexec,relatime,size=824176k,mode=755)/dev/mmcblk0p2 on / type ext4 (rw,noatime)securityfs on /sys/kernel/security type securityfs (rw,nosuid,nodev,noexec,relatime)tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k)cgroup2 on /sys/fs/cgroup type cgroup2 (rw,nosuid,nodev,noexec,relatime,nsdelegate,memory_recursiveprot)pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime)bpf on /sys/fs/bpf type bpf (rw,nosuid,nodev,noexec,relatime,mode=700)systemd-1 on /proc/sys/fs/binfmt_misc type autofs (rw,relatime,fd=29,pgrp=1,timeout=0,minproto=5,maxproto=5,direct,pipe_ino=6268)mqueue on /dev/mqueue type mqueue (rw,nosuid,nodev,noexec,relatime)tracefs on /sys/kernel/tracing type tracefs (rw,nosuid,nodev,noexec,relatime)debugfs on /sys/kernel/debug type debugfs (rw,nosuid,nodev,noexec,relatime)configfs on /sys/kernel/config type configfs (rw,nosuid,nodev,noexec,relatime)fusectl on /sys/fs/fuse/connections type fusectl (rw,nosuid,nodev,noexec,relatime)ramfs on /run/credentials/systemd-sysctl.service type ramfs (ro,nosuid,nodev,noexec,relatime,mode=700)ramfs on /run/credentials/systemd-sysusers.service type ramfs (ro,nosuid,nodev,noexec,relatime,mode=700)ramfs on /run/credentials/systemd-tmpfiles-setup-dev.service type ramfs (ro,nosuid,nodev,noexec,relatime,mode=700)/dev/mmcblk0p1 on /boot/firmware type vfat (rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,errors=remount-ro)ramfs on /run/credentials/systemd-tmpfiles-setup.service type ramfs (ro,nosuid,nodev,noexec,relatime,mode=700)binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc (rw,nosuid,nodev,noexec,relatime)sunrpc on /run/rpc_pipefs type rpc_pipefs (rw,relatime)tmpfs on /run/user/1000 type tmpfs (rw,nosuid,nodev,relatime,size=824160k,nr_inodes=206040,mode=700,uid=1000,gid=1000)gvfsd-fuse on /run/user/1000/gvfs type fuse.gvfsd-fuse (rw,nosuid,nodev,relatime,user_id=1000,group_id=1000)Code:
mount: /media/usbb: /dev/sda already mounted or mount point busy. dmesg(1) may have more information after failed mount system call.Thanks
Statistics: Posted by ocelotandall — Sat Apr 06, 2024 1:50 am