`<div dir="ltr">I have somewhat of a puzzle .<br><br>I have a rather large zpool which has been running for quite a while now.<br>This pool contains 8 vdevs in Raidz1. Each vdev contains 5 disks. There were also 5 spares in the pool.<br>Some time ago we had electricity problems so we had to take the whole box was down as a precaution. <br>It was on a ups so we took it down orderly.<br>When I started it up again later on I saw that during the startup 5 disks were replaced by the spares and thatthe pool was resilvering. The thing is that these disks all belonged to the same vdev.<br>Pool resilvered but still degraded. <br><br>I have the strong impression that nothing is really wrong with these disks but that at boot time these disks spun up too late <br>or something like that (might be of electricity problems) and so were replaced as zfs thought they were not there.<br>Now I cannot access the data in the pool.<br><br>Is there a way to fool zfs into accepting this vdev with the original disks back into the pool again in its original state?<br>Situation now is that: <br>2 of the old disks in the vdev are registered as removed<br>3 of the old disks in the vdev are registered as degraded<br>and<br>5 spares are registered as online<br><br>As far as I know zfs registers some info on each disk itself which tells what pool/vdev it belongs to.<br>If during resilvering, this info is not removed by zfs, is there a chance to :<br><br>situation 1:<br>1 shutdown the system<br>2 remove the spares<br>3 leave the originals<br>4 startup the system and hope for the best<br><br>situation 2:<br>do something low level on these disks (e.g. in case they do contain info which keeps them out of the pool/vdev.)<br><br>I know this all is far fetched but I want to try anything to save the files on this pool if possible.<br><br>Maybe someone has a good idea.<br>Will maybe also post at developers list.<br><br>Thank you,<br><br>Joe<br></div>
`