On a factory default setup, the root of the file system ("/") has object id 2. The first inode numbers are assigned as follows: 0 = invalid (can't happen)ġ = the parent of the "/" (root) directory - doesn't really existģ = the private directory ("private-dir")ħ = holder for purgeable files (not an actual directory) This usually means that this was one of the very first files or directories created on the file system. This is important for you as the number is very low. This is also otherwise referred to as the "inode number". The inode contains metadata about the object, such as for example when it was created, when it was last modified, how large it is, who owns it, etc.Īn "inode_val" is simply the value (contents) of the inode.Įach object has a unique number for identification purposes. The meaning of the file system check error message below:Įach object (file, directory, link, whatever) on your file system is represented as a data structure known as an "inode". ** The volume /dev/disk3s1 could not be verified completely.įWIW: I have the original 4 TB APFS drive with the invalid fsroot tree in my hands untouched if I need to do further troubleshooting and/or recovery. Disk was unmounted and it's not the boot disk, yet still had to use sudo to overcome permission denied errors. Running fsck_apfs again in debug mode -d. Is there another way to fix this drive? No 3rd party utilities can repair, but perhaps through debug mode finding the files that caused the error and restoring or deleting those? How do I know CCC copied all my files without corruption? Since it was apparently operating without issues except for the First Aid error, I have no idea if any files are missing or corrupted. What does the "invalid nchildren" error mean? The new HFS drive passes Disk First Aid without errors. I bought another 4 TB drive, formatted it as HFS, and used CCC to clone the "bad" APFS drive over and get the machine back into use. There seems to be no way to fix an invalid fsroot except for reformatting the drive. I've also attempted fsck via the terminal but that results in the exact same error and messages. I've already looked into third-party tools and there are none that can repair APFS drives. According to the documentation for fsck_apfs, exit code 0 means no errors. Restoring the original state found as unmounted.ĭisk Utility gives you the green checkmark "complete", and you have no idea there is an issue unless you click "see details". The volume /dev/rdisk3s1 could not be verified completely. While I was in Disk Utility I ran Disk First Aid on this hard drive and it found the following: Checking the APFS volume superblock.Įrror: inode_val: object (oid 0x3): invalid nchildren (-1) It's been working fine without issues as far as I know. When I installed it late last year, I formatted it as APFS and used CCC (Carbon Copy Cloner) to clone my old drive over to it. I use it for my 1.5 TB Home folder since it's way too big for my SSD boot drive. I have a fairly new 4 TB Seagate HDD (3.5") that I use strictly for data non-booting, no OS. Mac Pro model 5,1 (mid 2012, 3.33 Ghz 6-core Xeon) with 32 GB of stock RAM and the stock video card.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |