your files appear to be in a very precarious state.
You have a Seagate Disk driver loaded.
Best Practice on a Mac is that every drive intended for use only on a Mac should have been Erased at the Physical Device level with Disk Utility, so that Disk Utility Drivers "own" the drive, and every type of MacOS Utilities, including Recovery, can always access the drive.
When you keep the drive-maker's Utilities, you may only be able to access the drive with Full MacOS AND the drive-makers Extensions/Utilities loaded. This is not possible when you may need it most, such as after a failure.
In addition in your case, BOTH the Seagate driver and Disk Utility have encountered a drive situation or conflict so unusual, each experienced a kernel panic:
2026-10-18 11:09:49 diskutil - Crash (2 times)
Executable: /usr/sbin/diskutil
Details:
libsystem_platform.dylib: BUG IN CLIENT OF LIBPLATFORM: Trying to recu
rsively lock an os_unfair_lock
Abort Cause 259
2026-10-17 19:00:28 Kernel Panic
Details:
panic(cpu 0 caller 0xfffffe0053a668b0): com_seagate_IOSED01::setPowerS
tate(0xfffffe3327191710 : 0xfffffe005261e5b8, 0 -> 4) timed out after
20478 ms @IOServicePM.cpp:5669
Panicked task 0xfffffe278ff95cd0: 0 pages, 848 threads: pid 0: kernel_
task
Your drive is not operating correctly:
Performance:
System Load: 4.01 (1 min ago) 15.39 (5 min ago) 9.64 (15 min ago)
Nominal I/O usage: 48.40 MB/s
File system: 7.97 seconds
Write speed: 3275 MB/s**
Read speed: 5290 MB/s
**Write speed on M-series Macs is typically within five percent of the observed Read speed, often slightly higher due to write buffering effects