Tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,mode=755)Ĭgroup on /sys/fs/cgroup/unified type cgroup2 (rw,nosuid,nodev,noexec,relatime)Ĭgroup on /sys/fs/cgroup/systemd type cgroup (rw,nosuid,nodev,noexec,relatime,xattr,name=systemd) Tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k) Tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev) Securityfs on /sys/kernel/security type securityfs (rw,nosuid,nodev,noexec,relatime) dev/sde3 on / type ext4 (rw,relatime,data=ordered) Tmpfs on /run type tmpfs (rw,nosuid,noexec,relatime,size=4938092k,mode=755) Udev on /dev type devtmpfs (rw,nosuid,relatime,size=24666292k,nr_inodes=6166573,mode=755)ĭevpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000) Proc on /proc type proc (rw,nosuid,nodev,noexec,relatime) Sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
So i cant see anything wrong with the drive. sd 2:0:0:0: Write cache: enabled, read cache: enabled, does n't support DPO or FUA Quote from wolfesupport on August 5, 2020, 12:32 am You can also try to wipe the drive on some other box, even on Windows.Īnother thing is to check if there are no errors in the drive If nothing works and you can reboot, try rebooting and re-doing the above commands. If this fails, try the dd command by write 100M rather than 100 sectors.
If it is, try to find what process is using it We want to understand why the system thinks the device is in use.Ĭan you check if it is used as a mount point Quote from admin on August 3, 2020, 11:13 amĭid not list /dev/sdf so it does not look a an active lvm vg. I am adding a osd without journal or cache, as i cant add a cache or journal drive either. Wipefs: error: /dev/sdf: probing initialization failed: Device or resource busy Manually running the wipefs -a -f works, but not wipefs -a. Wipefs: error: /dev/sdf: probing initialization failed: Device or resource also fails. Yes i have also tried those pvs -o pv_name,vg_name
Quote from wolfesupport on August 3, 2020, 8:22 am There are only two volume groups, and they are on the disk that managed to add successfully. However attempting to add the disk again still fails. I/O size (minimum/optimal): 512 bytes / 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes Quote from wolfesupport on August 3, 2020, 2:09 am
0 kommentar(er)
