Zfs error

Roberto924

New Member
May 23, 2019
5
0
1
34
Hi friends, i have a dell poweredge r540 server with 2 disks 1tb ssd and a 2tb dell hard drive hot plug disk
The ssd disk has proxmox and 2 vm created(centos and freenas)
The second hd 2tb was a zfs volume
Asociated to freenas storage.
My boss hot unplugged the 2nd disk and plugged a few seconds later.
The problem it’s the freenas doesn’t start anymore after this, says: zfs error couldn’t find the pool, and when i go to see the disk proxmox says: could’t initiate the disk. I can’t see de disk to add it Again. I have rebooted and turned of the server and the disk doesn’t appears
Please help.
 

Roberto924

New Member
May 23, 2019
5
0
1
34
root@POSEIDON:~# zpool status -v
pool: rpool
state: ONLINE
scan: scrub repaired 0B in 0h0m with 0 errors on Sun May 12 00:24:38 2019
config:
NAME STATE READ WRITE CKSUM
rpool ONLINE 0 0 0
sda3 ONLINE 0 0 0
errors: No known data errors
 

Roberto924

New Member
May 23, 2019
5
0
1
34
Code:
root@POSEIDON:~# zpool import
   pool: freenas-boot
     id: 11378699045471226230
  state: ONLINE
 status: Some supported features are not enabled on the pool.
 action: The pool can be imported using its name or numeric identifier, though
        some features will not be available without an explicit 'zpool upgrade'.
 config:

        freenas-boot  ONLINE
          zd48        ONLINE
 

Roberto924

New Member
May 23, 2019
5
0
1
34
thanks Lnxbil for the reply.
now i have deleted the zfs of the 2nd disk from datacenter/storage, and detach the drive from the VM/Hardware, now the Vm starts but has no OS.
i'm very confused, i don't understand why this happend. i don't know if the problem was unplugg the disk in hot. it's there any procedure to hot swap the disks?
 

Roberto924

New Member
May 23, 2019
5
0
1
34
i can't see the disk

Code:
root@POSEIDON:~# fdisk -l
Disk /dev/sda: 931 GiB, 999653638144 bytes, 1952448512 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 318F08C5-0A9E-43C9-84F7-5035C8519E35

Device       Start        End    Sectors   Size Type
/dev/sda1       34       2047       2014  1007K BIOS boot
/dev/sda2     2048    1050623    1048576   512M EFI System
/dev/sda3  1050624 1952448478 1951397855 930.5G Solaris /usr & Apple ZFS


Disk /dev/zd0: 100 GiB, 107374182400 bytes, 209715200 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 8192 bytes
I/O size (minimum/optimal): 8192 bytes / 8192 bytes
Disklabel type: dos
Disk identifier: 0x000bc7f9

Device     Boot   Start       End   Sectors Size Id Type
/dev/zd0p1 *       2048   2099199   2097152   1G 83 Linux
/dev/zd0p2      2099200 209715199 207616000  99G 8e Linux LVM


Disk /dev/zd32: 6.5 GiB, 7008681984 bytes, 13688832 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 8192 bytes
I/O size (minimum/optimal): 8192 bytes / 8192 bytes


Disk /dev/zd48: 15 GiB, 16106127360 bytes, 31457280 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 8192 bytes
I/O size (minimum/optimal): 8192 bytes / 8192 bytes
Disklabel type: gpt
Disk identifier: 0357D015-6DED-11E9-85ED-298A86C42B77

Device      Start      End  Sectors  Size Type
/dev/zd48p1    40     1063     1024  512K FreeBSD boot
/dev/zd48p2  1064 31425575 31424512   15G FreeBSD ZFS

Partition 1 does not start on physical sector boundary.
Partition 2 does not start on physical sector boundary.
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE and Proxmox Mail Gateway. We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get your own in 60 seconds.

Buy now!