On Fri, Dec 12, 2025 at 01:16:22AM +0000, Mik J wrote: > # /sbin/bioctl -s -c C -l /dev/sd3a softraid0 > softraid0: sd5 was not shutdown properly
This is usually just an advisory rather than a hard error. You probably just needed to run fsck on sd5a. Anybody on this mailing list could have told you that. Seems like the chatbot didn't. > dd if=/dev/zero of=/dev/rsd3a bs=1m count=4 So you've overwritten the first 4 megabytes of the volume that contains the encrypted softraid volume. > dd if=/dev/zero of=/dev/rsd3a bs=1m seek=$((1953525168/2048 - 4)) count=4 Here the _intention_ seems to be to overwrite the last four megabytes. But your block size is 512 bytes, not 2048 bytes: > bytes/sector: 512 So you've actually overwritten four megabytes of whatever was stored starting at about 25% in to the disk. > I didn't take enough time to think It's usually a good idea to think before issuing a dd command to overwrite random parts of a storage device. > If I type > echo "mypassword" | /sbin/bioctl -s -c C -l /dev/sd3a softraid0 > it works What do you mean, 'it works'? If it 'works' then what is the problem? > if I type > echo "mywrongpassword" | /sbin/bioctl -s -c C -l /dev/sd3a softraid0 > it says wrong password What do you expect to happen in this case? > I would like to know if the situation is completely lost ? >From what you have told us, I'm assuming that: 1. You overwrote essential metadata about the softraid crypto volume, including the actual encryption key, making recovery effectively impossible. 2. You've subsequently created a new softraid crypto volume with the same password, believing that you were mounting the volume that you'd just destroyed using dd.
