FreeNAS increaing storage problem:

nbat58

Limp Gawd
Joined
Oct 12, 2009
Messages
170
I hope someone can help me recover my data on FreeNAS, I am very scared in loosing 3+tb worth of data, this is set up:

FreeNAS 0.7.4919 AMD64 full install
Abit AN8 SLI motherboard
AMD Opteron 165 dual core processor
2gb DDR2 Ram
HP SC44GE SAS Controller
PCI Graphics

I had 4 x 1.5tb Samsung F2 drives installed with approx 3+tb of media, I have installed the HP PCIE SC44GE SAS Controller and added 4 x 2tb Samsung F3 HDD's without any issues, I could see my drives on the FreeNAS GUI and proceeded with the following:

Disks|Management|Disk|Add
Added disk1, disk2, disk3, and disk4 Filesystem= 'ZFS storage pool device' and Status= 'ONLINE'.
('Add' & 'Apply changes')

Disks|ZFS|Pools|Virtual device|Add
Created one virtual device, name: 'Storage 2', type: 'Single-parity, RAID-5', all four devices selected, Description: 'vdev'
('Add' & 'Apply changes')

Disks|ZFS|Pools|Management|Add
Name: 'NAS1', Virtual devices: 'Storage 2 (raidz1, vdev)'.
'Root', 'Mount point' and 'Description' I left empty
('Add' & 'Apply changes')
Afterwards I can see: NAS1 - Health= ONLINE

I have not created any dataset.

I can see the new 2tb drives which are Health = online My problem now is that my old pool with the 4 x 1.5tb is showing as Health = unknown, have I trashed all my data or can I bring this pool back to online.

Many thanks for all your help.
 
Last edited:
Could you access FreeNAS via SSH (download Putty to connect via SSH) and show me the output of:

zpool status
 
Could you access FreeNAS via SSH (download Putty to connect via SSH) and show me the output of:

zpool status

I am not getting anything in the prompt box in puTTY, I am not sure whether it's a windows 7 incompatibility or I have not set puTTY correctly.

I can access FreeNAS via the web gui though, can I see if my drives have still got the data on somehow?
 
You need to enable SSH access to FreeNAS in the Web-GUI, then you use PuTTY to connect to FreeNAS via SSH.

You should then see a login prompt, after you've logged in you have shell access. Before you can login you need a username and password, this is how you create those via the Web-GUI:
http://www.howtoforge.com/network_attached_storage_with_freenas_p8

Be sure to tick 'give full shell to user', then try connecting with PuTTY to FreeNAS by entering its IP address and try to connect.
 
You need to enable SSH access to FreeNAS in the Web-GUI, then you use PuTTY to connect to FreeNAS via SSH.

You should then see a login prompt, after you've logged in you have shell access. Before you can login you need a username and password, this is how you create those via the Web-GUI:
http://www.howtoforge.com/network_attached_storage_with_freenas_p8

Be sure to tick 'give full shell to user', then try connecting with PuTTY to FreeNAS by entering its IP address and try to connect.

Humm, still can't access the freenas server, a question, if I delete the pool and re-anable it will this delete my data if it's still there that is?
 
Do not delete anything! You'll only make things worse.

What exactly doesn't work with connecting via SSH?

1. Setup a new user on FreeNAS with username and password and SSH enabled
2. Download and run PuTTY on your Windows system
3. Insert IP address of the FreeNAS system in the white address box
4. click connect, it should say "Login: " and there you type the username, hit enter
5. Now it asks for password, enter that and hit enter.
6. Now you should be logged in and able to enter "zpool status" and send me the output.

Does that work?
 
I am able to enter the user @ the prompt but I can't type anything when the password prompt appears.
 
The password will not be shown on the screen as it's entered. Just type it in and press enter.

Dustin
 
The password will not be shown on the screen as it's entered. Just type it in and press enter.

Dustin

Many thanks, once I type the password in the prompt box dissapears but not terminal box opens, do I need to do anything else after typing the ip address or maybe something I need to set up to get the terminal to show up?

Any idea, many thanks for all the help guys really appreciate it.
 
Here's a simpler method:

In the Web-GUI, hover the menu Advanced and click Command. Now enter "zpool" as command and hit enter. Copy/paste the output here.

A lot easier. :)
 
Here's a simpler method:

In the Web-GUI, hover the menu Advanced and click Command. Now enter "zpool" as command and hit enter. Copy/paste the output here.

A lot easier. :)

Thanks sub.mesa definitely a lot easier, the output looks pretty scary though, this is what I got back after that command:

$ zpool

Not a lot I am afraid, I hope this does not mean all data is lost :(:eek:
 
This is what I got back:

$ zpool status
no pools available

I can still see the virtual device under Disks|ZFS|Pools|Virtual device, does this mean that I can still add the pool and maybe retreive the data that way?
 
Please don't do anything until we got this sorted out - any action you trigger with the Web-GUI may only make things worse. I'm not sure what happened yet so a solution would have to wait until then.

Could you send me the output of the following commands (execute each line separately):

kldstat

ls -l /dev/sd*

ls -l /dev/ad*

ls -l /dev/da*

dmesg | grep -i ZFS

zpool import


Please note that ls -l is LS -L but with lower case, so not an upper case i.
 
Could you also send me a screenshot of what you see in the Web-GUI under Virtual Device? Are you sure you are using ZFS?
 
Please don't do anything until we got this sorted out - any action you trigger with the Web-GUI may only make things worse. I'm not sure what happened yet so a solution would have to wait until then.

Could you send me the output of the following commands (execute each line separately):

kldstat

ls -l /dev/sd*

ls -l /dev/ad*

ls -l /dev/da*

dmesg | grep -i ZFS

zpool import


Please note that ls -l is LS -L but with lower case, so not an upper case i.

I have sent you the output via pm, let me know if you would like me to post them on here if you have not received them.

Thanks for all your help man.
 
Alright thanks for the PM.

One more thing, could you also send the output of "mount" ?

You can post it here, unless you feel it is confidential or privacy sensitive.
 
here it is:

Code:
$ mount
/dev/ad0s1a on / (ufs, local, soft-updates)
devfs on /dev (devfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)
procfs on /proc (procfs, local)

Many thanks
 
Not a trace of ZFS or any other mounted filesystems.

Could you say again exactly what you did, and show me screenshots of your GUI where you still see something? Try to avoid triggering any 'scripts' that actually change things; just view the information.

If you're actually using UFS the output you gave me would make sense. Though i can't see any trace of software RAID (RAID0/1/5) either. This is weird! Thread carefully.
 
I can see all 8 drives online and also I can see two virtual devices, the problem is when I first added my second pool, I have named it the same as the first pool the one with data on it, after doing that the second pool was showing with exactly the same information as the first pool, ie capacity of pool, storage space etc...

So I went and deleted the new pool which I last added (with the new drives) and now my old pool (with the data on) is showing as unknown.

Should the new pool be named the same as the first or doesn't it matter?

Many thanks for all your help.

Screen shots:

http://img33.imageshack.us/g/hddscreenie.jpg/


The FreeNAS system page show that there are no disks configured.
 
sub.mesa,

Would a 'zdb -l' against the original drives be of any use in determining the state of zfs on those drives?
 
sub.mesa,

Would a 'zdb -l' against the original drives be of any use in determining the state of zfs on those drives?

I might try that later, I have been trying to find out how to add vdevs to an existing pool and there isn't much out there in terms of tutorials, it looks like maybe this is not possible via the web gui at all and need to use the command to do this.

I wonder if this wil work to try and recover the destroyed pool if indeed it has been destroyed:

zpool import -D

An example output for the above command:

# zpool destroy tank
# zpool import -D
pool: tank
id: 3778921145927357706
state: ONLINE (DESTROYED)
action: The pool can be imported using its name or numeric identifier. The
pool was destroyed, but can be imported using the '-Df' flags.
config:

tank ONLINE
mirror ONLINE
c1t0d0 ONLINE
c1t1d0 ONLINE

Then I could try recovering as this example:

# zpool import -D tank
# zpool status tank
pool: tank
state: ONLINE
scrub: none requested
config:

NAME STATE READ WRITE CKSUM
tank ONLINE 0 0 0
mirror ONLINE 0 0 0
c1t0d0 ONLINE 0 0 0
c1t1d0 ONLINE 0 0 0

errors: No known data errors

Of course I won't try any of the above until 100% sure that I am not going to make matters worse.
 
I'm just mystified the GUI shows the array but a simple zpool status yields nothing; also mount does not show any mounted zfs devices.

zpool import -D would not actually perform any import; just show any deleted pools that can be imported. It's worth a try, and yes doing a:

zdb -l /dev/da0s1

should reveal alot of information.
 
this is all I get with the first command:

$ zdb -l /dev/da0s1

This is what I get with the zpool import -D:

$ zpool import -D
pool: NAS
id: 2931973748826094776
state: ONLINE (DESTROYED)
action: The pool can be imported using its name or numeric identifier.
config:

NAS ONLINE
raidz1 ONLINE
da0 ONLINE
da1 ONLINE
da2 ONLINE
da3 ONLINE

pool: NAS
id: 3130679617404216863
state: ONLINE (DESTROYED)
action: The pool can be imported using its name or numeric identifier.
config:

NAS ONLINE
raidz1 ONLINE
ad4 ONLINE
ad6 ONLINE
ad8 ONLINE
ad10 ONLINE

Hopefully I will be able to do something with that seing it is showing the destroyed pool, I think one of the NAS pools is when I had created the second one with my new drives and named it the same, the question is which is the right one?

Edit:

The First NAS pool is definitly the last pool I created seeing the HDD names start with da.
Should I go for it and import the Second NAS pool?

Edit:

Just tried: zpool import -D 3130679617404216863

and got nothing apart from: $ zpool import -D 3130679617404216863
 
Last edited:
Hummm...really weird, this is what i get:

$ zpool status
no pools available

Could it be you are not doing them as root?

I remember freenas requires zfs and zpool cmds to be run as root right?
 
Bah; let's try working on the SSH shell instead; perhaps this shell just doesn't work right.

Create a user in the Web-GUI with a password, then login with that username/password using PuTTY. That should work; it works with FreeNAS in my VM (Virtualbox).
 
Bah; let's try working on the SSH shell instead; perhaps this shell just doesn't work right.

Create a user in the Web-GUI with a password, then login with that username/password using PuTTY. That should work; it works with FreeNAS in my VM (Virtualbox).
Yes and then do

su -

to access root, right?

Too many problems with FreeNAS and zfs when problems cropped up made me go to osol for zfs needs.
 
Using puTTY does not give me a terminal box after entering the password, the prompt box just disapears.
 
Does it ask you multiple times for the password? That would mean it is rejected. Did you create the user in the Web-GUI?

I'll try this soon with a fresh FreeNAS.
 
Where do you enter the password?

After you open Putty and type in the hostname (or ip address) and press open, a console window should open up asking for login username (and then login password)
 
Does it ask you multiple times for the password? That would mean it is rejected. Did you create the user in the Web-GUI?

I'll try this soon with a fresh FreeNAS.

I only enter the password once, yes I have created a user with password and enabled SSH in freenas.

Many thanks for all your help guys, I wonder whether I should also migrate to osol like vraa when hopefully this is sorted or upgrade to FreeNAS 0.7.1 5xxx.

I suppose I can make those decision afterwards, better taking little steps at a time.
 
Where do you enter the password?

After you open Putty and type in the hostname (or ip address) and press open, a console window should open up asking for login username (and then login password)

That's right after I enter the username, I then enter the password in the console, this closes the console without anything else happening.
 
Can you take a screenshot of your putty configuration screen?

You have selected connection type SSH right? Port 22?
 
Thanks

Change close window to NEVER
Although that won't fix your problem, it may give us a hint as to what is going on.
 
Back
Top