On Tue, Dec 01, 2015 at 05:53:22PM -0800, Nathan Wheeler wrote: > I have a similar sort of setup during installs and I clear out the > first 10m before setting up the CRYPTO disk and it works for me. I > don't think you're zeroing out enough at the beginning of the disk. > > dd if=/dev/zero of=/dev/rsd0c bs=10m count=1 >
Following your tip i tried the following series of commands which failed in the same way: === # dd if=/dev/zero of=/dev/rsd0d # dd if=/dev/zero of=/dev/rsd0a bs=1m count=1 # dd if=/dev/zero of=/dev/rsd0c bs=10m count=1 === I then tried the following variant which also failed: === # dd if=/dev/zero of=/dev/rsd0d # dd if=/dev/zero of=/dev/rsd0a bs=10m count=1 # dd if=/dev/zero of=/dev/rsd0c bs=1m count=1 === Finally i tried this just to cover all possibilities, which also failed: === # dd if=/dev/zero of=/dev/rsd0d # dd if=/dev/zero of=/dev/rsd0a bs=10m count=1 # dd if=/dev/zero of=/dev/rsd0c bs=10m count=1 === I might have been unclear on this point (and I am not sure if this is how you are doing it) but the above commands are executed on the running system before rebooting into the installer. Could it be that the kernel writes out some in-memory softraid information to the disk before rebooting? I have noticed that just leaving a "dd if=/dev/zero of=/dev/rsd0c bs=1m" "long enough" will work, but it feels too brittle, and my optimal situation would be that the system is able to operate after the above commands are run, only having an impact after a reboot or power outage, which the unbounded dd does not achieve (this might not be an achievable goal at all of course). -- Patrik Lundin
