Healthy ZFS Pool Causing SCALE (community) to Lockup System
Description
Problem/Justification
None
Impact
None
Attachments
4
Activity
Show:
Nate F March 3, 2025 at 1:12 AM
Here’s the current local console output prior to the lockup after being shutdown since I reported the bug.
Bonnie Follweiler February 24, 2025 at 6:58 PM
Good Afternoon .
I have moved this ticket into our queue to review now.
An engineering representative will update with any further questions or details in the near future.
Bug Clerk February 24, 2025 at 4:55 PM
Thank you for submitting this TrueNAS Bug Report! So that we can quickly investigate your issue, please attach a Debug file and any other information related to this issue through our secure and private upload service below. Debug files can be generated in the UI by navigating to System -> Advanced -> Save Debug.
https://ixsystems.atlassian.net/servicedesk/customer/portal/15/group/37/create/153
Pinned fields
Click on the next to a field label to start pinning.
Details
Details
Assignee
TrueNAS Backend TriageReporter
Nate FImpact
High
Components
Affects versions
Priority
LowMore fields
Time tracking
More fields
Time trackingKatalon Platform
Linked Test Cases, Katalon Defect Results, Katalon Studio Test Results
Katalon Platform
Linked Test Cases, Katalon Defect Results, Katalon Studio Test Results
Created February 24, 2025 at 4:55 PM
Updated March 3, 2025 at 1:12 AM
Unfortunately I do not have too much detailed information as the corruption happens after import and locks the kernel boot in a frozen state.
I was using 24.10.0.2 when this happened, at 2am the system rebooted and froze. I loaded the shell from install CD and am able to import the pool and check status and what not but when importing the config backup the system freezes when loading the kernel right after plugins. I tried ditching the config backup and importing via GUI which rebooted but never imported the pool and did not throw errors (can send whatever logs you need).
I then imported the pool via zpool CLI and after reboot it then causes the kernel to lock up during loading.
Bellow is the zpool info from CLI of install media - I do not know why I have to force import but that’s the only way it’ll import and be able to check the pool beyond that.
For now I’m not going to wipe the whole system and remake the pool as this may be a helpful bug for the system as a whole. Unfortunately this took out my storage node for storj so I don’t plan on bringing this server back as a node after I get it working again however route works.
Also not sure if related but on the install shell after importing the pool these log entries happen.