☰

Blk_update_request：I/O錯誤重啟錯誤

tag-icon • tag-icon boot dual-boot 20.04
Blk_update_request：I/O錯誤重啟錯誤

我的雙啟動 Windows 和 Ubuntu 20.04 的電腦啟動時黑屏，並顯示以下錯誤訊息：

[  647.729444] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x40000 action 0x0 
[  647.729482] ata1.00: irq_stat 0x40000001 
[  647.729498] ata1: SError: {CommWake }
[  647.729516] ata1.00: failed commands: READ DMA EXT
[  647.729534] ata1.00: cmd 25/00:00:20:64:63/00:01:11:00:00/e0 tag 28 dfma 131072 in
[  647.729534]          res 51/40:68:b8:64:63/00:01:11:00:00/f1 Emask 0x9 (media error)
[  647.729590] ata1.00: status: { DRDY ERR }
[  647.729606] ata1.00: error: { UNC }
[  647.730346] blk_update_request: I/O error, dev sda, sector 291726520 op 0x0:(READ) flags 0x80700 phys_seg 2 prio class 0

答案1

讓我們看看是否可以對該磁碟進行壞塊處理並使其恢復運行。

注意：不要中止壞塊掃描！

注意：不要對 SSD 進行壞塊操作

注意：首先備份您的重要文件！

注意：這將需要幾個小時

注意：您可能有待處理的硬碟故障

在「嘗試 Ubuntu」模式下啟動至 Ubuntu Live DVD/USB。

在terminal...

sudo fdisk -l# 辨識所有「Linux 檔案系統」分割區

sudo e2fsck -fcky /dev/sdXX# 唯讀測試

或者

sudo e2fsck -fccky /dev/sdXX# 無損讀/寫入測試（受到推崇的）

-k 很重要，因為它保存先前的壞塊表，並將任何新的壞塊添加到該表中。如果沒有 -k，您將丟失所有先前的壞塊資訊。

-fccky 參數...

   -f    Force checking even if the file system seems clean.

   -c    This option causes e2fsck to use badblocks(8) program to do
         a read-only scan of the device in order to find any bad blocks.
         If any bad blocks are found, they are added to the bad block
         inode to prevent them from being allocated to a file or direc‐
         tory.  If this option is specified twice, then the bad block scan
         will be done using a non-destructive read-write test.

   -k    When combined with the -c option, any existing bad blocks in the
         bad blocks list are preserved, and any new bad blocks found by
         running badblocks(8) will be added to the existing bad blocks
         list.

   -y    Assume an answer of `yes' to all questions; allows e2fsck to be
         used non-interactively. This option may not be specified at the
         same time as the -n or -p options.

相關內容