清单HFS+设备

Question

我试图读取(而不是写)基于HFS+的这个职位驱动器的内容。它会自动显示在文件管理器中，但我无法查看驱动器。关于它是否已安装有相互矛盾的信息。

我还有一个问题妨碍了我的实验能力:弹出没有响应，所以我要做的是拔掉/回复USB连接器。但是它没有被lsblk列出，在gnome实用程序中显示为“无媒体”。唯一的办法，使它重新安装，我已经能够提出，是重新启动。这显然是乏味的，所以我能做些什么呢？

重启后的Just：

$ lsblk
NAME                MAJ:MIN RM   SIZE RO TYPE  MOUNTPOINT
sda                   8:0    0 298.1G  0 disk  
├─sda1                8:1    0   512M  0 part  /boot/efi
├─sda2                8:2    0     1K  0 part  
├─sda5                8:5    0   731M  0 part  /boot
└─sda6                8:6    0 296.9G  0 part  
  └─sda6_crypt      253:0    0 296.9G  0 crypt 
    ├─vgmint-root   253:1    0 295.9G  0 lvm   /
    └─vgmint-swap_1 253:2    0   976M  0 lvm   [SWAP]
sdb                   8:16   0 232.9G  0 disk  
├─sdb1                8:17   0   200M  0 part  
├─sdb2                8:18   0 232.1G  0 part  
└─sdb3                8:19   0 619.9M  0 part  

After断开/连接

$ lsblk
NAME                MAJ:MIN RM   SIZE RO TYPE  MOUNTPOINT
sda                   8:0    0 298.1G  0 disk  
├─sda1                8:1    0   512M  0 part  /boot/efi
├─sda2                8:2    0     1K  0 part  
├─sda5                8:5    0   731M  0 part  /boot
└─sda6                8:6    0 296.9G  0 part  
  └─sda6_crypt      253:0    0 296.9G  0 crypt 
    ├─vgmint-root   253:1    0 295.9G  0 lvm   /
    └─vgmint-swap_1 253:2    0   976M  0 lvm   [SWAP]

<#>其他

我认为El Capitan是Mac上最后一个格式化这个驱动器的操作系统，所以我认为这排除了APFS。

$ apt list -a hfsprogs
Listing... Done
hfsprogs/focal,now 332.25-11build1 amd64 [installed]

此命令无限期挂起：

$ sudo fsck.hfsplus -f /dev/sdb
[sudo] password:  
** /dev/sdb

$ dmesg
[  853.373536] usb 3-2.2: New USB device found, idVendor=174c, idProduct=225c, bcdDevice= 0.01
[  853.373542] usb 3-2.2: New USB device strings: Mfr=2, Product=3, SerialNumber=1
[  853.373546] usb 3-2.2: Product: AS2235
[  853.373549] usb 3-2.2: Manufacturer: ASMedia
[  853.373553] usb 3-2.2: SerialNumber: 00000000000000000000
[  853.452921] usb-storage 3-2.2:1.0: USB Mass Storage device detected
[  853.453556] scsi host6: usb-storage 3-2.2:1.0
[  853.453728] usbcore: registered new interface driver usb-storage
[  853.475165] usbcore: registered new interface driver uas
[  854.465134] scsi 6:0:0:0: Direct-Access     ASMT     2235             0    PQ: 0 ANSI: 6
[  854.466208] sd 6:0:0:0: Attached scsi generic sg1 type 0
[  854.467472] sd 6:0:0:0: [sdb] 488397168 512-byte logical blocks: (250 GB/233 GiB)
[  854.468359] sd 6:0:0:0: [sdb] Write Protect is off
[  854.468368] sd 6:0:0:0: [sdb] Mode Sense: 43 00 00 00
[  854.468938] sd 6:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[  854.529233]  sdb: sdb1 sdb2 sdb3
[  854.559294] sd 6:0:0:0: [sdb] Attached SCSI disk
[  898.271130] usb 3-2.2: reset high-speed USB device number 4 using xhci_hcd
[ 1052.032857] sd 6:0:0:0: [sdb] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[ 1052.032865] sd 6:0:0:0: [sdb] tag#0 Sense Key : Not Ready [current] 
[ 1052.032870] sd 6:0:0:0: [sdb] tag#0 Add. Sense: Logical unit is in process of becoming ready
[ 1052.032876] sd 6:0:0:0: [sdb] tag#0 CDB: Read(10) 28 00 00 06 40 2a 00 00 01 00
[ 1052.032884] blk_update_request: I/O error, dev sdb, sector 409642 op 0x0:(READ) flags 0x800 phys_seg 1 prio class 0
[ 1052.032964] hfsplus: unable to find HFS+ superblock
[ 1314.406829] sd 6:0:0:0: [sdb] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[ 1314.406838] sd 6:0:0:0: [sdb] tag#0 Sense Key : Not Ready [current] 
[ 1314.406843] sd 6:0:0:0: [sdb] tag#0 Add. Sense: Logical unit is in process of becoming ready
[ 1314.406850] sd 6:0:0:0: [sdb] tag#0 CDB: Read(10) 28 00 00 06 40 2a 00 00 01 00
[ 1314.406858] blk_update_request: I/O error, dev sdb, sector 409642 op 0x0:(READ) flags 0x800 phys_seg 1 prio class 0
[ 1314.406934] hfsplus: unable to find HFS+ superblock
[ 1524.675415] sd 6:0:0:0: [sdb] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[ 1524.675418] sd 6:0:0:0: [sdb] tag#0 Sense Key : Not Ready [current] 
[ 1524.675420] sd 6:0:0:0: [sdb] tag#0 Add. Sense: Logical unit is in process of becoming ready
[ 1524.675422] sd 6:0:0:0: [sdb] tag#0 CDB: Read(10) 28 00 00 06 40 2a 00 00 01 00
[ 1524.675425] blk_update_request: I/O error, dev sdb, sector 409642 op 0x0:(READ) flags 0x800 phys_seg 1 prio class 0
[ 1524.675442] hfsplus: unable to find HFS+ superblock
[ 6405.037621] INFO: task pool-udisksd:6187 blocked for more than 120 seconds.

$ sudo smartctl -a -s on --tolerance=verypermissive /dev/sdc
smartctl 7.1 2019-12-30 r5022 [x86_64-linux-5.4.0-122-generic] (local build)
Copyright (C) 2002-19, Bruce Allen, Christian Franke, www.smartmontools.org

Read Device Identity failed: scsi error device will be ready soon

=== START OF INFORMATION SECTION ===
Device Model:     [No Information Found]
Serial Number:    [No Information Found]
Firmware Version: [No Information Found]
Device is:        Not in smartctl database [for details use: -P showall]
ATA Version is:   [No Information Found]
Local Time is:    Wed Jul 13 19:38:05 2022 EDT
SMART support is: Ambiguous - ATA IDENTIFY DEVICE words 82-83 don't show if SMART supported.
SMART support is: Ambiguous - ATA IDENTIFY DEVICE words 85-87 don't show if SMART is enabled.
                  Checking to be sure by trying SMART RETURN STATUS command.
SMART support is: Unknown - Try option -s with argument 'on' to enable it.
=== START OF ENABLE/DISABLE COMMANDS SECTION ===
SMART Enable failed: scsi error device will be ready soon

Read SMART Data failed: scsi error device will be ready soon


=== START OF READ SMART DATA SECTION ===
SMART Status command failed: scsi error device will be ready soon
SMART overall-health self-assessment test result: UNKNOWN!
SMART Status, Attributes and Thresholds cannot be read.

Read SMART Error Log failed: scsi error device will be ready soon

Read SMART Self-test Log failed: scsi error device will be ready soon

Selective Self-tests/Logging not supported

Answer 1

正如@Red七号在答案的注释中指出的那样，下面是dmesg输出的重要部分：

[ 7619.684210] blk_update_request: I/O error, dev sdb, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
[ 7619.684222] Buffer I/O error on dev sdb, logical block 0, async page read

这可能表示某种类型的硬件故障。我会在硬盘上做个自我检查。您可以使用smartctl命令行实用工具(可用选项的smartctl --help)或使用图形实用程序来实现这一点。我推荐GSmartControl，但仅仅因为这是我所熟悉的，而且相当合理--如果您找到另一个您更喜欢的工具，可以随意使用它。

我将首先运行一个完整的离线检查，并检查整体健康状况。然后检查此表中的属性，以红色高亮显示：https://en.wikipedia.org/wiki/S.M.A.R.T.#ATA_S.M.A.R.T._属性

这些值的较高水平(截至2022年7月)表明即将发生驱动器故障。

Answer 2

试试这个：

插入外接硬盘

卸载驱动器

运行：

 sudo apt update

 sudo apt install hfsprogs

 sudo fsck.hfsplus -f /dev/sdb2 

重装驱动器

驱动器现在是读-写。