You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thanks to Miyuki in the following forum thread for reporting another instance of a JMS567 based external drive enclosure miss-representing multiple drive serials as one.
Please also see the last pull request concerning a near identical change associated with a different serial number:
"Add another JMS567 controller serial obfuscation detection #2318" #2320 #2320
The text was updated successfully, but these errors were encountered:
phillxnet
changed the title
Add yet additional JMS567 controller serial obfuscation detection
Add yet another JMS567 controller serial obfuscation detection
Jan 7, 2022
phillxnet
added a commit
to phillxnet/rockstor-core
that referenced
this issue
Jan 10, 2022
Previously we had both backend (Python) and frontend(js) serial
rejections mechanisms. The former dealt with empty or repeat device
serial rejection/mitigation. The latter was used to inform the user
similarly of the former and it's own 'store' of known unreliable or
repeating within an external enclosure device serials.
Move all fake serial determination to the backend under the existing
'fake-serial-*' tag mechanism. Leaving the front end to react only to
this serial 'flag'.
## Includes:
- The addition of yet another unusable serial number associated with
a JMS567 multi-dev external enclosure.
- The removal from frontend js of a now defunct flag mechanism that
looked for drive name as serial number.
Thanks to Miyuki in the following forum thread for reporting another instance of a JMS567 based external drive enclosure miss-representing multiple drive serials as one.
Forum reference::
https://forum.rockstor.com/t/can-i-avoid-this-error-houston-weve-had-a-problem-duplicate-key-value-violates-unique-constraint-storageadmin-disk-name-key/8137
Please also see the last pull request concerning a near identical change associated with a different serial number:
"Add another JMS567 controller serial obfuscation detection #2318" #2320
#2320
The text was updated successfully, but these errors were encountered: