ZFS with HDDs in vdevs and outside of vdefs
Posted: 29 Aug 2016 17:43
Hello everybody!
I'm running nas4free for 2,5 years now.
Today I replaced mainboard, CPU, RAM and boot-device (I wasn't confident without ECC RAM for my ZFS.)
Formerly on a Athlon X2 with 4GB RAM, booting from a CF card on IDE everything ran fine.
It still does, now with a Core i3 4150 and 16GB ECC-DDR3 booting from USB pendrive.
The mainboard is a ASUS P9D-MV
All I had to do was re-configuring the network adapters and re-importing the drives.
Sooooo everything works.
I have 8 drives with 2TB each running RaidZ2.
The first 4 disks (ada0-ada3) are connected to a PCI-E SATA controller.
ada4 to ada7 are connected to the onboard intel controller (see below).
So much for my setup and all the history.
Now I checked everything after the upgrade and I notices the following:
My ZFS Pool runs as follows:
You may notice that ada0 has no ".nop".
Before changing everything, no drive had a ".nop".
Now I went into researching and I find the following:
ada0 is not part of the vdev like all the ".nop"-drives.
In fact, ada0 isn't part of any vdev as there's only one...
The vdev is configured as follows:
(I just cut out serial numbers and hd names...)
Soooo... I don't know if all disks have been part of the vdev before I replaced almost everything.
Anyhow: what might have happend?
And is there any way to get ada0 back into the vdev?
Or, if not, does it have any drawbacks if ada0 runs as "single"?
If I understood correctly, the raidz2 is built with the vdev, which would mean that a failure of ada0 would equal data loss.
ada4 has to be replaced (pending sector), which will happen tomorrow. The new drive will be a WD Red 4TB.
But that doesn't seem to have any effect...
Thank you very much in advance.
If you need any further information, please let me know.
Edit: I forgot to add the information which version of nas4free I'm running...
It's the current 10.3.0.3 - Pilingitam (Revision 2942)
I'm running nas4free for 2,5 years now.
Today I replaced mainboard, CPU, RAM and boot-device (I wasn't confident without ECC RAM for my ZFS.)
Formerly on a Athlon X2 with 4GB RAM, booting from a CF card on IDE everything ran fine.
It still does, now with a Core i3 4150 and 16GB ECC-DDR3 booting from USB pendrive.
The mainboard is a ASUS P9D-MV
All I had to do was re-configuring the network adapters and re-importing the drives.
Sooooo everything works.
I have 8 drives with 2TB each running RaidZ2.
The first 4 disks (ada0-ada3) are connected to a PCI-E SATA controller.
ada4 to ada7 are connected to the onboard intel controller (see below).
So much for my setup and all the history.
Now I checked everything after the upgrade and I notices the following:
My ZFS Pool runs as follows:
Code: Select all
pool: NASVolume
state: ONLINE
scan: none requested
config:
NAME STATE READ WRITE CKSUM
NASVolume ONLINE 0 0 0
raidz2-0 ONLINE 0 0 0
ada4.nop ONLINE 0 0 0
ada5.nop ONLINE 0 0 0
ada6.nop ONLINE 0 0 0
ada7.nop ONLINE 0 0 0
ada0 ONLINE 0 0 0
ada1.nop ONLINE 0 0 0
ada2.nop ONLINE 0 0 0
ada3.nop ONLINE 0 0 0
errors: No known data errorsBefore changing everything, no drive had a ".nop".
Now I went into researching and I find the following:
ada0 is not part of the vdev like all the ".nop"-drives.
In fact, ada0 isn't part of any vdev as there's only one...
The vdev is configured as follows:
Code: Select all
Geräteliste
Gerät Partition Modell Größe Controller
ada1 Gesamtes Laufwerk WDC WD20EURS-63S48Y0 1907730MB ahcich1 (Marvell 88SE9230 AHCI SATA controller)
ada2 Gesamtes Laufwerk WDC WD20EURS-63S48Y0 1907730MB ahcich2 (Marvell 88SE9230 AHCI SATA controller)
ada3 Gesamtes Laufwerk WDC WD20EURS-63S48Y0 1907730MB ahcich3 (Marvell 88SE9230 AHCI SATA controller)
ada4 Gesamtes Laufwerk WDC WD20EURS-63S48Y0 1907730MB ahcich6 (Intel Lynx Point AHCI SATA controller)
ada5 Gesamtes Laufwerk WDC WD20EURS-63S48Y0 1907730MB ahcich7 (Intel Lynx Point AHCI SATA controller)
ada6 Gesamtes Laufwerk WDC WD20EURS-63S48Y0 1907730MB ahcich8 (Intel Lynx Point AHCI SATA controller)
ada7 Gesamtes Laufwerk WDC WD20EURS-63S48Y0 1907730MB ahcich9 (Intel Lynx Point AHCI SATA controller) Soooo... I don't know if all disks have been part of the vdev before I replaced almost everything.
Anyhow: what might have happend?
And is there any way to get ada0 back into the vdev?
Or, if not, does it have any drawbacks if ada0 runs as "single"?
If I understood correctly, the raidz2 is built with the vdev, which would mean that a failure of ada0 would equal data loss.
ada4 has to be replaced (pending sector), which will happen tomorrow. The new drive will be a WD Red 4TB.
But that doesn't seem to have any effect...
Thank you very much in advance.
If you need any further information, please let me know.
Edit: I forgot to add the information which version of nas4free I'm running...
It's the current 10.3.0.3 - Pilingitam (Revision 2942)
