On 11/11/21 18:20, Jonathon Pendlum wrote:
Hey Rob,

Did you use bmaptool to write the image to your SD card? I ran into the
same issue when using bmaptool. I switched to using dd instead and that
fixed the issue.

Figure out the underlying issue, don't use dd. Seriously, dd eats hard drives if you make a typing mistake.

Philip



Jonathon

On Thu, Nov 11, 2021, 18:00 Rob Kossler <rkoss...@nd.edu> wrote:

Hi,
I'm having some issues with my E310 related to booting up the file system
(UHD 4.1 file system loaded using bmaptool). Any help appreciated!

    - Issue 1: during boot up, E310 linux fails mounting the /data
    partition and consequently doesn't configure the Ethernet correctly (such
    that I can't login via ssh) (see below startup log from console window).
       - Note that I can look at the micro SD card on my Ubuntu host and I
       see 4 partitions: /uboot, /data, & the 2 OS partitions.  Everything looks
       OK.
       - I'm starting to suspect a bad micro SD card, but I don't have
       solid reasoning for that.
    - Issue 2: when I'm in this failed startup state, I can use "ip addr
    add" to configure the eth0 device but I can't figure out how to restart the
    sshd so that I can ssh into it (note I can ssh out just fine after setting
    the IP addr). Does anyone know how to do so?
    - Issue 3: I can't figure out how to set the real-time clock.  If I
    run "date" after bootup, it shows "Aug 6".  I can fix this, but upon
    reboot, it is back to "Aug 6".  If I run "hwclock", it says it can't find
    the hwclock. Does anyone know how to set the time in a non-volatile way
    such that it won't be "Aug 6" after a power cycle.

Rob


*Bootup Console Log*
[  OK  ] Found device /dev/mmcblk0p1.
[  OK  ] Found device /dev/mmcblk0p4.
          Starting File System Check on /dev/mmcblk0p1...
          Starting File System Check on /dev/mmcblk0p4...
[  OK  ] Started File System Check on /dev/mmcblk0p1.
          Mounting /uboot...
[  OK  ] Mounted /uboot.
[FAILED] Failed to start File System Check on /dev/mmcblk0p4.
See 'systemctl status systemd-fsck@dev-mmcblk0p4.service' for details.
[DEPEND] Dependency failed for /data.
[DEPEND] Dependency failed for Local File Systems.
[DEPEND] Dependency failed for Grow File System on /data.
[  OK  ] Stopped Dispatch Password …ts to Console Directory Watch.
[  OK  ] Stopped Forward Password R…uests to Wall Directory Watch.

*hwclock output*
sh-5.0# hwclock --verbose
hwclock from util-linux 2.34
System Time: 1628268135.768399
Trying to open: /dev/rtc0
Trying to open: /dev/rtc
Trying to open: /dev/misc/rtc
No usable clock interface found.
hwclock: Cannot access the Hardware Clock via any known method.
_______________________________________________
USRP-users mailing list -- usrp-users@lists.ettus.com
To unsubscribe send an email to usrp-users-le...@lists.ettus.com



_______________________________________________
USRP-users mailing list -- usrp-users@lists.ettus.com
To unsubscribe send an email to usrp-users-le...@lists.ettus.com

_______________________________________________
USRP-users mailing list -- usrp-users@lists.ettus.com
To unsubscribe send an email to usrp-users-le...@lists.ettus.com

Reply via email to