Can not access my volume

[MrMacInCheese]

I am fairly new to this,
My dad unplugged the nas earlier today and we can no longer access the data that was stored on it. I was reading the log and I came across this http://pastebin.com/30GzmQFU
Everything was working fine until he unplugged it
He really needs this data
Again I'm new and kind of clueless so any help would be appreciated
Here is a screen shot of something that I think will help

 

[danb35]

From the CLI (shell button in the web GUI, or ideally via SSH), run the following commands and post the output here in code tags:

• zpool status
• zpool import
• camcontrol devlist

 

[MrMacInCheese]

From the CLI (shell button in the web GUI, or ideally via SSH), run the following commands and post the output here in code tags:

• zpool status
• zpool import
• camcontrol devlist

Code:

[root@freenas ~]# zpool status
pool: freenas-boot
state: ONLINE
scan: none requested
config:

NAME STATE READ WRITE CKSUM
freenas-boot ONLINE 0 0 0
da0p2 ONLINE 0 0 0

errors: No known data errors
[root@freenas ~]# zpool import
[root@freenas ~]# camcontrol devlist
<ST3000VN000-1HJ166 SC60> at scbus1 target 0 lun 0 (pass0,ada0)
<ST3000VN000-1HJ166 SC60> at scbus2 target 0 lun 0 (pass1,ada1)
<ST3000VN000-1HJ166 SC60> at scbus3 target 0 lun 0 (pass2,ada2)
<ST3000VN000-1HJ166 SC60> at scbus4 target 0 lun 0 (pass3,ada3)
<Corsair Voyager GO 000A> at scbus8 target 0 lun 0 (pass4,da0)
[root@freenas ~]#

Nothing showed up when I pasted zpool import

 

[danb35]

Frankly, that doesn't look good. What's the output of 'gpart show'?

 

[MrMacInCheese]

Code:

 
[root@freenas ~]# gpart show
=> 34 30282941 da0 GPT (14G)
34 1024 1 bios-boot (512k)
1058 6 - free - (3.0k)
1064 30280960 2 freebsd-zfs (14G)
30282024 951 - free - (475k)

[root@freenas ~]#

 

[Noctris]

Do you remember if this was a stripe, raid-Z, raid-Z2 ? mirrored stripe ?

Have you tried "zpool import -f Volume0"?

Could you post "zpool import -D"

and:

zpool import -d /dev/ada0
zpool import -d /dev/ada1
zpool import -d /dev/ada2
zpool import -d /dev/ada3

 

[danb35]

So your server is seeing four Seagate disks (ada0 - ada3), but doesn't have any indication that there's a pool on them, and doesn't show that any of them have a partition table. That looks bad. It also doesn't seem consistent with just having the plug pulled. I wouldn't be surprised to see some corrupted data, but to have the partition tables of all four disks completely trashed doesn't seem very plausible. Was there a particular reason he pulled the plug? Was something else going on at the time?

I don't know that it's especially relevant, but what's the rest of your hardware? I can see the CPU and RAM in your first post, but what motherboard are you using?

 

[MrMacInCheese]

I'm running four drives in RAID10

When I tried "zpool import -f Volume0" it said "cannot import 'Volume0': no such pool available"

Code:

 
[root@freenas ~]# zpool import -D
[root@freenas ~]# zpool import -d /dev/ada0
cannot open '/dev/ada0/': Not a directory
[root@freenas ~]# zpool import -d /dev/ada1
cannot open '/dev/ada1/': Not a directory
[root@freenas ~]# zpool import -d /dev/ada2
cannot open '/dev/ada2/': Not a directory
[root@freenas ~]# zpool import -d /dev/ada3

 

[MrMacInCheese]

There was a thunder storm going on dung the time he pulled the plug

Hardware:
CPU:Intel Xeon E3-1230V3
RAM:Crucial 16GB (2 x 8GB) 240-Pin DDR3 SDRAM ECC Unbuffered DDR3 1600
MOBO:SUPERMICRO MBD-X10SL7-F-O uATX Server Motherboard LGA 1150 Intel C222 DDR3 1600

 

[danb35]

How did you create the RAID10? Because FreeNAS itself doesn't, strictly speaking, do "RAID10", and if you used your motherboard's "RAID" controller, that's likely your problem. Did you change where you've plugged the drives into the motherboard?

 

[Noctris]

I agree with dan.. It's a bad sign none of the disks are showing any partition info..

could you post


gpart show ada0

and smartctl -A /dev/ada0


ps: dare i ask if there is a backup ?

 

[MrMacInCheese]

Here is "smartctl -A /dev/ada0"

Code:

[root@freenas ~]# smartctl -A /dev/ada0
smartctl 6.3 2014-07-26 r3976 [FreeBSD 9.3-RELEASE-p13 amd64] (local build)
Copyright (C) 2002-14, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF READ SMART DATA SECTION ===
SMART Attributes Data Structure revision number: 10
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
1 Raw_Read_Error_Rate 0x000f 112 100 006 Pre-fail Always - 44914816
3 Spin_Up_Time 0x0003 094 094 000 Pre-fail Always - 0
4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 9
5 Reallocated_Sector_Ct 0x0033 100 100 010 Pre-fail Always - 0
7 Seek_Error_Rate 0x000f 100 253 030 Pre-fail Always - 507399
9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 457
10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0
12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 9
184 End-to-End_Error 0x0032 100 100 099 Old_age Always - 0
187 Reported_Uncorrect 0x0032 100 100 000 Old_age Always - 0
188 Command_Timeout 0x0032 100 100 000 Old_age Always - 0
189 High_Fly_Writes 0x003a 100 100 000 Old_age Always - 0
190 Airflow_Temperature_Cel 0x0022 067 064 045 Old_age Always - 33 (Min/Max 31/33)
191 G-Sense_Error_Rate 0x0032 100 100 000 Old_age Always - 0
192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 7
193 Load_Cycle_Count 0x0032 100 100 000 Old_age Always - 27
194 Temperature_Celsius 0x0022 033 040 000 Old_age Always - 33 (0 20 0 0 0)
197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 0
198 Offline_Uncorrectable 0x0010 100 100 000 Old_age Offline - 0
199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 0

[root@freenas ~]#

And "gpart show ada0"

Code:

[root@freenas ~]# gpart show ada0
gpart: No such geom: ada0.

Sadly there is no backup we were talking about it but haven't gotten to it yet

 

[MrMacInCheese]

I created it in my motherboards "RAID" controller and I haven't changed where I've plugged the drives into the motherboard. I had and hopefully still have 500GB of data on the drives

 

[danb35]

OK. Using your motherboard's RAID controller was a Very Bad Thing (tm) for FreeNAS, and presuming you're able to recover the pool at all, I'd strongly encourage you to back up the data, destroy the pool, and recreate it through FreeNAS. But that said, it explains perfectly why FreeNAS isn't seeing a partition table, pool information, etc.--it wasn't previously seeing four individual disks; it was seeing a single disk presented by your motherboard's RAID controller. You'll need to get back into wherever in the BIOS you set up that RAID array, and try to recover it that way.

Unfortunately, I don't think I can help any further in that regard, as I'm not at all familiar with how those options work on your motherboard.

The good news is that your disk health looks fine.

 

[MrMacInCheese]

Okay, thank you for you help, I'll see what I can do

 

[Noctris]

It's strange that the raid controller "all of a sudden" presents the disks to freenas instead of the created raid volume.

You are sure you or your dad didn't change any settings or config after the power out ?

That being said: using the raid controller is indeed a bad idea ( freenas or rather ZFS IS the raid.. by using the onboard raid controller, you in fact took away zfs's abilities to fix stuff and keep the data safe).

Either way: what is done is done, just don't do it again.

I'm afraid i can't help you any further either...

You could try to 'import foreign config" ( this is dell lingo for checking the disks if the controller's previous configuration is still in there and read it back to the raid controller, i have no idea how this works on supermicro) but you have got to realize a couple of things:

All actions you do in that bios have a potential to destroy more then you could salvage.

BE VERY SURE BEFORE YOU PRESS SAVE AT ANY POINT

if this data is crucial, don't touch it and get a professional in there. if the raid controller messes up the volume on the disks even more changes of recovery will go to zero rapidly.

You might want to consider bringing in IX Systems ( creators of freenas) on this if you really need that data back ( sit down before asking a quote.. these kind of things don't come cheap)

If you should recover ( or start over) .. take a long browse through the forums. You have a nice setup and did everything right with the hardware only to cripple the setup by using the raid controller.

 

[MrMacInCheese]

I followed this build guid https://forums.freenas.org/index.php?threads/hardware-recommendations-read-this-first.23069/ and I saw nothing about not using on board RAID controls...oops
And this data is very important to my father because of his business

Also "import foreign config" produced

Code:

[root@freenas ~]# import foreign config
bash: import: command not found

 

[Darren Myers]

If you boot your server and go into the raid utility you used originally (bad idea as others have mentioned) does your raid array show there? Is it degraded or none existent? Or healthy?

 

[mjws00]

Basically, you will need to boot into the bios of the raid controller <CTRL-C> while posting. From there you can check the consistency of your raid array, and/or check for an existing array on the disks. It's just menu options. The manual for the 2308 lives here. If you look at your logs you will see reference to a /raid0 device... that's what you need to make the OS see.

Unfortunately the first thing most of us do when we buy this board, is wipe that software and install IT mode for tha 2308 which basically turns the 2308 into a pure HBA. So most of us can't even walk through the menus with you.

 

[Noctris]

I followed this build guid https://forums.freenas.org/index.php?threads/hardware-recommendations-read-this-first.23069/ and I saw nothing about not using on board RAID controls...oops
And this data is very important to my father because of his business

Also "import foreign config" produced

Code:

[root@freenas ~]# import foreign config
bash: import: command not found

Check the whole part about 'what not to do'... This clearly said any and all raid controllers or non-hba's

Sorry, i wasn't clear about the command. Import foreign config should indeed be something you see in the controller bios. Not freenas command line. Did you get a chance to check if it says anything? Also, you didn't quite answer the 'did you change anything' questions which makes me think you might have :s

I have yet to see a raid controller that dumps his raid and on it's own reverts from raid to jbod.

Please do realize what i posted before. The wrong kind of fiddeling wil make any chance of recovery zero.

Sent from my portable microwave