mhugelmann
Cadet
- Joined
- Mar 16, 2012
- Messages
- 8
Hi all,
First post here, but I have been using FreeNAS (and FreeBSD) for some time. I'm no n00b, but no expert either.
I have my FreeNAS box with a quad core AMD processor with 8GB RAM. The motherboard has 4 SATA ports, and additionally I have 2 PCI SATA cards each with 4 ports. I'm currently running 8.0.2-RELEASE and have not yet upgraded to 8.0.4. Up until last night I had 2 separate RAIDZ1 pools consisting of 4 drives. Pool1 has 4x WDEARS15 and Pool2 has 4x WDEARS20. Everything was working fine.
Last night, I decided to throw 4 500GB drives in to the server to make a 3rd RAIDZ1 pool. They were previously used on a Windows computer and formatted for NTFS. Upon powering up the server, I logged in to the shell via SSH and went ahead with creating the new volume. dmesg | grep ada showed that the new drives were ada8-ada11 (previous drives are ada0-ada7). I produced the pool with the following command: zpool create pool3 raidz ada8 ada9 ada10 ada11. The pool was successfully created and I verified with zpool status -v.
I then exported the zpool with zpool export pool3 so I could use the Auto Import tool in the WebGUI to be able to control the zpool from there. It listed no volumes to import.
I tried the normal Import option and it only listed ada8 and ada9 as available drives.
So, for sake of argument, I re-imported the pool via the cli and destroyed it. ada8 and ada9 were still the only drives listed in the Import screen. Then I tried to create the zpool from the GUI instead. It listed all 4 available volumes and I was able to create the pool. However, this is not the way I want to do it as the GUI slices the volume for the SWAP space (I want to use the whole device).
From there, I proceeded to destroy the pool I created from the GUI, and went ahead with the cli way again to see if it would make a difference. Same problem, I export it, but the GUI doesn't see any importable pools. For sake of thoroughness, I ran zpool import via the cli and it did, in fact, list the volume I had previously exported.
This made me think that some how it had to do with the system (or specifically the GUI) not being able to handle ada channels greater than 9. Is this a possible bug, or is my logic way off?
For the record, I have used the same method on the 2 previous pools I created on the server and didn't have any issue with the Auto Import tool.
Any help with the matter would be greatly appreciated as I don't know how else to force the GUI to recognize the new pool. Are there any other settings or options I should be looking at that could be the culprit behind the problem?
Thanks :)
First post here, but I have been using FreeNAS (and FreeBSD) for some time. I'm no n00b, but no expert either.
I have my FreeNAS box with a quad core AMD processor with 8GB RAM. The motherboard has 4 SATA ports, and additionally I have 2 PCI SATA cards each with 4 ports. I'm currently running 8.0.2-RELEASE and have not yet upgraded to 8.0.4. Up until last night I had 2 separate RAIDZ1 pools consisting of 4 drives. Pool1 has 4x WDEARS15 and Pool2 has 4x WDEARS20. Everything was working fine.
Last night, I decided to throw 4 500GB drives in to the server to make a 3rd RAIDZ1 pool. They were previously used on a Windows computer and formatted for NTFS. Upon powering up the server, I logged in to the shell via SSH and went ahead with creating the new volume. dmesg | grep ada showed that the new drives were ada8-ada11 (previous drives are ada0-ada7). I produced the pool with the following command: zpool create pool3 raidz ada8 ada9 ada10 ada11. The pool was successfully created and I verified with zpool status -v.
I then exported the zpool with zpool export pool3 so I could use the Auto Import tool in the WebGUI to be able to control the zpool from there. It listed no volumes to import.
I tried the normal Import option and it only listed ada8 and ada9 as available drives.
So, for sake of argument, I re-imported the pool via the cli and destroyed it. ada8 and ada9 were still the only drives listed in the Import screen. Then I tried to create the zpool from the GUI instead. It listed all 4 available volumes and I was able to create the pool. However, this is not the way I want to do it as the GUI slices the volume for the SWAP space (I want to use the whole device).
From there, I proceeded to destroy the pool I created from the GUI, and went ahead with the cli way again to see if it would make a difference. Same problem, I export it, but the GUI doesn't see any importable pools. For sake of thoroughness, I ran zpool import via the cli and it did, in fact, list the volume I had previously exported.
This made me think that some how it had to do with the system (or specifically the GUI) not being able to handle ada channels greater than 9. Is this a possible bug, or is my logic way off?
For the record, I have used the same method on the 2 previous pools I created on the server and didn't have any issue with the Auto Import tool.
Any help with the matter would be greatly appreciated as I don't know how else to force the GUI to recognize the new pool. Are there any other settings or options I should be looking at that could be the culprit behind the problem?
Thanks :)