Timeline for Can't partition hard drive - "corrupt", exit code 8
Current License: CC BY-SA 3.0
20 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 15, 2020 at 8:04 | history | edited | CommunityBot |
Commonmark migration
|
|
| Sep 8, 2017 at 23:26 | vote | accept | LinusG. | ||
| Sep 8, 2017 at 23:26 | answer | added | klanomath | timeline score: 2 | |
| Sep 8, 2017 at 23:22 | comment | added | LinusG. | Perfect! I can now partition my drive. Thanks so much, @klanomath. Post an answer, if you wish, and I’ll accept it. | |
| Sep 8, 2017 at 22:59 | comment | added | LinusG. | Cool, that seemed to do it. It‘s disk18. It found the incorrect block count has "successfully repaired the volume". I’ll see how the partitioning goes and get back to you. Thanks so far! @klanomath | |
| Sep 8, 2017 at 22:45 | comment | added | klanomath |
Your main volume isn't mounted! Enter diskutil cs list. With the UUID of the Logical Volume enter diskutil cs unlockVolume UUID. Then diskutil list and with the disk identifier of the now mounted main volume diskutil verifyVolume diskX.
|
|
| Sep 8, 2017 at 22:32 | comment | added | LinusG. | Nothing. There’s no result. | |
| Sep 8, 2017 at 22:27 | comment | added | LinusG. | Well that’s what I’m saying: the only disk with a comparable size is disk1. When I scroll down, there’s only disks with a few kilo- or megabytes. @klanomath | |
| Sep 8, 2017 at 22:14 | comment | added | LinusG. |
Right, so as you can see in the first image of the 2nd edit, there’s a disk w/ the id disk1 that’s 500.3GB big. Running the verify command for disk1, gives me this error: "Error starting file system verification for disk1: invalid request (-69886)". Running the same command for disk1s2, however, actually finishes the verification. Same for the repair command. - @klanomath
|
|
| Sep 8, 2017 at 21:34 | history | edited | LinusG. | CC BY-SA 3.0 |
added 795 characters in body
|
| Sep 8, 2017 at 18:14 | comment | added | Steve Chambers | I would go with the disk utility but reformatting is cheaper, though time consuming. Also klanomath may have some suggestions, he's better at disk utility via command line than I am... | |
| Sep 8, 2017 at 18:14 | history | edited | LinusG. | CC BY-SA 3.0 |
added 715 characters in body
|
| Sep 8, 2017 at 18:07 | comment | added | LinusG. | Ha, love the analogy. So, should I rather try the 3rd party apps you’ve mentioned, or reformat my drive? | |
| Sep 8, 2017 at 18:06 | comment | added | Steve Chambers | It looks like the error is on the Mac side. Just like a cut, if you ignore it it might heal or it might get infected. I always have an updated copy of Diskwarior on hand for the (rare) times this happens. I never ignore disk errors. | |
| Sep 8, 2017 at 18:01 | comment | added | LinusG. | @SteveChambers, if I ignore the error (and obviously don’t install Windows), will this error affect my machine in any other way? | |
| Sep 8, 2017 at 17:59 | history | edited | Glorfindel♦ | CC BY-SA 3.0 |
grammar corrections
|
| Sep 8, 2017 at 17:56 | history | edited | LinusG. | CC BY-SA 3.0 |
deleted 4 characters in body
|
| Sep 8, 2017 at 17:55 | comment | added | Steve Chambers | Reformatting might be the least expensive way to "fix" the issue. Other solutions that I can think of involve 3rd party disk utilities like DiskWarrior or DriveGenius. | |
| Sep 8, 2017 at 17:54 | history | edited | klanomath | CC BY-SA 3.0 |
deleted 11 characters in body
|
| Sep 8, 2017 at 17:27 | history | asked | LinusG. | CC BY-SA 3.0 |