- Joined
- May 13, 2015
- Messages
- 2,478
Hmmm... I don't know!Just a quick question. I am running through this again with a few more drives.
I am up to badblocks.
Code:[root@freenas] ~# sysctl kern.geom.debugflags=0x10 kern.geom.debugflags: 16 -> 16 [root@freenas] ~# badblocks -b 4096 -ws /dev/ada2 Testing with pattern 0xaa: set_o_direct: Inappropriate ioctl for device 26.12% done, 2:36:16 elapsed. (0/0/0 errors)
Do i need to do anything with the "inappropriate ioctl for devices'?
Or is that OK for a 6TB drive?
Thanks,
Rich
Looks as though
badblocks
is running, so at least it didn't bomb out. I would abort the test and restart it with a larger block size - badblocks -b 8192 -ws /dev/ada2
- to check and see if it's a glitch attributable to the large size of your drive. BTW, if you find out that my hunch is correct - let me know and I will modify this script on Github.EDIT: I got the same message when I ran badblocks on a 2TB drive under FreeNAS 9.10.2. I looked at the source code and in my semi-expert opinion it's more in the nature of a warning than an error in our case, as it doesn't seem to adversely affect the program's operation.
Last edited: