文档建议反馈控制台
首页
学习
活动
专区
圈层
工具
MCP广场
文章/答案/技术大牛
发布
社区首页 >问答首页 >尝试在Kubernetes集群中使用iSCSI卷，但得到了“错误的fs类型、糟糕的选项、/dev/sdb上的坏超级块、缺少代码页或助手程序”

问尝试在Kubernetes集群中使用iSCSI卷，但得到了“错误的fs类型、糟糕的选项、/dev/sdb上的坏超级块、缺少代码页或助手程序”
EN

Stack Overflow用户
提问于 2021-04-14 01:37:25
回答 1查看 825关注 0票数 0

由于NFS 参考可能导致的问题，我试图在K8S集群中构建iSCSI卷挂载，但是我得到了错误：

MountVolume.MountDevice对卷“iscsipd”失败:挂载失败:退出状态32 安装参数：--description=Kubernetes用于/var/lib/kubelet/plugins/kubernetes.io/iscsi/iface-default/192.168.20.100:3260-iqn.2020-09.com.xxxx:yyyy.testtarget-lun-1的临时挂载--范围--挂载-t ext4 -o默认值/dev/disk/by-path/ip-192.168.20.100:3260-iscsi-iqn.2020-09.com.xxxx:yyyy.testtarget-lun-1 /var/lib/kubelet/plugins/kubernetes.io/iscsi/iface-default/192.168.20.100:3260-iqn.2020-09.com.xxxx:yyyy.testtarget-lun-1 安装: /var/lib/kubelet/plugins/kubernetes.io/iscsi/iface-default/192.168.20.100:3260-iqn.2020-09.com.xxxx:yyyy.testtarget-lun-1:错误fs类型、坏选项、/dev/sdb上的坏超级块、缺少代码页或助手程序或其他错误。

开始时，我遵循本文件创建iSCSI启动器，由于不同情况导致的错误，我多次尝试不同的设置。iSCSI启动器连接看起来很好

代码语言：javascript
复制
Command (m for help): p
Disk /dev/sdb: 1 GiB, 1073741824 bytes, 2097152 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 2CDE61DE-F57A-4C0B-AFB6-9DD7040A8BBD

Tue Apr 13 15:41:57 i@kt04:~$ lsblk
NAME                      MAJ:MIN RM  SIZE RO TYPE MOUNTPOINT
sda                         8:0    0   64G  0 disk
├─sda1                      8:1    0    1M  0 part
├─sda2                      8:2    0    1G  0 part /boot
├─sda3                      8:3    0   49G  0 part
│ └─ubuntu--vg-ubuntu--lv 253:0    0   63G  0 lvm  /
└─sda4                      8:4    0   14G  0 part
  └─ubuntu--vg-ubuntu--lv 253:0    0   63G  0 lvm  /
sdb                         8:16   0    1G  0 disk
sr0                        11:0    1 1024M  0 rom

Tue Apr 13 15:45:33 i@kt04:~$ sudo ls -l /dev/disk/by-path/
total 0
lrwxrwxrwx 1 root root  9 Apr 13 15:41 ip-192.168.20.100:3260-iscsi-iqn.2020-09.com.xxxx:yyyy.testtarget-lun-1 -> ../../sdb
lrwxrwxrwx 1 root root  9 Apr 13 11:07 pci-0000:00:10.0-scsi-0:0:0:0 -> ../../sda
lrwxrwxrwx 1 root root 10 Apr 13 11:07 pci-0000:00:10.0-scsi-0:0:0:0-part1 -> ../../sda1
lrwxrwxrwx 1 root root 10 Apr 13 11:07 pci-0000:00:10.0-scsi-0:0:0:0-part2 -> ../../sda2
lrwxrwxrwx 1 root root 10 Apr 13 11:07 pci-0000:00:10.0-scsi-0:0:0:0-part3 -> ../../sda3
lrwxrwxrwx 1 root root 10 Apr 13 11:07 pci-0000:00:10.0-scsi-0:0:0:0-part4 -> ../../sda4
lrwxrwxrwx 1 root root  9 Apr 13 01:55 pci-0000:02:01.0-ata-1 -> ../../sr0

Tue Apr 13 15:46:18 i@kt04:~$ sudo iscsiadm -m session -P 3
iSCSI Transport Class version 2.0-870
version 2.0-874
Target: iqn.2020-09.com.xxxx:yyyy.testtarget (non-flash)
        Current Portal: 192.168.20.100:3260,1
        Persistent Portal: 192.168.20.100:3260,1
                **********
                Interface:
                **********
                Iface Name: default
                Iface Transport: tcp
                Iface Initiatorname: iqn.2020-09.com.xxxx:yyyy.testtarget
                Iface IPaddress: 192.168.30.24
                Iface HWaddress: <empty>
                Iface Netdev: <empty>
                SID: 2
                iSCSI Connection State: LOGGED IN
                iSCSI Session State: LOGGED_IN
                Internal iscsid Session State: NO CHANGE
                *********
                Timeouts:
                *********
                Recovery Timeout: 120
                Target Reset Timeout: 30
                LUN Reset Timeout: 30
                Abort Timeout: 15
                *****
                CHAP:
                *****
                username: <empty>
                password: ********
                username_in: <empty>
                password_in: ********
                ************************
                Negotiated iSCSI params:
                ************************
                HeaderDigest: None
                DataDigest: None
                MaxRecvDataSegmentLength: 262144
                MaxXmitDataSegmentLength: 262144
                FirstBurstLength: 65536
                MaxBurstLength: 262144
                ImmediateData: Yes
                InitialR2T: Yes
                MaxOutstandingR2T: 1
                ************************
                Attached SCSI devices:
                ************************
                Host Number: 33 State: running
                scsi33 Channel 00 Id 0 Lun: 1
                        Attached scsi disk sdb          State: running

Tue Apr 13 15:57:55 i@kt04:~$ sudo systemctl status open-iscsi
● open-iscsi.service - Login to default iSCSI targets
   Loaded: loaded (/lib/systemd/system/open-iscsi.service; enabled; vendor preset: enabled)
   Active: active (exited) since Tue 2021-04-13 11:03:20 CST; 5h 6min ago
     Docs: man:iscsiadm(8)
           man:iscsid(8)
  Process: 1352 ExecStop=/lib/open-iscsi/logout-all.sh (code=exited, status=0/SUCCESS)
  Process: 1351 ExecStop=/bin/sync (code=exited, status=0/SUCCESS)
  Process: 1301 ExecStop=/lib/open-iscsi/umountiscsi.sh (code=exited, status=0/SUCCESS)
  Process: 1416 ExecStart=/lib/open-iscsi/activate-storage.sh (code=exited, status=0/SUCCESS)
  Process: 1383 ExecStart=/sbin/iscsiadm -m node --loginall=automatic (code=exited, status=0/SUCCESS)
 Main PID: 1416 (code=exited, status=0/SUCCESS)

Apr 13 11:03:20 kt04 systemd[1]: Starting Login to default iSCSI targets...
Apr 13 11:03:20 kt04 iscsiadm[1383]: Logging in to [iface: default, target: iqn.2020-09.com.xxxx:yyyy.testtarget, portal: 192.168.20.100,3260] (multiple)
Apr 13 11:03:20 kt04 iscsiadm[1383]: Login to [iface: default, target: iqn.2020-09.com.xxxx:yyyy.testtarget, portal: 192.168.20.100,3260] successful.
Apr 13 11:03:20 kt04 systemd[1]: Started Login to default iSCSI targets.

Tue Apr 13 16:09:28 i@kt04:~$ sudo systemctl status iscsid
● iscsid.service - iSCSI initiator daemon (iscsid)
   Loaded: loaded (/lib/systemd/system/iscsid.service; enabled; vendor preset: enabled)
   Active: active (running) since Tue 2021-04-13 11:03:20 CST; 5h 6min ago
     Docs: man:iscsid(8)
  Process: 1374 ExecStart=/sbin/iscsid (code=exited, status=0/SUCCESS)
  Process: 1364 ExecStartPre=/lib/open-iscsi/startup-checks.sh (code=exited, status=0/SUCCESS)
 Main PID: 1377 (iscsid)
    Tasks: 2 (limit: 4915)
   CGroup: /system.slice/iscsid.service
           ├─1376 /sbin/iscsid
           └─1377 /sbin/iscsid

Apr 13 11:03:20 kt04 systemd[1]: Starting iSCSI initiator daemon (iscsid)...
Apr 13 11:03:20 kt04 iscsid[1374]: iSCSI logger with pid=1376 started!
Apr 13 11:03:20 kt04 systemd[1]: Started iSCSI initiator daemon (iscsid).
Apr 13 11:03:21 kt04 iscsid[1376]: iSCSI daemon with pid=1377 started!
Apr 13 11:03:21 kt04 iscsid[1376]: Connection2:0 to [target: iqn.2020-09.com.xxxx:yyyy.testtarget, portal: 192.168.20.100,3260] through [iface: default] is operational now

Tue Apr 13 16:21:21 i@kt04:~$ cat /proc/scsi/scsi
Attached devices:
Host: scsi2 Channel: 00 Id: 00 Lun: 00
  Vendor: NECVMWar Model: VMware SATA CD00 Rev: 1.00
  Type:   CD-ROM                           ANSI  SCSI revision: 05
Host: scsi32 Channel: 00 Id: 00 Lun: 00
  Vendor: VMware   Model: Virtual disk     Rev: 2.0
  Type:   Direct-Access                    ANSI  SCSI revision: 06
Host: scsi33 Channel: 00 Id: 00 Lun: 01
  Vendor: SYNOLOGY Model: iSCSI Storage    Rev: 4.0
  Type:   Direct-Access                    ANSI  SCSI revision: 05

我尝试过"sdb“像上面所示的那样作为原始磁盘工作，并创建了一个用ext4文件系统挂载的ext4分区(甚至创建了一次LVM )，这导致了”挂载失败:退出状态32 /dev/sdb已经挂载或挂载点忙“错误。

我用过

代码语言：javascript
复制
apiVersion: v1
kind: Pod
metadata:
  name: iscsipd
spec:
  nodeName: kt04
  containers:
  - name: iscsipd-rw
    image: kubernetes/pause
    volumeMounts:
    - mountPath: "/mnt/iscsipd"
      name: iscsipd-rw
  restartPolicy: Always
  volumes:
  - name: iscsipd-rw
    iscsi:
      targetPortal: 192.168.20.100:3260
      iqn: iqn.2020-09.com.xxxx:yyyy.testtarget
      lun: 1
      fsType: ext4
      readOnly: false

最后一次尝试使用fdisk创建一个sdb1分区，该分区带有ext4，但没有安装到/mnt，结果如下：“错误fs类型、坏选项、/dev/sdb上的坏超级块、缺少代码页或帮助程序”。

代码语言：javascript
复制
Wed Apr 14 11:25:06 ice@kt04:~$ lsblk
NAME                      MAJ:MIN RM  SIZE RO TYPE MOUNTPOINT
sda                         8:0    0   64G  0 disk
├─sda1                      8:1    0    1M  0 part
├─sda2                      8:2    0    1G  0 part /boot
├─sda3                      8:3    0   49G  0 part
│ └─ubuntu--vg-ubuntu--lv 253:0    0   63G  0 lvm  /
└─sda4                      8:4    0   14G  0 part
  └─ubuntu--vg-ubuntu--lv 253:0    0   63G  0 lvm  /
sdb                         8:16   0    1G  0 disk
└─sdb1                      8:17   0 1023M  0 part
sr0                        11:0    1 1024M  0 rom

在NAS(使用语法RS1221) iSCSI配置面板上，它显示目标是连接的(Lun是厚配置)。

裸金属版k8s : 1.19.6

iscsiadm版本2.0-874

开放-iscsi版本2.0.874-5 ubuntu2.10

任何人都可以提供一些建议，我可以尝试使它发挥作用，或指出我做错了什么？

persistent-volumes
iscsi
kubernetes
EN

回答 1

Stack Overflow用户

回答已采纳

发布于 2021-04-14 05:53:36

问题解决了。感谢龙武园上的斯莱克#库伯内特斯-用户。

在解决问题之前提供的资料：

代码语言：javascript
复制
$ df -h
Filesystem                         Size  Used Avail Use% Mounted on
udev                               7.9G     0  7.9G   0% /dev
tmpfs                              1.6G  3.5M  1.6G   1% /run
/dev/mapper/ubuntu--vg-ubuntu--lv   62G   10G   49G  18% /
tmpfs                              7.9G     0  7.9G   0% /dev/shm
tmpfs                              5.0M     0  5.0M   0% /run/lock
tmpfs                              7.9G     0  7.9G   0% /sys/fs/cgroup
/dev/sda2                          976M  146M  764M  16% /boot

$ lsblk
NAME                      MAJ:MIN RM  SIZE RO TYPE MOUNTPOINT
sda                         8:0    0   64G  0 disk
├─sda1                      8:1    0    1M  0 part
├─sda2                      8:2    0    1G  0 part /boot
├─sda3                      8:3    0   49G  0 part
│ └─ubuntu--vg-ubuntu--lv 253:0    0   63G  0 lvm  /
└─sda4                      8:4    0   14G  0 part
  └─ubuntu--vg-ubuntu--lv 253:0    0   63G  0 lvm  /
sdb                         8:16   0    1G  0 disk
└─sdb1                      8:17   0 1023M  0 part
sr0                        11:0    1 1024M  0 rom

然后删除吊舱

代码语言：javascript
复制
$ df -h
Filesystem                         Size  Used Avail Use% Mounted on
udev                               7.9G     0  7.9G   0% /dev
tmpfs                              1.6G  3.5M  1.6G   1% /run
/dev/mapper/ubuntu--vg-ubuntu--lv   62G   10G   49G  18% /
tmpfs                              7.9G     0  7.9G   0% /dev/shm
tmpfs                              5.0M     0  5.0M   0% /run/lock
tmpfs                              7.9G     0  7.9G   0% /sys/fs/cgroup
/dev/sda2                          976M  146M  764M  16% /boot

然后执行sudo dd if=/dev/zero of=/dev/sdb bs=1M count=512 status=progress

代码语言：javascript
复制
$ sudo dd if=/dev/zero of=/dev/sdb bs=1M count=512 status=progress
512+0 records in
512+0 records out
536870912 bytes (537 MB, 512 MiB) copied, 4.85588 s, 111 MB/s
$ lsblk
NAME                      MAJ:MIN RM  SIZE RO TYPE MOUNTPOINT
sda                         8:0    0   64G  0 disk
├─sda1                      8:1    0    1M  0 part
├─sda2                      8:2    0    1G  0 part /boot
├─sda3                      8:3    0   49G  0 part
│ └─ubuntu--vg-ubuntu--lv 253:0    0   63G  0 lvm  /
└─sda4                      8:4    0   14G  0 part
  └─ubuntu--vg-ubuntu--lv 253:0    0   63G  0 lvm  /
sdb                         8:16   0    1G  0 disk
sr0                        11:0    1 1024M  0 rom

然后再涂一次豆荚，效果很好！，df -h & lsblk在吊舱工作后的信息

代码语言：javascript
复制
$ df -h
Filesystem                         Size  Used Avail Use% Mounted on
udev                               7.9G     0  7.9G   0% /dev
tmpfs                              1.6G  3.7M  1.6G   1% /run
/dev/mapper/ubuntu--vg-ubuntu--lv   62G   10G   49G  17% /
tmpfs                              7.9G     0  7.9G   0% /dev/shm
tmpfs                              5.0M     0  5.0M   0% /run/lock
tmpfs                              7.9G     0  7.9G   0% /sys/fs/cgroup
/dev/sda2                          976M  146M  764M  16% /boot

$ lsblk
NAME                      MAJ:MIN RM  SIZE RO TYPE MOUNTPOINT
sda                         8:0    0   64G  0 disk
├─sda1                      8:1    0    1M  0 part
├─sda2                      8:2    0    1G  0 part /boot
├─sda3                      8:3    0   49G  0 part
│ └─ubuntu--vg-ubuntu--lv 253:0    0   63G  0 lvm  /
└─sda4                      8:4    0   14G  0 part
  └─ubuntu--vg-ubuntu--lv 253:0    0   63G  0 lvm  /
sdb                         8:16   0    1G  0 disk
sr0                        11:0    1 1024M  0 rom

如前所述，我应该更好地了解错误消息“坏超级块”，并找到解决方案，或者我的环境在这种iSCSI卷情况下的错误配置是什么。

票数 -1
EN
页面原文内容由Stack Overflow提供。腾讯云小微IT领域专用引擎提供翻译支持
原文链接：

https://stackoverflow.com/questions/67084405

复制
相关文章

相似问题

领券

腾讯云开发者

扫码关注腾讯云开发者

扫码关注腾讯云开发者

领取腾讯云代金券

热门产品

热门推荐

更多推荐

Copyright © 2013 - 2026 Tencent Cloud. All Rights Reserved. 腾讯云 版权所有 

深圳市腾讯计算机系统有限公司 ICP备案/许可证号：粤B2-20090059 粤公网安备44030502008569号

腾讯云计算（北京）有限责任公司 京ICP证150476号 |  京ICP备11018762号

问题归档专栏文章快讯文章归档关键词归档开发者手册归档开发者手册 Section 归档