electricd7
Explorer
- Joined
- Jul 16, 2012
- Messages
- 81
I'll give it a shot. The only problem is that the original pool only shows "replace" for da3 since I already off lined it. I don't know how to replace it with itself as it errors If I try that?
I'll give it a shot. The only problem is that the original pool only shows "replace" for da3 since I already off lined it. I don't know how to replace it with itself as it errors If I try that?
can you elaborate?zpool clear..... inconsistent state...
zpool online pool1 9217263701387507910 gptid/01754a95-9202-11e4-9761-002590760c9d
Technically, you could have kept the original da3 drive, unless it is under warranty and then you could RMA it then.OK, so after having disks connected to local motherboard for 12+ hours I replaced the M1015 HBA with a SuperMicro AOC-S2308L-L8e HBA. I have the new disk installed in place of the failing da3 and am re-silvering. I will keep you posted, but think maybe the issue was with the M1015 after all.
That is a little bit unusual in my experience. Hard drive problems should not be causing crashes that leave no traces... Please remember that the operating system is not being run from the hard drives, although it writes to them and in theory it needs to read some state files from .system. I think it only writes to .system and has these files in memory. FreeNAS might panic while being unable to handle problems with either reading or writing to hard drives, but it should report about it to the console...So just to close the loop. The problem with my FreeNAS system turned out to be disks. I thought it was controller, but after moving to the motherboard, I still couldn't get more than 12 hours or so of uptime. I then unplugged one of my disks that was still getting SMART errors and was able to get a couple of runs of 12+ hours, but not consistent. Finally I backed up all the data, replaced all 6 disks, created a new pool and copied the data back. I am on 48 hours of uptime at this point which I haven't seen since late November. Thanks all for your help!
That is very true, that is why I keep .system in a zpool that has its disks and controller different from my data pool. I have just entirely forgotten about that :)Cyberjock has previously implied that FreeNAS isn't very resilient against a missing .system dataset, since it's assumed to be on a redundant ZFS pool. The rationale being that the point where that happens is at or beyond that of data loss.
That is very true, that is why I keep .system in a zpool that has its disks and controller different from my data pool. I have just entirely forgotten about that :)
A troubleshooting lesson learned could be to insert a USB memory device (another one beyond the OS one) and migrate .system onto it. That as soon as possible move .system out of equation. And thus possibly enabling preservation of log files, if the problems are related to either a SATA/SAS controller or disks.
I am reformulating the question in such a way:I do not use 9.3 yet, but since 9.2.1.6 using GUI to move .system to another zpool (by pointing to the new location) just worked.
GUI → System → Settings → System Dataset → System dataset pool → Save :)
There should be no risk to data (unless someone manually placed data inside .system and other unusual scenarios), however a reboot is required to complete the process.
My original comment was about having .system on a USB device only temporarily, while troubleshooting any disks and/or controller issues.I am reformulating the question in such a way:
What makes the pool containing the .system folder more reliable than the data pool? If the pool containing the .system folder crashes, then does it mean Freenas will panic and reboot or is it going to use a copy in RAM if any or other means? I would think on a RAIDZ2 it should be safer than a single drive hosting .system.