Search results

I have installed on 6 disks choosing zfs raid 10. Isn't the boot partition installed on all disks?

1 more hint. Tried installing with only 6x600gb using zfs raid10. The server start in grub command line with the error Unknown device 1 Entering rescue mode Grub rescue>

If i have only the 2 os disk It boot. If i have the 2 os disk (in the First 2 bays) and the other 6 disk It doesn't boot

But if i remove all other disk It boot. Edit: i haven't find an order inside the controller. I can choose cd,USB, internal sata, hp smartarray, network boot

No. It Just not boot, it pass all the boot order until It reach the last option(network boot). Is like It is missing where to boot. But if i remove all the disk except for the 2 with the os it boot. I have no option on boot order. I have cd,USB, ecc and hp smartarray. But inside smartarray i...

Can you elaborate more? Doesn't Work because of hp card? because of 2 different pool? Or because of zfs? So If the problem is 2 different pool i can discard the 2 disk for the os and Just use the single pool with the bigger drive for install and vm Image. If the problem is zfs for boot i can...

I'm having a similar problem. HP440ar with 2 zpool 2disk mirror with proxmox + 6 disk zfs raid10. The server boot only if i remove the 6 disk raid10. Have someone had the same problem?

I've tried installing on the first 2 disk, everything is fine but when i reboot it doesn't boot. Legacy mode active, order bios is ok to boot first from HP 440ar, Hp400ar is in HBA. I've tried to install with only the 2 disk installed and it boot correctly, but if add the others disk it...

so, i'll go with 2 pool ZFS. Thanks

Hi, i need advice on the best setup for the hardware i have. HP DL360 Gen9 64GB Ram 2x300GB SAS 15K 6x600GB SAS 15K My plan is to use zfs on the 6x600 GB in Raid 10 for a total of 1.8TB usable and the 2x300GB for mirroring the proxmox installation. What's the best way? Install using zfs...

Sorry, missed your post above! Sector Sizes: 512 bytes logical, 4096 bytes physical Sector Sizes: 512 bytes logical, 4096 bytes physical NAME PROPERTY VALUE SOURCE rpool ashift 12 local NAME PROPERTY VALUE SO...

7.2K rpm. I found the "problem". setting my only vm with 2 gb ram, rebooting proxmox , shut down and restarted the vm several time (something like 30) and is blazing fast (5 second for shutdown and 10/15 for startup to windows password login prompt). Set the vm with 4 gb ram and rebooted...

Thanks for your feedback, the only reason i'm testing zfs is because of the ability to do a vm replica in a second node as a disaster recovery but without zfs is not possible( If i understood correct)

1. they are normal sata hp branded 1 TB disk, so 4k i think. 2. default setting from installer. so 12 3. compression lz4, volblock i don't know how to see it. anyway default setting. 4. ARC limited to 1 GB min and 2 GB max. arc summary...

here while is booting. #zpool iostat -v 5 #atop cpu is at 100% in atop. and 25% global from proxmox interface. it seem it is using only 1 core, i think this could be aggravate even more the problem of having only 8 gb of ram. EDIT: started!! 56min for booting. :(

Thanks for your answers, i'll give it a try with 16 GB of Ram and setting ARC max to 5 GB (4gb +1GB/Tb)

Hi @SomerHimson, i'm having the same problem, same amount of disk and ram. Has adding extra ram solved your problem? PS. the reboot is because you have to set arc min and arc max, the swappines and these setting on the swap partition zfs set primarycache=metadata rpool/swap zfs set...

The server is 1 months old, and before yesterday was running hyper v with 2 vms without problem using internal "hw" raid. Is an HP ML 10 not ML110. In bios i set sata to AHCI, enabled CSM in legacy only mode ( no uefi), am i missing some setting? I can try without ZFS in any case, probably 8 GB...

Really? Over 30 minutes to start a Just installed(so clean) Windows vm? It is insane...

i understand that a mirror of 2 drives is not the best setupm but i've shut down 1 vm (30 sec). Restarted and took exactly more than 30 min to boot a clean windows installation. I don't think this is normal.