You are not logged in.

#1 2022-10-07 11:34:18

Jazztache
Member
Registered: 2022-10-07
Posts: 63

USB Stick Diagonstics, Need Help With Fixing USB Stick

USB Stick Diagnostics, Need Help With Fixing USB Stick
2140Fri07Oct22 → 2211Fri07Oct22
jazztache@jazztarche
══════════──────────══════════
Hello!

I have been looking around online for a solution for this, and I would like to check if I have killed this USB Stick.
I'm gonna start with what happened then what commands I tried. I'll try to be as detailed as I can.

Don't worry! I had backups! But I'm more concerned about the USB stick Hardware... which means a fresh 64gb USB stick was (hopefully not!) lost.
This is happening on my Arch Linux install.

= WHAT HAPPENED =

Today, I decided to open up a fresh Lexar 64GB USB Stick.
I then decided it would be a cool idea to partition the disk such that the first partition was 80% of the disk, formatted in ext4. The label was "Jazz The Tache"
I then formatted the second partition in fat32, and named the partition "Jazz but W*ndows (ew)"
I did this in KDE Partition manager, and it seemed fine. Dolphin picked up both partitions easily.
Weirdly enough, I didn't have access the the ext4 part of the drive. Couldn't create new files in Dolphin or copy paste.
Me attempting to take it stride and be proactive decided to just use `sudo cp` and it was working fine. Had to interrupt a few ones but otherwise everything was OK. I copied some stuff over from my NTFS External 2TB Drive, but it was only a few megabytes and it wasn't too intensive.
Regardless, the terminals started to hang. I had a few different `sudo cp` transfers, and I decided to cancel all but one of them.

I had a party to go out to, and I was copying over my Uni files. I thought, "Huh, guess those pictures and Multimedia stuff is taking it's time. Guess I can leave it on whilst I do stuff." And so, I did stuff. For three hours.

I get back home to see the transfer still going on, so I cancel it, then try to dismount the USB. I forget which error the Disks UI said, but it was in red. After a while, it unmounted and I pulled the USB stick out, and put it back in.
Nothing comes up. 'Oh, guess that corrupted the files... Guess I'll check partitions'. Open KDE Partition Manager, and it's not even on the list! Oh. I do the usual `lsblk -f` and it's there! With no partitions...
I try several different solutions from the internet, all of them come up with a similar error. I even tried testdisk and got the same error.

Below is the output of me trying different solutions, all with sudo. The device file is detected in `/dev/sdb` on my Arch main PC.
NOTE: For the `dmesg` output, the 2TB Drive is a seperate drive from the 64GB USB Stick. Issues seem to start around `[37060.942742]`.
NOTE 2: The `mkfs.exfat` works on my EndeavourOS laptop. It's not installed on my Arch main PC. Tried this on both.

= COMMAND OUTPUT =

jazztache@jazztarche ~> lsblk -f
NAME               FSTYPE      FSVER LABEL      UUID                                 FSAVAIL FSUSE% MOUNTPOINTS
sda                                                                                                 
├─sda1                                                                                              
└─sda2             ntfs              New Volume 2A522A035229D3FB                      491.4G    82% /mnt/EssDeeAye
sdb                                                                                                 
zram0                                                                                               [SWAP]
nvme0n1                                                                                             
├─nvme0n1p1        vfat        FAT32            A45B-574D                             445.7M    13% /boot
├─nvme0n1p2        ext4        1.0              1c795a9f-1163-4f67-afbf-29d64da4076f    6.1G    63% /
└─nvme0n1p3        crypto_LUKS 2                2bb84a5b-fa35-48a1-b43a-9f822a8dc335                
  └─ainstnvme0n1p3 ext4        1.0              6e3aec9d-f0a1-4d13-b9f7-a6de42a6aad0  394.4G     7% /home
jazztache@jazztarche ~> lsblk -f
NAME               FSTYPE      FSVER LABEL      UUID                                 FSAVAIL FSUSE% MOUNTPOINTS
sda                                                                                                 
├─sda1                                                                                              
└─sda2             ntfs              New Volume 2A522A035229D3FB                      491.4G    82% /mnt/EssDeeAye
zram0                                                                                               [SWAP]
nvme0n1                                                                                             
├─nvme0n1p1        vfat        FAT32            A45B-574D                             445.7M    13% /boot
├─nvme0n1p2        ext4        1.0              1c795a9f-1163-4f67-afbf-29d64da4076f    6.1G    63% /
└─nvme0n1p3        crypto_LUKS 2                2bb84a5b-fa35-48a1-b43a-9f822a8dc335                
  └─ainstnvme0n1p3 ext4        1.0              6e3aec9d-f0a1-4d13-b9f7-a6de42a6aad0  394.4G     7% /home
jazztache@jazztarche ~> sudo fdisk /dev/sdb
[sudo] password for jazztache: 

Welcome to fdisk (util-linux 2.38.1).
Changes will remain in memory only, until you decide to write them.
Be careful before using the write command.

fdisk: cannot open /dev/sdb: No medium found
jazztache@jazztarche ~ [1]> sudo dd if=/dev/zero of=/dev/sdb bs=4096 status=progress
dd: failed to open '/dev/sdb': No medium found
jazztache@jazztarche ~ [1]> sudo mkfs.exfat /dev/sdb
sudo: mkfs.exfat: command not found
jazztache@jazztarche ~ [1]> sudo dmesg | grep sdb
[    4.192999] sd 4:0:0:0: [sdb] 3906963456 512-byte logical blocks: (2.00 TB/1.82 TiB)
[    4.193310] sd 4:0:0:0: [sdb] Write Protect is off
[    4.193312] sd 4:0:0:0: [sdb] Mode Sense: 47 00 10 08
[    4.193604] sd 4:0:0:0: [sdb] No Caching mode page found
[    4.193606] sd 4:0:0:0: [sdb] Assuming drive cache: write through
[    4.198341]  sdb: sdb1
[    4.198426] sd 4:0:0:0: [sdb] Attached SCSI disk
[15545.899438] sd 4:0:0:0: [sdb] Spinning up disk...
[15549.017810] sd 4:0:0:0: [sdb] 3906963456 512-byte logical blocks: (2.00 TB/1.82 TiB)
[15549.018159] sd 4:0:0:0: [sdb] Write Protect is off
[15549.018162] sd 4:0:0:0: [sdb] Mode Sense: 47 00 10 08
[15549.018469] sd 4:0:0:0: [sdb] No Caching mode page found
[15549.018471] sd 4:0:0:0: [sdb] Assuming drive cache: write through
[15549.057411]  sdb: sdb1
[15549.057615] sd 4:0:0:0: [sdb] Attached SCSI disk
[16674.128093] sd 4:0:0:0: [sdb] Spinning up disk...
[16677.250017] sd 4:0:0:0: [sdb] 3906963456 512-byte logical blocks: (2.00 TB/1.82 TiB)
[16677.250299] sd 4:0:0:0: [sdb] Write Protect is off
[16677.250301] sd 4:0:0:0: [sdb] Mode Sense: 47 00 10 08
[16677.250590] sd 4:0:0:0: [sdb] No Caching mode page found
[16677.250591] sd 4:0:0:0: [sdb] Assuming drive cache: write through
[16677.296443]  sdb: sdb1
[16677.296617] sd 4:0:0:0: [sdb] Attached SCSI disk
[36954.154291] sd 4:0:0:0: [sdb] Media removed, stopped polling
[36954.154482] sd 4:0:0:0: [sdb] Attached SCSI removable disk
[37030.201566] sd 4:0:0:0: [sdb] Media removed, stopped polling
[37030.201799] sd 4:0:0:0: [sdb] Attached SCSI removable disk
[37057.785126] sd 4:0:0:0: [sdb] Spinning up disk...
[37060.903165] sd 4:0:0:0: [sdb] 3906963456 512-byte logical blocks: (2.00 TB/1.82 TiB)
[37060.903496] sd 4:0:0:0: [sdb] Write Protect is off
[37060.903497] sd 4:0:0:0: [sdb] Mode Sense: 47 00 10 08
[37060.903788] sd 4:0:0:0: [sdb] No Caching mode page found
[37060.903788] sd 4:0:0:0: [sdb] Assuming drive cache: write through
[37060.942648]  sdb: sdb1
[37060.942742] sd 4:0:0:0: [sdb] Attached SCSI disk
[37273.738839] sd 4:0:0:0: [sdb] Media removed, stopped polling
[37273.739070] sd 4:0:0:0: [sdb] Attached SCSI removable disk
[37667.329213] /dev/sdb: Can't open blockdev
[39756.580723] sd 4:0:0:0: [sdb] Media removed, stopped polling
[39756.580943] sd 4:0:0:0: [sdb] Attached SCSI removable disk
[42537.652027] sd 4:0:0:0: [sdb] Media removed, stopped polling
[42537.652229] sd 4:0:0:0: [sdb] Attached SCSI removable disk
jazztache@jazztarche ~> 

A bit afterwards, I ran testdisk

jazztache@jazztarche ~> testdisk /dev/sdb
TestDisk 7.1, Data Recovery Utility, July 2019
Christophe GRENIER <grenier@cgsecurity.org>
[url]https://www.cgsecurity.org[/url]

Unable to open file or device /dev/sdb: Permission denied
jazztache@jazztarche ~ [1]> sudo testdisk /dev/sdb
TestDisk 7.1, Data Recovery Utility, July 2019
Christophe GRENIER <grenier@cgsecurity.org>
[url]https://www.cgsecurity.org[/url]

Unable to open file or device /dev/sdb: No medium found
jazztache@jazztarche ~ [1]> 

= HELP =

I'm hoping to salvage my USB Stick. I don't mind if I have to go back to exFat, and the data on it has been backup up from other sources, since I'm usually good with backing up stuff and keeping copies before I am sure I can move it over completely. This isn't a data salvage thing, I just wanna make sure the USB Stick is all good.

Hopefully this is good for someone to help me out of this situation. If anyone has been in this situation and can help me, please pipe up!
I'm kind of expecting to be my USB Stick's autopsy... but I'll probs learn a bit out of this <:).
Any `man` pages thrown my way will be welcome, even if I prefer mostly just a command output so I can get back on my feet with this quickly.

Thanks for any help in advance smile

Last edited by Jazztache (2022-10-07 11:39:11)

Offline

#2 2022-10-07 11:46:34

V1del
Forum Moderator
Registered: 2012-10-16
Posts: 25,157

Re: USB Stick Diagonstics, Need Help With Fixing USB Stick

These outputs are all over the place. Run

sudo dmesg -w

plug in the stick post all outputs generated from that moment on if you do not want to share a full dmesg.

Last edited by V1del (2022-10-07 11:48:37)

Offline

#3 2022-10-07 12:27:59

Jazztache
Member
Registered: 2022-10-07
Posts: 63

Re: USB Stick Diagonstics, Need Help With Fixing USB Stick

Truncated DMESG output, comin up.
Starting from 30964, which is a bit earlier. Found some interesting stuff that was highlighted in red.
Also, I >>'d the full dmesg into a .log file so I have it for later. Gonna make that standard from now on incase this happens.

[30964.315599] INFO: task cp:14380 blocked for more than 122 seconds.
[30964.315604]       Tainted: P           OE     5.19.13-arch1-1 #1
[30964.315608] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[30964.315611] task:cp              state:D stack:    0 pid:14380 ppid: 14379 flags:0x00004002
[30964.315618] Call Trace:
[30964.315621]  <TASK>
[30964.315624]  __schedule+0x356/0x11a0
[30964.315631]  ? node_dirty_ok+0xd7/0x170
[30964.315641]  schedule+0x5e/0xd0
[30964.315647]  wait_transaction_locked+0x8a/0xd0 [jbd2 f4d8af8d9bb39a8834426b078afff6f192256a22]
[30964.315674]  ? cpuacct_percpu_seq_show+0x20/0x20
[30964.315681]  add_transaction_credits+0x1a0/0x300 [jbd2 f4d8af8d9bb39a8834426b078afff6f192256a22]
[30964.315707]  start_this_handle+0x104/0x590 [jbd2 f4d8af8d9bb39a8834426b078afff6f192256a22]
[30964.315732]  ? jbd2__journal_start+0x94/0x1f0 [jbd2 f4d8af8d9bb39a8834426b078afff6f192256a22]
[30964.315756]  ? kmem_cache_alloc+0x16a/0x300
[30964.315763]  jbd2__journal_start+0xfc/0x1f0 [jbd2 f4d8af8d9bb39a8834426b078afff6f192256a22]
[30964.315788]  __ext4_journal_start_sb+0x109/0x120 [ext4 5986551db1265b7ec1cf767c291bb4a87c08658e]
[30964.315861]  ext4_dirty_inode+0x38/0x80 [ext4 5986551db1265b7ec1cf767c291bb4a87c08658e]
[30964.315940]  __mark_inode_dirty+0x1bc/0x3c0
[30964.315951]  generic_write_end+0xf9/0x1a0
[30964.315963]  generic_perform_write+0x11b/0x210
[30964.315978]  ext4_buffered_write_iter+0x7c/0x110 [ext4 5986551db1265b7ec1cf767c291bb4a87c08658e]
[30964.316053]  new_sync_write+0x137/0x1c0
[30964.316068]  vfs_write+0x1ef/0x270
[30964.316074]  ksys_write+0x6f/0xf0
[30964.316081]  do_syscall_64+0x5c/0x90
[30964.316094]  ? vfs_read+0x126/0x190
[30964.316099]  ? vfs_read+0x126/0x190
[30964.316105]  ? syscall_exit_to_user_mode+0x1b/0x40
[30964.316113]  ? do_syscall_64+0x6b/0x90
[30964.316122]  ? syscall_exit_to_user_mode+0x1b/0x40
[30964.316129]  ? do_syscall_64+0x6b/0x90
[30964.316138]  entry_SYSCALL_64_after_hwframe+0x63/0xcd
[30964.316149] RIP: 0033:0x7fe9465f9e54
[30964.316155] RSP: 002b:00007ffc4f38de68 EFLAGS: 00000202 ORIG_RAX: 0000000000000001
[30964.316163] RAX: ffffffffffffffda RBX: 0000000000020000 RCX: 00007fe9465f9e54
[30964.316168] RDX: 0000000000020000 RSI: 00007fe9461df000 RDI: 0000000000000005
[30964.316173] RBP: 0000000000020000 R08: 00000000ffffffff R09: 0000000000000000
[30964.316177] R10: 0000000000000022 R11: 0000000000000202 R12: 00007fe9461df000
[30964.316181] R13: 0000000000000005 R14: 0000000000020000 R15: 0000000000000000
[30964.316189]  </TASK>
[36348.841968] sd 5:0:0:0: [sdc] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=0s
[36348.841971] sd 5:0:0:0: [sdc] tag#0 Sense Key : Not Ready [current] 
[36348.841972] sd 5:0:0:0: [sdc] tag#0 Add. Sense: Medium not present
[36348.841973] sd 5:0:0:0: [sdc] tag#0 CDB: Write(10) 2a 00 01 80 0f 90 00 00 d8 00
[36348.841974] I/O error, dev sdc, sector 25169808 op 0x1:(WRITE) flags 0x103000 phys_seg 27 prio class 0
[36348.841977] Buffer I/O error on dev sdc1, logical block 3145970, lost async page write
[36348.841979] Buffer I/O error on dev sdc1, logical block 3145971, lost async page write
[36348.841980] Buffer I/O error on dev sdc1, logical block 3145972, lost async page write
[36348.841981] Buffer I/O error on dev sdc1, logical block 3145973, lost async page write
[36348.841982] Buffer I/O error on dev sdc1, logical block 3145974, lost async page write
[36348.841983] Buffer I/O error on dev sdc1, logical block 3145975, lost async page write
[36348.841983] Buffer I/O error on dev sdc1, logical block 3145976, lost async page write
[36348.841984] Buffer I/O error on dev sdc1, logical block 3145977, lost async page write
[36348.841985] Buffer I/O error on dev sdc1, logical block 3145978, lost async page write
[36348.841986] Buffer I/O error on dev sdc1, logical block 3145979, lost async page write
[36348.842434] sd 5:0:0:0: [sdc] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=0s
[36348.842435] sd 5:0:0:0: [sdc] tag#0 Sense Key : Not Ready [current] 
[36348.842436] sd 5:0:0:0: [sdc] tag#0 Add. Sense: Medium not present
[36348.842437] sd 5:0:0:0: [sdc] tag#0 CDB: Write(10) 2a 00 01 80 12 20 00 00 f0 00
[36348.842437] I/O error, dev sdc, sector 25170464 op 0x1:(WRITE) flags 0x107000 phys_seg 30 prio class 0
[36348.842818] sd 5:0:0:0: [sdc] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=0s
[36348.842819] sd 5:0:0:0: [sdc] tag#0 Sense Key : Not Ready [current] 
[36348.842820] sd 5:0:0:0: [sdc] tag#0 Add. Sense: Medium not present
[36348.842821] sd 5:0:0:0: [sdc] tag#0 CDB: Write(10) 2a 00 01 80 13 10 00 00 f0 00
[36348.842821] I/O error, dev sdc, sector 25170704 op 0x1:(WRITE) flags 0x107000 phys_seg 30 prio class 0
[36348.843201] sd 5:0:0:0: [sdc] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=0s
[36348.843202] sd 5:0:0:0: [sdc] tag#0 Sense Key : Not Ready [current] 
[36348.843203] sd 5:0:0:0: [sdc] tag#0 Add. Sense: Medium not present
[36348.843203] sd 5:0:0:0: [sdc] tag#0 CDB: Write(10) 2a 00 01 80 14 00 00 00 f0 00
[36348.843204] I/O error, dev sdc, sector 25170944 op 0x1:(WRITE) flags 0x107000 phys_seg 30 prio class 0
[36348.843583] sd 5:0:0:0: [sdc] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=0s
[36348.843584] sd 5:0:0:0: [sdc] tag#0 Sense Key : Not Ready [current] 
[36348.843585] sd 5:0:0:0: [sdc] tag#0 Add. Sense: Medium not present
[36348.843585] sd 5:0:0:0: [sdc] tag#0 CDB: Write(10) 2a 00 01 80 14 f0 00 00 f0 00
[36348.843586] I/O error, dev sdc, sector 25171184 op 0x1:(WRITE) flags 0x107000 phys_seg 30 prio class 0
[36348.843965] sd 5:0:0:0: [sdc] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=0s
[36348.843966] sd 5:0:0:0: [sdc] tag#0 Sense Key : Not Ready [current] 
[36348.843967] sd 5:0:0:0: [sdc] tag#0 Add. Sense: Medium not present
[36348.843968] sd 5:0:0:0: [sdc] tag#0 CDB: Write(10) 2a 00 01 80 15 e0 00 00 f0 00
[36348.843968] I/O error, dev sdc, sector 25171424 op 0x1:(WRITE) flags 0x107000 phys_seg 30 prio class 0
[36348.844325] sd 5:0:0:0: [sdc] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=0s
[36348.844325] sd 5:0:0:0: [sdc] tag#0 Sense Key : Not Ready [current] 
[36348.844326] sd 5:0:0:0: [sdc] tag#0 Add. Sense: Medium not present
[36348.844327] sd 5:0:0:0: [sdc] tag#0 CDB: Write(10) 2a 00 03 06 43 78 00 00 08 00
[36348.844327] I/O error, dev sdc, sector 50742136 op 0x1:(WRITE) flags 0x800 phys_seg 1 prio class 0
[36348.844330] Aborting journal on device sdc1-8.
[36348.844685] sd 5:0:0:0: [sdc] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=0s
[36348.844686] sd 5:0:0:0: [sdc] tag#0 Sense Key : Not Ready [current] 
[36348.844687] sd 5:0:0:0: [sdc] tag#0 Add. Sense: Medium not present
[36348.844687] sd 5:0:0:0: [sdc] tag#0 CDB: Write(10) 2a 00 01 80 16 d0 00 00 f0 00
[36348.844688] I/O error, dev sdc, sector 25171664 op 0x1:(WRITE) flags 0x107000 phys_seg 30 prio class 0
[36348.845045] sd 5:0:0:0: [sdc] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=0s
[36348.845046] sd 5:0:0:0: [sdc] tag#0 Sense Key : Not Ready [current] 
[36348.845047] sd 5:0:0:0: [sdc] tag#0 Add. Sense: Medium not present
[36348.845047] sd 5:0:0:0: [sdc] tag#0 CDB: Write(10) 2a 00 03 04 08 00 00 00 08 00
[36348.845048] I/O error, dev sdc, sector 50595840 op 0x1:(WRITE) flags 0x800 phys_seg 1 prio class 0
[36348.845050] JBD2: Error -5 detected when updating journal superblock for sdc1-8.
[36348.845405] sd 5:0:0:0: [sdc] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=0s
[36348.845406] sd 5:0:0:0: [sdc] tag#0 Sense Key : Not Ready [current] 
[36348.845407] sd 5:0:0:0: [sdc] tag#0 Add. Sense: Medium not present
[36348.845408] sd 5:0:0:0: [sdc] tag#0 CDB: Write(10) 2a 00 01 80 17 c0 00 00 f0 00
[36348.845408] I/O error, dev sdc, sector 25171904 op 0x1:(WRITE) flags 0x107000 phys_seg 30 prio class 0
[36348.851042] sd 5:0:0:0: [sdc] tag#0 access beyond end of device
[36348.851042] sdc: detected capacity change from 122880000 to 0
[36348.851067] sd 5:0:0:0: [sdc] tag#0 access beyond end of device
[36348.851090] sd 5:0:0:0: [sdc] tag#0 access beyond end of device
[36348.851110] sd 5:0:0:0: [sdc] tag#0 access beyond end of device
[36348.851118] EXT4-fs error (device sdc1): ext4_journal_check_start:83: comm kworker/u32:7: Detected aborted journal
[36348.851124] sd 5:0:0:0: [sdc] tag#0 access beyond end of device
[36348.851128] sd 5:0:0:0: [sdc] tag#0 access beyond end of device
[36348.851129] EXT4-fs (sdc1): I/O error while writing superblock
[36348.851130] EXT4-fs (sdc1): Remounting filesystem read-only
[36348.851131] EXT4-fs (sdc1): ext4_writepages: jbd2_start: 1024 pages, ino 791104; err -30
[36348.875486] sd 5:0:0:0: [sdc] tag#0 access beyond end of device
[36348.875497] sd 5:0:0:0: [sdc] tag#0 access beyond end of device
[36348.881346] sd 5:0:0:0: [sdc] tag#0 access beyond end of device
[36348.881355] sd 5:0:0:0: [sdc] tag#0 access beyond end of device
[36348.881361] sd 5:0:0:0: [sdc] tag#0 access beyond end of device
[36348.895167] sd 5:0:0:0: [sdc] tag#0 access beyond end of device
[36348.895177] sd 5:0:0:0: [sdc] tag#0 access beyond end of device
[36348.902795] sd 5:0:0:0: [sdc] tag#0 access beyond end of device
[36348.902805] sd 5:0:0:0: [sdc] tag#0 access beyond end of device
[36348.910415] sd 5:0:0:0: [sdc] tag#0 access beyond end of device
[36348.910424] sd 5:0:0:0: [sdc] tag#0 access beyond end of device
[36348.911754] sd 5:0:0:0: [sdc] tag#0 access beyond end of device
[36348.911764] sd 5:0:0:0: [sdc] tag#0 access beyond end of device
[36861.794901] audit: type=1100 audit(1665134353.319:172): pid=16758 uid=1000 auid=1000 ses=3 msg='op=PAM:unix_chkpwd acct="jazztache" exe="/usr/bin/unix_chkpwd" hostname=? addr=? terminal=? res=failed'
[36867.609962] audit: type=1100 audit(1665134359.132:173): pid=16763 uid=1000 auid=1000 ses=3 msg='op=PAM:unix_chkpwd acct="jazztache" exe="/usr/bin/unix_chkpwd" hostname=? addr=? terminal=? res=success'
[36886.316432] sdc1: Can't mount, would change RO state
[36894.715723] audit: type=1106 audit(1665134386.243:174): pid=14379 uid=1000 auid=1000 ses=3 msg='op=PAM:session_close grantors=pam_systemd_home,pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/2 res=success'
[36894.715792] audit: type=1104 audit(1665134386.243:175): pid=14379 uid=1000 auid=1000 ses=3 msg='op=PAM:setcred grantors=pam_faillock,pam_permit,pam_faillock acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/2 res=success'
[36896.882344] sdc1: Can't mount, would change RO state
[36898.315134] sdc1: Can't mount, would change RO state
[36905.282869] usb 1-5: USB disconnect, device number 11
[36915.118292] usb 1-5: new high-speed USB device number 13 using xhci_hcd
[36915.258561] usb 1-5: New USB device found, idVendor=ffff, idProduct=1201, bcdDevice= 0.00
[36915.258563] usb 1-5: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[36915.259751] usb-storage 1-5:1.0: USB Mass Storage device detected
[36915.260005] scsi host6: usb-storage 1-5:1.0
[36916.285575] scsi 6:0:0:0: Direct-Access     NAND     USB2DISK         0.00 PQ: 0 ANSI: 4
[36916.286244] sd 6:0:0:0: [sdd] Media removed, stopped polling
[36916.286498] sd 6:0:0:0: [sdd] Attached SCSI removable disk
[36924.932122] audit: type=1100 audit(1665134416.461:176): pid=16868 uid=1000 auid=1000 ses=3 msg='op=PAM:authentication grantors=pam_faillock,pam_permit,pam_faillock acct="jazztache" exe="/usr/lib/polkit-1/polkit-agent-helper-1" hostname=? addr=? terminal=? res=success'
[36924.932320] audit: type=1101 audit(1665134416.461:177): pid=16868 uid=1000 auid=1000 ses=3 msg='op=PAM:accounting grantors=pam_unix,pam_permit,pam_time acct="jazztache" exe="/usr/lib/polkit-1/polkit-agent-helper-1" hostname=? addr=? terminal=? res=success'
[36935.031530] usb 1-9: USB disconnect, device number 12
[36940.578755] usb 1-5: USB disconnect, device number 13
[36952.986837] usb 1-9: new high-speed USB device number 14 using xhci_hcd
[36953.127067] usb 1-9: New USB device found, idVendor=ffff, idProduct=1201, bcdDevice= 0.00
[36953.127069] usb 1-9: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[36953.128204] usb-storage 1-9:1.0: USB Mass Storage device detected
[36953.128534] scsi host4: usb-storage 1-9:1.0
[36954.153780] scsi 4:0:0:0: Direct-Access     NAND     USB2DISK         0.00 PQ: 0 ANSI: 4
[36954.154291] sd 4:0:0:0: [sdb] Media removed, stopped polling
[36954.154482] sd 4:0:0:0: [sdb] Attached SCSI removable disk
[36999.279934] EXT4-fs error (device sdc1): __ext4_find_entry:1658: inode #1310723: comm Journalise.sh: reading directory lblock 0
[36999.280000] EXT4-fs error (device sdc1): __ext4_find_entry:1658: inode #1310723: comm Journalise.sh: reading directory lblock 0
[36999.280006] EXT4-fs error (device sdc1): __ext4_find_entry:1658: inode #1310723: comm Journalise.sh: reading directory lblock 0
[36999.280019] EXT4-fs error (device sdc1): __ext4_find_entry:1658: inode #1310723: comm Journalise.sh: reading directory lblock 0
[36999.280028] EXT4-fs error (device sdc1): __ext4_find_entry:1658: inode #1310723: comm Journalise.sh: reading directory lblock 0
[36999.280065] EXT4-fs error (device sdc1): __ext4_find_entry:1658: inode #1310723: comm Journalise.sh: reading directory lblock 0
[36999.280076] EXT4-fs error (device sdc1): __ext4_find_entry:1658: inode #1310723: comm Journalise.sh: reading directory lblock 0
[36999.280092] EXT4-fs error (device sdc1): __ext4_find_entry:1658: inode #1310723: comm Journalise.sh: reading directory lblock 0
[37016.115084] usb 1-9: USB disconnect, device number 14
[37029.053927] usb 1-9: new high-speed USB device number 15 using xhci_hcd
[37029.194183] usb 1-9: New USB device found, idVendor=ffff, idProduct=1201, bcdDevice= 0.00
[37029.194185] usb 1-9: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[37029.195325] usb-storage 1-9:1.0: USB Mass Storage device detected
[37029.195700] scsi host4: usb-storage 1-9:1.0
[37030.200960] scsi 4:0:0:0: Direct-Access     NAND     USB2DISK         0.00 PQ: 0 ANSI: 4
[37030.201566] sd 4:0:0:0: [sdb] Media removed, stopped polling
[37030.201799] sd 4:0:0:0: [sdb] Attached SCSI removable disk
[37039.590846] audit: type=1100 audit(1665134531.122:178): pid=17174 uid=1000 auid=1000 ses=3 msg='op=PAM:authentication grantors=pam_faillock,pam_permit,pam_faillock acct="jazztache" exe="/usr/lib/polkit-1/polkit-agent-helper-1" hostname=? addr=? terminal=? res=success'
[37039.590939] audit: type=1101 audit(1665134531.122:179): pid=17174 uid=1000 auid=1000 ses=3 msg='op=PAM:accounting grantors=pam_unix,pam_permit,pam_time acct="jazztache" exe="/usr/lib/polkit-1/polkit-agent-helper-1" hostname=? addr=? terminal=? res=success'
[37053.327827] usb 1-9: USB disconnect, device number 15
[37056.552878] usb 1-9: new high-speed USB device number 16 using xhci_hcd
[37056.750504] usb 1-9: New USB device found, idVendor=1058, idProduct=2621, bcdDevice=10.26
[37056.750506] usb 1-9: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[37056.750506] usb 1-9: Product: Elements 2621
[37056.750507] usb 1-9: Manufacturer: Western Digital
[37056.750508] usb 1-9: SerialNumber: 5758333145423944394E5734
[37056.761698] usb-storage 1-9:1.0: USB Mass Storage device detected
[37056.762079] scsi host4: usb-storage 1-9:1.0
[37057.783773] scsi 4:0:0:0: Direct-Access     WD       Elements 2621    1026 PQ: 0 ANSI: 6
[37057.785126] sd 4:0:0:0: [sdb] Spinning up disk...
[37058.812791] ...ready
[37060.903165] sd 4:0:0:0: [sdb] 3906963456 512-byte logical blocks: (2.00 TB/1.82 TiB)
[37060.903496] sd 4:0:0:0: [sdb] Write Protect is off
[37060.903497] sd 4:0:0:0: [sdb] Mode Sense: 47 00 10 08
[37060.903788] sd 4:0:0:0: [sdb] No Caching mode page found
[37060.903788] sd 4:0:0:0: [sdb] Assuming drive cache: write through
[37060.942648]  sdb: sdb1
[37060.942742] sd 4:0:0:0: [sdb] Attached SCSI disk
[37063.829725] ntfs3: Unknown parameter 'windows_names'
[37252.796144] usb 1-9: USB disconnect, device number 16
[37272.588017] usb 1-10: new high-speed USB device number 17 using xhci_hcd
[37272.728261] usb 1-10: New USB device found, idVendor=ffff, idProduct=1201, bcdDevice= 0.00
[37272.728263] usb 1-10: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[37272.729416] usb-storage 1-10:1.0: USB Mass Storage device detected
[37272.729772] scsi host4: usb-storage 1-10:1.0
[37273.738433] scsi 4:0:0:0: Direct-Access     NAND     USB2DISK         0.00 PQ: 0 ANSI: 4
[37273.738839] sd 4:0:0:0: [sdb] Media removed, stopped polling
[37273.739070] sd 4:0:0:0: [sdb] Attached SCSI removable disk
[37276.214550] usb 1-9: new high-speed USB device number 18 using xhci_hcd
[37276.412385] usb 1-9: New USB device found, idVendor=1058, idProduct=2621, bcdDevice=10.26
[37276.412387] usb 1-9: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[37276.412388] usb 1-9: Product: Elements 2621
[37276.412389] usb 1-9: Manufacturer: Western Digital
[37276.412390] usb 1-9: SerialNumber: 5758333145423944394E5734
[37276.423608] usb-storage 1-9:1.0: USB Mass Storage device detected
[37276.424039] scsi host6: usb-storage 1-9:1.0
[37277.455363] scsi 6:0:0:0: Direct-Access     WD       Elements 2621    1026 PQ: 0 ANSI: 6
[37277.456764] sd 6:0:0:0: [sdd] Spinning up disk...
[37278.484463] ...ready
[37280.574899] sd 6:0:0:0: [sdd] 3906963456 512-byte logical blocks: (2.00 TB/1.82 TiB)
[37280.575273] sd 6:0:0:0: [sdd] Write Protect is off
[37280.575274] sd 6:0:0:0: [sdd] Mode Sense: 47 00 10 08
[37280.575565] sd 6:0:0:0: [sdd] No Caching mode page found
[37280.575566] sd 6:0:0:0: [sdd] Assuming drive cache: write through
[37280.613988]  sdd: sdd1
[37280.614121] sd 6:0:0:0: [sdd] Attached SCSI disk
[37300.665865] ntfs3: Unknown parameter 'windows_names'
[37320.090326] usb 1-9: USB disconnect, device number 18
[37570.938533] audit: type=1100 audit(1665135062.489:180): pid=17955 uid=1000 auid=1000 ses=3 msg='op=PAM:unix_chkpwd acct="jazztache" exe="/usr/bin/unix_chkpwd" hostname=? addr=? terminal=? res=success'
[37631.930613] audit: type=1100 audit(1665135123.484:181): pid=18252 uid=1000 auid=1000 ses=3 msg='op=PAM:authentication grantors=pam_faillock,pam_permit,pam_faillock acct="jazztache" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
[37631.930663] audit: type=1101 audit(1665135123.484:182): pid=18252 uid=1000 auid=1000 ses=3 msg='op=PAM:accounting grantors=pam_unix,pam_permit,pam_time acct="jazztache" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
[37631.931013] audit: type=1110 audit(1665135123.484:183): pid=18252 uid=1000 auid=1000 ses=3 msg='op=PAM:setcred grantors=pam_faillock,pam_permit,pam_faillock acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
[37631.938439] audit: type=1105 audit(1665135123.494:184): pid=18252 uid=1000 auid=1000 ses=3 msg='op=PAM:session_open grantors=pam_systemd_home,pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
[37650.204478] audit: type=1106 audit(1665135141.762:185): pid=18252 uid=1000 auid=1000 ses=3 msg='op=PAM:session_close grantors=pam_systemd_home,pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
[37650.204669] audit: type=1104 audit(1665135141.762:186): pid=18252 uid=1000 auid=1000 ses=3 msg='op=PAM:setcred grantors=pam_faillock,pam_permit,pam_faillock acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
[37667.326810] audit: type=1101 audit(1665135158.882:187): pid=18298 uid=1000 auid=1000 ses=3 msg='op=PAM:accounting grantors=pam_unix,pam_permit,pam_time acct="jazztache" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
[37667.327382] audit: type=1110 audit(1665135158.882:188): pid=18298 uid=1000 auid=1000 ses=3 msg='op=PAM:setcred grantors=pam_faillock,pam_permit,pam_env,pam_faillock acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
[37667.327469] audit: type=1105 audit(1665135158.882:189): pid=18298 uid=1000 auid=1000 ses=3 msg='op=PAM:session_open grantors=pam_systemd_home,pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
[37667.329213] /dev/sdb: Can't open blockdev
[37667.329406] audit: type=1106 audit(1665135158.882:190): pid=18298 uid=1000 auid=1000 ses=3 msg='op=PAM:session_close grantors=pam_systemd_home,pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
[37667.329431] audit: type=1104 audit(1665135158.882:191): pid=18298 uid=1000 auid=1000 ses=3 msg='op=PAM:setcred grantors=pam_faillock,pam_permit,pam_env,pam_faillock acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
[37838.950453] EXT4-fs warning (device sdc1): htree_dirblock_to_tree:1067: inode #2: lblock 0: comm git: error -5 reading directory block
[37838.950470] EXT4-fs warning (device sdc1): htree_dirblock_to_tree:1067: inode #2: lblock 0: comm git: error -5 reading directory block
[37843.554474] EXT4-fs error (device sdc1): __ext4_find_entry:1658: inode #2: comm lsblk: reading directory lblock 0
[37843.554480] EXT4-fs error (device sdc1): __ext4_find_entry:1658: inode #2: comm lsblk: reading directory lblock 0
[37843.557284] EXT4-fs warning (device sdc1): htree_dirblock_to_tree:1067: inode #2: lblock 0: comm git: error -5 reading directory block
[37843.557301] EXT4-fs warning (device sdc1): htree_dirblock_to_tree:1067: inode #2: lblock 0: comm git: error -5 reading directory block
[37854.395242] EXT4-fs (sdc1): unmounting filesystem.
[39254.048319] audit: type=1100 audit(1665136745.664:192): pid=19382 uid=1000 auid=1000 ses=3 msg='op=PAM:unix_chkpwd acct="jazztache" exe="/usr/bin/unix_chkpwd" hostname=? addr=? terminal=? res=success'
[39343.364260] usb 1-10: USB disconnect, device number 17
[39755.416546] usb 1-9: new high-speed USB device number 19 using xhci_hcd
[39755.556801] usb 1-9: New USB device found, idVendor=ffff, idProduct=1201, bcdDevice= 0.00
[39755.556804] usb 1-9: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[39755.557793] usb-storage 1-9:1.0: USB Mass Storage device detected
[39755.558032] scsi host4: usb-storage 1-9:1.0
[39756.580240] scsi 4:0:0:0: Direct-Access     NAND     USB2DISK         0.00 PQ: 0 ANSI: 4
[39756.580723] sd 4:0:0:0: [sdb] Media removed, stopped polling
[39756.580943] sd 4:0:0:0: [sdb] Attached SCSI removable disk
[39764.164237] usb 1-9: USB disconnect, device number 19
[41203.879268] audit: type=1100 audit(1665138695.562:193): pid=20816 uid=1000 auid=1000 ses=3 msg='op=PAM:authentication grantors=pam_faillock,pam_permit,pam_faillock acct="jazztache" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/2 res=success'
[41203.879360] audit: type=1101 audit(1665138695.562:194): pid=20816 uid=1000 auid=1000 ses=3 msg='op=PAM:accounting grantors=pam_unix,pam_permit,pam_time acct="jazztache" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/2 res=success'
[41203.879712] audit: type=1110 audit(1665138695.562:195): pid=20816 uid=1000 auid=1000 ses=3 msg='op=PAM:setcred grantors=pam_faillock,pam_permit,pam_faillock acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/2 res=success'
[41203.879768] audit: type=1105 audit(1665138695.562:196): pid=20816 uid=1000 auid=1000 ses=3 msg='op=PAM:session_open grantors=pam_systemd_home,pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/2 res=success'
[41241.805523] audit: type=1106 audit(1665138733.493:197): pid=20816 uid=1000 auid=1000 ses=3 msg='op=PAM:session_close grantors=pam_systemd_home,pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/2 res=success'
[41241.805596] audit: type=1104 audit(1665138733.493:198): pid=20816 uid=1000 auid=1000 ses=3 msg='op=PAM:setcred grantors=pam_faillock,pam_permit,pam_faillock acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/2 res=success'
[42536.497678] usb 1-9: new high-speed USB device number 20 using xhci_hcd
[42536.637910] usb 1-9: New USB device found, idVendor=ffff, idProduct=1201, bcdDevice= 0.00
[42536.637912] usb 1-9: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[42536.639001] usb-storage 1-9:1.0: USB Mass Storage device detected
[42536.639234] scsi host4: usb-storage 1-9:1.0
[42537.651399] scsi 4:0:0:0: Direct-Access     NAND     USB2DISK         0.00 PQ: 0 ANSI: 4
[42537.652027] sd 4:0:0:0: [sdb] Media removed, stopped polling
[42537.652229] sd 4:0:0:0: [sdb] Attached SCSI removable disk
[42602.266667] audit: type=1100 audit(1665140094.003:199): pid=21169 uid=1000 auid=1000 ses=3 msg='op=PAM:authentication grantors=pam_faillock,pam_permit,pam_faillock acct="jazztache" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/4 res=success'
[42602.266755] audit: type=1101 audit(1665140094.003:200): pid=21169 uid=1000 auid=1000 ses=3 msg='op=PAM:accounting grantors=pam_unix,pam_permit,pam_time acct="jazztache" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/4 res=success'
[42602.267262] audit: type=1110 audit(1665140094.003:201): pid=21169 uid=1000 auid=1000 ses=3 msg='op=PAM:setcred grantors=pam_faillock,pam_permit,pam_faillock acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/4 res=success'
[42602.267349] audit: type=1105 audit(1665140094.003:202): pid=21169 uid=1000 auid=1000 ses=3 msg='op=PAM:session_open grantors=pam_systemd_home,pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/4 res=success'
[42602.271930] audit: type=1106 audit(1665140094.010:203): pid=21169 uid=1000 auid=1000 ses=3 msg='op=PAM:session_close grantors=pam_systemd_home,pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/4 res=success'
[42602.271975] audit: type=1104 audit(1665140094.010:204): pid=21169 uid=1000 auid=1000 ses=3 msg='op=PAM:setcred grantors=pam_faillock,pam_permit,pam_faillock acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/4 res=success'
[42678.033913] audit: type=1100 audit(1665140169.773:205): pid=21208 uid=1000 auid=1000 ses=3 msg='op=PAM:authentication grantors=pam_faillock,pam_permit,pam_faillock acct="jazztache" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
[42678.034004] audit: type=1101 audit(1665140169.773:206): pid=21208 uid=1000 auid=1000 ses=3 msg='op=PAM:accounting grantors=pam_unix,pam_permit,pam_time acct="jazztache" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
[42678.034500] audit: type=1110 audit(1665140169.773:207): pid=21208 uid=1000 auid=1000 ses=3 msg='op=PAM:setcred grantors=pam_faillock,pam_permit,pam_faillock acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
[42678.034575] audit: type=1105 audit(1665140169.773:208): pid=21208 uid=1000 auid=1000 ses=3 msg='op=PAM:session_open grantors=pam_systemd_home,pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
[42678.036861] audit: type=1106 audit(1665140169.776:209): pid=21208 uid=1000 auid=1000 ses=3 msg='op=PAM:session_close grantors=pam_systemd_home,pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
[42678.036907] audit: type=1104 audit(1665140169.776:210): pid=21208 uid=1000 auid=1000 ses=3 msg='op=PAM:setcred grantors=pam_faillock,pam_permit,pam_faillock acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
[42726.000033] audit: type=1101 audit(1665140217.741:211): pid=21305 uid=1000 auid=1000 ses=3 msg='op=PAM:accounting grantors=pam_unix,pam_permit,pam_time acct="jazztache" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
[42726.000274] audit: type=1110 audit(1665140217.741:212): pid=21305 uid=1000 auid=1000 ses=3 msg='op=PAM:setcred grantors=pam_faillock,pam_permit,pam_env,pam_faillock acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
[42726.000330] audit: type=1105 audit(1665140217.741:213): pid=21305 uid=1000 auid=1000 ses=3 msg='op=PAM:session_open grantors=pam_systemd_home,pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
[42726.009037] audit: type=1106 audit(1665140217.751:214): pid=21305 uid=1000 auid=1000 ses=3 msg='op=PAM:session_close grantors=pam_systemd_home,pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
[42726.009056] audit: type=1104 audit(1665140217.751:215): pid=21305 uid=1000 auid=1000 ses=3 msg='op=PAM:setcred grantors=pam_faillock,pam_permit,pam_env,pam_faillock acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
[42751.698529] audit: type=1101 audit(1665140243.439:216): pid=21339 uid=1000 auid=1000 ses=3 msg='op=PAM:accounting grantors=pam_unix,pam_permit,pam_time acct="jazztache" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
[42779.207803] audit: type=1101 audit(1665140270.950:217): pid=21371 uid=1000 auid=1000 ses=3 msg='op=PAM:accounting grantors=pam_unix,pam_permit,pam_time acct="jazztache" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
[42779.208099] audit: type=1110 audit(1665140270.950:218): pid=21371 uid=1000 auid=1000 ses=3 msg='op=PAM:setcred grantors=pam_faillock,pam_permit,pam_env,pam_faillock acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
[42779.208143] audit: type=1105 audit(1665140270.950:219): pid=21371 uid=1000 auid=1000 ses=3 msg='op=PAM:session_open grantors=pam_systemd_home,pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
[42779.214486] audit: type=1106 audit(1665140270.956:220): pid=21371 uid=1000 auid=1000 ses=3 msg='op=PAM:session_close grantors=pam_systemd_home,pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
[42779.214489] audit: type=1104 audit(1665140270.956:221): pid=21371 uid=1000 auid=1000 ses=3 msg='op=PAM:setcred grantors=pam_faillock,pam_permit,pam_env,pam_faillock acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
[43407.082422] audit: type=1100 audit(1665140898.850:222): pid=21520 uid=1000 auid=1000 ses=3 msg='op=PAM:authentication grantors=pam_faillock,pam_permit,pam_faillock acct="jazztache" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
[43407.082490] audit: type=1101 audit(1665140898.850:223): pid=21520 uid=1000 auid=1000 ses=3 msg='op=PAM:accounting grantors=pam_unix,pam_permit,pam_time acct="jazztache" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
[43407.082956] audit: type=1110 audit(1665140898.850:224): pid=21520 uid=1000 auid=1000 ses=3 msg='op=PAM:setcred grantors=pam_faillock,pam_permit,pam_faillock acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
[43407.083017] audit: type=1105 audit(1665140898.850:225): pid=21520 uid=1000 auid=1000 ses=3 msg='op=PAM:session_open grantors=pam_systemd_home,pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
[43407.086412] audit: type=1106 audit(1665140898.853:226): pid=21520 uid=1000 auid=1000 ses=3 msg='op=PAM:session_close grantors=pam_systemd_home,pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
[43407.086443] audit: type=1104 audit(1665140898.853:227): pid=21520 uid=1000 auid=1000 ses=3 msg='op=PAM:setcred grantors=pam_faillock,pam_permit,pam_faillock acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
[43407.091044] audit: type=1101 audit(1665140898.856:228): pid=21539 uid=1000 auid=1000 ses=3 msg='op=PAM:accounting grantors=pam_unix,pam_permit,pam_time acct="jazztache" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
[43407.091413] audit: type=1110 audit(1665140898.856:229): pid=21539 uid=1000 auid=1000 ses=3 msg='op=PAM:setcred grantors=pam_faillock,pam_permit,pam_env,pam_faillock acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
[43407.091455] audit: type=1105 audit(1665140898.856:230): pid=21539 uid=1000 auid=1000 ses=3 msg='op=PAM:session_open grantors=pam_systemd_home,pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
[43411.870985] audit: type=1106 audit(1665140903.637:231): pid=21539 uid=1000 auid=1000 ses=3 msg='op=PAM:session_close grantors=pam_systemd_home,pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
[43457.089758] kauditd_printk_skb: 1 callbacks suppressed
[43457.089760] audit: type=1101 audit(1665140948.855:233): pid=21601 uid=1000 auid=1000 ses=3 msg='op=PAM:accounting grantors=pam_unix,pam_permit,pam_time acct="jazztache" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
[43457.090016] audit: type=1110 audit(1665140948.855:234): pid=21601 uid=1000 auid=1000 ses=3 msg='op=PAM:setcred grantors=pam_faillock,pam_permit,pam_env,pam_faillock acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
[43457.090148] audit: type=1105 audit(1665140948.858:235): pid=21601 uid=1000 auid=1000 ses=3 msg='op=PAM:session_open grantors=pam_systemd_home,pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
[43457.091412] audit: type=1106 audit(1665140948.858:236): pid=21601 uid=1000 auid=1000 ses=3 msg='op=PAM:session_close grantors=pam_systemd_home,pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
[43457.091482] audit: type=1104 audit(1665140948.858:237): pid=21601 uid=1000 auid=1000 ses=3 msg='op=PAM:setcred grantors=pam_faillock,pam_permit,pam_env,pam_faillock acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
[44607.712275] audit: type=1100 audit(1665142099.524:238): pid=22650 uid=1000 auid=1000 ses=3 msg='op=PAM:unix_chkpwd acct="jazztache" exe="/usr/bin/unix_chkpwd" hostname=? addr=? terminal=? res=success'
[45403.828131] audit: type=1100 audit(1665142895.667:239): pid=23041 uid=1000 auid=1000 ses=3 msg='op=PAM:authentication grantors=pam_faillock,pam_permit,pam_faillock acct="jazztache" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/2 res=success'
[45403.828282] audit: type=1101 audit(1665142895.670:240): pid=23041 uid=1000 auid=1000 ses=3 msg='op=PAM:accounting grantors=pam_unix,pam_permit,pam_time acct="jazztache" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/2 res=success'
[45403.828793] audit: type=1110 audit(1665142895.670:241): pid=23041 uid=1000 auid=1000 ses=3 msg='op=PAM:setcred grantors=pam_faillock,pam_permit,pam_faillock acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/2 res=success'
[45403.828880] audit: type=1105 audit(1665142895.670:242): pid=23041 uid=1000 auid=1000 ses=3 msg='op=PAM:session_open grantors=pam_systemd_home,pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/2 res=success'
[45403.835077] audit: type=1106 audit(1665142895.677:243): pid=23041 uid=1000 auid=1000 ses=3 msg='op=PAM:session_close grantors=pam_systemd_home,pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/2 res=success'
[45403.835080] audit: type=1104 audit(1665142895.677:244): pid=23041 uid=1000 auid=1000 ses=3 msg='op=PAM:setcred grantors=pam_faillock,pam_permit,pam_faillock acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/2 res=success'
[45423.561958] audit: type=1101 audit(1665142915.404:245): pid=23085 uid=1000 auid=1000 ses=3 msg='op=PAM:accounting grantors=pam_unix,pam_permit,pam_time acct="jazztache" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/2 res=success'
[45423.562410] audit: type=1110 audit(1665142915.404:246): pid=23085 uid=1000 auid=1000 ses=3 msg='op=PAM:setcred grantors=pam_faillock,pam_permit,pam_env,pam_faillock acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/2 res=success'
[45423.562484] audit: type=1105 audit(1665142915.404:247): pid=23085 uid=1000 auid=1000 ses=3 msg='op=PAM:session_open grantors=pam_systemd_home,pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/2 res=success'
[45423.568684] audit: type=1106 audit(1665142915.411:248): pid=23085 uid=1000 auid=1000 ses=3 msg='op=PAM:session_close grantors=pam_systemd_home,pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/2 res=success'
[45423.568687] audit: type=1104 audit(1665142915.411:249): pid=23085 uid=1000 auid=1000 ses=3 msg='op=PAM:setcred grantors=pam_faillock,pam_permit,pam_env,pam_faillock acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/2 res=success'
[45439.418989] audit: type=1101 audit(1665142931.258:250): pid=23098 uid=1000 auid=1000 ses=3 msg='op=PAM:accounting grantors=pam_unix,pam_permit,pam_time acct="jazztache" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/2 res=success'
[45439.419447] audit: type=1110 audit(1665142931.258:251): pid=23098 uid=1000 auid=1000 ses=3 msg='op=PAM:setcred grantors=pam_faillock,pam_permit,pam_env,pam_faillock acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/2 res=success'
[45439.419506] audit: type=1105 audit(1665142931.258:252): pid=23098 uid=1000 auid=1000 ses=3 msg='op=PAM:session_open grantors=pam_systemd_home,pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/2 res=success'
[45439.425599] audit: type=1106 audit(1665142931.265:253): pid=23098 uid=1000 auid=1000 ses=3 msg='op=PAM:session_close grantors=pam_systemd_home,pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/2 res=success'
[45439.425602] audit: type=1104 audit(1665142931.265:254): pid=23098 uid=1000 auid=1000 ses=3 msg='op=PAM:setcred grantors=pam_faillock,pam_permit,pam_env,pam_faillock acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/2 res=success'
[46211.723203] audit: type=1100 audit(1665143703.593:255): pid=23272 uid=1000 auid=1000 ses=3 msg='op=PAM:unix_chkpwd acct="jazztache" exe="/usr/bin/unix_chkpwd" hostname=? addr=? terminal=? res=success'
[47569.226644] audit: type=1100 audit(1665145061.141:256): pid=24412 uid=1000 auid=1000 ses=3 msg='op=PAM:authentication grantors=pam_faillock,pam_permit,pam_faillock acct="jazztache" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/2 res=success'
[47569.226697] audit: type=1101 audit(1665145061.141:257): pid=24412 uid=1000 auid=1000 ses=3 msg='op=PAM:accounting grantors=pam_unix,pam_permit,pam_time acct="jazztache" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/2 res=success'
[47569.227074] audit: type=1110 audit(1665145061.144:258): pid=24412 uid=1000 auid=1000 ses=3 msg='op=PAM:setcred grantors=pam_faillock,pam_permit,pam_faillock acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/2 res=success'
[47569.227156] audit: type=1105 audit(1665145061.144:259): pid=24412 uid=1000 auid=1000 ses=3 msg='op=PAM:session_open grantors=pam_systemd_home,pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/2 res=success'

Interesting thing I found.
So if my SSD is nvmen01,
and my internal hard drive is sda,
and my external hard drive is sdb, and my usb stick has two partitions, but only sdd is showing...
then that means sdc has gone wrong, but that means Linux is picking up that device with two partitions as two seperate devices...

Offline

#4 2022-10-07 12:49:39

V1del
Forum Moderator
Registered: 2012-10-16
Posts: 25,157

Re: USB Stick Diagonstics, Need Help With Fixing USB Stick

[37277.455363] scsi 6:0:0:0: Direct-Access     WD       Elements 2621    1026 PQ: 0 ANSI: 6
[37277.456764] sd 6:0:0:0: [sdd] Spinning up disk...
[37278.484463] ...ready
[37280.574899] sd 6:0:0:0: [sdd] 3906963456 512-byte logical blocks: (2.00 TB/1.82 TiB)
[37280.575273] sd 6:0:0:0: [sdd] Write Protect is off

sdd is your external drive/ sdb is some nand disk, is one of the drives an ssd that is not the USB?. Generally the drive letters don't mean anything and are allocated on an as available basis, do not draw conclusions from abcdefg... lettering of the /sd device. look at lsblk -f and fdisk -l and the like and at UUIDs that guarantee to identify a partition.

Assuming the stick in question is sdc in this output, then it indeed reads like it's pretty much fucked, and from your initial description sounds like you did a lot of random/parallel writes, that you didn't end up flushing/unmounting properly due to time constraints before pulling it all of which can increase the likelyhood of failures like this. Maybe you also just had bad luck and bought a stick that wasn't good from the get go, already written much to etcetc.

PS while that won't be related to your ultimate issue but:

Weirdly enough, I didn't have access the the ext4 part of the drive. Couldn't create new files in Dolphin or copy paste.

that's POSIX file permissions at work and completely expected, if you want to be able to write there you need to chown the mounted directory to your user: https://wiki.archlinux.org/title/File_p … attributes

Last edited by V1del (2022-10-07 12:54:33)

Offline

#5 2022-10-07 14:05:12

Jazztache
Member
Registered: 2022-10-07
Posts: 63

Re: USB Stick Diagonstics, Need Help With Fixing USB Stick

Yeah, one of the drives is a terrabyte drive.
Just for clarification...
1. Would parallel processes mess up the partition table?
2. Is there any way I can wipe that partition table and start again or did I just like *fry* the USB Stick?
3. Is it a dumb idea to have a partitioned USB stick in the first place, assuming I need a Linux-specific partition and a Windows partition separately?
4. Is there some way to translate the output of dmesg to use disk UUIDs instead of device files?

Offline

#6 2022-10-07 15:08:55

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 75,307

Re: USB Stick Diagonstics, Need Help With Fixing USB Stick

The "X" in sdX refers to a device, partitions are counted, eg. sdc1 & sdc2
The head of the dmesg segment in #3 looks like you yanked the usb key (or some other device) while it was accessed. Don't do that. It's not going to fry the drive, but cause FS errors for almost sure.

There're two USB devices in that segment, a "WD Elements 2621" (1058:2621) and "ffff:1201" which is more or less invalid and likely the problematic key and that's probably dead.

1. reboot w/o the troublesome key attached.
2. run "dmesg -w"
3. plug the key
4. post the dmesg output that this produces - not more, not less.

Offline

#7 2022-10-08 00:34:01

Jazztache
Member
Registered: 2022-10-07
Posts: 63

Re: USB Stick Diagonstics, Need Help With Fixing USB Stick

Ok, I'll output the dmesg from a fresh reboot.
Yeah, I'm sorry I got you guys confused. The WD Elements is a seperate drive. That one's doing just fine.
I did a fresh reboot, and here's the dmesg -w

[  104.769866] usb 1-9: new high-speed USB device number 9 using xhci_hcd
[  104.909990] usb 1-9: New USB device found, idVendor=ffff, idProduct=1201, bcdDevice= 0.00
[  104.909993] usb 1-9: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[  104.911130] usb-storage 1-9:1.0: USB Mass Storage device detected
[  104.911503] scsi host4: usb-storage 1-9:1.0
[  105.916143] scsi 4:0:0:0: Direct-Access     NAND     USB2DISK         0.00 PQ: 0 ANSI: 4
[  105.916637] sd 4:0:0:0: [sdb] Media removed, stopped polling
[  105.916854] sd 4:0:0:0: [sdb] Attached SCSI removable disk

If you need me to try again, or needed me to wait a bit longer, I'll be happy to give it another try.

Offline

#8 2022-10-08 06:21:34

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 75,307

Re: USB Stick Diagonstics, Need Help With Fixing USB Stick

ffff:1201 most likely means that the controller/firmware of the drive is dead.
You can "fdisk -l /dev/sdb" (matching the "sdb" that shows up in dmesg) but it'll likely show that there's no partition on that key and that it has an underwhelming capacity.
This doesn't happen because of unsynced writes (what is still a big no-go in and by itself) but is a common death for USB keys (while the NAND behind would eventually become unwritable but remain readable)

Offline

#9 2022-10-09 01:25:21

Jazztache
Member
Registered: 2022-10-07
Posts: 63

Re: USB Stick Diagonstics, Need Help With Fixing USB Stick

Is there any way to flash a new firmware onto the stick or do any hardware repairs? Interested in learning about it.

Offline

#10 2022-10-09 06:21:53

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 75,307

Re: USB Stick Diagonstics, Need Help With Fixing USB Stick

You can possibly desolder the NAND and solder it to an equal but functional controller or you can google for some (typically chinese & windows only and w/ dubious background) model sepcific tool to flash the firmware (what is unlikely to actually revive the key for very long but unless the controller is physically damaged, you can make the firmware hide that…) but for all intents and purposes: the key is dead.

Offline

#11 2022-10-10 07:11:04

Jazztache
Member
Registered: 2022-10-07
Posts: 63

Re: USB Stick Diagonstics, Need Help With Fixing USB Stick

OK. It was worth a shot. Thanks for the help.
Should I bother with creating separate partitions for the purpose of having a hidden partition? Should I just have an encrypted folder if I want to use that?

Offline

#12 2022-10-10 07:46:52

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 75,307

Re: USB Stick Diagonstics, Need Help With Fixing USB Stick

Should I bother with creating separate partitions for the purpose of having a hidden partition? Should I just have an encrypted folder if I want to use that?

Context? How does that relate to this topic?

Offline

#13 2025-05-01 23:42:37

mrtn123
Member
Registered: 2025-05-01
Posts: 1

Re: USB Stick Diagonstics, Need Help With Fixing USB Stick

Sorry to revive this old thread but this is closely related, except for the fact that my USB stick shows sda dead like OP sdb AND sdb that shows up properly. Like 2 physical disks on the flash drive.
dmesg output:

[ 4904.026284] usb 4-2: new SuperSpeed USB device number 5 using xhci_hcd
[ 4904.070516] usb 4-2: New USB device found, idVendor=0bda, idProduct=0306, bcdDevice= 1.17
[ 4904.070535] usb 4-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 4904.070541] usb 4-2: Product: USB3.0 Card Reader
[ 4904.070547] usb 4-2: Manufacturer: Realtek
[ 4904.070552] usb 4-2: SerialNumber: 201506301013
[ 4904.077733] usb-storage 4-2:1.0: USB Mass Storage device detected
[ 4904.078526] scsi host0: usb-storage 4-2:1.0
[ 4905.132559] scsi 0:0:0:0: Direct-Access     Generic- USB3.0 CRW   -SD 1.00 PQ: 0 ANSI: 6
[ 4905.149528] scsi 0:0:0:1: Direct-Access     Generic- USB3.0 CRW   -SD 1.00 PQ: 0 ANSI: 6
[ 4905.152790] sd 0:0:0:0: [sda] Media removed, stopped polling
[ 4905.153860] sd 0:0:0:0: [sda] Attached SCSI removable disk
[ 4906.530069] sd 0:0:0:1: [sdb] 62521344 512-byte logical blocks: (32.0 GB/29.8 GiB)
[ 4906.530849] sd 0:0:0:1: [sdb] Write Protect is off
[ 4906.530859] sd 0:0:0:1: [sdb] Mode Sense: 2f 00 00 00
[ 4906.531268] sd 0:0:0:1: [sdb] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
[ 4906.593729]  sdb: sdb1 sdb2
[ 4906.594403] sd 0:0:0:1: [sdb] Attached SCSI removable disk
[ 4906.771086] ISO 9660 Extensions: Microsoft Joliet Level 3
[ 4906.772501] ISO 9660 Extensions: Microsoft Joliet Level 3
[ 4906.773301] ISO 9660 Extensions: RRIP_1991A

sdb was burnt with a bootable ISO, doesn't want to boot...

Anything I can do to wipe it off entirely and start from scratch?

TIA

Offline

#14 2025-05-02 09:56:47

V1del
Forum Moderator
Registered: 2012-10-16
Posts: 25,157

Re: USB Stick Diagonstics, Need Help With Fixing USB Stick

Open up a new topic and detail the exact issue or problem you think you're having. You have a card reader there, and I'm assuming your ISO is flashed to an SD card? Card readers will allocate as many sdX devices as there are slots, whith only actually populated cards/slots getting a proper device node all of which seems to happen correctly here. Whether your BIOS can boot an ISO off of that strongly depends on said BIOS, what is it? Which kind of system do you want to do this with?

Closing this old thread.

Offline

Board footer

Powered by FluxBB