(05-31-2019, 01:39 PM)Nikolay_Po Wrote: Emask=0x10 probably can be deciphered by an enumerator of current linux source torvalds/linux/include/linux/libata.h:
Code:enum ata_completion_errors {
AC_ERR_DEV = (1 << 0), /* device reported error */
AC_ERR_HSM = (1 << 1), /* host state machine violation */
AC_ERR_TIMEOUT = (1 << 2), /* timeout */
AC_ERR_MEDIA = (1 << 3), /* media error */
AC_ERR_ATA_BUS = (1 << 4), /* ATA bus error */
AC_ERR_HOST_BUS = (1 << 5), /* host bus error */
AC_ERR_SYSTEM = (1 << 6), /* system error */
AC_ERR_INVALID = (1 << 7), /* invalid argument */
AC_ERR_OTHER = (1 << 8), /* unknown */
AC_ERR_NODEV_HINT = (1 << 9), /* polling device detection hint */
AC_ERR_NCQ = (1 << 10), /* marker for offending NCQ qc */
};
0x10 means 4-th bit is set, ATA bus error. Not a device reported error, not an SBC failure, not a drive media failure, not an SBC bus (PCIe) error, not an unknown error. Exactly ATA bus error. This is mean that the SATA controller itself has reported a bus error. Looking forward...
Hello Nikolay,
Thank you for looking into it! I just thought i may have provided the wrong logs. It probably would be of better benefit to look at successful boot of omv and unsuccessful of omv, not successful armbian as i couldn't reproduce with it.
I finally found an attachment button on this forum.