Date: Thu, 30 Jan 2020 15:42:31 +0100 From: =?utf-8?Q?Peter_Rap=C4=8Dan?= <peter.rapcan@savba.sk> To: freebsd-hackers@freebsd.org Subject: How do I tell gptzfsboot NOT to analyze other disks (or specify which disks to analyze)? Message-ID: <EC3F4FDB-7186-4F24-9EC9-771ED239510D@savba.sk>
next in thread | raw e-mail | index | archive | help
Hi, Is there a way to tell gptzfsboot NOT to analyze other disks (or specify = which disks to analyze)? (My system is on PATA disk(s) while the data = disks are SATA, hence there is no use to probe the SATA disks to search = for a bootable system). I am asking this to get around the following problem (bug?) I = encountered (tried both freeBSD 12.1 and freeNAS [11.2-U4 though = 11.3-RC2]):=20 When booting, I get "gptzfsboot: error 128 lba some_block_number" errors = in the phase when gptzfsboot is probing my data HDDs (on which there is = no bootloader, nor system, the drives can be even empty, with or without = a partition table).=20 The system boots eventually but the boot takes cca N x 7 minutes, where = N is the number of data disks gptzfsboot is trying to analyze (there are = several gptzfsboot: error 128 lba some_block_number lines per disk and = each takes some time to appear). Note: installer CD boots the installer system just fine. Also, once the = system is installed, and the system has booted from HDD (this takes ~30 = minutes with multiple gptzfsboot: error 128 lba some_block_number for = each disk) the system works just fine, including the very same data = disks that "produce" the errors.=20 Anyway, should this be reported as a bug? Any help is greatly appreciated. Cheers, --Peter P.S.: When putting the drives in another PC, the behavior is the same, = only gptzfsboot: error 128 lba some_block_number becomes gptzfsboot: = error 32 [if I remember the number correctly] lba some_block_number.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?EC3F4FDB-7186-4F24-9EC9-771ED239510D>