RT87

btw: that worked flawlessly

okay, thank you very much, I will try switching the disks, I think in my particular case that is probably the better method.

If I have another drive which could serve as cache (which incidentally I do), I assume I could just copy the data and use that drive (after proper init), correct?

That's the only option? (sry!)

ok, that at least worked worked in starting the array with the disk, but now it indeed says "unmountable: wrong or no filesystem"

okay, so.... I cannot start the array without the disk, i.e. "Missing", and when I start it using the correct disk (although not recognized), it says "Unmountable: No pool uuid".

nope, not the regular array :)! Thanks for your help, I'll try!

sry, Ich meant "cache pool" (which to my knowledge have parties or at least redundancy, although I haven't used that so far) Does your answer still apply? Because I can start the array, even though the next to the cache disk it says "Wrong", but I am unsure of what will be the result...

the pool is basically only this drive (no second drive, neither parity nor regular), if that is what you mean

Hi, I changed my pool drive from an internal SATA conncetion to an external (SATA case plugged in as regular USB; I know it's not exactly "recommended" to do so). Now it doesn't recognize the disk since apparently the UUID has changed (I assume the SATA case transmits the ID of the controller chip or similar). Can I explicitly tell UNRAID to recognize this drive as the one that has been in that exact position? I.e. by manually changing the UUID mapping? Alternatively, how can I resolve this situation without compromising my pool? Best and thanks Richard

is there any progress to this? I am still experiencing this very issue with v2.1 XP.

not sure what you mean by "original". the device itself does not get recognized, not a particular partition. gparted (e.g.) simply does not show anything but my regular internal drives.

exactly... I thought maybe this occurred before and somebody knows the root cause of this issue... OK, so a new usb drive it is ;). Anyway, thanks!

true, but how come that I was still able to boot from it? The loader detected it just fine and the gui/shell came up as expected... just the PW didn't work

I have several backups, the latest one right from before the migration, so that should not be an issue. I guess I could do that, but I would probably order a new usb drive first, so as to avoid an old one having any issues. however, I would be a little sad that this upgrade (kind of) broke my usb drive. not the worst thing in the world, but still...