I have 3 physical drives - SSD with
/ mounted, 1st HDD used as
/home, 2nd HDD - recovery storage for backups. The HDD with backups should stay most of the time in standby and unmounted state caused by cron and bash scripts with
The problem is external USB-drives mounting/umounting (with GUI or terminal) causes resuming of sleeping drive from standby state.
Deeper investigation shows that
umount utilities execute
dumpe2fs -h /dev/sdXn command for every partition (including unmounted) of every drive installed, which causes directly sleeping drives wake up.
For example, if the external USB-drive/stick
/dev/sdd is being mounted/dismounted, this causes in my case consequent execution of the commands (pieces from real log with some explanations):
dumpe2fs -h /dev/sda1 #this is / (root) partition at SSD [...] dumpe2fs -h /dev/sdc4 #this is /var partition at HDD #1 [...] dumpe2fs -h /dev/sdc3 #this is /home partition at HDD #1 [...] dumpe2fs -h /dev/sdb1 #this is recovery storage partition at HDD #2 [...]
Ubuntu 16.04 and earlier versions (I have migrated from Red Hat to Debian and Ubuntu in 2006) haven't such the strange behaviour. Thus, we can come to resonable conclusion the behavior caused by a bug of Ubuntu 18.04. Is there any way to solve the problem?
Note: There is related question (but not a duplicate) in Unix & Linux community: Why is dumpe2fs called without user interaction?.
UPDATE. I have discovered solution for the problem - it will be posted some later today. The problem is solved. My deepest appreciation for help to @神秘德里克 - thank you so much, friend!