Timeline for RAID6 unable to mount EXT4-fs: bad geometry: block count exceeds size of device
Current License: CC BY-SA 4.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 10, 2023 at 23:11 | vote | accept | jameszp | ||
| Apr 10, 2023 at 9:48 | answer | added | frostschutz | timeline score: 0 | |
| Apr 10, 2023 at 0:47 | comment | added | frostschutz | So anything that isn't on your 4 disk array won't be fully recoverable / if at all. Thus you have an extreme case of "block count exceeds size of device" where the missing section can mostly be considered lost. Your best bet is that the filesystem didn't store anything important beyond that point. It's possible but there's no guarantee for anything since technically filesystems are allowed to store their data anywhere. Shrinking filesystems usually also involves relocating data. | |
| Apr 10, 2023 at 0:14 | comment | added | frostschutz | Your first link says 1. Reduce the filesystem size. It seems like this wasn't done at all and trying to fsck in that state only makes things worse. Since the RAID has already been reshaped, the 7 drives won't help you much. Their data, if untouched, now represents a 11 drive raid6 with 4 drives missing. raid6 can only survive 2 missing drives. So their parity chunks are useless and only data chunks remain, so it's all in bits and pieces. | |
| S Apr 9, 2023 at 23:55 | review | First questions | |||
| Apr 10, 2023 at 23:15 | |||||
| S Apr 9, 2023 at 23:55 | history | asked | jameszp | CC BY-SA 4.0 |