No...as I mentioned in comment #33, "sudo hdparm -B 255 /dev/sdb1" ran after HDD woke up. But maybe I misunderstand, if you meant that after execute that command is the HDD still can go into sleep state?; my answer is: YES (in about 5-7 minutes then HDD entered sleep state).
And then I executed "sudo hdparm -B 254 /dev/sdb1" while bug reoccured, the result was:
/dev/sdb1:
setting Advanced Power Management level to 0xfe (254)
HDIO_DRIVE_CMD failed: Invalid argument
APM_level = 254
After previous command, same behavior reoccured (looks like that command has no effect).
No...as I mentioned in comment #33, "sudo hdparm -B 255 /dev/sdb1" ran after HDD woke up. But maybe I misunderstand, if you meant that after execute that command is the HDD still can go into sleep state?; my answer is: YES (in about 5-7 minutes then HDD entered sleep state).
And then I executed "sudo hdparm -B 254 /dev/sdb1" while bug reoccured, the result was:
/dev/sdb1:
setting Advanced Power Management level to 0xfe (254)
HDIO_DRIVE_CMD failed: Invalid argument
APM_level = 254
After previous command, same behavior reoccured (looks like that command has no effect).