Re: Case of the missing softraid
On 2020-10-03, tera torn wrote: > I've been a happy user of OpenBSD softraid RAID 1 mirroring, and I'm > attemtping to migrate data off of a degraded RAID 1 mirror. > > I've booted before from the 6.7 install USB (amd64) and this degraded > chunk was detected and the volume was brought up and my data was there. > > I'm not sure what's happened but now when I boot the same media I'm > unable to detect the softraid volume. I would guess that it most likely got too far into the installer and overwrote the partition table information. What was on the disk - one big single partition for softraid, or was it more complex? > Is there a way to debug this? > Can the chunk be manually mounted as an ffs volume? it should still > contain a normal ffs filesystem somewhere right? Show us current fdisk/disklabel output to eyeball first before you make any changes. If it used the default partition start position and the entire disk was used to create one big softraid partition (with other partitions inside that), then creating a new disklabel with the same configuration should be easy enough. I'm not sure you can get bioctl/softraid to forcibly assemble a new softraid device on a single disk but if the partition is setup in the disklabel and has the correct filesystem type (RAID) it should assemble at boot. If that doesn't help, maybe scan_ffs might be able to find the filesystem inside the softraid; then it should be fairly straightforward to construct a new disklabel allowing it to be mounted. Unfortunately scan_ffs only supports FFS not FFS2 so if it was a newly created or large filesystem that might not be able to help.
Re: Case of the missing softraid
On 2020-10-03 17:45, tera torn wrote: > Hello, > > I've been a happy user of OpenBSD softraid RAID 1 mirroring, and I'm > attemtping to migrate data off of a degraded RAID 1 mirror. > > I've booted before from the 6.7 install USB (amd64) and this degraded > chunk was detected and the volume was brought up and my data was > there. > > I'm not sure what's happened but now when I boot the same media I'm > unable to detect the softraid volume. > > softraid0 is listed by the kernel, but no additional sd device is > configured for the softraid volume. That is always shown, whether softraid is used on the system or not. > Is there a way to debug this? or detect or correct disk corruption so > that this chunk is properly recognized again? The dmesg will give some clues as to what is going on. Hopefully, for Some Reason, the drive just isn't showing up to the machine, the dmesg will show that. Next step, if it is in the dmesg, see if you can get an fdisk and disklabel out of it...does that look sane? > Can the chunk be manually mounted as an ffs volume? it should still > contain a normal ffs filesystem somewhere right? kinda. But rebuilding that would probably be more work than fixing the real problem. > Looking for any way to recover the data in this chunk! Any help > greatly appreciated. I think you need to start with figuring out WHY the volume vanished. Let's hope it's an electrical or mechanical problem. Nick.
Case of the missing softraid
Hello, I've been a happy user of OpenBSD softraid RAID 1 mirroring, and I'm attemtping to migrate data off of a degraded RAID 1 mirror. I've booted before from the 6.7 install USB (amd64) and this degraded chunk was detected and the volume was brought up and my data was there. I'm not sure what's happened but now when I boot the same media I'm unable to detect the softraid volume. softraid0 is listed by the kernel, but no additional sd device is configured for the softraid volume. Is there a way to debug this? or detect or correct disk corruption so that this chunk is properly recognized again? Can the chunk be manually mounted as an ffs volume? it should still contain a normal ffs filesystem somewhere right? Looking for any way to recover the data in this chunk! Any help greatly appreciated. Cheers, -Eric
