我的 SD 卡有一些問題，但無法修復。
這是磁碟在 GNOME 磁碟中的樣子：
當我運行時gdisk /dev/sdb，它給出以下輸出：
sudo gdisk /dev/sdb
GPT fdisk (gdisk) version 1.0.3
Caution: invalid backup GPT header, but valid main header; regenerating
backup header from main header.
Warning! Main and backup partition tables differ! Use the 'c' and 'e' options
on the recovery & transformation menu to examine the two tables.
Warning! One or more CRCs don't match. You should repair the disk!
Partition table scan:
MBR: hybrid
BSD: not present
APM: not present
GPT: damaged
Found valid MBR and corrupt GPT. Which do you want to use? (Using the
GPT MAY permit recovery of GPT data.
我不確定應該使用哪個分割區表，但我使用了 GPT（建立空白 GPT 沒有幫助）分割區如下所示：
Command (? for help): p
Disk /dev/sdb: 125067264 sectors, 59.6 GiB
Model: Multi-Card
Sector size (logical/physical): 512/512 bytes
Disk identifier (GUID): 76A0F070-E171-475B-9409-53840D61AD12
Partition table holds up to 128 entries
Main partition table begins at sector 2 and ends at sector 33
First usable sector is 34, last usable sector is 4194270
Partitions will be aligned on 2048-sector boundaries
Total free space is 671677 sectors (328.0 MiB)
Number Start (sector) End (sector) Size Code Name
1 2048 67583 32.0 MiB 0C01 hassos-boot
2 67584 116735 24.0 MiB 8300 hassos-kernel0
3 116736 641023 256.0 MiB 8300 hassos-system0
4 641024 690175 24.0 MiB 8300 hassos-kernel1
5 690176 1214463 256.0 MiB 8300 hassos-system1
6 1214464 1230847 8.0 MiB 8300 hassos-bootstate
7 1230848 1427455 96.0 MiB 8300 hassos-overlay
8 1427456 3524607 1024.0 MiB 8300 hassos-data
當我想驗證磁碟時我會得到這個資訊：
Caution: The CRC for the backup partition table is invalid. This table may
be corrupt. This program will automatically create a new backup partition
table when you save your partitions.
Problem: The secondary header's self-pointer indicates that it does not 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.
Identified 2 problems!
我可以設法解決這些問題，然後我得到了這個按摩：
No problems found. 121544637 free sectors (58.0 GiB) available in 2
segments, the largest of which is 121542623 (58.0 GiB) in size.
但寫完後我得到了這個：
OK: writing new GUID partition table (GPT) to /dev/sdb.
The operation has completed successfully.
但當我再次檢查分區時，它仍然是一樣的。我嘗試一一刪除所有分割區，然後建立一個新的空 GUID 分割區表，但寫入後我得到以下資訊：
OK: writing new GUID partition table (GPT) to /dev/sdb.
The operation has completed successfully.
但當我再次檢查分區時，它仍然是一樣的。我認為這是因為混合MBR和損壞的GPT。有什麼辦法可以同時刪除這兩張表嗎？或者我還能做什麼來解決這個問題？
先致謝
答案1
我最近實際上也遇到了同樣的問題。您的 SD 卡可能處於某種寫入保護模式。可能的原因：
- 閃存已磨損，無法再寫入。 （這不好！）
- 實體寫入保護開關可能已啟用。 （將其關閉以再次啟用寫入。）
就我而言，在閃存發生故障後，閃存磁碟控制器會默默地丟棄我的寫入，因此即使寫入看起來成功，損壞的分區表也會在下次讀取時返回。
如果您的 SD 卡出現這樣的情況，則它很可能已故障，您需要換一張新卡。
我懷疑您遇到了第一個問題，因為如果寫入保護開關處於活動狀態，您會看到某種「只讀」通知，因為 Linux 可以偵測隨身碟或 SD 卡是否受到寫入保護。 （看/var/log/syslog）
寫入保護閃存驅動器範例/dev/sdc：
5 月 29 日 18:26:44 演示核心：[32319.722491] scsi 2:0:0:0：直接存取 NA NA 1.26 PQ：0 ANSI：5 5 月 29 日 18:26:44 演示內核：[32319.723377] sd 2:0:0:0：附加 scsi generic sg1 type 0 5 月 29 日 18:26:44 示範核心：[32319.724325] sd 2:0:0:0: [sdc] 31266816 512 位元組邏輯區塊：(16.0 GB/14.9 GiB) 5 月 29 日 18:26:44 示範核心：[32319.725131] sd 2:0:0:0: [sdc] 寫入保護已開啟 5 月 29 日 18:26:44 演示核心：[32319.725137] sd 2:0:0:0: [sdc] 模式感知：43 00 80 00 5 月 29 日 18:26:44 示範核心：[32319.725389] sd 2:0:0:0: [sdc] 寫入快取：已停用，讀取快取：已啟用，不支援 DPO 或 FUA 5 月 29 日 18:26:44 演示核心：[32319.737297] sdc：sdc1 5 月 29 日 18:26:44 示範核心：[32319.739266] sd 2:0:0:0: [sdc] 附加 SCSI 可移動磁碟
示範
/dev/sdb是我損壞的隨身碟，它默默地丟棄了寫入內容。
嘗試清除分割區表：
root@demo [~]# gdisk /dev/sdb GPT fdisk (gdisk) version 1.0.3 Caution: invalid backup GPT header, but valid main header; regenerating backup header from main header. Warning! Main and backup partition tables differ! Use the 'c' and 'e' options on the recovery & transformation menu to examine the two tables. Warning! One or more CRCs don't match. You should repair the disk! Partition table scan: MBR: hybrid BSD: not present APM: not present GPT: damaged Found valid MBR and corrupt GPT. Which do you want to use? (Using the GPT MAY permit recovery of GPT data.) 1 - MBR 2 - GPT 3 - Create blank GPT Your answer: 2 Command (? for help): p Disk /dev/sdb: 7897087 sectors, 3.8 GiB Model: USB Flash Disk Sector size (logical/physical): 512/512 bytes Disk identifier (GUID): 5904C65E-B410-474D-B22F-9FEA7E3582C2 Partition table holds up to 128 entries Main partition table begins at sector 2 and ends at sector 33 First usable sector is 34, last usable sector is 7897053 Partitions will be aligned on 2048-sector boundaries Total free space is 2014 sectors (1007.0 KiB) Number Start (sector) End (sector) Size Code Name 1 2048 4095 1024.0 KiB EF02 BIOS boot partition 2 4096 106495 50.0 MiB EF00 EFI System 3 106496 7897053 3.7 GiB 8300 Linux filesystem Command (? for help): x Expert command (? for help): z About to wipe out GPT on /dev/sdb. Proceed? (Y/N): y GPT data structures destroyed! You may now partition the disk using fdisk or other utilities. Blank out MBR? (Y/N): y壞分區表立即回傳：
root@demo [~]# gdisk /dev/sdb GPT fdisk (gdisk) version 1.0.3 Caution: invalid backup GPT header, but valid main header; regenerating backup header from main header. Warning! Main and backup partition tables differ! Use the 'c' and 'e' options on the recovery & transformation menu to examine the two tables. Warning! One or more CRCs don't match. You should repair the disk! Partition table scan: MBR: hybrid BSD: not present APM: not present GPT: damaged Found valid MBR and corrupt GPT. Which do you want to use? (Using the GPT MAY permit recovery of GPT data.) 1 - MBR 2 - GPT 3 - Create blank GPT Your answer:擦除磁碟的開頭
dd也沒有任何效果：root@demo [~]# hexdump -C /dev/sdb | head 00000000 eb 63 90 00 00 00 00 00 00 00 00 00 00 00 00 00 |.c..............| 00000010 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................| * 00000050 00 00 00 00 00 00 00 00 00 00 00 80 00 08 00 00 |................| 00000060 00 00 00 00 ff fa 90 90 f6 c2 80 74 05 f6 c2 70 |...........t...p| 00000070 74 02 b2 80 ea 79 7c 00 00 31 c0 8e d8 8e d0 bc |t....y|..1......| 00000080 00 20 fb a0 64 7c 3c ff 74 02 88 c2 52 bb 17 04 |. ..d|<.t...R...| 00000090 f6 07 03 74 06 be 88 7d e8 17 01 be 05 7c b4 41 |...t...}.....|.A| 000000a0 bb aa 55 cd 13 5a 52 72 3d 81 fb 55 aa 75 37 83 |..U..ZRr=..U.u7.| 000000b0 e1 01 74 32 31 c0 89 44 04 40 88 44 ff 89 44 02 |[email protected].| root@demo [~]# dd if=/dev/zero of=/dev/sdb bs=1M count=1 status=progress 1+0 records in 1+0 records out 1048576 bytes (1.0 MB, 1.0 MiB) copied, 0.0219383 s, 47.8 MB/s root@demo [~]# hexdump -C /dev/sdb | head 00000000 eb 63 90 00 00 00 00 00 00 00 00 00 00 00 00 00 |.c..............| 00000010 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................| * 00000050 00 00 00 00 00 00 00 00 00 00 00 80 00 08 00 00 |................| 00000060 00 00 00 00 ff fa 90 90 f6 c2 80 74 05 f6 c2 70 |...........t...p| 00000070 74 02 b2 80 ea 79 7c 00 00 31 c0 8e d8 8e d0 bc |t....y|..1......| 00000080 00 20 fb a0 64 7c 3c ff 74 02 88 c2 52 bb 17 04 |. ..d|<.t...R...| 00000090 f6 07 03 74 06 be 88 7d e8 17 01 be 05 7c b4 41 |...t...}.....|.A| 000000a0 bb aa 55 cd 13 5a 52 72 3d 81 fb 55 aa 75 37 83 |..U..ZRr=..U.u7.| 000000b0 e1 01 74 32 31 c0 89 44 04 40 88 44 ff 89 44 02 |[email protected].|