@petermc Hello again.
quote=“petermc, post:1, topic:4813”]
As soon as I connect it, it says it is part of my pool. That’s not right as I didn’t add it to my pool.
[/quote]
Thanks for the report: that’s quite a strange one.
I don’t think it’s related to the drive names as the kernel ensures that each drive has a unique name so we should be good there.
Yes, but we use device serial numbers to uniquely identify/track drives and their settings:
From this I’m assuming this is not a drive you have previously used with Rockstor or have installed Rockstor on. If it is then you may need to do a proper wipe, ie via ‘wipefs -a’ (very carefully), as just removing the partitions is not enough to remove any prior btrfs signatures.
Hopefully yes. I can’t think currently how this could happen unless you are running a really really old version of Rockstor which from your previous posts is not likely (it was years ago now).
Could you first confirm your Rockstor version via a paste of the following command (run as root):
yum info rockstor
and to help diagnose what’s happening here it would help if you could post a screen grab of both your Disks and Pools page, with the problem drive attached, as well as the output of the following commands:
btrfs fi show
ls -la /dev/disk/by-id
and
lsblk -P -o NAME,MODEL,SERIAL,SIZE,TRAN,VENDOR,HCTL,TYPE,FSTYPE,LABEL,UUID
It would also be good if you could post any drive / pool related messages you find within your:
less /opt/rockstor/var/log/rockstor.log
which is also accessible via the Web-UI from System - Logs Manager (thanks to @Flyer).
I’m due to have another look at drive management in the near future so it would be good to understand what’s happened with your setup prior to that stint.
Thanks again for the report and lets hope we can get this one sorted as it’s quiet strange.