DVitoD
Explorer
- Joined
- Dec 13, 2014
- Messages
- 78
Well, this is a great way of discovering a lot of features :D
After discovering some other bugs yesterday (still need to post these, it concerns /dev/ada name switches, GUI hanging needing hard poweroff in the CLI, etc), I now face a most interesting feature :)p):
Sysinfo:
I'm lost at what to do now. Clearly, I can not do status -v if the pool itself doesn't even show up, which makes sense because the drive suddenly isn't detected anymore.
Is there anyway to fix this or should I nuke the box and start all over again?
Thank you in advance for help :D:)
After discovering some other bugs yesterday (still need to post these, it concerns /dev/ada name switches, GUI hanging needing hard poweroff in the CLI, etc), I now face a most interesting feature :)p):
- Install with one SSD for FreeNAS itself, and 1 WD Black 2TB drive. 1 pool/volume, called 'tankpool'.
- Ran that for a couple of days, then added 1 Hitachi 1TB and 2 WD Black 2TB's to it for a total now of 4 HDD's and 1 SSD. Did not change the pool, left the disks there for testing only.
- Now I know why these two WD's from .2. were lying isolated in the closet: they were defective. Smart emailed me nicely about this.
- Today I moved out these two defective ones, and put in 1 WD RE4 500 GB and another WD Black 2TB. These disks were 100% fine, because I took them out of my Synologies where they were as hot spares.
- Didn't change any cabling: the original disks from .1. stayed at the same cable.
- Boot. Log in in GUI: alert (also via email):
The volume tankpool (ZFS) state is UNKNOWN
- So the two new disks are recognized, 1 of the already existing disks is recognized, but the one and only disk that is relevant, the volume 'tankpool' from step 1, is suddenly gone.
- The GUI shows as is attached.
- SSH: some CLI commands:
- Code:
FreeBSD 9.3-RELEASE-p5 (FREENAS.amd64) #2 r275790+f84e770: Tue Dec 23 23:35:33 PST 2014 [root@freenas] ~# zpool status pool: freenas-boot state: ONLINE scan: none requested config: NAME STATE READ WRITE CKSUM freenas-boot ONLINE 0 0 0 ada0p2 ONLINE 0 0 0 errors: No known data errors [root@freenas] ~# zpool status tankpool cannot open 'tankpool': no such pool [root@freenas] ~# grep 'ada[0-9]' /var/run/dmesg.boot ada0 at ahcich0 bus 0 scbus0 target 0 lun 0 ada0: <M4-CT128M4SSD2 040H> ATA-9 SATA 3.x device ada0: Serial Number ada0: 600.000MB/s transfers (SATA 3.x, UDMA5, PIO 8192bytes) ada0: Command Queueing enabled ada0: 122104MB (250069680 512 byte sectors: 16H 63S/T 16383C) ada0: quirks=0x1<4K> ada0: Previously was known as ad4 ada1 at ahcich2 bus 0 scbus2 target 0 lun 0 ada1: <WDC WD5002ABYS-02B1B0 02.03B03> ATA-8 SATA 2.x device ada1: Serial Number ada1: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes) ada1: Command Queueing enabled ada1: 476940MB (976773168 512 byte sectors: 16H 63S/T 16383C) ada1: Previously was known as ad8 ada2 at ahcich3 bus 0 scbus3 target 0 lun 0 ada2: <WDC WD2002FAEX-007BA0 05.01D05> ATA-8 SATA 3.x device ada2: Serial Number ada2: 600.000MB/s transfers (SATA 3.x, UDMA6, PIO 8192bytes) ada2: Command Queueing enabled ada2: 1907729MB (3907029168 512 byte sectors: 16H 63S/T 16383C) ada2: Previously was known as ad10 ada3 at ahcich4 bus 0 scbus4 target 0 lun 0 ada3: <Hitachi HDS721010CLA332 JP4OA3MA> ATA-8 SATA 2.x device ada3: Serial Number ada3: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes) ada3: Command Queueing enabled ada3: 953869MB (1953525168 512 byte sectors: 16H 63S/T 16383C) ada3: Previously was known as ad12 [root@freenas] ~#
Sysinfo:
- FreeNAS-9.3-STABLE-201412240734
- 7618MB RAM
I'm lost at what to do now. Clearly, I can not do status -v if the pool itself doesn't even show up, which makes sense because the drive suddenly isn't detected anymore.
Is there anyway to fix this or should I nuke the box and start all over again?
Thank you in advance for help :D:)