Trying to recover files from an 8-year-old Freenas

georgeamp

Cadet
Joined
Jan 19, 2021
Messages
4
Hi guys, good to be here.

I've been trying to access my old Freenas setup that it had been sitting in a closet for about 8 years.
Unfortunately the files are way too important for me so I kept it as a treasure through the years.

Now, the situation is really tricky and I believe I'm walking on wafer thin ice.
I've tried many-many things but since I'm not an expert, I think I'm doing more damage
with each piece of code I enter, so I'd be really glad if somebody could help me.

Resilvering wasn't intended, I hope I didn't ruin everything.

Here it goes.

Code:
zpool import -f
   pool: FreeNAS
     id: 16638828376374347280
  state: DEGRADED
 status: One or more devices were being resilvered.
 action: The pool can be imported despite missing or damaged devices.  The
    fault tolerance of the pool may be compromised if imported.
 config:

    FreeNAS     DEGRADED
      raidz1-0  DEGRADED
        ada0p2  UNAVAIL
        sdb2    ONLINE
        sdd2    ONLINE
        sdc2    ONLINE


Code:
zpool import -d /dev
   pool: FreeNAS
     id: 16638828376374347280
  state: ONLINE
 status: One or more devices were being resilvered.
 action: The pool can be imported using its name or numeric identifier.
 config:

    FreeNAS     ONLINE
      raidz1-0  ONLINE
        sda2    ONLINE
        sdb2    ONLINE
        sdd2    ONLINE
        sdc2    ONLINE


Code:
zfs list
NAME                                                       USED  AVAIL     REFER  MOUNTPOINT
FreeNAS                                                   1,45T  1,11T     1,45T  /FreeNAS
FreeNAS/.system                                           1,23M  1,11T      209K  legacy
FreeNAS/.system/configs-e6cb7c26dd1243d3962c3f87f9eddfe5   209K  1,11T      209K  legacy
FreeNAS/.system/cores                                      209K  1,11T      209K  legacy
FreeNAS/.system/rrd-e6cb7c26dd1243d3962c3f87f9eddfe5       209K  1,11T      209K  legacy
FreeNAS/.system/samba4                                     209K  1,11T      209K  legacy
FreeNAS/.system/syslog-e6cb7c26dd1243d3962c3f87f9eddfe5    209K  1,11T      209K  legacy


Code:
zpool status -v
  pool: FreeNAS
 state: DEGRADED
status: One or more devices has experienced an error resulting in data
    corruption.  Applications may be affected.
action: Restore the file in question if possible.  Otherwise restore the
    entire pool from backup.
   see: http://zfsonlinux.org/msg/ZFS-8000-8A
  scan: resilvered 3,67M in 0 days 10:39:55 with 12 errors on Tue Jan 19 11:42:26 2021
config:

    NAME                      STATE     READ WRITE CKSUM
    FreeNAS                   DEGRADED     0     0     0
      raidz1-0                DEGRADED     0     0     0
        14090199790126997999  UNAVAIL      0     0     0  was /dev/ada0p2
        sdb2                  DEGRADED     0     0    24  too many errors
        sdd2                  DEGRADED     0     0    24  too many errors
        sdc2                  DEGRADED     0     0    24  too many errors

errors: Permanent errors have been detected in the following files:

        FreeNAS@auto-20121217.1000-1w:/CONCERTS/LED ZEPPELIN (1979) live at knebworth.avi
        FreeNAS@auto-20121217.1000-1w:/CONCERTS/LOU DONALDSON QUARTET (2004) live at new morning.avi
       


It's obvious though the files still exist. The problem is that I cannot access/mount the proper dataset(?).
Could be a case of a duplicate name or something?

Thanks for your time reading this. (:
 

sretalla

Powered by Neutrality
Moderator
Joined
Jan 1, 2016
Messages
9,700
It's obvious though the files still exist. The problem is that I cannot access/mount the proper dataset(?)

FreeNAS@auto-20121217.1000-1w:/CONCERTS/LED ZEPPELIN (1979) live at knebworth.avi
FreeNAS@auto-20121217.1000-1w:/CONCERTS/LOU DONALDSON QUARTET (2004) live at new morning.avi
Both of those impacted files are in the same snapshot: FreeNAS@auto-20121217.1000-1w

There's every chance that the real copy of them is OK and if you destroy the snapshot the problem could disappear and the resilver will complete or possibly find further issues (you should certainly look into it at some point in terms of the health of the remaining disks).
 

georgeamp

Cadet
Joined
Jan 19, 2021
Messages
4
these two files is the least of my worries, meaning that I don't mind saving them or not.

so, destroying the snapshot you think it'd help?
What about the rest snaps?

Code:
zfs list -t all -r
NAME                                                       USED  AVAIL     REFER  MOUNTPOINT
FreeNAS                                                   1,45T  1,11T     1,45T  /FreeNAS
FreeNAS@manual-20111119                                    140K      -      163K  -
FreeNAS@auto-20121217.1000-1w                                0B      -     1,45T  -
FreeNAS@auto-20121217.1100-1w                                0B      -     1,45T  -
FreeNAS@auto-20121217.1200-1w                                0B      -     1,45T  -
FreeNAS@auto-20121217.1300-1w                                0B      -     1,45T  -
FreeNAS@auto-20121217.1400-1w                                0B      -     1,45T  -
FreeNAS@auto-20121217.1500-1w                                0B      -     1,45T  -
FreeNAS@auto-20121217.1600-1w                                0B      -     1,45T  -
FreeNAS@auto-20121217.1700-1w                                0B      -     1,45T  -
FreeNAS@auto-20121217.1800-1w                                0B      -     1,45T  -
FreeNAS/.system                                           1,23M  1,11T      209K  legacy
FreeNAS/.system/configs-e6cb7c26dd1243d3962c3f87f9eddfe5   209K  1,11T      209K  legacy
FreeNAS/.system/cores                                      209K  1,11T      209K  legacy
FreeNAS/.system/rrd-e6cb7c26dd1243d3962c3f87f9eddfe5       209K  1,11T      209K  legacy
FreeNAS/.system/samba4                                     209K  1,11T      209K  legacy
FreeNAS/.system/syslog-e6cb7c26dd1243d3962c3f87f9eddfe5    209K  1,11T      209K  legacy


in terms of health sdb2, sdc2, sdd2 used to be okay yesterday.
Today for some reason they've been degraded.
sda2 is the problematic one since day1.
 

georgeamp

Cadet
Joined
Jan 19, 2021
Messages
4
okay i sorted it out, by accident but still...

first i made a new folder with mkdir /mnt/test
and then i mounted one of the snaps mount -t zfs FreeNAS@auto-20121217.1800-1w /mnt/test

thanks sretalla for pointing me to the right direction
Cheers
 

sretalla

Powered by Neutrality
Moderator
Joined
Jan 1, 2016
Messages
9,700
and then i mounted one of the snaps mount -t zfs FreeNAS@auto-20121217.1800-1w /mnt/test
To access snapshots it's usually better to get there via the active dataset path, so /mnt/FreeNAS/.zfs/snapshots/auto-20121217.1800-1w/

Although I would comment that the feature to mount them there perhaps wasn't effective when your pool was last mounted, so maybe not the case for you.
 
Top