![]() Mdadm: hot removed /dev/nvme1n1p2 from ~ # mdadm /dev/md2 -fail /dev/nvme0n1p2 -remove /dev/nvme0n1p2 Mdadm: set /dev/nvme1n1p2 faulty in /dev/md2 Mdadm -add /dev/md2 ~ # mdadm /dev/md2 -fail /dev/nvme1n1p2 -remove /dev/nvme1n1p2 Mdadm: set device faulty failed for /dev/nvme1n1p2: Device or resource busy Mdadm: hot removed /dev/nvme0n1p2 from ~ # mdadm /dev/md2 -fail /dev/nvme1n1p2 -remove /dev/nvme1n1p2 ![]() Mdadm: set /dev/nvme0n1p2 faulty in /dev/md2 Mdadm: Cannot get exclusive access to /dev/md2:Perhaps a running process, mounted filesystem or active volume ~ # mdadm /dev/md2 -fail /dev/nvme0n1p2 -remove /dev/nvme0n1p2 I also can't stop the mdam array to set the while raid array to fail: ~ # mdadm -stop /dev/md2 -force ![]() dev/md2 is apparently in use by the system will not make a filesystem here! Last mounted on /boot on Fri Sep 18 21:33:34 2020 dev/md2 contains a ext4 file system labelled 'boot' Wipefs: error: /dev/md2: probing initialization failed: Device or resource ~ # mkfs.ext4 -L boot /dev/md2 I'm unable to reformat or destroy the partition: ~ # wipefs /dev/md2 Touch: cannot touch '/boot/a': Structure needs cleaningĭmesg shows me: EXT4-fs error (device md2): ext4_find_dest_de:1932: inode #2: block 518: comm touch: bad entry in directory: rec_len is smaller than minimal - offset=0, inode=0, rec_len=0, name_len=0, size=1024Įven after successfully umount the device, I can't fsck ~ # umount ~ # e2fsck /dev/md2Į2fsck: Cannot continue, ~ # fsck.ext4 /dev/md2 While is normally no problem due backups, I can't write to the partition anymore.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |