No luck today.
I have 3 versions of the HDD images I made with DD:
1) Original HDD image when the problem came and I switched to SSD
2) MY girlfriends HDD image from her car which is exactly the same setup like mine
3) Working HDD image that was working, when I put my GF HDD image in the car, all started to work (with her entertaintment database and songs) and when I put the original image in, everything worked somehow. so...its crazy anyways I made the image for later just in case
I had 3 disks with me, all with above images, I put them in the newly flashed CIC and... same problem!
I also re-flashed the firmware twice, once with WinKPF and second time with ISTA/P which included flashing and coding. This shit really beats me
Can it be a hardware issue but why? I dont see anything in the logs.
I still believe its the database issue and not the hardware issue. I believe that Music Library is where all the songs are placed and they are managed like database in QBD. I see that qbd server is not running after I start the navi boots for some reason and I dont know why is not starting
The databases are opened in temporary persistence file in flash however they are backed up on disk and again recreated after the reboot, that is what I believe not what I know for sure. BUT.. the QDB is just not starting for some reason..
I started the qdb by using the following command:
/usr/sbin/qdb -t block -T block -c /usr/mme/db/qdb.cfg -O unblock=0,tempstore=/fs/tmpfs,thread=20 -R set -vvv
Then I was able to connect by qdbc but I am totally unfamiliar with the commands so I could not verify the content of the database more that I can see that there are tables when writing ? and entering it in the qdbc clients interactive shell
As you can see the QDB is according to the config starting with the "-R" recovery option to "set"
Options are:
- auto -
File manipulation is fully automatic and a best effort is always made to establish a valid database connection at startup. Files are backed up individually and restored individually.A corrupt or missing database file is restored from the most recent valid backup that can be located. If there's no such backup, a blank database is recreated from the original schema definition.
- manual -
The only action performed is to create a blank database from the original schema definition if the database file is missing at startup. Databases are not restored from backups. If the file is corrupt, the server will not start. If the file is missing or corrupt at runtime, no access to that database is permitted and it will not be restored or recreated. This mode is intended to allow the creation of a new system or to give manual control over error recovery (e.g., to preserve the corrupt database for later analysis).
- set -
Backups of attached databases are treated as a coherent set, so an error with any of the component databases causes QDB to restore a complete and matching set of all database files. This is useful if attached databases refer to each other.The
set master is the database that attaches other databases (by using the
AutoAttach option in the configuration object). The
backup set contains the set master and all attached databases that have
BackupAttached enabled. Note that the set master can be backed up incrementally and still belong to the set.
The problem is that the music library in CIC is not "seeing" either the database that "acts" as a hard drive or the actual hard drive but I dont think the hard drive is there as a device but maybe as a database but I really dont know. We need someone who coded this damned appllication
All hard drives and their mounted points are mounted and visible to the OS and to me by terminal
Its eiter the database or something fishy with the srv-hddmgr which is executing the hddmgr.conf in /etc and there might be something wrong in the execution or persistency or some dirty file and the srv-hddmgr doesnt execute correctly trough
[ srv-hddmgr ]
eide_driver_path = /dev/hd0
strategy_flags = -linked_mode;
/* Path to hddmgr persistency file, no longer needed so save in ramdisk */
persistency_file_path = /dev/shmem/persistency.hddmgr;
eeprom_file_path = /dev/eeprom/SH4/SH4Params/DirtyByte;
eeprom_interpret_ff_as_zero =1
mount_path_name = -r -Z -t qnx6 -C { /usr/bin/touch /dev/shmem/chkfsys.done } /dev/hd0t77 /mnt/hbnavi;
mount_path_name = -r -Z -t qnx6 -C { /usr/bin/touch /dev/shmem/chkfsys.done } /dev/hd0t77.1 /mnt/hbcddb;
mount_path_name = -r -Z -t qnx6 -C { /usr/bin/touch /dev/shmem/chkfsys.done } /dev/hd0t77.2 /mnt/hbdata;
mount_path_name = -w -Z -t qnx6 -C { /usr/bin/touch /dev/shmem/chkfsys.done } /dev/hd0t77.3 /mnt/hbuser;
mount_path_name = -w -Z -t qnx6 -C { /usr/bin/touch /dev/shmem/chkfsys.done } /dev/hd0t77.4 /mnt/hbmedia;
mount_path_name = -w -Z -t qnx6 -C { /usr/bin/touch /dev/shmem/chkfsys.done } /dev/hd0t77.5 /mnt/hbdebug;
Im running out of ideas soon
All advice and help is appreciated
