Unable to import the storage pool on TrueNAS after cut power

[shy0511]

I had enabled SMB services, and during a file transfer, the speed dropped to 0. Subsequently, Windows Explorer became unresponsive, and after restarting Explorer, all computers are unable to connect to the NAS.

Upon power restoration, I can access the web UI, but the notification bar indicates 'importing storage,' with the progress bar stuck at 80%. Most functions are inaccessible.

Our studio's entire data is on the NAS. Is there any way to resolve this issue or export the storage pool files to another device?

 

[morganL]

I had enabled SMB services, and during a file transfer, the speed dropped to 0. Subsequently, Windows Explorer became unresponsive, and after restarting Explorer, all computers are unable to connect to the NAS.

Upon power restoration, I can access the web UI, but the notification bar indicates 'importing storage,' with the progress bar stuck at 80%. Most functions are inaccessible.

Our studio's entire data is on the NAS. Is there any way to resolve this issue or export the storage pool files to another device?

Please follow forum rules above.

We need a full description of hardware and software version and pool layout

 

[shy0511]

software version: TrueNAS-SCALE-22.02.4

hardware information:
CPU:

Architecture: x86_64
CPU op-mode(s): 32-bit, 64-bit
Byte Order: Little Endian
Address sizes: 39 bits physical, 48 bits virtual
CPU(s): 4
On-line CPU(s) list: 0-3
Thread(s) per core: 1
Core(s) per socket: 4
Socket(s): 1
NUMA node(s): 1
Vendor ID: GenuineIntel
CPU family: 6
Model: 156
Model name: Intel(R) Celeron(R) N5105 @ 2.00GHz
Stepping: 0
CPU MHz: 2800.464
CPU max MHz: 2900.0000
CPU min MHz: 800.0000
BogoMIPS: 3993.60
Virtualization: VT-x
L1d cache: 128 KiB
L1i cache: 128 KiB
L2 cache: 1.5 MiB
L3 cache: 4 MiB
NUMA node0 CPU(s): 0-3

Mother Board:

畅网 CWN/6005
Base Board Information
Manufacturer: MW
Product Name: MW-NVR-N5105
Version: Default string
Serial Number: Default string
Asset Tag: Default string

Memory:

Physical Memory Array
Location: System Board Or Motherboard
Use: System Memory
Error Correction Type: None
Maximum Capacity: 32 GB
Error Information Handle: Not Provided
Number Of Devices: 2

Handle 0x0047, DMI type 17, 100 bytes
Memory Device
Array Handle: 0x003A
Error Information Handle: Not Provided
Total Width: 64 bits
Data Width: 64 bits
Size: 8 GB
Form Factor: SODIMM
Set: None
Locator: Controller0-ChannelA
Bank Locator: BANK 0
Type: DDR4
Type Detail: Synchronous
Speed: 3200 MT/s
Manufacturer: Gloway International Co Ltd
Serial Number: D4320866
Asset Tag: 9876543210
Part Number: WAR4S3200D22081C
Rank: 1
Configured Memory Speed: 2933 MT/s
Minimum Voltage: 1.2 V
Maximum Voltage: 1.2 V
Configured Voltage: 1.2 V
Memory Technology: DRAM
Memory Operating Mode Capability: Volatile memory
Firmware Version: Not Specified
Module Manufacturer ID: Bank 9, Hex 0x13
Module Product ID: Unknown
Memory Subsystem Controller Manufacturer ID: Unknown
Memory Subsystem Controller Product ID: Unknown
Non-Volatile Size: None
Volatile Size: 8 GB
Cache Size: None
Logical Size: None

Handle 0x0048, DMI type 17, 100 bytes
Memory Device
Array Handle: 0x003A
Error Information Handle: Not Provided
Total Width: 64 bits
Data Width: 64 bits
Size: 8 GB
Form Factor: SODIMM
Set: None
Locator: Controller0-ChannelB
Bank Locator: BANK 1
Type: DDR4
Type Detail: Synchronous
Speed: 3200 MT/s
Manufacturer: Gloway International Co Ltd
Serial Number: D4320866
Asset Tag: 9876543210
Part Number: WAR4S3200D22081C
Rank: 1
Configured Memory Speed: 2933 MT/s
Minimum Voltage: 1.2 V
Maximum Voltage: 1.2 V
Configured Voltage: 1.2 V
Memory Technology: DRAM
Memory Operating Mode Capability: Volatile memory
Firmware Version: Not Specified
Module Manufacturer ID: Bank 9, Hex 0x13
Module Product ID: Unknown
Memory Subsystem Controller Manufacturer ID: Unknown
Memory Subsystem Controller Product ID: Unknown
Non-Volatile Size: None
Volatile Size: 8 GB
Cache Size: None
Logical Size: None

Disks:

ZHITAI PC005 Active 256GB for system,
WDC WD20EFAX-68B * 3 for default raid-z(just I remembered, because system cannot output any information with using zfs or zpool command)

Disk /dev/nvme0n1: 238.47 GiB, 256060514304 bytes, 500118192 sectors
Disk model: ZHITAI PC005 Active 256GB
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: 786C3817-A178-497D-AA09-3320F20ABC4B

Device Start End Sectors Size Type
/dev/nvme0n1p1 4096 6143 2048 1M BIOS boot
/dev/nvme0n1p2 6144 1054719 1048576 512M EFI System
/dev/nvme0n1p3 34609152 500118158 465509007 222G Solaris /usr & Apple ZFS
/dev/nvme0n1p4 1054720 34609151 33554432 16G Linux swap

Partition table entries are not in disk order.


Disk /dev/sda: 1.82 TiB, 2000398934016 bytes, 3907029168 sectors
Disk model: WDC WD20EFAX-68B
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: DBF19ABB-95F5-45F9-BAD7-1C1C2EFBEABC

Device Start End Sectors Size Type
/dev/sda1 128 4194304 4194177 2G Linux swap
/dev/sda2 4194432 3907029134 3902834703 1.8T Solaris /usr & Apple ZFS


Disk /dev/sdb: 1.82 TiB, 2000398934016 bytes, 3907029168 sectors
Disk model: WDC WD20EFAX-68B
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: 08724041-0E89-45A7-9788-674359DA54B3

Device Start End Sectors Size Type
/dev/sdb1 128 4194304 4194177 2G Linux swap
/dev/sdb2 4194432 3907029134 3902834703 1.8T Solaris /usr & Apple ZFS


Disk /dev/sdc: 1.82 TiB, 2000398934016 bytes, 3907029168 sectors
Disk model: WDC WD20EFAX-68B
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: EEAAFB97-A9CB-4FCF-9E4A-2B3E2C5FA956

Device Start End Sectors Size Type
/dev/sdc1 128 4194304 4194177 2G Linux swap
/dev/sdc2 4194432 3907029134 3902834703 1.8T Solaris /usr & Apple ZFS


Disk /dev/mapper/nvme0n1p4: 16 GiB, 17179869184 bytes, 33554432 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

 

[shy0511]

Please follow forum rules above.

We need a full description of hardware and software version and pool layout

Thanks for your reply, and apologize for my careless.
This is my first time to ask for help on froum, and Im not good at english.
I just post all information above I can get

 

[morganL]

Before importing the pool.. can you see the health of the disks and the HBA.

The symptoms sound like a hardware failure... HBA?

 

[HoneyBadger]

Hello @shy0511

You unfortunately have WD Red SMR (Shingled Magnetic Recording) drives (WD20EFAX) which do have known issues with ZFS. You may be experiencing problems with the drives re-shingling in the background, which can cause them to become unresponsive for long periods of time. Leaving the system powered-on in the BIOS screen (ie: not attempting further disk I/O) may give the drives sufficient time to perform their own housekeeping, and then we can attempt to import again - but note that this would only be a temporary fix. I recommend you seek out WD Red Plus or other "CMR" drives to use as replacements as soon as possible.

The symptoms sound like a hardware failure... HBA?

Most of these types of boards use a JMicron JMB585 SATA controller on a PCIe x1 link, so this could also be a bottleneck point for performance/rebuilds - it shouldn't necessarily prevent an import, but it may prove to be a problem for recovery.

 

[shy0511]

Before importing the pool.. can you see the health of the disks and the HBA.

The symptoms sound like a hardware failure... HBA?

There is nothing shows on dashboard and storage page, and i tried zpool and zfs, but no echo on screen

 

[shy0511]

Hello @shy0511

You unfortunately have WD Red SMR (Shingled Magnetic Recording) drives (WD20EFAX) which do have known issues with ZFS. You may be experiencing problems with the drives re-shingling in the background, which can cause them to become unresponsive for long periods of time. Leaving the system powered-on in the BIOS screen (ie: not attempting further disk I/O) may give the drives sufficient time to perform their own housekeeping, and then we can attempt to import again - but note that this would only be a temporary fix. I recommend you seek out WD Red Plus or other "CMR" drives to use as replacements as soon as possible.



Most of these types of boards use a JMicron JMB585 SATA controller on a PCIe x1 link, so this could also be a bottleneck point for performance/rebuilds - it shouldn't necessarily prevent an import, but it may prove to be a problem for recovery.

Thanks, i will try it and see if it works

 

[shy0511]

Hello @shy0511

You unfortunately have WD Red SMR (Shingled Magnetic Recording) drives (WD20EFAX) which do have known issues with ZFS. You may be experiencing problems with the drives re-shingling in the background, which can cause them to become unresponsive for long periods of time. Leaving the system powered-on in the BIOS screen (ie: not attempting further disk I/O) may give the drives sufficient time to perform their own housekeeping, and then we can attempt to import again - but note that this would only be a temporary fix. I recommend you seek out WD Red Plus or other "CMR" drives to use as replacements as soon as possible.



Most of these types of boards use a JMicron JMB585 SATA controller on a PCIe x1 link, so this could also be a bottleneck point for performance/rebuilds - it shouldn't necessarily prevent an import, but it may prove to be a problem for recovery.

It didn't work

 

[morganL]

It didn't work

How many days did you give it? ... ii can take over a week to recover.