Timeline for mdadm raid10 recovery - is this filesystem corrupted? Is it fixable?
Current License: CC BY-SA 4.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Sep 13, 2018 at 8:36 | comment | added | derobert | @adrinux better yet, if there are details beyond you had to run assemble, post your own answer. | |
| Sep 13, 2018 at 8:34 | comment | added | adrinux | Success! Thanks for you help @derobert I'll update the question with what I did. | |
| Sep 13, 2018 at 8:27 | vote | accept | adrinux | ||
| Sep 12, 2018 at 17:39 | comment | added | adrinux | It's going to take till tomorrow morning for me to get fresh disk images copied into place. I'll let you know how it goes. | |
| Sep 12, 2018 at 17:30 | comment | added | derobert | @adrinux with --force it should work. | |
| Sep 12, 2018 at 17:28 | comment | added | adrinux | Thanks. My attempts at assemble failed, but might have done that after running create (notes inaccessible right now). I'll give it another shot once I have fresh disk images copied into place. | |
| Sep 12, 2018 at 17:25 | comment | added | derobert | @adrinux Your partition table is not lost, there is no reason to be using testdisk to attempt to rediscover it. (And honestly, no idea what that message means from testdisk ... but it could easily be confused by having ⅔ of a filesystem on the disk). | |
| Sep 12, 2018 at 17:19 | comment | added | adrinux | Thinking back, the 3 disk array was created as 2 + 1 missing from the ubuntu installer, the OS installed and the third disk added later once booted - that would explain the discrepancy in size and different fs type designation. Good point about the size. That still leaves Testdisk's 'Bad relative sector' to be puzzled over. | |
| Sep 12, 2018 at 15:00 | history | answered | derobert | CC BY-SA 4.0 |