...
Following logs messages appear continuously with SET and CLEAR action. LC/0/1/CPU0:Mar 30 18:59:11.654 : pfm_node_lc[296]: %PLATFORM-AHCI-2-DEV_HD0_NOT_RESPONDING : Set|ahci-mon[32789]|0x1000000|HD0 device not responding LC/0/1/CPU0:Mar 30 18:59:11.654 : ahci-mon[65557]: AHCI: redundancy_state=REDUNDANCY_ACTIVE, standby_state=STANDBY_STATE_DOWN, boot_protocol=14 LC/0/1/CPU0:Mar 30 18:59:21.991 : ahci-mon[65557]: AHCI: Cannot spawn show_media, errno=2 LC/0/1/CPU0:Mar 30 18:59:22.131 : ahci-mon[65557]: AHCI: working /dev/hd0: npass=587724, sector=0x22787400, fail count=313339/0 LC/0/1/CPU0:Mar 30 18:59:22.139 : ahci-mon[65557]: AHCI: My Nodeid=0x811, Partner Nodeid=0x0, Primary=0 devb-ahci_pid=32787 followed by clear message :- LC/0/1/CPU0:Mar 30 19:00:24.127 : pfm_node_lc[296]: %PLATFORM-AHCI-2-DEV_HD0_NOT_RESPONDING : Clear|ahci-mon[32789]|0x1000000|HD0 device not responding
NA
NA
The fix of this issue is bifurcated in multiple sections:- (1) %PLATFORM-AHCI-2-DEV_HD0_NOT_RESPONDING ? cannot read from /dev/hd0 False alarm ? Already Fixed in CSCuw97473 (2) AHCI: Cannot spawn show_media, errno=2 Cosmetic issue - Will be fixed in CSCuz02374 (3) %PLATFORM-AHCI-2-DEV_HD0_NOT_RESPONDING ? cannot read from /dev/hd0 If the sector number is huge (close to 1GB), check for truncation of /eusb/xrdisk.img (this should be 1gb size) Truncation issue - Will be fixed in CSCuz02374 Steps to check: Login to the VSM host OS and check the size of /eusb/xrdisk.img RP/0/RSP0/CPU0:Esc#run attachCon 0/2/cpu0 Fri Apr 22 03:38:00.739 UTC attachCon: Starting console session to node 0/2/cpu0 attachCon: To quit console session type 'detach' attachCon: WARNING - Type only 'detach' in the shell. Do not combine other keys. Current Baud 115200 Setting Baud to 115200 [host:/]$ ls -lh /eusb/xrdisk.img -rwxr-xr-x 1 root root 1.0G Apr 19 07:13 /eusb/xrdisk.img Command output should show 1.0G space for xrdisk.img . Sometimes it will show less than 1G size which indicates that this file is truncated which is a problem. (4) %PLATFORM-AHCI-2-DEV_HD0_NOT_RESPONDING (Fix In-progress) Possibly /eusb is mounted to a non-existent drive where /dev/sdc is not correctly mounted to the 2GB built-in drive Bad Mount issue - Will be fixed in CSCuz02374 Steps to check: Login to the VSM host OS and run ?blkid? to see if the built-in EUSB is mounted to /dev/sdc RP/0/RSP0/CPU0:Esc#run attachCon 0/2/cpu0 Fri Apr 22 03:38:00.739 UTC attachCon: Starting console session to node 0/2/cpu0 attachCon: To quit console session type 'detach' attachCon: WARNING - Type only 'detach' in the shell. Do not combine other keys. Current Baud 115200 Setting Baud to 115200 [host:~]$ cd /usr/bin [host:/usr/bin]$ blkid | grep CeUSB /dev/sdc1: SEC_TYPE="msdos" LABEL="CeUSB" UUID="8349-B24C" TYPE="vfat" |||||<--- This should show that the CeUSB device is mounted on /dev/sdc1. Sometimes it will show /dev/sdd1 which is incorrect. (5) Process devb-ahci pid 32787 tid 3 prio 21 using 25 percent is a CPU Hog (Investigation In-progress) This error message may lead to HD0 errors and possibly LC reset QNX FS driver (SIM_INTERRUPT) issue