A6 MMI 3G+ woes

[dspl1236]

Hello I have a 2013 A6 with the MMI 3G+. Years ago I did the NAR 6.16.2 (HN+R_US_AU_K0942_3) with the extra activation SD (UK Vendor in 2018). I have always had activation issues but the Nav worked. Few months ago I decided to do an SSD upgrade for space. Never could get it working from my cloned HDD. Would just wait forever and time out. Car was in storage for 2 months and I decided to put the original 60gb back in. Same problem. Nothing loads, timing out with no Nav data. Jukebox doesnt work, hit or miss if it will even play music off an SD card. Security/Activation codes persist after clearing with VCDS. I decide to firmware up (HN+R_US_AU_K0942_6) for the NAR 6.24.0.

Same issue. Nav time out/not found, radio will load quicker, jukebox missing.

In QNX VM everything looks fine. Been reading and trying things for days from the A5 and Touareg groups. Nav data looks intact. I just need some helping hands.


I also have a 2012 A6 with an untouched MMI 3G+ running (HN+R_US_AU_P0409) with NAR 5.5.3. I have been temped to jump it up to K0942_6 for testing.....but it works.


SO i decided to put the 2013 drive in the 2012. Map Data complained it was incorrect (firmware issue) but the jukebox loaded up quickly and started playing. Makes me think the drive is fine.
2012 drive in the 2013 and just hangs as it always does.

I have a feeling there is a dying/corrupt/bad setting/something MMI issue.

2013 MMI INFO

INFO] Start: Thu Jan 01 00:39:18 UTC 1970; Timestamp: 20231021_153407
[INFO] MMI3G Info Dump: mmi3ginfo3-v230701

[INFO] MU train name: HN+_US_AU3G_K0942_6
[INFO] MU software version: 1038
[INFO] MU variant: 9411-E1
[INFO] MU hwSample: E1

[INFO] Installed HDD: TOSHIBA MK6050GAC sn 13Q2TWXRT fw TJ104A
[INFO] HDD reported cylinders: 57231
[INFO] HDD capacity (512 byte sectors): 117209088
[INFO] HDD partition table:

   _____OS_____     Start      End     ______Number______   Size    Boot  
   name    type    Cylinder  Cylinder  Cylinders   Blocks                 

1. QNX       77          0      28159     28160  57673287  28160 MB   *
2. QNY       78      28160      47621     19462  39857265  19461 MB
3. QNZ       79      47622      48664      1043   2136645   1043 MB
4. Extd'd     5      48665      57230      8566  17542980   8565 MB


[INFO] HDD navigation database info: 8R0060884JE NAR 6.24.0 2021/2022
[INFO] Nav database release activation file: 00040022.fsc
[INFO] Nav database release FSC file not found !
[INFO] H-B navdb activation: enabled !
[INFO] Found LVM patch in /usr/bin/manage_cd.sh.

[INFO] Gracenote CD-Database part number: 8R0060961E
[INFO] Gracenote CD-Database version: 4949

[INFO] HMI type: 3GPLUS_AUDI
[INFO] HMI region: NAR


[INFO] Mounted filesystems (mount):
/dev/sdcard20t12 on /fs/sd1 type dos (fat32) 
/dev/blk/ram-1-alloc-0-tmp on /fs/tmpfs type tmp 
multicored on /hbsystem/multicore type multicore 
/dev/sdcard20t12 on /mnt/sdcard20t12 type dos (fat32) 
/dev/hd0t187.4 on /mnt/pv-cache type qnx6 
/dev/hd0t187.3 on /mnt/img-cache type qnx6 
/dev/hd0t187.2 on /mnt/persistence type qnx6 
/dev/hd0t187.1 on /mnt/mmebackup1 type qnx6 
/dev/hd0t78 on /mnt/mediadisk type qnx6 
/dev/hd0t187 on /mnt/gracenode type qnx6 
/dev/hd0t77 on /mnt/nav type qnx6 
/dev/fs4p1 on /mnt/phonedb type flash 
/dev/fs1p3 on /mnt/hmisql type flash 
/dev/hd0t79 on /mnt/sss type qnx6 
/dev/fs0p3 on /mnt/efs-persist type flash 
/mnt/gracenode/boardbook/boardbook.iso on /mnt/efs-persist/boardbook type cd (joliet) 
/dev/fs0p2 on /mnt/efs-system type flash 
/dev/fs0p1 on /mnt/efs-extended type flash 

[INFO] Free space (df -k -P):
Filesystem           1024-blocks      Used Available Capacity  Mounted on      
/dev/sdcard20t12         1993092       240   1992852       1%  /mnt/sdcard20t12
/dev/blk/ram-1-allo        12288       616     11672       6%  /fs/tmpfs/      
/hbsystem/multicore         1072      1072         0     100%  /hbsystem/multic
/dev/hd0t187.4           1044176     64347    979829       7%  /mnt/pv-cache/  
/dev/hd0t187.3           2136596     81390   2055206       4%  /mnt/img-cache/ 
/dev/hd0t187.2            176664     12804    163860       8%  /mnt/persistence
/dev/hd0t187.1            168632     10990    157642       7%  /mnt/mmebackup1/
/dev/hd0t78             19928616   5573791  14354825      28%  /mnt/mediadisk/ 
/dev/hd0t187             5245172   1748503   3496669      34%  /mnt/gracenode/ 
/dev/hd0t77             28836624  23507060   5329564      82%  /mnt/nav/       
/dev/fs4p1                  8128       143      7984       2%  /mnt/phonedb    
/dev/fs1p3                   960       124       835      13%  /mnt/hmisql     
/dev/hd0t79              1068304    196263    872041      19%  /mnt/sss/       
/dev/fs0p3                 29440      2682     26757      10%  /mnt/efs-persist
/mnt/gracenode/boar       562504    562504         0     100%  /mnt/efs-persist
/dev/fs0p2                 37632     35587      2044      95%  /mnt/efs-system 
/dev/fs0p1                 12032       117     11914       1%  /mnt/efs-extende
/dev/sdcard20            1997312   1997312         0     100%                  
/dev/hd0                58605120  58605120         0     100%

https://drive.google.com/file/d/12h0...usp=share_link



2012 MMI INFO

[INFO] Start: Thu Jan 01 00:28:00 UTC 1970; Timestamp: 20231022_104050
[INFO] MMI3G Info Dump: mmi3ginfo3-v230701

[INFO] MU train name: HN+R_US_AU_P0409    
[INFO] MU software version: 0294
[INFO] MU variant: 9411
[INFO] MU hwSample: n/a

[INFO] Installed HDD: TOSHIBA MK6050GAC sn 31D4T9MTT fw TJ104A
[INFO] HDD reported cylinders: 57231
[INFO] HDD capacity (512 byte sectors): 117209088
[INFO] HDD partition table:

   _____OS_____     Start      End     ______Number______   Size    Boot  
   name    type    Cylinder  Cylinder  Cylinders   Blocks                 

1. QNX       77          0      28159     28160  57673287  28160 MB   *
2. QNY       78      28160      47621     19462  39857265  19461 MB
3. QNZ       79      47622      48664      1043   2136645   1043 MB
4. Extd'd     5      48665      57230      8566  17542980   8565 MB


[INFO] HDD navigation database info: 8R0060884AC NAR 5.5.3 2011     
[INFO] Nav database release activation file: 00040003.fsc
[INFO] Found nav database release FSC file.
[INFO] H-B navdb activation: enabled !
[INFO] LVM patch not found !

[INFO] Gracenote CD-Database part number: 8R0060961A
[INFO] Gracenote CD-Database version: 2712

[INFO] HMI type: 3GPLUS_AUDI
[INFO] HMI region: NAR

[INFO] Mounted filesystems (mount):
/mnt/nav/db/pkgdb/SDS3GP_NAR/SDS_Data.iso on /SDS type cd (joliet) 
/dev/sdcard10t12 on /fs/sd0 type dos (fat32) 
/dev/blk/ram-1-alloc-0-tmp on /fs/tmpfs type tmp 
multicored on /hbsystem/multicore type multicore 
/dev/sdcard10t12 on /mnt/sdcard10t12 type dos (fat32) 
/dev/fs4p1 on /mnt/phonedb type flash 
/dev/hd0t187.4 on /mnt/pv-cache type qnx6 
/dev/hd0t187.3 on /mnt/img-cache type qnx6 
/dev/hd0t187.2 on /mnt/persistence type qnx6 
/dev/hd0t187.1 on /mnt/mmebackup1 type qnx6 
/dev/hd0t78 on /mnt/mediadisk type qnx6 
/dev/hd0t187 on /mnt/gracenode type qnx6 
/dev/hd0t77 on /mnt/nav type qnx6 
/dev/fs1p3 on /mnt/hmisql type flash 
/dev/hd0t79 on /mnt/sss type qnx6 
/dev/fs0p3 on /mnt/efs-persist type flash 
/dev/fs0p2 on /mnt/efs-system type flash 
/dev/fs0p1 on /mnt/efs-extended type flash 

[INFO] Free space (df -k -P):
Filesystem           1024-blocks      Used Available Capacity  Mounted on      
/mnt/nav/db/pkgdb/S       463522    463522         0     100%  /SDS/           
/dev/sdcard10t12         1993092      1004   1992088       1%  /mnt/sdcard10t12
/dev/blk/ram-1-allo        12288       616     11672       6%  /fs/tmpfs/      
/hbsystem/multicore         1072      1072         0     100%  /hbsystem/multic
/dev/fs4p1                  8128       142      7985       2%  /mnt/phonedb    
/dev/hd0t187.4           1044176     64347    979829       7%  /mnt/pv-cache/  
/dev/hd0t187.3           2136596   1716510    420086      81%  /mnt/img-cache/ 
/dev/hd0t187.2            176664     10891    165773       7%  /mnt/persistence
/dev/hd0t187.1            168632     10985    157647       7%  /mnt/mmebackup1/
/dev/hd0t78             19928616    680900  19247716       4%  /mnt/mediadisk/ 
/dev/hd0t187             5245172   1159333   4085839      23%  /mnt/gracenode/ 
/dev/hd0t77             28836624  19022996   9813628      66%  /mnt/nav/       
/dev/fs1p3                   960       109       850      12%  /mnt/hmisql     
/dev/hd0t79              1068304    192690    875614      19%  /mnt/sss/       
/dev/fs0p3                 29440      4580     24859      16%  /mnt/efs-persist
/dev/fs0p2                 37632     30529      7102      82%  /mnt/efs-system 
/dev/fs0p1                 12032      1500     10531      13%  /mnt/efs-extende
/dev/sdcard10            1997312   1997312         0     100%                  
/dev/hd0                58605120  58605120         0     100%                  
/dev/cd0                       0         0         0     100%  (/fs/cd0/)

[DrGER]

Hello I have a 2013 A6 with the MMI 3G+. Years ago I did the NAR 6.16.2 (HN+R_US_AU_K0942_3) with the extra activation SD (UK Vendor in 2018). I have always had activation issues but the Nav worked. Few months ago I decided to do an SSD upgrade for space. Never could get it working from my cloned HDD. Would just wait forever and time out. Car was in storage for 2 months and I decided to put the original 60gb back in. Same problem. Nothing loads, timing out with no Nav data. Jukebox doesnt work, hit or miss if it will even play music off an SD card. Security/Activation codes persist after clearing with VCDS. I decide to firmware up (HN+R_US_AU_K0942_6) for the NAR 6.24.0.

Same issue. Nav time out/not found, radio will load quicker, jukebox missing.

In QNX VM everything looks fine. Been reading and trying things for days from the A5 and Touareg groups. Nav data looks intact. I just need some helping hands.
...

The MMI3G Info script is mine.
I recommend that you post your MMI3G script logs to Google Drive in an an open (unrestricted) folder for review & comment by the community (the log file you posted above is restricted). Log files have no PII (except, maybe, for your taste in music stored in the Jukebox).

So you bought the MMI3GP update BS from the guy in the UK, too, back in '18. I've since determined his SD cards are fakes and their contents sourced from the internet. Oh, well.

In any case, we should examine the full MMI3G Info log for your 2013 (with its original 60 GB HDD) after running for 4-5 minutes from startup with "INFO_SYSLOG=Y" to see what might be happening with the HDD. Given that the log excerpt you posted above returns good information, the HDD seems OK.
You might want to look at the GEM /environment/hdd/smart/viewsmart screens for indications/suggestions of trouble.

BTW, the so-called "activator" provided by the UK guy is likely the so-called Vlasoff script from early 2016. I comment on it in a few posts, for example:
https://www.vwvortex.com/threads/som...ocess.9532682/
and
https://www.audizine.com/forum/showt...-3G-3G-Systems

You note that you updated the MMI software on the '13 from K0942_3 to K0942_6 , but there is no release called HN+R_US_AU_K0942_6. HN+R and HN+ are for different MMI3GP hardware variants (9411 & 9498, respectively). Done incorrectly, a software update can introduce new problems with regard to system functionality.

Update -- after looking at this again, I see you applied HN+_US_AU3G_K0942_6 to your '13 A6. No, that was not a good idea. You need to force HN+R_US_AU_K0942_3 MU9411 back on -- you may be able to do this as a User Defined update.

I see you have the same username over at vwvortex -- if you want to follow-up in either the B8 or Audio/Electronics forums, that works, too.

I also recommend (highly) getting good at taking PNG screenshots of the MMI display to a FAT32 SD card in slot 1 as a means of documentation -- on the A6, press and hold [<]+[>] (left+right arrow) buttons for 3+ seconds (or until the center console LEDs start to flash). --g

[dspl1236]

You note that you updated the MMI software on the '13 from K0942_3 to K0942_6 , but there is no release called HN+R_US_AU_K0942_6. HN+R and HN+ are for different MMI3GP hardware variants (9411 & 9498, respectively). Done incorrectly, a software update can introduce new problems with regard to system functionality.

Update -- after looking at this again, I see you applied HN+_US_AU3G_K0942_6 to your '13 A6. No, that was not a good idea. You need to force HN+R_US_AU_K0942_3 MU9411 back on -- you may be able to do this as a User Defined update.

I see you have the same username over at vwvortex -- if you want to follow-up in either the B8 or Audio/Electronics forums, that works, too.

I also recommend (highly) getting good at taking PNG screenshots of the MMI display to a FAT32 SD card in slot 1 as a means of documentation -- on the A6, press and hold [<]+[>] (left+right arrow) buttons for 3+ seconds (or until the center console LEDs start to flash). --g

Thank you Dr. Great tools by the way. Would you preferer here or elsewhere for a continuation of this discussion?

I see what I did with the incorrect FW (HN+_US_AU3G_K0942_6) application. I will try to force it back to (HN+R_US_AU_K0942_3) to further diagnose.

2013 MMI info for all to read with incorrect FW
https://drive.google.com/file/d/12h0...ew?usp=sharing

[DrGER]

... Would you preferer here or elsewhere for a continuation of this discussion?
...

We can continue here.
This is why your 2013 nav is hanging:

...
[INFO] Cannot find file acios_db.ini
...

So, the first thing you need to do is restore K0942_3 MU9411 components; this will overwrite ifs-root and efs-system flash memory filesystems (but do all the MU9411 components, including emg & fpga). Also, run the MMI3G Info script no later that 5 minutes after system startup, as QNX syslog uses a ring buffer, and earlier messages at system startup get overwritten over time (as is the case with your posted log file). --g

[dspl1236]

We can continue here.
This is why your 2013 nav is hanging:

...
[INFO] Cannot find file acios_db.ini
...

So, the first thing you need to do is restore K0942_3 MU9411 components; this will overwrite ifs-root and efs-system flash memory filesystems (but do all the MU9411 components, including emg & fpga). Also, run the MMI3G Info script no later that 5 minutes after system startup, as QNX syslog uses a ring buffer, and earlier messages at system startup get overwritten over time (as is the case with your posted log file). --g

K0942_3 MU9411 has been completely restored.

I ran your mkaciosdb-230509.zip

Nav super slow, but eventually loaded a blank screen with gui overlays. Went back to grab a screenshot and said nav data missing. Jukebox missing greyed out.

mmi3ginfo-20231023_114852_post MU9411&acios.txt
https://drive.google.com/file/d/13BY...ew?usp=sharing

Screen_0_231023_1150_0006.png

[DrGER]

K0942_3 MU9411 has been completely restored.

I ran your mkaciosdb-230509.zip

Nav super slow, but eventually loaded a blank screen with gui overlays. Went back to grab a screenshot and said nav data missing. Jukebox missing greyed out.
...

This doesn't look good:

...
Jan 01 00:00:14    3 20002   400 Starting srv-hddmgr [ver. 2.1.28]. pid: 126989
Jan 01 00:00:14    5 20002   400 Added mount path of </dev/hd0t79> to </mnt/sss>, type <qnx6>, data <>
Jan 01 00:00:14    5 20002   400 Added mount path of </dev/hd0t77> to </mnt/nav>, type <qnx6>, data <>
Jan 01 00:00:14    5 20002   400 Added mount path of </dev/hd0t187> to </mnt/gracenode>, type <qnx6>, data <>
Jan 01 00:00:14    5 20002   400 Added mount path of </dev/hd0t78> to </mnt/mediadisk>, type <qnx6>, data <>
Jan 01 00:00:14    5 20002   400 Added mount path of </dev/hd0t187.1> to </mnt/mmebackup1>, type <qnx6>, data <>
Jan 01 00:00:14    5 20002   400 Added mount path of </dev/hd0t187.2> to </mnt/persistence>, type <qnx6>, data <>
Jan 01 00:00:14    5 20002   400 Added mount path of </dev/hd0t187.3> to </mnt/img-cache>, type <qnx6>, data <>
Jan 01 00:00:14    5 20002   400 Added mount path of </dev/hd0t187.4> to </mnt/pv-cache>, type <qnx6>, data <>
Jan 01 00:00:14    5 20002   400 Persistency is loaded [ h: 318, t: 230, boot: Normal, debug: UNKNOWN ]
Jan 01 00:00:14    2 20002   400 Failed connection establishment with </dev/hd0>.
Jan 01 00:00:14    2 20002   400 Can't get Temperature conditions.
Jan 01 00:00:14    5 20002   400 Default: Switch to HDD_MALFUNCTION.
Jan 01 00:00:14    5 20002   500 Opened /dev/hddmgr
...

This from a UK A8 with HN+R system:

...
Jan 01 00:00:04    3 20002   400 Starting srv-hddmgr [ver. 2.1.28]. pid: 126989
Jan 01 00:00:04    5 20002   400 Added mount path of </dev/hd0t79> to </mnt/sss>, type <qnx6>, data <>
Jan 01 00:00:04    5 20002   400 Added mount path of </dev/hd0t77> to </mnt/nav>, type <qnx6>, data <>
Jan 01 00:00:04    5 20002   400 Added mount path of </dev/hd0t187> to </mnt/gracenode>, type <qnx6>, data <>
Jan 01 00:00:04    5 20002   400 Added mount path of </dev/hd0t78> to </mnt/mediadisk>, type <qnx6>, data <>
Jan 01 00:00:04    5 20002   400 Added mount path of </dev/hd0t187.1> to </mnt/mmebackup1>, type <qnx6>, data <>
Jan 01 00:00:04    5 20002   400 Added mount path of </dev/hd0t187.2> to </mnt/persistence>, type <qnx6>, data <>
Jan 01 00:00:04    5 20002   400 Added mount path of </dev/hd0t187.3> to </mnt/img-cache>, type <qnx6>, data <>
Jan 01 00:00:04    5 20002   400 Added mount path of </dev/hd0t187.4> to </mnt/pv-cache>, type <qnx6>, data <>
Jan 01 00:00:04    5 20002   400 Persistency is loaded [ h: 51, t: 450, boot: Normal, debug: UNKNOWN ]
Jan 01 00:00:05    5 20002   400 Opened EIDE driver at path: /proc/mount/dev/hd0/0,40976,7,4,0, max retries: 3
Jan 01 00:00:05    3 20002   400 Established connection with </dev/hd0> on </proc/mount/dev/hd0/0,40976,7,4,0>.
Jan 01 00:00:05    2 20002   400 Device APM Level is: 192
Jan 01 00:00:05    6 20000     0 Interface [86]: 'AVAIL' '/dev/hddmgr'
...

Suggest comparing this to your '12 A6 with P0409. --g

[dspl1236]

2012 C7 A6 MMI Info:
https://drive.google.com/file/d/1VH3...ew?usp=sharing

Jan 01 00:00:04    3 20002   400 Starting srv-hddmgr [ver. 2.1.28]. pid: 159757
Jan 01 00:00:04    5 20002   400 Added mount path of </dev/hd0t79> to </mnt/sss>, type <qnx6>, data <>
Jan 01 00:00:04    5 20002   400 Added mount path of </dev/hd0t77> to </mnt/nav>, type <qnx6>, data <>
Jan 01 00:00:04    5 20002   400 Added mount path of </dev/hd0t187> to </mnt/gracenode>, type <qnx6>, data <>
Jan 01 00:00:04    5 20002   400 Added mount path of </dev/hd0t78> to </mnt/mediadisk>, type <qnx6>, data <>
Jan 01 00:00:04    5 20002   400 Added mount path of </dev/hd0t187.1> to </mnt/mmebackup1>, type <qnx6>, data <>
Jan 01 00:00:04    5 20002   400 Added mount path of </dev/hd0t187.2> to </mnt/persistence>, type <qnx6>, data <>
Jan 01 00:00:04    5 20002   400 Added mount path of </dev/hd0t187.3> to </mnt/img-cache>, type <qnx6>, data <>
Jan 01 00:00:04    5 20002   400 Added mount path of </dev/hd0t187.4> to </mnt/pv-cache>, type <qnx6>, data <>
Jan 01 00:00:04    5 20002   400 Persistency is loaded [ h: 309, t: 110, boot: Normal, debug: UNKNOWN ]
Jan 01 00:00:04    5 20002   400 Opened EIDE driver at path: /proc/mount/dev/hd0/0,40977,7,5,0, max retries: 3
Jan 01 00:00:04    3 20002   400 Established connection with </dev/hd0> on </proc/mount/dev/hd0/0,40977,7,5,0>.
Jan 01 00:00:04    2 20002   400 Device APM Level is: 254
Jan 01 00:00:04    6 20000     0 Interface [86]: 'AVAIL' '/dev/hddmgr'

2013:
I see this being repeated as well.

Jan 01 00:00:57    5    19     0 hbfpga_reset: resetting ATAPI core in FPGA (delay=2000ms)
Jan 01 00:00:59    6 10000     0 GPU: 75141K, GPU_maxAlloc: 65432K
Jan 01 00:00:59    2    19     0 eide_reset:  complete 2043 ms
Jan 01 00:00:59    2    19     0 eide_identify: chk 4 cmd a1, tid 0, status 7f, astatus 7f, error 7f
Jan 01 00:00:59    2    19     0 eide_identify: chk 4 cmd a1, tid 0, status 7f, astatus 7f, error 7f
Jan 01 00:00:59    5    19     0 hbfpga_reset: resetting ATAPI core in FPGA (delay=2000ms)
Jan 01 00:01:00    5    20     1 io-media-nvidia: Failing read with EINTR, rcvid=2752519

Also found
Dirty bit is set for </dev/hd0t79>
Dirty bit is set for </dev/hd0t77>
Dirty bit is set for </dev/hd0t187>
Dirty bit is set for </dev/hd0t78>
Dirty bit is set for </dev/hd0t187.1>
Dirty bit is set for </dev/hd0t187.2>
Dirty bit is set for </dev/hd0t187.3>
Dirty bit is set for </dev/hd0t187.4>

Sounds like a dying drive or corruption.... which could have happened during cloning the drive as I did not use clonezilla originally and accidently booted off the original drive in an old laptop.
I wonder if a fsck repair or something might work.

I would say dying drive. Thoughts?

[DrGER]

But, wait, later in the syslog we find this:

...
Jan 01 00:04:31    6 20000     0 Interface [07]: 'AVAIL' '/dev/hd0t78'
Jan 01 00:04:31    5 20002   400 Opened EIDE driver at path: /proc/mount/dev/hd0/0,40976,4,2,0, max retries: 3
Jan 01 00:04:31    3 20002   400 Established connection with </dev/hd0> on </proc/mount/dev/hd0/0,40976,4,2,0>.
Jan 01 00:04:31    2 20002   400 Device APM Level is: 254
Jan 01 00:04:31    2 20002   400 Temperature conditions renewed.
Jan 01 00:04:31    5 20002   400 HDD_MALFUNCTION: Switch to INIT.
Jan 01 00:04:31    5 20002   401 Loaded/PowerOn hours ratio: 0.997
Jan 01 00:04:31    5 20002   401 Loaded/PowerOn hours ratio: 0.997
Jan 01 00:04:31    2 20002   400 ERROR <No such file or directory> reading EEPROM data from </tmp/hddmgr.dirtybits>.Info not available on hard drive consistency.
Jan 01 00:04:31    5 20002   400 Launched the disk checking thread...
Jan 01 00:04:31    5 20002   400 Detected partition </dev/hd0t79>
Jan 01 00:04:31    5 20002   400 Detected partition </dev/hd0t77>
Jan 01 00:04:31    5 20002   400 Detected partition </dev/hd0t187>
Jan 01 00:04:31    5 20002   400 Detected partition </dev/hd0t78>
Jan 01 00:04:31    5 20002   400 Detected partition </dev/hd0t187.1>
Jan 01 00:04:31    5 20002   400 Detected partition </dev/hd0t187.2>
Jan 01 00:04:31    5 20002   400 Detected partition </dev/hd0t187.3>
Jan 01 00:04:31    5 20002   400 Detected partition </dev/hd0t187.4>
Jan 01 00:04:31    6 20011     1 libmldr:AtapiCtrlDeviceOpen:: could not open device (/dev/cam0/000)
Jan 01 00:04:32    5 20002   400 Disk checking/Initializing: waiting for trigger ...
Jan 01 00:04:32    5 20002   400 helperPerformDiskChecksThread: partition </mnt/sss>
Jan 01 00:04:32    2 20002   400 Dirty bit is set for </dev/hd0t79>
...

Something appears to be blocking access to the HDD controller earlier in the boot process ... maybe this:

Jan 01 00:00:03    2    19     0 eide_identify_devices: XILINX ATAPI vid 10ee, did 9411, class 78000 rev 1, busno 0, dfunc 0
Jan 01 00:00:03    2    19     0 eide_identify_devices: cmd_addr c0060040, cntl_addr c0060070, irq 30, chnl 0, udma -1, mdma 2, sdma -1, pio 4
Jan 01 00:00:03    3    20     1 io-media-nvidia/a2dp_player: The 'metadata-timeout' setting is missing or has an invalid value, defaulting to 4000ms
Jan 01 00:00:03    2    19     0 eide_identify: chk 4 cmd a1, tid 0, status 7f, astatus 7f, error 7f
Jan 01 00:00:03    2    19     0 eide_identify: chk 4 cmd a1, tid 0, status 7f, astatus 7f, error 7f
Jan 01 00:00:03    5    19     0 hbfpga_reset: resetting ATAPI core in FPGA (delay=2000ms)
...

The UK log shows this:

Jan 01 00:00:03    2    19     0 eide_identify_devices: XILINX ATAPI vid 10ee, did 9411, class 78000 rev 1, busno 0, dfunc 0
Jan 01 00:00:03    2    19     0 eide_identify_devices: cmd_addr c0060040, cntl_addr c0060070, irq 30, chnl 0, udma -1, mdma 2, sdma -1, pio 4
Jan 01 00:00:03    2    19     0 eide_display_devices: mdl FUJITSU TEN DVD-ROM DV-05FT2 sn  fw 5020 tid 0, cable 40, max udma -1, cur udma -1, max mdma 2, cur mdma 2, max sdma -1, cur sdma -1, pio 4, mblk 0
Jan 01 00:00:03    4    19     0 [pcidma] FPGA (8 channels, module version 08365A [mod.40 rev. 1.1.0]) initialized; reset was 0
Jan 01 00:00:03    4    19     0 [pcidma] hardware initialized: SH7785
Jan 01 00:00:03    2    19     0 eide_init_devices: FUJITSU TEN DVD-ROM DV-05FT2 path 0, tid 0, udma -1, mdma 2, sdma -1, pio 4, mblk 0
Jan 01 00:00:03    2    19     0 eide_identify_devices: XILINX ATAPI vid 10ee, did 9411, class 78000 rev 1, busno 0, dfunc 0
Jan 01 00:00:03    2    19     0 eide_identify_devices: cmd_addr c0800040, cntl_addr c0800070, irq 30, chnl 0, udma -1, mdma 2, sdma -1, pio 4
Jan 01 00:00:03    2    19     0 eide_display_devices: mdl Hitachi HEJ421080G9AT00 sn F502A7AEKWHVTJ fw F5CJA40C tid 1, cable 80, max udma 5, cur udma 0, max mdma 2, cur mdma 2, max sdma -1, cur sdma -1, pio 4, mblk 16
...

Is the cable to the DVD drive seated properly ? --g

[DrGER]

In your QNX 6.5.0SP1 VM, chkqnx6fs is the fsck equivalent:

# chkqnx6fs -v /dev/umass0t77 # check the nav partition

and so on for the remaining QNX partitions. --g

[dspl1236]

But, wait, later in the syslog we find this:

Is the cable to the DVD drive seated properly ? --g

Took the ribbon out entirely for full reseat. Everything functions. Nav, Tel, Juke, SD, ect.

But shortly after moving from menu to menu the nav drops back out. But shows the map cached between menus.
Screen_0_231023_1447_0005.png

Reboot 2013:
MMI Info
https://drive.google.com/file/d/1yw4...ew?usp=sharing

I do see the /dev/cd0 mounting unlike the times before. When I was looking at CD mount in the 2012 MMI, I assumed it was the 6-disk changer my 2013 does not have.

Still picking through this last log. Have not tried chkqnx6fs yet, but it is next.

[DrGER]

That's better. Your nav is trying to find the correct FSC to activate the database:

...
[INFO] HDD navigation database info: 8R0060884JE NAR 6.24.0 2021/2022
[INFO] Nav database release activation file: 00040022.fsc
[INFO] Nav database release FSC file not found !
[INFO] H-B navdb activation: enabled !
[INFO] LVM patch not found !
...

Run my unblocker patch to disable normal activation: https://github.com/DrGER2/MMI3G-Navdb-Unblocker

The map graphic under the menu is old data from one of the nVidia video layers -- it isn't live.
I would expect that you should see the "nav data unavailable" note when selecting [NAV] after this. --g

[dspl1236]

ran the tool

INFO] Start: Thu Jan 01 00:02:15 UTC 1970; Timestamp: 19700101_000215; MU: MMI3GP

[INFO] MMI3G Nav Database Unblocker: navunblocker-v221225

[ACTI] Appending patch to /usr/bin/manage_cd.sh ...
mv: Moving /mnt/efs-system/usr/bin/manage_cd.sh to /mnt/efs-system/usr/bin/manage_cd.sh-ORIG
cp: Copying /mnt/efs-system/usr/bin/manage_cd.sh-ORIG to /mnt/efs-system/usr/bin/manage_cd.sh

[ACTI] Copy FSC and acios_db.ini files to /mnt/sdcard20t12/var
cp: Copying /mnt/efs-persist/FSC/0004000B.fsc to /mnt/sdcard20t12/var/0004000B.fsc
cp: Copying /mnt/efs-persist/navi/db/acios_db.ini to /mnt/sdcard20t12/var/acios_db.ini

[INFO] End: Thu Jan 01 00:02:17 UTC 1970; Timestamp: 19700101_000217
press any key

After reboot the MMI shows NAR 6.16.2 still but MMI Info script shows "8R0060884JE NAR 6.24.0 2021/2022"

Screen_0_231023_1427_0002.png
the 6.24 map install was done with the incorrect firmware on the (MU9411).


Should I attempt the Map NAR 6.24.0 install in user mode again?

[DrGER]

That sure is odd -- I don't see any config files from the NAR 6.16.2 installation in /mnt/nav (and the MMI3G Info scripts looks at these, too).
Yeah, run the [Delete database (will need reboot)] shell script from the GEM /nav/databaseupdate screen (do not select [Delete Nav HDD partition]), and re-install NAR 6.24.0 (you will need to do it as user-defined, in any case). I think you're almost back to normal. --g

[dspl1236]

Good news. Everything seems back to normal, but I will always be Abby Normal

Screen_0_231023_1817_0001.png


Last 2013:
https://drive.google.com/file/d/12fd...ew?usp=sharing



Thank you and thank you for your contributions for MMI as a whole.

Would it be beneficial to have access to an imaged 60gb 8R0060884AC NAR 5.5.3 2011/FW P0409 drive? Along with the current?

[DrGER]

Glad to hear it. So maybe the DVD drive ribbon cable connection(s) has been dodgy for a while ?

You know, I'm not so interested in the old navdb as I am its PKG file (saved in /mnt/nav/db/pkgdb) and the factory FSC file that is saved in flash memory /mnt/efs-persist/FSC. If you could post those to your Google Drive folder before updating the '11 A6, that would be useful. Before & after Info logs are nice as references, too. Cheers --g

[dspl1236]

I will work on grabbing that. Thank you again. I may need to get a cell connection up again just for the Google maps.

[DrGER]

Did you see my post on the topic of provisioning the MMI3GP main unit with internet data from an external LTE router: https://www.audizine.com/forum/showt...st-3G-Shutdown --g