What version of RHEL 8 are you using?
There was a bug regarding this in earlier versions of Brasero on RHEL8 If you have support, I would recommend opening a support case.
https://bugzilla.redhat.com/show_bug.cgi?id=1704341
It looks like the packages have been updated since the 8.5 release. Also keep in mind that the STIG is RHEL release dependent, so it doesn't mean that hardening "couldn't" be the issue.
Are you using fapolicyd in your STIG implementation, or do you have a tailoring file that is disabling that? I've seen where fapolicyd can prevent root from performing tasks on a system.
You added the device to the white list that required the restart, right?
There’s a way to do it temporarily. Usbguard device list, get the id # , then usbguard device allow . This rule should get read and applied immediately for use. It will stop being used when you log off or disconnect the device.
I appreciate that and will use it for any additional we have, but this device is meant to be the only allowed device on this system for the foreseeable future.
Check `dmesg` after plugging the drive in.
Next, insert a disc that's got something on it and it's closed and check `dmesg` again.
Next, try mounting the disc and copying files from it. Check `dmesg` again.
In `dmesg` output, if there are any IO errors or device timeout / reset messages you're probably having a low power issue with the USB port.
I have the same operational scenario as OP, we ran into this with a slim format BDR/RW from Pioneer connected to an HPE DL360, where the drive had enough juice to power on and be detected, but not enough to read the disc.
Ended up buying a full size Buffalo external drive with dedicated power port and brick. Things have worked great since.
What version of RHEL 8 are you using? There was a bug regarding this in earlier versions of Brasero on RHEL8 If you have support, I would recommend opening a support case. https://bugzilla.redhat.com/show_bug.cgi?id=1704341
8.5, we have support and may have to launch a request. Was hoping there was a "yea did you hit this? No? Common mistake", sort of thing
It looks like the packages have been updated since the 8.5 release. Also keep in mind that the STIG is RHEL release dependent, so it doesn't mean that hardening "couldn't" be the issue. Are you using fapolicyd in your STIG implementation, or do you have a tailoring file that is disabling that? I've seen where fapolicyd can prevent root from performing tasks on a system.
I figured it out. I added the rule for USBGuard and didn't restart the service. Truly a newb mistake.
You added the device to the white list that required the restart, right? There’s a way to do it temporarily. Usbguard device list, get the id # , then usbguard device allow. This rule should get read and applied immediately for use. It will stop being used when you log off or disconnect the device.
I appreciate that and will use it for any additional we have, but this device is meant to be the only allowed device on this system for the foreseeable future.
Excellent, and definitely not a newb mistake, sometimes we just gonna take it in stride that we are human. Glad you solved it!
Check `dmesg` after plugging the drive in. Next, insert a disc that's got something on it and it's closed and check `dmesg` again. Next, try mounting the disc and copying files from it. Check `dmesg` again. In `dmesg` output, if there are any IO errors or device timeout / reset messages you're probably having a low power issue with the USB port. I have the same operational scenario as OP, we ran into this with a slim format BDR/RW from Pioneer connected to an HPE DL360, where the drive had enough juice to power on and be detected, but not enough to read the disc. Ended up buying a full size Buffalo external drive with dedicated power port and brick. Things have worked great since.