我有一个3TB的驱动器,希望将其分区为ext4。GParted部分有用。该设备通过eSATA电缆连接到磁盘盒中。
这是gparted_details.html
奇怪的是,调用行读取mkfs.ext4 -F -O ^64bit -L '' '/dev/sda1'
但htm中的错误消息读取64-bit filesystem support is not enabled. The larger fields afforded by this feature enable full-strength checksumming. Pass -O 64bit to rectify.
还是在'64'之前的插入号有效?
保存htm文件后,出现许多有关同步错误的对话框。
GParted 0.30.0 --enable-libparted-dmraid --enable-online-resize
Libparted 3.2
Create Primary Partition #1 (ext4, 2.73 TiB) on /dev/sda 00:00:56 ( ERROR )
create empty partition 00:00:00 ( SUCCESS )
path: /dev/sda1 (partition)
start: 2048
end: 5860532223
size: 5860530176 (2.73 TiB)
clear old file system signatures in /dev/sda1 00:00:00 ( SUCCESS )
write 512.00 KiB of zeros at byte offset 0 00:00:00 ( SUCCESS )
write 4.00 KiB of zeros at byte offset 67108864 00:00:00 ( SUCCESS )
write 4.00 KiB of zeros at byte offset 274877906944 00:00:00 ( SUCCESS )
write 512.00 KiB of zeros at byte offset 3000590925824 00:00:00 ( SUCCESS )
write 4.00 KiB of zeros at byte offset 3000591384576 00:00:00 ( SUCCESS )
write 8.00 KiB of zeros at byte offset 3000591441920 00:00:00 ( SUCCESS )
flush operating system cache of /dev/sda 00:00:00 ( SUCCESS )
set partition type on /dev/sda1 00:00:01 ( SUCCESS )
new partition type: ext4
create new ext4 file system 00:00:55 ( ERROR )
mkfs.ext4 -F -O ^64bit -L '' '/dev/sda1' 00:00:55 ( ERROR )
64-bit filesystem support is not enabled. The larger fields afforded by this feature enable full-strength checksumming. Pass -O 64bit to rectify.
Creating filesystem with 732566272 4k blocks and 183148544 inodes
Filesystem UUID: 326821ce-0b99-4928-b0cc-8efeb99a3cf4
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000, 7962624, 11239424, 20480000, 23887872, 71663616, 78675968,
102400000, 214990848, 512000000, 550731776, 644972544
Allocating group tables: done
Writing inode tables: done
Creating journal (262144 blocks): done
Writing superblocks and filesystem accounting information:
mke2fs 1.44.1 (24-Mar-2018)
Warning, had trouble writing out superblocks.
========================================
关于以后
在我看来,我可以运行badblocks
并查看是否有任何驱动器,这不是新驱动器。
sudo badblocks -w -s -v /dev/sda -o badblocks.txt
因此,这是一个读/写测试,其中状态消息将坏块编号输出到badblocks.txt。几分钟后,badblocks.txt填满了1.2GB的躲藏区编号。
Warning, had trouble writing out superblocks.
是关键:要写入超级块的块是坏的。
几小时后
因此,问题很严重。我重新分区,为坏扇区区域提供了足够的空间,然后创建了稍微小的/ dev / sda1。我目前正在新分区上运行badblocks,以防万一。
假设这是一个新的,空的,空的3TB硬盘,首先需要使用gparted
一个新的GPT分区表(这将擦除磁盘),然后创建所需大小的ext4分区。
更新#1:
不良封锁
注意:请勿中止错误的块扫描!
注意:不要坏块SSD
注意:首先备份您的重要文件!
注意:这将需要几个小时
注意:您可能有待处理的硬盘故障
引导至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.
本文收集自互联网,转载请注明来源。
如有侵权,请联系[email protected] 删除。
我来说两句