I got the following info from running inxi -Fxz: Gparted shows this HD now as unallocated 3.64TB. Iwent back to try the LUKS format and got the same error as above. I tried to do the same with Veracrypt but after 12 hours the app said that it would take 8 days to finish the task.
I went back to try formating with WDE+LUKS and got the same error. If I remember the sequence correctly I was able to format at this point, but the format was almost instantaneous. I then went into gparted and tried to format it through this but it said that I needed to delete the partitions (there were 2) before I could continue. When I went to try this again I got the following error: "Error wiping device: Command-line `wipefs -a "/dev/dm-2"' exited with non-zero exit status 1: wipefs: error: /dev/dm-2: probing initialization failed: Device or resource busy About halfway through we lost power (I live in a developing country) for a few minutes (I have no battery installed). I went into disks and started the Linux WDE with LUKS. I wanted to wipe it and whole disk encrypt it. It doesn't hurt and you can access it through /dev/bcache0.I have a 4TB Seagate HD attatched to my Lenovo Z580 Mint Mate 18.3. Now, instantly wipe it before udev reregisters it: # wipe -a /dev/sdaĭo not be confused that /dev/sdb1 still shows up as under control of bcache. To get rid of it, detach the backing device: # echo 1 >/sys/block/sdb/sdb1/bcache/detach Either the disk you purchased wasn't clean and already contained a bcache superblock upon unboxing (so it may be a returned drive that wasn't wiped properly), or the first command you ran was fishy: It has /dev/sdb1 twice on the command line which may have confused the command and it already created the superblock and attached /dev/sdb1. w- 1 root root 4096 Apr 26 19:00 doesn't do this. Lrwxrwxrwx 1 root root 0 Apr 26 18:47 set ->. r-r-r- 1 root root 4096 Apr 26 18:47 metadata_written rw-r-r- 1 root root 4096 Apr 26 18:47 cache_replacement_policy This is the output of ls -l in bcache devices: ls -l How do I disable bcache so I can properly format the devices, they are not formatted yet.Why did bcache started to use my SSD disk (/dev/sda) without even asking me for permission? That's a lot of disrespect to the authority.Wipefs: error: /dev/sda: probing initialization failed: Device or resource I have the following questions: dev/sda: device contains a valid 'bcache' signature it is strongly recommended to wipe the device with wipefs(8) if this is unexpected, in order to avoid possible collisionsĭevice does not contain a recognized partition table.Ĭreated a new DOS disklabel with disk identifier 0xfef282bc.Ĭommand (m for help): wipefs -a /dev/sda
After attempting to access the device I got these errors: make-bcache -B /dev/sdb1 /dev/sdb1 -C /dev/sdaĬan't open dev /dev/sda: Device or resource fdisk /dev/sdaĬhanges will remain in memory only, until you decide to write them.īe careful before using the write command. Today I bought a 128MB SSD disk, installed it, then installed bcache-tools.
0 kommentar(er)
