Opened 18 months ago
Closed 16 months ago
#1039 closed defect (fixed)
disk replacement glitch
| Reported by: | esamett | Owned by: | |
|---|---|---|---|
| Priority: | major | Milestone: | |
| Component: | GUI | Version: | 8.0.2-RELEASE |
| Keywords: | Cc: |
Description
see:
http://forums.freenas.org/showthread.php?4546-Help-Data-Corruption-now-what&p=17116#post17116
I had disk errors I couldn't get to go away after dealing with some loose cabling. Following advice I removed one of the "bad" but online drives and wiped with GPARTED. It took some doing but I got array back on line, cleared and scrubbed. The "replace" GUI function first gave error then worked after I rechecked cables.
I replaced the disk that should have been labeled ada8. As mentioned in an older ticket it instead had been previously been labeled with a really long number sequence but I was advised that this was OK.
As shown in the attached first image, the ID and Name fields are blank for this disk but the array is on line.
As shown in the second image the disk status screen looks "normal."
The array seems to be functioning otherwise OK.
Attachments (2)
Change History (6)
Changed 18 months ago by esamett
Changed 18 months ago by esamett
comment:1 Changed 18 months ago by william
comment:2 Changed 18 months ago by william
As a side node, it should be all fixed in trunk (upcoming 8.2)
comment:3 Changed 18 months ago by esamett
seems ok now. i got nervous when I saw the checkmark for scratching the data!
comment:4 Changed 16 months ago by gcooper
- Resolution set to fixed
- Status changed from new to closed
Marking FIXED based on comment # 2.
As a workaround you can try exporting the pool from GUI and then reimport it back using Auto Import, that should fix the ada8 entry