SSD SanDisk Ultra-II GPT не соответствует размеру PMBR

Мой SSD был использован в моем MacBook через месяц без каких-либо проблем, SSD больше не используется. Я не могу установить его, я не могу отформатировать его. Я не знаю, что делать. Я не возражаю против каких-либо данных, которые они потеряли, но я хочу, чтобы мой SSD вернулся в моем MacBook с твердотельным накопителем на 480 ГБ, и было дорого тратить его.

bjoern@bjoernr:~/Schreibtisch/testdisk$ sudo fdisk -l /dev/sda GPT PMBR size mismatch (937703087 != 937703086) will be corrected by w(rite). The backup GPT table is corrupt, but the primary appears OK, so that will be used. Medium /dev/sda: 447,1 GiB, 480103980544 Bytes, 937703087 Sektoren Einheiten: sectors von 1 * 512 = 512 Bytes Sektorengröße (logisch/physisch): 512 Bytes / 512 Bytes I/O Größe (minimal/optimal): 512 Bytes / 512 Bytes Typ der Medienbezeichnung: gpt Medienkennung: 75036D89-9E67-40CC-879F-2E7ADCEDD63E Gerät Start Ende Sektoren Größe Typ /dev/sda1 40 409639 409600 200M EFI System /dev/sda2 409640 936433511 936023872 446,3G Apple Core storage /dev/sda3 936433512 937703047 1269536 619,9M Apple boot

- Если я открою графический интерфейс GParted, я получаю :

Libparted-Error: резервная таблица GPT повреждена, но основная информация отображается ОК, поэтому она будет использоваться. Я не могу отформатировать SSD, не могу изменить разделы. Он запрашивает «Ошибка при чтении конца файла»

- Если я открываю GParted GUI, я получаю:

bjoern@bjoernr:~/Schreibtisch/testdisk$ sudo gdisk /dev/sda GPT fdisk (gdisk) version 1.0.1 Warning! Disk size is smaller than the main header indicates! Loading secondary header from the last sector of the disk! You should use 'v' to verify disk integrity, and perhaps options on the experts' menu to repair the disk. Caution: invalid backup GPT header, but valid main header; regenerating backup header from main header. Partition table scan: MBR: protective BSD: not present APM: not present GPT: damaged **************************************************************************** Caution: Found protective or hybrid MBR and corrupt GPT. Using GPT, but disk verification and recovery are STRONGLY recommended. **************************************************************************** Command (? for help): v Problem: The secondary header's self-pointer indicates that it doesn't reside at the end of the disk. If you've added a disk to a RAID array, use the 'e' option on the experts' menu to adjust the secondary header's and partition table's locations. Problem: Disk is too small to hold all the data! (Disk size is 937703087 sectors, needs to be 937703088 sectors.) The 'e' option on the experts' menu may fix this problem. Identified 2 problems! Command (? for help): x Expert command (? for help): e Relocating backup data structures to the end of the disk Expert command (? for help): w Final checks complete. About to write GPT data. THIS WILL OVERWRITE EXISTING PARTITIONS!! Do you want to proceed? (Y/N): Y OK; writing new GUID partition table (GPT) to /dev/sda. The operation has completed successfully.

Он все еще поврежден

bjoern@bjoernr:~/Schreibtisch/testdisk$ sudo gdisk /dev/sda GPT fdisk (gdisk) version 1.0.1 Warning! Disk size is smaller than the main header indicates! Loading secondary header from the last sector of the disk! You should use 'v' to verify disk integrity, and perhaps options on the experts' menu to repair the disk. Caution: invalid backup GPT header, but valid main header; regenerating backup header from main header. Partition table scan: MBR: protective BSD: not present APM: not present GPT: damaged bjoern@bjoernr:~/Schreibtisch/testdisk$ sudo smartctl --attributes --log=selftest /dev/sda smartctl 6.6 2016-05-31 r4324 [x86_64-linux-4.13.0-32-generic] (local build) Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org === START OF READ SMART DATA SECTION === SMART Attributes Data Structure revision number: 4 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 5 Reallocated_Sector_Ct 0x0032 100 100 --- Old_age Always - 0 9 Power_On_Hours 0x0032 253 100 --- Old_age Always - 1747 12 Power_Cycle_Count 0x0032 100 100 --- Old_age Always - 4839 165 Total_Write/Erase_Count 0x0032 100 100 --- Old_age Always - 223411569605 166 Min_W/E_Cycle 0x0032 100 100 --- Old_age Always - 10 167 Min_Bad_Block/Die 0x0032 100 100 --- Old_age Always - 38 168 Maximum_Erase_Cycle 0x0032 100 100 --- Old_age Always - 208 169 Total_Bad_Block 0x0032 100 100 --- Old_age Always - 0 171 Program_Fail_Count 0x0032 100 100 --- Old_age Always - 0 172 Erase_Fail_Count 0x0032 100 100 --- Old_age Always - 0 173 Avg_Write/Erase_Count 0x0032 100 100 --- Old_age Always - 33 174 Unexpect_Power_Loss_Ct 0x0032 100 100 --- Old_age Always - 82 187 Reported_Uncorrect 0x0032 100 100 --- Old_age Always - 3 194 Temperature_Celsius 0x0022 066 045 --- Old_age Always - 34 (Min/Max 3/45) 199 SATA_CRC_Error 0x0032 100 100 --- Old_age Always - 0 230 Perc_Write/Erase_Count 0x0032 100 100 --- Old_age Always - 4651554178620 232 Perc_Avail_Resrvd_Space 0x0033 100 100 004 Pre-fail Always - 100 233 Total_NAND_Writes_GiB 0x0032 100 100 --- Old_age Always - 13762 234 Perc_Write/Erase_Ct_BC 0x0032 100 100 --- Old_age Always - 19813 241 Total_Writes_GiB 0x0030 253 253 --- Old_age Offline - 9139 242 Total_Reads_GiB 0x0030 253 253 --- Old_age Offline - 6725 244 Thermal_Throttle 0x0032 000 100 --- Old_age Always - 0 SMART Self-test log structure revision number 1 Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Short offline Completed: read failure 00% 1747 622138136 # 2 Short offline Completed: read failure 00% 1746 369836824 # 3 Short offline Completed without error 00% 1746 - # 4 Extended offline Completed: read failure 00% 1746 2458432 # 5 Short offline Aborted by host 00% 1204 - # 6 Short offline Aborted by host 00% 1207 - # 7 Short offline Aborted by host 00% 1207 - # 8 Short offline Aborted by host 00% 1207 - # 9 Short offline Aborted by host 00% 1207 - #10 Short offline Aborted by host 00% 1207 - #11 Short offline Aborted by host 00% 1206 - #12 Short offline Aborted by host 00% 1206 - #13 Short offline Aborted by host 00% 1206 - #14 Short offline Aborted by host 00% 1206 - #15 Short offline Aborted by host 00% 1206 - #16 Short offline Aborted by host 00% 1206 - #17 Short offline Aborted by host 00% 1206 - #18 Short offline Aborted by host 00% 1206 - #19 Short offline Aborted by host 00% 1205 - #20 Short offline Aborted by host 00% 1205 - #21 Short offline Aborted by host 00% 1205 -

Я благодарю вас за любую помощь !!!!!!!!!!!!!

0
задан 26 January 2018 в 17:00

0 ответов

Другие вопросы по тегам:

Похожие вопросы: