Hi @tom I can confirm the VOXL 2s I have are QRB5165M.

Hi,

I'm trying to follow the steps listed here to unbrick a VOXL 2: https://docs.modalai.com/voxl2-unbricking. However, after the process completes I'm unable to access it through adb. I tried running it on two computers and multiple VOXL 2s with the same results. The following is the output of the QDL Tool:

Selected Flat Build:2024-06-17-1.7.4-M0054-1
Provisioning UFS...
{"message": "UFS provisioning succeeded, please reset power to the device\n"}
Flashing CDT...
{"message": "Flash CDT succeeded\n"}
Flashing Flat Build...
{"message": "Flash flat build passed\n"}

After that and a reboot adb wait-for-device hangs for over 5 minutes

@Advait-Pandit Did you ever figure this out? We're running into the same problem on multiple VOXL 2s.

@tom I tried restoring the superblock using mke2fs -n /dev/sda8 to find backups and then trying all of them with e2fsck -b <backup_superblock> /dev/sda8 All of them failed to restore the filesystem. I'm seeing this on multiple VOXL 2s so it's not isolated just to this one.

@tom I just tried it, got stuck at the following step even after hard rebooting the device:

...
Flashing: modalai_cal | m0054-cal-fs.ext4
[------------------------------------------------------------    ]( 94%)
Done Flashing
[----------------------------------------------------------------](100%)
< waiting for any device >
./flash-system-image.sh: line 624: 36563 Killed: 9               fastboot reboot
[INFO] Waiting for ADB, if this takes more than 1 minute power cycle VOXL

Nothing using adb devices

Hi, I'm using a brand new VOXL 2 flashed with 1.7.1 and I'm having issues using I2C on port number 5. I've been able to use it without problems in the past, but all of a sudden I'm not seeing any devices on it when running i2cdetect -r -y 5 and I'm getting the following error messages in the kernel log; this is happening with any I2C device on the port:

[   14.043169] i2c_geni 990000.i2c: Bus arbitration lost, clock line undriveable
[   14.043364] i2c_geni 990000.i2c: Bus proto err, noisy/unepxected start/stop
[   14.043492] i2c_geni 990000.i2c: i2c error :-71

@tom said in VOXL 2 /data mount error:

@czarsimon Are you having this issue on every reboot?

Yes, I tried re-flashing as well as completely wiping it using the qdl tool, same issue.

Hi, using a brand new VOXL flashed with 1.7.1 I'm having issues with the data.mount service failing with the following error which is preventing other applications which use it as a dependency from running:

voxl2:/$ systemctl status data.mount
● data.mount - /data
   Loaded: loaded (/lib/systemd/system/data.mount; static; vendor preset: enabled)
   Active: failed (Result: exit-code) since Thu 2023-03-02 12:58:04 UTC; 4min 44s ago
    Where: /data
     What: /dev/disk/by-partlabel/userdata
  Process: 1155 ExecMount=/bin/mount /dev/disk/by-partlabel/userdata /data -t ext4 -o noatime,nosuid,nodev,barrier=1,data=ordered,noaut

Mar 02 12:58:04 m0054 systemd[1]: Mounting /data...
Mar 02 12:58:04 m0054 mount[1155]: mount: /data: wrong fs type, bad option, bad superblock on /dev/sda8, missing codepage or helper pro
Mar 02 12:58:04 m0054 systemd[1]: data.mount: Mount process exited, code=exited status=32
Mar 02 12:58:04 m0054 systemd[1]: data.mount: Failed with result 'exit-code'.
Mar 02 12:58:04 m0054 systemd[1]: Failed to mount /data.

Additionally dmesg says the following:

EXT4-fs (sda8): VFS: Can't find ext4 filesystem

Running the mount command manually:

voxl2:/$ /bin/mount /dev/disk/by-partlabel/userdata /data -t ext4 -o noatime,nosuid,nodev,barrier=1,data=ordered,noauto_da_alloc,discard,x-systemd.automount,x-systemd.growfs,rootcontext=system_u:object_r:data_t:s0
mount: /data: wrong fs type, bad option, bad superblock on /dev/sda8, missing codepage or helper program, or other error.

/data is actually mounted and I am able to write to it, this is the first time I have encountered this problem. How can it be fixed?

Thanks for the hint @Alex-Gardner, I tried two separate modules on 3.3.0, 3.6.0, and 3.8.0 and they worked just fine, it is only with system image 4.0.0 and voxl-sdk 0.9 that neither one works which makes me conclude that it's not the sensor but something with the software. Also both modules works just fine when run by themselves, it is only in conjunction with other sensors like stereo/tof that the hires is causing issues.

Hi @Alex-Gardner I'm trying to accomplish the same thing as the OP but I'm running into some problems (my thread: https://forum.modalai.com/topic/1703/non-standard-camera-configuration-on-voxl-running-4-0-0-0-9-4). When connecting the stereo to J3 and hires to J4 voxl-camera-server -l outputs only two cameras which are the stereo, it does not recognize hires unless its on J2 but that has its own slew of problems which I've gone into more detail in my thread. Any help with this would be appreciated.