# VOXL 2 /data mount error

Source: https://forum.modalai.com/topic/3144/voxl-2-data-mount-error
Category: General Questions (https://forum.modalai.com/category/2/general-questions)
Posted: 2024-02-23 22:40:24 UTC by czarsimon
Replies: 6 · Views: 1589

## czarsimon · 2024-02-23 22:40:24 UTC

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?

## Reply by tom (ModalAI staff) · 2024-02-23 22:47:10 UTC

@czarsimon Are you having this issue on every reboot?

## Reply by czarsimon · 2024-02-23 23:34:46 UTC (in reply to tom)

@tom said in [VOXL 2 /data mount error](/post/14899):
> @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.

## Reply by tom (ModalAI staff) · 2024-02-26 00:27:59 UTC (in reply to czarsimon)

@czarsimon Have you tried flashing the latest SDK using the full "wipe all partitions option"?

`./install.sh -w`

## Reply by czarsimon · 2024-02-26 08:06:01 UTC (in reply to tom)

@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`

## Reply by czarsimon · 2024-02-26 08:37:52 UTC (in reply to tom)

@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.

## Reply by tom (ModalAI staff) · 2024-02-26 17:30:13 UTC (in reply to czarsimon)

@czarsimon Interesting, I've never seen it get stuck during flashing like that. Can you try forcing it into fastboot with the button (https://docs.modalai.com/voxl2-voxl2-mini-system-image/#force-voxl-2-into-fastboot) and then using `./install.sh -w`