可是過了1個月後發現它竟然壞軌了…
而且買回來沒三天就將硬碟從外接盒拆出,
當時的目的是為了擴展筆電的容量(筆電預載的是 500G),
所以也買了一個筆電用內接盒把光碟機替換掉。
這顆硬碟切成三個分區,
其分配如下:
- NTFS-500G(給 Windows 放置其他的資料)
- ReiserFS-400G(給 Ubuntu 掛載至「~/影片」之下)
- NTFS(放系統備份還原檔)
ReiserFS 的掛載是修改 Ubuntu 中於 /etc/fstab 設定檔:
lancer@lancer-desktop:~$ cat /etc/fstab
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc nodev,noexec,nosuid 0 0
# / was on /dev/sda2 during installation
UUID=f4c88cc3-0caa-4476-83ef-b0699139d98c / ext4 errors=remount-ro 0 1
# /home was on /dev/sda6 during installation
UUID=37718ea7-60bd-4639-919e-f3d0f22c121f /home reiserfs defaults 0 2
# ~/影片
UUID=03cde11a-3c79-48db-ac17-3732413bab13 /home/lancer/影片 reiserfs defaults 0 0
# swap was on /dev/sda7 during installation
UUID=3332b5d5-f42a-44de-82be-f0302136741b none swap sw 0 0
lancer@lancer-desktop:~$
|
由於之前設定 fstab 時使用開機時自動以 fsck 檢查,
但發生硬碟磁區壞了以後開機檢查到壞軌時就完全卡住,
雖然能看到警示訊息,
但進不去系統總是令人頭痛…
The problem has occured looks like a hardware problem. If you have bad blocks, we advise you to get a new hard drive, because once you get one bad block that the disk drive internals cannot hide from your sight, the chances of getting more are generally said to become much higher (precise statistics are unknown to us), and this disk is probably not expensive enough for you to you to risk your time and data on it. If you don't want to follow that follow that advice then if you have just a few bad blocks, try writting to the bad blocks and see if the drive remaps the bad blocks (that means it takes a block it has in reserve and allocates it for use for of that block number). If it cannot remap the block, use badblock option (-B) with reiserfs utils to handle this block correctly. bread: Cannot read the block (1984): (Input/output error). fsck: Warning... fsck.reiserfs for device /dev/sdb2 exited with signal 6. mountall: fsck ...... |
後來想想損壞的地方暫時不管了,
能進系統才是重點!
利用 LiveCD or LiveUSB 啟動 Ubuntu,
掛載本機的碟碟然後修改 fstab 的設定,
將出問題的磁區從開機自動檢查設定修改成不檢查。
fstab 相關的設定可以參考鳥哥的網站,
不過我還是得記錄一下各個欄位所代表的意義:
<file system>
磁碟裝置掛載名稱或 UUID。
UUID 可藉由這條指令得以查尋「sudo blkid -s UUID」。
將磁碟裝置掛載於何處,
我所壞的分區就是掛載於家目錄下的影片目錄中(/home/lancer/影片)。
磁碟分區的檔案格式。
如 ext3、ext4、reiserfs、nfs、vfat…等。
<options>
- async/sync
- auto/noauto
- rw/ro
- exec/noexec
- user/nouser
- suid/nosuid
- usrquota
- grpquota
- defaults
是否執行備份指令。
0 代表不要做 dump 備份。
1 代表要每天進行 dump 的動作。
2 代表其他不定日期的 dump 備份動作。
開機時是否執行 fsck 以檢查磁碟分區。
0 是不要檢查。
1 是優先檢查,一般是系統分區。
2 是接續優先檢查後再進行檢查。
沒有留言:
張貼留言