Hi All
So this is what I got from the import command.
root@truenas[~]# zpool import
pool: AEWC DATA
id: 15761599832217586264
state: ONLINE
action: The pool can be imported using its name or numeric identifier.
config:
to avoid problems due to the space in the name, or I guess this should work with the numeric ID (haven’t imported that way before).
zpool import 15761599832217586264
Edit: just to clarify, do you see the pool in GUI right now? If so and importing via CLI doesn’t work, try to see if you can export the pool in the GUI.
root@truenas[~]# zpool import “AEWC DATA”
zpool import 15761599832217586264
cannot import ‘AEWC DATA’: I/O error
Recovery is possible, but will result in some data loss.
Returning the pool to its state as of Sat May 4 01:54:22 2024
should correct the problem. Approximately 9 seconds of data
must be discarded, irreversibly. Recovery can be attempted
by executing ‘zpool import -F AEWC DATA’. A scrub of the pool
is strongly recommended after recovery.
Looks like you’re going to need to use the F (force) switch and lose some data. Courtesy of an @dan earlier post, I quote "There are two “force” options to ‘zpool import’. -f will import the otherwise-healthy pool if it appears it was last in use on another system. -F (capital F) will attempt to roll back the last n transactions (where n is a constant whose value I don’t know) to try to bring the pool to a mountable state. You can combine -F with -n to do a “dry run” of the force import–it will tell you if it could import your pool that way, but won’t actually import it. That command would look like ‘zpool import -F -n AEWC DATA’. "
I typed the recovery option above - zpool import -F AEWC DATA - All i got was
root@truenas[~]# zpool import -F AEWC DATA
cannot import ‘AEWC’: no such pool available
So nothing seemed to be working. it seemed to be constantly looking for AEWC and not AEWC DATA. i tried using the ID number too, and that didn’t recognise.
Then…the pool suddenly appeared, it shows one drive faulted and has resilvered into one of the spare ones.
No idea what or how it worked, or if it was anything i did??
Only thing now is it isn’t showing folders in network as it isn’t recognising any password to access this?
Maybe I wasn’t clear with my post / I also don’t know the correct syntax on top of my head, you have spaces in your pool name. This will terminate the command at AEWC because there’s a space after it will not properly recognize AEWC DATA as the full name, hence I suggested using "AEWC DATA".
It told you by pouting out it didn’t find the pool named AEWC.
It seemed to have worked the post before and apparently (since the pool is there again) seems to have worked now, too. What message did lead you to thinking it didn’t work?
Out of curiosity, zpool status again please
Not my specialty, maybe the import command screwed up the mount point?
Can you ssh into the machine and do ls / you can then navigate to your pool, should be under /mnt/poolname and check for your files there. Remember the space in the name, use “”.
Then go to your SMB shares or whatever you were using and verify:
correct users have access / that’s the credentials you are trying to access it
the path is still correct
When the path is correct you may add a new user to the share, apply permissions recursively and see if you can get to your data.
Your next step should be to figure out a viable backup solution. Personally I’d advise to use your spare unit (if it isn’t too old by now, I haven’t checked the specs) or get another system and create a new NAS with less drives. Keep your current NAS as a backup.
I haven’t read your whole linked thread in the time obviously. Why is this necessary?
But it gave me an idea to a another explanation: maybe the system dataset got corrupted during tossing the last x seconds, and hence the file share is broken?
You may need to reconfigure the share as I pointed out earlier.
Hi Chuck
I tried all of the above, “aewc data” and it all showed the same response as above. When it tried the ID number it just didn’t recognise.
root@truenas[~]# zpool status
pool: AEWC DATA
state: DEGRADED
status: One or more devices are faulted in response to persistent errors.
Sufficient replicas exist for the pool to continue functioning in a
degraded state.
action: Replace the faulted device, or use ‘zpool clear’ to mark the device
repaired.
scan: resilvered 88.7M in 00:07:01 with 0 errors on Mon May 6 14:03:44 2024
config:
Follow @Stux advice first, as suspected (and according to @pmh input, the path is now probably different).
Already one eye closed here but I would double check that, at a glance it seems like you are already using all your spaces and would need to replace the faulted drive manually now, I do not think you have a spare left and neither is the pool healthy. This requires timely action on your side. Since you are using raidz3 you should have some time left but you’re also using a really wide system.
At least one of those was successful, your pool is imported again