January 31Jan 31 I need some help with adding an existing pool to Unraid.This pool comes from another Unraid server and was encrypted by Unraid itself. The password is the same as the one used for my other pools.I have already done a few test runs. Sometimes the pool could be added, but after a reboot I always had to manually import the pool again. In addition, the Unraid dashboard keeps showing “Format disk” on the front page, which feels quite risky.Now I would like to perform the migration properly for real.Both pools are currently named mainstorage. Is it possible to rename one of the pools and then safely import it into Unraid? https://prnt.sc/r1AeXY9hr2Gz Edited February 9Feb 9 by beantje
January 31Jan 31 Community Expert You should be able to import it as a new pool, if you tried to import it before, on main click on the first device for that pool and then "remove pool"back on main, create a new pool with the name you want and the correct number of slotsassign the pool device(s), leave the filesystem set to autostart the array to import the pool
February 9Feb 9 Author did not work, unraid wont accept same pool name twice, and im not able to copy 140TB
February 9Feb 9 Community Expert 3 hours ago, beantje said:did not work, unraid wont accept same pool name twice, and im not able to copy 140TBYou can use a different name; just create a new pool with one, if that is not working, post the diags after doing the steps above.
February 9Feb 9 Author i created new pool with different name ( but the hard disk have pool name same as the other one )it worked until i restarted and now it does not want to import my pool mainstorage anymore...oot@:~# zpool import -d /dev/mapper pool: mainstorage id: 18075257269857129199 state: UNAVAILstatus: One or more devices contains corrupted data.action: The pool cannot be imported due to damaged devices or data. see: https://openzfs.github.io/openzfs-docs/msg/ZFS-8000-5Econfig: mainstorage UNAVAIL insufficient replicas raidz1-0 UNAVAIL insufficient replicas sdh1 ONLINE sdc1 ONLINE sdf1 ONLINE sdd1 ONLINE sde1 UNAVAIL invalid label sdg1 UNAVAIL invalid labelwhatever i do i can't repair this ... lost 60TB i did not format anything yet, but i spend whole day trying
February 9Feb 9 Author this is the best i could get but still LightshotSchermafbeeldingVastgelegd met Lightshot Edited February 9Feb 9 by beantje
February 9Feb 9 Community Expert The pool is damaged; it's just not an import issue, since it's raidz1 and there are two missing devices, it may not be recoverable, still.2 hours ago, JorgeB said:post the diags after doing the steps above.
February 9Feb 9 Author well it happend after i imported pool with same name from different unraid,had to test first before doing on my main straight away
February 9Feb 9 Community Expert Just importing the pool would not damage it, at least not using the steps I provided above.
February 9Feb 9 Author 2 hours ago, JorgeB said:Just importing the pool would not damage it, at least not using the steps I provided above.yes import worked once i rebooted it could not import because there where 2 pools with name "mainstorage"then things got mixed up, wrote zfs info on wrong disk or something like that
February 10Feb 10 Community Expert 10 hours ago, beantje said:yes import worked once i rebooted it could not import because there where 2 pools with name "mainstorage"The GUI won't accept two pools with the same name, so you must have done something different.
February 10Feb 10 Author 1 hour ago, JorgeB said:The GUI won't accept two pools with the same name, so you must have done something different.the gui don'tbut i gave it different name in gui, but the poolname was already set in that zfs pool and that cant be changed so in the end you have 2 different pool names in gui, but still 2 same underneath and that makes problem
February 10Feb 10 Community Expert 2 hours ago, beantje said:but the poolname was already set in that zfs pool and that cant be changedIt can, if you give it a new name in the GUI, Unraid will import the pool with the new name, and it always imports the pool based on the pool UUID, not the old/current name; it just sets the new name during import, e.g.:Feb 6 07:54:26 Tower7 emhttpd: shcmd (451): /usr/sbin/zpool import -f -m -N -o autoexpand=on -d /dev/nvme0n1p1 -d /dev/nvme4n1p1 -d /dev/nvme5n1p1 -d /dev/nvme6n1p1 -d /dev/nvme7n1p1 5823356380338176758 cacheThe pool is imported using the UUID 5823356380338176758 and at the same time named as cache, this behavior is the same regardless of the old name.
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.