phillxnet
December 5, 2016, 6:18pm
2
@Tomasz_Kusmierz Yes this is a know issue (inelegance instantiated):
opened 01:08PM - 27 Jan 16 UTC
closed 09:38AM - 03 Oct 17 UTC
To improve the user experience when removing drives (bin icon) it would be good … to suggest a Rescan prior to drive removal. The mechanism uses the Name column and that is updated after each rescan but a rescan / drive re-naming can occur without the WebUI being updated, this can result in no db entry by that name, especially with the updated mechanism (>3.8.10.01) removed drives whose name (db index) changes with every re-scan.
There was a major change (by me so my fault) in how we managed drives and this is a straggling issue / side effect. Easily worked around currently by just making sure you Rescan shortly before the device removal.
A couple more forum threads address the same issue and are, like this one, sighted in the above issue:
Brief description of the problem
Trying to remove a cleanly removed and unpluged disk from the system throws this error. Not critical by any mean, just annoying
Detailed step by step instructions to reproduce the problem
Used a USB HD during migration from freeNAS to move data between pools (FZS->btrfs) and created a single 6 disk pool where 5 where together in a USB raid box (through port multiplier, disks individually seen) and the one showing the error physically apart, but in the same logic…
Brief description of the problem
[write here]
Detailed step by step instructions to reproduce the problem
i tried to create a nfs share in the gui and the following error occured.
since i deleted an HDD from the array cause its broken i guess the system searches for the wrong disk. the btrfs array itself is working.
Web-UI screenshot
[Drag and drop the image here]
Error Traceback provided on the Web-UI
Traceback (most recent call last):
File “/opt/rockstor/src/rockstor/rest_fr…
Hope that helps.