NSA325 RAID1 lost
All Replies
-
Hello Mijzelf,
This is dmesg log. As you said before I have to investigate it and found the issue
GPT:Primary header thinks Alt. header is not at the end of the disk. GPT:5860577133 != 7814037167 GPT:Alternate GPT header not at the end of the disk. GPT:5860577133 != 7814037167
I fixed Primary header but not backup (Alt. header). NAS OS found this ussie and won't start. Both message before about the same: Alt Header is not corresponding with Primary and with the end of the disk (It is rationally to cover all HDD space in GPT).
You are right: a backup GPT header stored at the final LBA, looks like OS found it somehow in sector 5860577133 (3Tb)
So the GPT interpreter here seems to look at a 3TB disk having a 4TB GPT, or vise versa.
IDK how is it working and actually I have only common understanding of GPT.
I have only one explanation: 5 december I fixed Primary header and initial size (4tb) was restored (confirmed by TestDisk screenshot). It had correct information about Max LBA. Now interpreter could look at Secondary Header and may be he found an incorrect addres about size in SecHeader
0
Categories
- All Categories
- 415 Beta Program
- 2.3K Nebula
- 141 Nebula Ideas
- 94 Nebula Status and Incidents
- 5.6K Security
- 218 USG FLEX H Series
- 262 Security Ideas
- 1.4K Switch
- 71 Switch Ideas
- 1K Wireless
- 39 Wireless Ideas
- 6.3K Consumer Product
- 245 Service & License
- 382 News and Release
- 81 Security Advisories
- 27 Education Center
- 8 [Campaign] Zyxel Network Detective
- 3.1K FAQ
- 34 Documents
- 34 Nebula Monthly Express
- 83 About Community
- 71 Security Highlight