[SOLVED] New Mobo/CPU can't mount drives. Dupe UUID

[datZ]

Got a new CPU/Mobo upgraded and swapped everything over.

 

All 6 of my drives that are plugged directly into the mobo controller are all having this issue of not being able to mount. 

The log says dupe UUID. I tried changing the UUID on 1 drive but that didn't seem to "merge" them. After a reboot the issue came back with that drive also...

 

Error I get and when I try to mount a drive manually:

unassigned.devices: Mount of '/dev/sdl1' failed. Error message: mount: /mnt/disks/KINGSTON_SUV400S37240G_50026B766700088B: wrong fs type, bad option, bad superblock on /dev/sdl1, missing codepage or helper program, or other error. 

 

Not sure what to do. Just don't really want to lose my data... I read that I could just swap and Unraid would know by serial #.

superserver-diagnostics-20190805-0748.zip

Edited August 5, 2019 by datZ

[JorgeB]

You have some array drives appearing also as unassigned devices with a different identifier, rebooting should fix it, if not post new diags.

[datZ]

5 hours ago, johnnie.black said:

You have some array drives appearing also as unassigned devices with a different identifier, rebooting should fix it, if not post new diags.

 

Tried that. The diags you see are the results after.

[JorgeB]

Disable the VM service, reboot, and see if the same happens, I'm suspecting the SATA controller is wrongly being passed through to a VM

[datZ]

16 minutes ago, johnnie.black said:

Disable the VM service, reboot, and see if the same happens, I'm suspecting the SATA controller is wrongly being passed through to a VM

You are correct! thank you so much!

Do I just need to edit my VM to resolve this?

[JorgeB]

2 minutes ago, datZ said:

Do I just need to edit my VM to resolve this?

Yes, likely the addresses on the old board were different, you'll need to replace old address with current one for the card you're passing through.