Likely some of them at the least. Not that you bothered to mention what the panics are. The txg the pool was rolled back to also may not have been the most consistent one. That's water under the bridge at this point though.
Ehr... Okay, next time I have a kernel panic, I will stop working, get into my car and drive
35 minutes to home and take a picture of the kernel panic from the screen. Big chance I will be to late, since it reboots automatically after
15 seconds. So please don't say that I didn't bother to mention it, it's kinda impossible to achieve this when I am at work and doing everything remotely. And furthermore; I was at that time more interested to get my most important stuff transfered to my computer (= priority number one)!!
I would try importing the pool read-only as this may possibly allow you to copy other things you couldn't before. You could also try setting the
failmode to
continue and see if that behaves any better. That seems familiar.
Since you didn't mention the correct command to do this, I am guessing it is the code below:
Code:
zpool import -f -R /mnt -o rdonly=on storage
You could use the old stick, but I would at the least detach the old pool to remove it from the db before creating a new one. For the plugins, reinstall everything first then copy the config files over with the jail shutdown or the plugins shutdown at least.
Okay, so if I am correct; bootup with the FreeNAS USBstick > detach pool from GUI (or shell) > create new pool.
In regards to the plugins, are the config.ini files all that I need?
Sidenote; If I would save my FreeNAS settings and a completely new / clean install of FreeNAS to this USB stick and import the settings / config file of FreeNAS, wouldn't this be better?
For the experimentation phase I would setup a 3 x disk raidz1 pool and a 3 x disk UFS raid3 pool. Then use rsync to backup the zpool to the UFS array.
Okay I think I understand what you mean. I guess (with my limited knowledge) I am going to test this with doing some big writes to the raidz1 pool right?
And I guess I would have to use "dd"-command for this, correct? I will be needing the correct command to do a big write on the raidz1 (or I could copy over some big files, if it's better).
SMART is hardly absolute. All the manufacturers made sure of that. I agree it does make it unlikely to physically be the disks though.
Ah okay... Well I guess doing the setup (experimental phase, as you described above) could be a good thing to (re)test everything hardware-related (including harddisks). And if something's wrong, I guess we shall see it.
HHawk, this has already been mentioned before, but I will repeat it: No form of RAID is a substitute for backups. ZFS being RAID-like. A real backup is also not physically connected to the same system. You don't have any data unless you have a second unrelated, independent copy of it.
Well I am not arguing this, but I never had this kind of dataloss before with any RAID-setup I have used over the past years. This even includes RAID 0 array with four 80 GB harddisk (yes, that's several years ago). Lucky? Most probably.
Anyways, I think it will become very expensive to get several more harddisks of sufficient size to backup my stuff on the NAS. On the other side, I have learned my lessons and I will backup the "most" important stuff differently; like burning pictures to DVD and similar.
Nobody answered your question.
The UPS service is designed to do just that! Because the improper shutdown is the problem when you go on the UPS, if you have setup the service, the server should shut itself down automatically without your intervention on a loss of power. Any OS that can't handle that simple function with a UPS isn't worth jack squat.
Thanks for the answer cyberjock. I already found an affordable solution for my UPS-needs: PowerWalker VI 1200
And should work with the "blazer_usb" driver. I only have to look into it, how to set it up correctly when I order it and receive it of course...