question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

'//Disk init fail!\r\n'

See original GitHub issue

Going pretty mad with this one as I’ve tried everything I can within the couple of guides and relevant issues I’ve found. Three fresh installs and a scouring of the issue reports on here, but nothing. I’ve checked issues other issues: #152 #235 #340

I am essentially having the same issue as #152. When I run a print file, I get an error like this:

Traceback (most recent call last):
  File "/opt/venvs/mariner3d/lib/python3.7/site-packages/flask/app.py", line 1950, in full_dispatch_request
    rv = self.dispatch_request()
  File "/opt/venvs/mariner3d/lib/python3.7/site-packages/flask/app.py", line 1936, in dispatch_request
    return self.view_functions[rule.endpoint](**req.view_args)
  File "/opt/venvs/mariner3d/lib/python3.7/site-packages/mariner/server/api.py", line 208, in printer_command
    elegoo_mars.start_printing(filename)
  File "/opt/venvs/mariner3d/lib/python3.7/site-packages/mariner/mars.py", line 132, in start_printing
    self.select_file(filename)
  File "/opt/venvs/mariner3d/lib/python3.7/site-packages/mariner/mars.py", line 111, in select_file
    raise UnexpectedPrinterResponse(response)
mariner.exceptions.UnexpectedPrinterResponse: //Disk init fail!

I believe this to be down to mounting the virtual USB but I’m not sure where I’m going wrong.

This is on a Phrozen 4K Mini. My wiring is fine, hardware in general is fine (tried two boards, alternative power sources and get a different error in Mariner when I remove the jumpers entirely, which indicates to me that this is an issue with how I’ve set up my Pis.

Here’re my important files: (Mostly checked against #152 so you might see a few small bits not in the official guide)

/boot/cmdline.txt

dwc_otg.lpm_enable=0 console=tty1 root=PARTUUID=b9509d4a-02 rootfstype=ext4 elevator=deadline fsck.repair=yes rootwait modules-load=dwc2 quiet splash

/boot/config.txt […]

[all]
#dtoverlay=vc4-fkms-v3d

# Enable UART
dtoverlay=dwc2
start_x=1
enable_uart=1

gpu_mem=128

/etc/fstab

proc            /proc           proc    defaults          0       0
PARTUUID=b9509d4a-01  /boot           vfat    defaults          0       2
PARTUUID=b9509d4a-02  /               ext4    defaults,noatime  0       1
# a swapfile is not a swap partition, no line here
#   use  dphys-swapfile swap[on|off]  for that
/piusb.bin /mnt/usb_share vfat users,gid=mariner,umask=002 0 2

/etc/rc.local

#!/bin/sh -e
#
# rc.local
#
# This script is executed at the end of each multiuser runlevel.
# Make sure that the script will "" on success or any other
# value on error.
#
# In order to enable or disable this script just change the execution
# bits.
#
# By default this script does nothing.

# Print the IP address
_IP=$(hostname -I) || true
if [ "$_IP" ]; then
  printf "My IP address is %s\n" "$_IP"
fi


/bin/sleep 5

modprobe g_mass_storage file=/piusb.bin removable=1 ro=1 stall=0 removable=1

    /sbin/iwconfig wlan0 power off

    exit 0

dmesg

[    9.754791] EXT4-fs (mmcblk0p2): re-mounted. Opts: (null)
[   10.467858] systemd-journald[88]: Received request to flush runtime journal from PID 1
[   10.892785] FAT-fs (loop0): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
[   12.852908] mc: Linux media interface: v0.10
[   13.013706] vc_sm_cma: module is from the staging directory, the quality is unknown, you have been warned.
[   13.016375] bcm2835_vc_sm_cma_probe: Videocore shared memory driver
[   13.039833] [vc_sm_connected_init]: start
[   13.067315] [vc_sm_connected_init]: installed successfully
[   13.097154] videodev: Linux video capture interface: v2.00
[   13.190277] bcm2835_mmal_vchiq: module is from the staging directory, the quality is unknown, you have been warned.
[   13.193296] bcm2835_mmal_vchiq: module is from the staging directory, the quality is unknown, you have been warned.
[   13.194878] bcm2835_mmal_vchiq: module is from the staging directory, the quality is unknown, you have been warned.
[   13.213886] bcm2835_v4l2: module is from the staging directory, the quality is unknown, you have been warned.
[   13.225234] bcm2835_isp: module is from the staging directory, the quality is unknown, you have been warned.
[   13.235887] snd_bcm2835: module is from the staging directory, the quality is unknown, you have been warned.
[   13.248408] bcm2835_audio bcm2835_audio: there is not valid maps for state default
[   13.290120] bcm2835_codec: module is from the staging directory, the quality is unknown, you have been warned.
[   13.910036] bcm2835-isp bcm2835-isp: Device node output[0] registered as /dev/video13
[   13.910234] bcm2835-codec bcm2835-codec: Device registered as /dev/video10
[   13.910809] bcm2835-codec bcm2835-codec: Loaded V4L2 decode
[   13.912206] bcm2835-isp bcm2835-isp: Device node capture[0] registered as /dev/video14
[   13.912974] bcm2835-isp bcm2835-isp: Device node capture[1] registered as /dev/video15
[   13.914032] bcm2835-isp bcm2835-isp: Device node stats[2] registered as /dev/video16
[   13.914095] bcm2835-isp bcm2835-isp: Register output node 0 with media controller
[   13.914133] bcm2835-isp bcm2835-isp: Register capture node 1 with media controller
[   13.914165] bcm2835-isp bcm2835-isp: Register capture node 2 with media controller
[   13.914194] bcm2835-isp bcm2835-isp: Register capture node 3 with media controller
[   13.916014] bcm2835-codec bcm2835-codec: Device registered as /dev/video11
[   13.916089] bcm2835-codec bcm2835-codec: Loaded V4L2 encode
[   13.940950] bcm2835-isp bcm2835-isp: Loaded V4L2 bcm2835-isp
[   14.037392] bcm2835-codec bcm2835-codec: Device registered as /dev/video12
[   14.037470] bcm2835-codec bcm2835-codec: Loaded V4L2 isp
[   15.098602] cfg80211: Loading compiled-in X.509 certificates for regulatory database
[   15.500805] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
[   16.152702] brcmfmac: F1 signature read @0x18000000=0x1541a9a6
[   16.176978] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43430-sdio for chip BCM43430/1
[   16.177406] usbcore: registered new interface driver brcmfmac
[   16.265944] brcmfmac mmc1:0001:1: Direct firmware load for brcm/brcmfmac43430-sdio.raspberrypi,model-zero-w.txt failed with error -2
[   16.542642] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43430-sdio for chip BCM43430/1
[   16.542857] brcmfmac: brcmf_c_process_clm_blob: no clm_blob available (err=-2), device may have limited channels available
[   16.544056] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM43430/1 wl0: Oct 22 2019 01:59:28 version 7.45.98.94 (r723000 CY) FWID 01-3b33decd
[   23.446874] random: crng init done
[   23.446910] random: 7 urandom warning(s) missed due to ratelimiting
[   23.970650] uart-pl011 20201000.serial: no DMA platform data
[   24.414629] 8021q: 802.1Q VLAN Support v1.8
[   25.268841] Adding 102396k swap on /var/swap.  Priority:-2 extents:1 across:102396k SSFS
[   25.710336] brcmfmac: brcmf_cfg80211_set_power_mgmt: power save enabled
[   28.572533] Bluetooth: Core ver 2.22
[   28.572739] NET: Registered protocol family 31
[   28.572755] Bluetooth: HCI device and connection manager initialized
[   28.586561] Bluetooth: HCI socket layer initialized
[   28.586599] Bluetooth: L2CAP socket layer initialized
[   28.586668] Bluetooth: SCO socket layer initialized
[   28.602806] Bluetooth: HCI UART driver ver 2.3
[   28.602836] Bluetooth: HCI UART protocol H4 registered
[   28.602982] Bluetooth: HCI UART protocol Three-wire (H5) registered
[   28.603271] Bluetooth: HCI UART protocol Broadcom registered
[   29.268963] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[   29.757124] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[   29.757151] Bluetooth: BNEP filters: protocol multicast
[   29.757185] Bluetooth: BNEP socket layer initialized
[   41.866698] Mass Storage Function, version: 2009/09/11
[   41.866732] LUN: removable file: (no medium)
[   41.866920] LUN: removable read only file: /piusb.bin
[   41.866939] Number of LUNs=1
[   41.886668] g_mass_storage gadget: Mass Storage Gadget, version: 2009/09/11
[   41.886700] g_mass_storage gadget: userspace failed to provide iSerialNumber
[   41.886712] g_mass_storage gadget: g_mass_storage ready
[   41.886733] dwc2 20980000.usb: bound driver g_mass_storage
[   41.912809] brcmfmac: brcmf_cfg80211_set_power_mgmt: power save disabled

Issue Analytics

  • State:closed
  • Created 2 years ago
  • Comments:6

github_iconTop GitHub Comments

1reaction
KTheMancommented, Apr 10, 2021

(weird thing is the install script I used on this last-ditch effort - https://github.com/KTheMan/Mariner-Autoinstaller - should apparently have allocated ‘all available space’ to the virtual USB, but it looks like it’s been allocated much less).

Little bit of misinterpretation there. It’s expanding the filesystem of Raspbian Lite to the whole microSD card, and not the virtual USB unfortunately. If you’re looking to add a larger amount of space to that virtual USB you can change the size line 116 (in the script) from its default of 4096 (which shows as 4.0G when you ran df -h) sudo dd bs=1M if=/dev/zero of=/piusb.bin count={Your_Virt_USB_Size_Here}

Have you tried plugging your micro USB end into the other port on your Pi Zero?

0reactions
drashnacommented, Apr 10, 2021

I’m running into the same issue. Rebooting the pi fixed the issue for me, though.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Newly inserted disk shows as failed - NetApp Knowledge Base
Newly inserted disk is showed as failed in sysconfig -a; disk show -broken reports it as init failed; event log reported the following...
Read more >
Can't Initialize Disk: 4 Ways to Fix or Force Your Drive
3. Try fixing the drive · Open Disk Management (as explained in the first solution). · Right-click on the affected disk and open...
Read more >
[Solved] Disk Unknown Not Initialized in Windows 10/8/7
1. How do I fix disk 1 unknown not initialized? · Initialize the disk with Disk Management · Recover data from the unknown...
Read more >
The hard drive is unknown, not initialized. How to recover the ...
Among the main reasons for disk initialization error, we can distinguish the following: operating system failures, faulty connection cables, physical damage of ...
Read more >
'//Disk init fail!\r\n' · Issue #152 · luizribeiro/mariner - GitHub
Make sure your /piusb.bin was formatted as FAT32 (i.e. mkdosfs /piusb.bin -F 32 -I ). I know that the Mars has trouble reading...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found