Welcome to Overclockers Forums! Join us to reply in threads, receive reduced ads, and to customize your site experience!
root@server1 [~]# pvremove /dev/sdb1
PV /dev/sdb1 belongs to Volume Group vg so please use vgreduce first.
(If you are certain you need pvremove, then confirm by using --force twice.)
root@server1 [~]# lvremove /dev/sdb1
Volume group "sdb1" not found
Skipping volume group sdb1
root@server1 [~]# dmsetup remove /dev/sdb1
Device sdb1 not found
Command failed
root@server1 [~]# dmsetup remove /dev/sdb
Device sdb not found
Command failed
root@server1 [~]#
root@server1 [~]# mdadm --detail /dev/md127
mdadm: cannot open /dev/md127: No such file or directory
mdadm --zero-superblock devicepath
root@server1 [~]# lvs
LV VG Attr LSize Pool Origin Data% Move Log Cpy%Sync Convert
root vg -wi-ao---- 922.66g
swap vg -wi-a----- 7.84g
tmp vg -wi-ao---- 1.00g
Yes, destructive command.After skimming the man page of mdadm, I see that running --zero-superblock just rewrites the drive with nothing but 0s. I am pretty sure the drive(s) are not in any RAID array. I asked my server provider and they assured me my hardware isn't capable of hardware RAID and software RAID isn't being used.
hbarta@olive:~$ ls /etc/init.d/mdadm*
/etc/init.d/mdadm /etc/init.d/mdadm-raid /etc/init.d/mdadm-waitidle
hbarta@olive:~$
hbarta@olive:~$ dpkg -l|grep mdadm
ii mdadm 3.3-2 amd64 tool to administer Linux MD arrays (software RAID)
hbarta@olive:~$
root@128:~# mkfs.ext4 /dev/sda6
mke2fs 1.42.9 (28-Dec-2013)
/dev/sda6 is apparently in use by the system; will not make a filesystem here!
dmesg | grep sda6
[ 3.831755] sda: sda1 sda2 sda3 sda4 < sda5 sda6 sda7 >
[ 34.215409] EXT3-fs (sda6): using internal journal
[ 34.218922] EXT3-fs (sda6): mounted filesystem with ordered data mode
dd if=/dev/zero of=/dev/sda6 bs=1024000 count=32000
reboot
Glad I could help.Made an account just to say, thank you. Your information helped me save a USB drive I thought was toast. =)