Hi Harry In the situation you are in there is nothing you can do anymore for that one disk. It's gone. You'll need a new one.
That said thanks to ZFS all your data is still there and you can get into a clean state very easily. 1. Buy or Organize a new Disk with the same RPM and the same or Bigger Capacity. If your current disk is not sold anymore then just focus on a brand you trust with the same RPM and bigger Capacity. If the new disk is bigger than c5d1 then any excess will simply not be addressable by ZFS. Which is not be an issue if it is just a couple of GB. If you wish to have two new disks as you final configuration then just grab any two disks you like or even SSD's. The main assumption is of course that any disk you pick fits your physical Plugs. 2. Insert the new disk in place where c5d0 was. 3. Issue "zpool replace rpool c5d0s0" 4. Wait until done. If you wish to also renew c5d1 with a new model you would continue as follows. If not ignore the steps below: 5. Issue "zpool offline rpool c5d1" and pull the disk 6. Insert new disk in place of c5d1 and Issue "zpool replace rpool c5d1" 7. Wait for completion 8. Issue "zpool set autoexpand=on rpool" Now you have a pool on two new disks exanded to the max capacity. Pro tip: Always buy an extra disk and store it on a shelf inside it's protective bag. That way you can quickly replace the drive without having to worry about getting new ones. Hope this helps Greetings Till On 18.12.19 10:29, Harry Putnam wrote: > Running quite an old version of hipster > > SunOS 2x 5.11 illumos-a356818ef9 i86pc i386 i86pc > > I have a setup so shaky I've been afraid to try update to current > hipster. But that is not the subject of this post: > > I found this message on rpool > > ,---- > | root # zpool status rpool > | pool: rpool > | state: DEGRADED > | status: One or more devices are faulted in response to persistent errors. > | Sufficient replicas exist for the pool to continue functioning in a > | degraded state. > | action: Replace the faulted device, or use 'zpool clear' to mark the device > | repaired. > | scan: scrub repaired 0 in 1h18m with 0 errors on Mon Jan 8 18:38:42 2018 > | config: > | > | NAME STATE READ WRITE CKSUM > | rpool DEGRADED 0 0 0 > | mirror-0 DEGRADED 0 0 0 > | c5d0s0 FAULTED 0 0 0 too many errors > | c5d1 ONLINE 0 0 0 > `---- > > As you see, this status was taken after completing a scrub attempting > to correct the problems > > You see the result of the scrub was goose eggs > > I also tried the `zpool clear' recommended in status report above. > > That failed to clear the problem. > > I decided to detached the bad disk (c5d0s0), thinking there was some repair > possibilities working on the disk by itself... and soon discovered I > didn't really have a clue how proceed. > > Googling turned up a good bit about working on s pool, but having trouble > finding what I can do to the detached disk to fix it. > > Can anyone offer a way to proceed? > > > _______________________________________________ > openindiana-discuss mailing list > [email protected] > https://openindiana.org/mailman/listinfo/openindiana-discuss > _______________________________________________ openindiana-discuss mailing list [email protected] https://openindiana.org/mailman/listinfo/openindiana-discuss
