8bf5
8bf5 8bf5 8bf5
8bf5 Getting an error from diskutil 8bf5 on a macOS Monterey USB 8bf5 Drive:
8bf5
8bf5 ** Checking the item map.
error: 8bf5 (oid 0x23274b) om: btn: invalid 8bf5 o_type (0x40000002, anticipated 0x40000003)
error: (oid 8bf5 0x23274b) om: btn: invalid o_subtype 8bf5 (0xf, anticipated 0xb)
8bf5 Object map is invalid.
8bf5
8bf5 is the error message in 8bf5 query, returned from
8bf5
8bf5 sudo fsck_apfs /dev/disk9s1
8bf5
8bf5 What I’ve tried:
8bf5
8bf5 drat 8bf5 (was often called apfstools, 8bf5 I believe) Couldn’t get it 8bf5 to compile in any respect. 8bf5 First it errored out due 8bf5 to warnings a couple of 8bf5 variable being outlined and never 8bf5 used. Edited the make file 8bf5 to stop treating warnings as 8bf5 errors, then it claimed it 8bf5 could not discover file ‘argp.h’
8bf5
8bf5 libfsapfs 8bf5 This at the very 8bf5 least produced executables. Nevertheless neither 8bf5 fsapfsinfo nor fsapsmount proved helpful. 8bf5 From information I acquired:
8bf5
8bf5 libcfile_file_read_buffer_with_error_code: unable to learn from 8bf5 file with error: Permission denied
libcfile_file_read_buffer: 8bf5 unable to learn from file.
libbfio_file_io_handle_read_buffer: 8bf5 unable to learn from file: 8bf5 /dev/disk9s1.
libbfio_file_range_io_handle_read_buffer: unable to learn from 8bf5 file IO deal with.
libbfio_internal_handle_read_buffer: unable 8bf5 to learn from deal with.
libbfio_handle_read_buffer_at_offset: 8bf5 unable to learn buffer.
libfsapfs_container_superblock_read_file_io_handle: unable 8bf5 to learn container superblock information 8bf5 at offset: 0 (0x00000000).
libfsapfs_internal_container_open_read: unable 8bf5 to learn container superblock at 8bf5 offset: 0 (0x00000000).
libfsapfs_container_open_file_io_handle: unable to 8bf5 learn from file IO deal 8bf5 with.
info_handle_open_input: unable to open enter 8bf5 container.
8bf5
8bf5 and mount merely says “unable 8bf5 to open supply container” and 8bf5 repeats the errors from information.
8bf5
8bf5 At this level the drive 8bf5 is ineffective, so I am 8bf5 OK with instantly modifying the 8bf5 Objectmap entry it was complaining 8bf5 about within the first place. 8bf5 Complicating think about that is 8bf5 the TimeMachine backup drive failed 8bf5 on the similar time, so 8bf5 I am assuming it was 8bf5 {an electrical} “excellent storm” that 8bf5 triggered this (we had a 8bf5 pair fast up/down energy sparkles 8bf5 across the similar time) or 8bf5 simply the Worst Luck Ever. 8bf5 Information is presently misplaced, so 8bf5 I do not see I’ve 8bf5 something to lose if I 8bf5 simply begin modifying it, until 8bf5 somebody right here has a 8bf5 greater thought.
8bf5
8bf5 Presumably associated or useful info: 8bf5 For some unusual purpose the 8bf5 precise drive exhibits up in 8bf5 Disk Utilities as disk8 whereas 8bf5 the lone container contained in 8bf5 the drive exhibits as disk9 8bf5 (the precise information being on 8bf5 drive9s1). I am suspecting this 8bf5 occurred on account of making 8bf5 a drive picture copy of 8bf5 a boot drive someplace alongside 8bf5 the lifetime of this drive, 8bf5 however for the reason that 8bf5 entire thought of apfs containers 8bf5 is international to me, I 8bf5 may simply be speaking via 8bf5 one other a part of 8bf5 my anatomy. This is perhaps 8bf5 regular for a container.
8bf5
8bf5