• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

ZFS issues

B

bluerain41

n00b
Joined
Sep 27, 2013
Messages
2
Greetings to you all,

I was referred here from a chatroom, as I have begun on a venture with ZFS (a file system recommended by me from my friend, and also few of my friends in IRC {#gentoo-chat}). I had roughly 1.4TB of storage saved on my ZFS based on my initial setup. My setup were as follows:

zpool create raidz1 backup sdb sdd sde
zpool destroy backup
zpool create raidz1 backup ata-Mobius_DISK_1_W300BG06 ata-Mobius_DISK_2_Z300JBFL ata-Mobius_DISK_3_W300E7Z9
zfs create backup/home/
zfs create backup/home/distantstar/

I have pretty much changed my mountpoint to /mnt/backup. Yesterday, my Gentoo drive has completely locked up. When I attempted to login, before Grub-legacy attempting to start, it returned this message (https://www.dropbox.com/s/stl9z88kw0ei9mq/IMG_20130926_201945.jpg) I assumed my MBR was overwritten somehow. Initially, after upon logging into my drive via chroot, I noticed my Gentoo drive has changed to GPT and partitions will be explained below:

1048MB boot ext2 zfs
2.0 TB
0 MB Free space

I have thought I lost my drive for good as my partitions were completely altered. Parted and fdisk both gave the same result, which caused me to accept the fate. Later on that day, I overwrote my Gentoo drive with fresh copy of Kubuntu. Installation was successful but attempting to load the drive has returned similar message as posted in Dropbox, making me think something is wrong with my MBR. But upon a bit of navigation into my own thoughts, I figured Ubuntu just wrote the MBR into my windows partitions instead of my Gentoo partition, as there were no area to choose the device in which you wish to store the MBR. What I thought was actually correct and (K)ubuntu loaded successfully once selected in Grub menu. I have immediate proceeded to install the ZFS software from PPA, as the ZFS they present in Aptitude were a version behind, and I was running their unstable version in Gentoo (it was unstable in Gentoo too, to be fair). Once loaded, I issued the commands:

sudo zpool import
no pools available to import
sudo zpool import backup
cannot import 'backup': no such pool available

I have come to blame my incompetence in not understanding how ZFS works and how it functions; however, I seek your expert attention in getting my backup devices back – if possible.
These are the Information necessary, perhaps for understanding what’s going on. Because I am at work at the moment, I’m taking a lazy way out. Once I am home, I will update this information. At the moment, I have Kubuntu on my drive and sudo zpool import shows no pools available.


http://www.biostar.com.tw/app/en/mb/introduction.php?S_ID=480
http://oyendigital.com/hard-drives/store/3R5-EB3-M.html


On a side note, gdisk has shown that there is ZFS file system and that GPT is somewhat readable, but the zpool table list (?) is gone. My dataset name should be backup. I could post the output of gdisk once I am at home. If you seek any additional information, please do not hesitate to ask. If I have done something stupid, - well, don’t hesitate to say them too; though I’d prefer judgements are kept to themselves.


Thank you very much
 
Please post the output of 'blkid' and 'lsblk'. Use CODE tags here to preserve indentation.
 
This is the output of blkid

Code: 
/dev/sda1: UUID="E0CCCFF5CCCFC44E" TYPE="ntfs" 
/dev/sda2: UUID="C4CCC1CFCCC1BC44" TYPE="ntfs" 
/dev/sdb1: UUID="d0bc4726-2776-41ee-9bda-c19c96506628" TYPE="ext4" 
/dev/sdb5: UUID="eb973506-8ad5-4089-83df-25356a27e0db" TYPE="swap" 
/dev/sdc1: LABEL="test" UUID="1520259099280226214" UUID_SUB="14679226576155955772" TYPE="zfs_member" 
/dev/sdd1: LABEL="test" UUID="1520259099280226214" UUID_SUB="9787624832041401075" TYPE="zfs_member" 
/dev/sde1: LABEL="test" UUID="1520259099280226214" UUID_SUB="9819075911817660190" TYPE="zfs_member"

And this is the output of lsblk

Code: 
NAME   MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
sda      8:0    0 232.9G  0 disk 
├─sda1   8:1    0   100M  0 part 
└─sda2   8:2    0 232.8G  0 part 
sdb      8:16   0   1.8T  0 disk 
├─sdb1   8:17   0   1.8T  0 part /
├─sdb2   8:18   0     1K  0 part 
└─sdb5   8:21   0    12G  0 part [SWAP]
sdc      8:32   0   3.7T  0 disk 
├─sdc1   8:33   0   3.7T  0 part 
└─sdc9   8:41   0     8M  0 part 
sdd      8:48   0   3.7T  0 disk 
├─sdd1   8:49   0   3.7T  0 part 
└─sdd9   8:57   0     8M  0 part 
sde      8:64   0   3.7T  0 disk 
├─sde1   8:65   0   3.7T  0 part 
└─sde9   8:73   0     8M  0 part

To give an explanation of why you see the LABEL test was because I have inadvertantly created the ZFS raidz1 as test, when backup was not found. I had removed the test dataset.

Also, when test dataset was created, the free space available were different in Gentoo and on Ubuntu: Gentoo gave 8TB free space, whereas Ubuntu gave more than 10TB; though I should actually have data in there in dataset "backup"
 
Please do not confuse the terms dataset and pool. 'test' is a pool, just like 'backup'. You created a new ZFS pool on the disks where the old pool was located? If that is the case I don't see how you can bring the old pool back.
 
What you did was similar to having a working partition, then quick formatting it with another partition.

when you zfs create to raw devices it will quick format the raw drives.

If you zfs create inside an existing zfs virtual device it simply creates a new filesystem (I guess you could say it's similar to a folder, except with lots of customization and power).

In theory you could possibly get some/most of data back by manually searching for remaining metadata but its extremely painstaking, and pretty much considered "master level" zfs http://www.joyent.com/blog/zfs-forensics-recovering-files-from-a-destroyed-zpool

At this point though most normal people would consider the data completely toasted and do a restore from backup.

though you could try the hail-mary command of:

zpool import -Df backup
 
Did you have partitions on your ZFS drives? If so, maybe those are missing or changed, so that your old ZFS metadata has been 'hidden' by the shift?

On each of your former drives, try this:
head -c10000000 /dev/sdb |strings | egrep "(vdev|guid|create|metaslab|backup)"

If some interesting stuff comes up, particularly with the name of your original pool in it, there should be a way to get it visible and maybe still import it.
 
You must log in or register to reply here.
Back
Top