收起左侧

外挂USB硬盘随机改变盘符导致系统报存储空间损坏

4
回复
528
查看
[ 复制链接 ]

1

主题

2

回帖

0

牛值

江湖小虾

2025-1-8 10:47:48 显示全部楼层 阅读模式

设备环境:物理机CPU intel8100 主板msi B360M 虚拟机pve8.3 q35安装fnos0.8.29

BUG现象:主机通过USB3.0接口挂载移动硬盘,pve直通给fnos。硬盘能够分配存储空间正常使用,但是会在系统运行十几个小时后出现“存储空间已损坏”提示,存储空间无法访问。通过重启fnos虚拟机后可以重新识别存储空间,这种情况目前在运行了4天中已出现了3次,平均都是10个多小时出现问题。查看系统日志发现在出问题时sda(外部usb硬盘)会断开连接,然后usb硬盘重新枚举并识别为sdc系统检查出错。下面是日志片段:

2025-01-08T02:35:03.146602+08:00 fnos-bo systemd[1]: Starting apt-daily.service - Daily apt download activities... 2025-01-08T02:35:03.265970+08:00 fnos-bo apt.systemd.daily[49894]: /usr/lib/apt/apt.systemd.daily: 341: cd: can't cd to /var/backups 2025-01-08T02:35:03.638102+08:00 fnos-bo systemd[1]: apt-daily.service: Deactivated successfully. 2025-01-08T02:35:03.638309+08:00 fnos-bo systemd[1]: Finished apt-daily.service - Daily apt download activities. 2025-01-08T02:35:12.137350+08:00 fnos-bo kernel: [14941.547857] usb 6-1: USB disconnect, device number 2 2025-01-08T02:35:12.138877+08:00 fnos-bo kernel: [14941.548305] sd 12:0:0:0: [sda] tag#21 FAILED Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK cmd_age=0s 2025-01-08T02:35:12.138884+08:00 fnos-bo kernel: [14941.548307] sd 12:0:0:0: [sda] tag#21 CDB: Read(10) 28 00 05 34 0d 00 00 03 e8 00 2025-01-08T02:35:12.139180+08:00 fnos-bo kernel: [14941.548308] I/O error, dev sda, sector 87297280 op 0x0:(READ) flags 0x0 phys_seg 125 prio class 2 2025-01-08T02:35:12.139191+08:00 fnos-bo kernel: [14941.548339] sd 12:0:0:0: [sda] tag#22 FAILED Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK cmd_age=0s 2025-01-08T02:35:12.139193+08:00 fnos-bo kernel: [14941.548340] sd 12:0:0:0: [sda] tag#22 CDB: Read(10) 28 00 00 06 b0 00 00 00 20 00 2025-01-08T02:35:12.139193+08:00 fnos-bo kernel: [14941.548341] I/O error, dev sda, sector 438272 op 0x0:(READ) flags 0x0 phys_seg 4 prio class 2 2025-01-08T02:35:12.139193+08:00 fnos-bo kernel: [14941.548356] BTRFS error (device dm-1): bdev /dev/mapper/trim_4db1b5c8_c737_4eaf_85dc_57f3ef139495-0 errs: wr 0, rd 1, flush 0, corrupt 0, gen 0 2025-01-08T02:35:12.139532+08:00 fnos-bo kernel: [14941.548484] device offline error, dev sda, sector 2535424 op 0x0:(READ) flags 0x0 phys_seg 4 prio class 2 2025-01-08T02:35:12.139534+08:00 fnos-bo kernel: [14941.548503] BTRFS error (device dm-1): bdev /dev/mapper/trim_4db1b5c8_c737_4eaf_85dc_57f3ef139495-0 errs: wr 0, rd 2, flush 0, corrupt 0, gen 0 2025-01-08T02:35:12.140289+08:00 fnos-bo kernel: [14941.548725] device offline error, dev sda, sector 6732472 op 0x0:(READ) flags 0x0 phys_seg 5 prio class 2 2025-01-08T02:35:12.140293+08:00 fnos-bo kernel: [14941.548776] device offline error, dev sda, sector 438272 op 0x0:(READ) flags 0x0 phys_seg 4 prio class 2 2025-01-08T02:35:12.140294+08:00 fnos-bo kernel: [14941.548794] BTRFS error (device dm-1): bdev /dev/mapper/trim_4db1b5c8_c737_4eaf_85dc_57f3ef139495-0 errs: wr 0, rd 3, flush 0, corrupt 0, gen 0 2025-01-08T02:35:12.817178+08:00 fnos-bo MAINEVENT[1344]: MAINEVENT:{"cat":0,"template":"EjectDisk","name":"sda","model":"BUP_Slim","serial":"00000000NABK6EWY"} 2025-01-08T02:35:14.686500+08:00 fnos-bo kernel: [14944.099222] usb 6-1: New USB device found, idVendor=0bc2, idProduct=ac19, bcdDevice= 1.00 2025-01-08T02:35:14.686515+08:00 fnos-bo kernel: [14944.099226] usb 6-1: New USB device strings: Mfr=2, Product=3, SerialNumber=1 2025-01-08T02:35:14.686516+08:00 fnos-bo kernel: [14944.099228] usb 6-1: Product: BUP Slim 2025-01-08T02:35:14.686516+08:00 fnos-bo kernel: [14944.099229] usb 6-1: Manufacturer: Seagate 2025-01-08T02:35:14.686517+08:00 fnos-bo kernel: [14944.099230] usb 6-1: SerialNumber: 00000000NABK6EWY 2025-01-08T02:35:14.689869+08:00 fnos-bo kernel: [14944.102928] scsi host13: uas 2025-01-08T02:35:14.689884+08:00 fnos-bo kernel: [14944.104045] scsi 13:0:0:0: Direct-Access Seagate BUP Slim 0004 PQ: 0 ANSI: 6 2025-01-08T02:35:14.697083+08:00 fnos-bo kernel: [14944.110039] sd 13:0:0:0: [sdc] 1953525167 512-byte logical blocks: (1.00 TB/932 GiB) 2025-01-08T02:35:14.697093+08:00 fnos-bo kernel: [14944.110340] sd 13:0:0:0: [sdc] Write Protect is off 2025-01-08T02:35:14.697094+08:00 fnos-bo kernel: [14944.110342] sd 13:0:0:0: [sdc] Mode Sense: 4f 00 00 00 2025-01-08T02:35:14.697094+08:00 fnos-bo kernel: [14944.111497] sd 13:0:0:0: [sdc] Preferred minimum I/O size 4096 bytes 2025-01-08T02:35:14.844121+08:00 fnos-bo MAINEVENT[1344]: MAINEVENT:{"cat":0,"template":"InsertDisk","name":"sdc","model":"","serial":""} 2025-01-08T02:35:14.874844+08:00 fnos-bo share_service[49970]: exportfs: No file systems exported! 2025-01-08T02:35:14.898760+08:00 fnos-bo share_service[49975]: exportfs: No file systems exported! 2025-01-08T02:35:14.947485+08:00 fnos-bo nmbd[1296]: [2025/01/08 02:35:14.946199, 0] ../../source3/nmbd/nmbd_workgroupdb.c:279(dump_workgroups)

出现频率:必现

联系方式:953940866@qq.com

收藏
送赞 1
分享

1

主题

2

回帖

0

牛值

江湖小虾

2025-1-9 10:22:57 楼主 显示全部楼层
这个硬盘没有独立供电,假设是供电不够稳定导致有概率使usb断开连接。在断开后usb又立即进行了枚举并正确识别了设备的VID、PID以及设备描述信息,说明设备还是能够正常使用的,但是系统分配了一个新的盘符,这可能是导致系统无法识别存储空间的原因。系统使用uuid绑定盘符能不能解决这个问题

43

主题

8436

回帖

0

牛值

管理员

2025-1-8 15:08:53 显示全部楼层
外接硬盘休眠会导致系统识别成存储空间损坏
日志中有休眠和唤醒的记录通常都没有问题,出现问题时的情况是USB意外断开连接,之后重新枚举时盘符改变了,导致硬盘无法被正确识别  详情 回复
2025-1-8 15:21

1

主题

2

回帖

0

牛值

江湖小虾

2025-1-8 15:21:44 楼主 显示全部楼层
日志中有休眠和唤醒的记录通常都没有问题,出现问题时的情况是USB意外断开连接,之后重新枚举时盘符改变了,导致硬盘无法被正确识别
那要检查一下接口和线材是否松动  详情 回复
2025-1-8 17:54

43

主题

8436

回帖

0

牛值

管理员

2025-1-8 17:54:42 显示全部楼层
qb574500110 发表于 2025-1-8 15:21
日志中有休眠和唤醒的记录通常都没有问题,出现问题时的情况是USB意外断开连接,之后重新枚举时盘符改变了 ...

那要检查一下接口和线材是否松动
您需要登录后才可以回帖 登录 | 立即注册

本版积分规则