First, I want to apologize. I meant to include the zpool status command as the best way you can verify all is well. I was intending to provide that command with a link to a google search of how to break it all down. Other websites can explain it better than I could. All I did in my first post was tell you to do your homework, and your thread was basically "I'm trying to do my homework and I'm stuck on this question". Not too useful.
I'm not sure what twed0 and twed1 is. Normally hard drives are adaX or daX. twedX is new to me. Not sure I've ever seen it in the forum either. (Are you using a hardware RAID??? See below for more discussion on this) /shrug
I'm not 100% sure of your share issue, but I can give you some advice that many people aren't aware of. In Windows, you can only use one user per server. When you provide credentials to any share on a given server, you are stuck with that user until you logout/reboot or run the net use * /delete. Note that this will delete all connections to all servers. The net use command will tell you what connections you will lose. You can also take my command and if you google it I'm sure you can figure out how to delete just the connections you want if deleting all connections to all servers isn't a good idea. If I'm not making sense, here's an example:
If I map //freenas/share1 and put in my username(cyberjock) and password and connect, then try to map //freenas/share2 Windows will automatically use my previous username "cyberjock". If "cyberjock" isn't supposed to have write permissions but you wanted to use the username "fred" it won't work. You'll have to delete the connection as I mentioned above....or use the workaround. If you map to the local IP(such as 192.168.1.10/share2) then you can input a username/password again. But, that's all you get. You can't map a 3rd user any other way unless you have more IPs to map.
Just an FYI that Linux doesn't have this limitation. So if you are very lost and know linux enough to do network mapping on linux you can make sure everything server-side is/isn't working and then try it on Windows. Just a little tip as I had some issues trying to get FreeNAS permissions right at first and I needed a way to rule out Windows as the cause of my grief(it was for my situation). To be honest, despite being a total noob in linux, if you read how to mount shares from the command line in linux, a VM of linux is really helpful as it seems to be a "go/no-go" versus Window's cryptic responses when stuff doesn't work. I was left scratching my head as to if the message was a local or remote issue where Linux makes things very obvious and has none of the Windows limitations.
If you know all of this, then I don't have any other recommendations to help you. :( Permissions are something that kick many people's butt here. A quick for search of this forum will find all the plights of past newbies that have been owned by it. Troubleshooting them over forums is fairly difficult because you have to compare user/group permissions to the file/folder and subdirectories as well as the users in the groups. It can suddenly be overwhelming to look at in a forum setting.
One other comment. ZFS technically doesn't have "RAID1". It has "mirrors" The difference is that RAID1 has only 2 copies where ZFSs mirrors could be 10 disks of mirrors. Generally here we call it mirrors or RAID1 as appropriate. Since you used "RAID1" I'm going to mention that ZFS shouldn't be mixed with hardware RAID. By "hardware RAID" I mean they should be unconfigured by your 3ware controller. If you are running them in JBOD mode then all is okay and you can ignore this warning(this is a common mistake and I'm trying to save you pain later if you have made this mistake). Also, if you are running the disk as individual RAIDs and then using ZFS to mirror them, that's also a bad idea. If you are running them on a hardware RAID with UFS, you are okay too. It's just that ZFS should never be mixed with hardware RAID at all. ZFS is intended to replace hardware RAID. Running both is like having 1 car with 2 drivers. You might or might not get to your destination, it might or might not be fast, and it might fail you at any time. You should also verify you can read SMART data from the disks as well as run SMART tests. If the serial numbers for your disk are not showing up in the GUI that can also be a bad sign.
Hope I'm more helpful this time. :)
