Hi all,
I am using a Raspberry PI 2 with FreeBSD 11.1 on it. There's an external 1TB disk hooked up via USB, on which I am trying to create a ZFS pool. However, every time I try to create a ZFS pool on this disk, it reboots the Pi.
What I have tried:
1) Creating a pool on the disk itself /dev/da0
2) Creating a pool on the first partition of the disk /dev/da0p1
3) Removing all partitions and repeating step 1
4) Adding a freebsd-zfs partition and repeating step 2
The disk isn't corrupted:
There is no known ZFS pool:
I can't get the disk online:
But I can't create a new pool unless I use the -f flag:
However, whenever I do that, the machine reboots again
I think my next attempt at solving this will be to hook the disk on to another machine, and try from there. But I still think this is really odd. Any help is appreciated.
I am using a Raspberry PI 2 with FreeBSD 11.1 on it. There's an external 1TB disk hooked up via USB, on which I am trying to create a ZFS pool. However, every time I try to create a ZFS pool on this disk, it reboots the Pi.
What I have tried:
1) Creating a pool on the disk itself /dev/da0
2) Creating a pool on the first partition of the disk /dev/da0p1
3) Removing all partitions and repeating step 1
4) Adding a freebsd-zfs partition and repeating step 2
The disk isn't corrupted:
Code:
[root@kn0x ~]# gpart show /dev/da0
=> 40 1953525088 da0 GPT (932G)
40 2008 - free - (1.0M)
2048 1953521664 1 freebsd-zfs (932G)
1953523712 1416 - free - (708K)
There is no known ZFS pool:
Code:
[root@kn0x ~]# zpool status
no pools available
I can't get the disk online:
Code:
[root@kn0x ~]# zpool online tank /dev/da0
cannot open 'tank': no such pool
[root@kn0x ~]# zpool online tank /dev/da0p1
cannot open 'tank': no such pool
But I can't create a new pool unless I use the -f flag:
Code:
[root@kn0x ~]# zpool create tank da0
invalid vdev specification
use '-f' to override the following errors:
/dev/da0 is part of potentially active pool 'tank'
However, whenever I do that, the machine reboots again
I think my next attempt at solving this will be to hook the disk on to another machine, and try from there. But I still think this is really odd. Any help is appreciated.