Title: zpool name change from default (Causes Errors post_install), Virtualized in VirtualBox 7.0 Debian-12.1.0-amd64 - FreeBSD 14.0-RELEASE-amd64 Guest O/S
Hey everyone!
My production server has been offline for over 1 year now due to unlawful Compromising. (Besides that _Fact_),
I am backing up everything this Month (This week, Possibly next however long it takes), Taking my time and Decided it would be wise to run an Alpha Test Run in VirtualBox 7.0 - Debian-12.1.0-amd64 (My BrickTop T420 Laptop) while I wait for backups to slowly offload over my Mobile Cell Phone Data (Long Story and not relevant to the question & answer I present to you today).
I mirrored my Host's Hard Drive Size in Virtual without Allocations "Now". For Dynamic Growth/Fill as to not maximize my Hard Drives Usage or Exceed what's available on my Host Debian 12.1.0-amd64 Linux Native O/S.
I chose the actual: 160GB
With my Previous Installation FreeBSD-12.1-RELEASE I left the "pool name" for zfs at default as "zroot".
I decided to change it as the Installer allows for this... (However it doesn't indicate any Best Practices, or any Cautions)... I chose the following Name:
Pool Name [zpool]: SuperNovaAlphaR2_zpool1
After I committed the changes and it restarted (Strangely without prompting me to create a root password & username); I also chose to Mirror Swap and Encrypt it; along with the zpool zfs non-raid striped Disk.
This is what happened on boot:
My questions are:
a) Why does FreeBSD-14.0-RELEASE0-amd64 have the ability to change the zpool name if doing so _can_ cause BootError's
... & Why not include indications of Naming Practices (if that's _truly_ root cause of my BootError's).
b) What do the Experts do regarding initial Installation of zpool Naming Conventions on Virtual or Production Servers?
Obliges to any Feedback, Suggestions/Shared Practices!
Best Regards,
Brandon Kastning
irc.libera.chat - KnowledgeShark
P.S. - Update Thread: Appended my Signature as It was excluded for some _unknown_factual_reason_to_me_
[Mod: Removed because it violated rule #3: Forum rules]
Hey everyone!
My production server has been offline for over 1 year now due to unlawful Compromising. (Besides that _Fact_),
I am backing up everything this Month (This week, Possibly next however long it takes), Taking my time and Decided it would be wise to run an Alpha Test Run in VirtualBox 7.0 - Debian-12.1.0-amd64 (My BrickTop T420 Laptop) while I wait for backups to slowly offload over my Mobile Cell Phone Data (Long Story and not relevant to the question & answer I present to you today).
I mirrored my Host's Hard Drive Size in Virtual without Allocations "Now". For Dynamic Growth/Fill as to not maximize my Hard Drives Usage or Exceed what's available on my Host Debian 12.1.0-amd64 Linux Native O/S.
I chose the actual: 160GB
With my Previous Installation FreeBSD-12.1-RELEASE I left the "pool name" for zfs at default as "zroot".
I decided to change it as the Installer allows for this... (However it doesn't indicate any Best Practices, or any Cautions)... I chose the following Name:
Pool Name [zpool]: SuperNovaAlphaR2_zpool1
After I committed the changes and it restarted (Strangely without prompting me to create a root password & username); I also chose to Mirror Swap and Encrypt it; along with the zpool zfs non-raid striped Disk.
This is what happened on boot:
Code:
(ada0:ata0:0:0:0): CAM status: Command timeout
(ada0:ata0:0:0:0): Retrying command, 3 more tries remain
ada0 at ata0 bus 0 scbus0 target 0 lun0
ada0: <VBOX HARDDISK 1.0> s/n VB[8-digit-redaction]-[8-digit-redaction] detached
GEOM_ELI: g_eli_write_done() failed (error=6) ada0p3.eli[WRITE(offset=3559800832, length=4096)]
GEOM_ELI: g_eli_read_done() failed (error=6) ada0p3.eli[READ(offset=270336, length=8192)]
GEOM_ELI: g_eli_read_done() failed (error=6) ada0p3.eli[READ(offset=169648332800, length=8192)]
GEOM_ELI: g_eli_read_done() failed (error=6) ada0p3.eli[READ(offset=169648594944, length=8192)]
GEOM_ELI: g_eli_read_done() failed (error=6) ada0p3.eli[WRITE(offset=4308537344, length=86016)]
GEOM_ELI: g_eli_read_done() failed (error=6) ada0p3.eli[WRITE(offset=3559804928, length=20480)]
Solaris: WARNING: Pool 'SuperNovaAlphaR2_zpool1' has encountered an uncorrectable I/O failed and has been suspended.
Mar 6 12:59:55 ZFS[1615]: vdev probe failure, zpool=SuperNovaAlphaR2_zpool1 path=/dev/ada0ps3.eli
Mar 6 12:59:56 ZFS[1851]: catastrophic pool I/O failure, zpool=SuperNovaAlphaR2_zpool1My questions are:
a) Why does FreeBSD-14.0-RELEASE0-amd64 have the ability to change the zpool name if doing so _can_ cause BootError's
... & Why not include indications of Naming Practices (if that's _truly_ root cause of my BootError's).b) What do the Experts do regarding initial Installation of zpool Naming Conventions on Virtual or Production Servers?
Obliges to any Feedback, Suggestions/Shared Practices!
Best Regards,
Brandon Kastning
irc.libera.chat - KnowledgeShark
P.S. - Update Thread: Appended my Signature as It was excluded for some _unknown_factual_reason_to_me_
[Mod: Removed because it violated rule #3: Forum rules]