Jump to content

[Odroid HC2] Sata install


kingi

Recommended Posts

I tried to install armbian to my internal sata drive (SSD: Samsung Evo 850).
But the device fails to boot after the root fs is moved.

I used the command nand-sata-install with following option:
Boot from SD   - system on SATA or USB

 

I tried different filesystem formats (ext4, btrfs) and armbian builds:
Armbian_5.37_Odroidxu4_Debian_jessie_next_4.9.71 (stable)
Armbian_5.37_Odroidxu4_Ubuntu_xenial_next_4.9.71 (stable)
Armbian_5.41_Odroidxu4_Debian_stretch_next_4.9.83 (self-built)

 

I dont have a terminal adapter to access the boot logs.
Any hints how to get additional information or to fix this issue?

Link to comment
Share on other sites

On 3/1/2018 at 1:37 PM, kingi said:

I dont have a terminal adapter to access the boot logs.

Sure you do -

https://docs.armbian.com/User-Guide_Fine-Tuning/#how-to-toogle-verbose-boot

Follow the instructions in that and the next section to get a boot log file.

 

Many times an OP may ask you to provide the dmesg output ...

root@c2~#dmesg > dmesg.txt

 

Did you try it from inside armbian-config?

 

 

Link to comment
Share on other sites

On 1. 3. 2018 at 7:37 PM, kingi said:

Any hints how to get additional information or to fix this issue?


I made a self-build and it works normally. http://ix.io/UpD


Try this one: https://dl.armbian.com/odroidxu4/Debian_jessie_next.7z

I hope you are not removing SD card after the process is finished? The bootloader can only be loaded from SD card.

Link to comment
Share on other sites

18 hours ago, Technicavolous said:

Sure you do -

https://docs.armbian.com/User-Guide_Fine-Tuning/#how-to-toogle-verbose-boot

Follow the instructions in that and the next section to get a boot log file.

 

Many times an OP may ask you to provide the dmesg output ...

root@c2~#dmesg > dmesg.txt

 

Did you try it from inside armbian-config?

 

 

Thanks I will try that option on my next retry. Are the logs stored on sd or on the sata drive?
I checked both locations the last time, but didnt find anything useful (maybe more luck with verbose configuration).

 

Yes, I tried both armbian-config and the direct execution of nand-sata-install.

 

17 hours ago, Igor said:


I made a self-build and it works normally. http://ix.io/UpD


Try this one: https://dl.armbian.com/odroidxu4/Debian_jessie_next.7z

I hope you are not removing SD card after the process is finished? The bootloader can only be loaded from SD card.

 

Thanks for the information. I will retry with this version.
No, I didnt remove the SD card. Just rebooted after script finished without errors.

Link to comment
Share on other sites

7 hours ago, kingi said:

I will retry with this version.


This one was tested yesterday and if it does not work, check the hardware. I used first option - an ext4 rootfs partition.

Link to comment
Share on other sites

I retried with your suggested version:
Armbian_5.41_Odroidxu4_Debian_jessie_next_4.9.86.img

 

But still it didnt work.

I also used an ext4 rootfs and increased the boot log verbositiy to 7.

 

There were no errors in /var/log/nand-sata-install.log.
The only errors (pre-reboot) were in /var/log/syslog:

Mar 10 11:36:26 localhost kernel: [  218.364181] EXT4-fs (sda1): Unrecognized mount option "compress-force=zlib" or missing value
Mar 10 11:36:26 localhost kernel: [  218.389349] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null)

 

After reboot (soft/hard) the device didnt respond over network anymore.
There were no new entries to the logs (neither sdcard nor sata).

 

The sata device works without problems.

Maybe I will buy an uart adpater to check the terminal.

 

Link to comment
Share on other sites

I  got the same installation problem with Armbian_5.41_Odroidxu4_Debian_jessie_next_4.9.86.img on a SATA HD connected to an Odroid HC-1.

 

Tried twice to move rootfs to no avail (ext4 rootfs partition). The green light blinked continuously and the device wasn't reachable anymore over network. I haven't got an uart adapter to check what it's wrong.

 

I finally succeeded at the first attempt with Armbian_5.37_Odroidxu4_Debian_jessie_next_4.9.71.img.

Link to comment
Share on other sites

Hmm, strange. I'll try to replicate - I suspect network failed to initialize but why ... what about with a default or DEV kernel? Can you try to power cycle this 4.9.86 build?

Link to comment
Share on other sites

Hmm, really strange. I retried:

Booted from sd card -> change boot to ssd -> Reboot -> Works.

Rebooted several times and after third reboot, I was unable to connect by network.

Power cyled -> unable to connect (3x times).

Changed back to sd boot -> Works.

Link to comment
Share on other sites

I run into the same issue. My system consists out of:

  • Odroid HC1
  • SDCard: 32GB Scandisk Ultra
  • SSD: Samsung EVO 860 250GB
  • Armbian image: Armbian_5.41_Odroidxu4_Debian_jessie_next_4.9.86

Running a fresh Armbian installation on the sdcard is working flawless. Once I use  armbian-conf/system/install (nand-sata-install) to move the system to my SSD my system ends up in a loop during boot. See below how my HC1 boots using UART:

U-Boot 2017.05-armbian (Mar 09 2018 - 06:06:57 +0100) for ODROID-XU4

CPU:   Exynos5422 @ 800 MHz
Model: Odroid XU4 based on EXYNOS5422
Board: Odroid XU4 based on EXYNOS5422
Type:  xu4
DRAM:  2 GiB
MMC:   EXYNOS DWMMC: 0, EXYNOS DWMMC: 1
MMC Device 0 ( SD ): 29.7 GiB
Card did not respond to voltage select!
mmc_init: -95, time 11
*** Warning - bad CRC, using default environment

In:    serial
Out:   serial
Err:   serial
Net:   No ethernet found.
Press quickly 'Enter' twice to stop autoboot:  0
** Unrecognized filesystem type **
** File not found /boot.ini **
12400 bytes read in 19 ms (636.7 KiB/s)
cfgload addr = 0x50000000, Loading boot.ini from ext4 0:1 /boot/boot.ini
cfgload: applying boot.ini...
cfgload: setenv initrd_high "0xffffffff"
cfgload: setenv fdt_high "0xffffffff"
cfgload: setenv macaddr "00:1e:06:61:7a:55"
cfgload: setenv rootdev UUID=ed131532-0780-430a-8441-53df7188b6c5
cfgload: setenv rootfstype ext4
cfgload: setenv console "both"
cfgload: setenv verbosity "1"
cfgload: if ext4load mmc 0:1 0x44000000 /boot/armbianEnv.txt || fatload mmc 0:1 0x44000000 armbianEnv.txt || ext4load mmc 0:1 0x44000000 armbianEnv.txt; then env import -t 0x44000000 ${filesize}; fi
** File not found /boot/armbianEnv.txt **
** Unrecognized filesystem type **
** File not found armbianEnv.txt **
cfgload: if test "${console}" = "display" || test "${console}" = "both"; then setenv consoleargs "console=tty1"; fi
cfgload: if test "${console}" = "serial" || test "${console}" = "both"; then setenv consoleargs "${consoleargs} console=ttySAC2,115200n8"; fi
cfgload: setenv bootrootfs "${consoleargs} consoleblank=0 loglevel=${verbosity} panic=10 root=${rootdev} rootfstype=${rootfstype} rootwait rw"
cfgload: setenv vout "hdmi"
cfgload: setenv cecenable "false" # false or true
cfgload: setenv governor "performance"
cfgload: setenv ddr_freq 825
cfgload: setenv HPD "true"
cfgload: setenv hdmi_tx_amp_lvl  "31"
cfgload: setenv hdmi_tx_lvl_ch0      "3"
cfgload: setenv hdmi_tx_lvl_ch1      "3"
cfgload: setenv hdmi_tx_lvl_ch2      "3"
cfgload: setenv hdmi_tx_emp_lvl      "6"
cfgload: setenv hdmi_clk_amp_lvl     "31"
cfgload: setenv hdmi_tx_res      "0"
cfgload: setenv hdmi_phy_control "hdmi_tx_amp_lvl=${hdmi_tx_amp_lvl} hdmi_tx_lvl_ch0=${hdmi_tx_lvl_ch0} hdmi_tx_lvl_ch1=${hdmi_tx_lvl_ch1} hdmi_tx_lvl_ch2=${hdmi_tx_lvl_ch2} hdmi_tx_emp_lvl=${hdmi_tx_emp_lvl} hdmi_clk_amp_lvl=${hdmi_clk_amp_lvl} hdmi_tx_res=${hdmi_tx_res} HPD=${HPD} vout=${vout}"
cfgload: ext4load mmc 0:1 0x40008000 /boot/zImage || fatload mmc 0:1 0x40008000 zImage || ext4load mmc 0:1 0x40008000 zImage
6062464 bytes read in 486 ms (11.9 MiB/s)
cfgload: ext4load mmc 0:1 0x42000000 /boot/uInitrd || fatload mmc 0:1 0x42000000 uInitrd || ext4load mmc 0:1 0x42000000 uInitrd
4091659 bytes read in 338 ms (11.5 MiB/s)
cfgload: if test "${board_name}" = "xu4"; then setenv fdtfile "exynos5422-odroidxu4.dtb"; fi
cfgload: if test "${board_name}" = "xu3"; then setenv fdtfile "exynos5422-odroidxu3.dtb"; fi
cfgload: if test "${board_name}" = "xu3l"; then setenv fdtfile "exynos5422-odroidxu3-lite.dtb"; fi
cfgload: if ext4load mmc 0:1 0x00000000 "/boot/.next" || fatload mmc 0:1 0x00000000 ".next"  || ext4load mmc 0:1 0x00000000 ".next"; then echo "Found mainline kernel configuration"; else setenv fdtfile "exynos5422-odroidxu3.dtb"; fi
0 bytes read in 16 ms (0 Bytes/s)
Found mainline kernel configuration
cfgload: ext4load mmc 0:1 0x44000000 /boot/dtb/${fdtfile} || fatload mmc 0:1 0x44000000 dtb/${fdtfile} || ext4load mmc 0:1 0x44000000 dtb/${fdtfile}
61714 bytes read in 64 ms (941.4 KiB/s)
cfgload: fdt addr 0x44000000
cfgload: if test "${cecenable}" = "false"; then fdt rm /cec@101B0000; fi
cfgload: setenv bootargs "${bootrootfs} ${videoconfig} smsc95xx.macaddr=${macaddr} governor=${governor} ${hdmi_phy_control} usb-storage.quirks=${usbstoragequirks} ${extraargs}"
cfgload: dmc ${ddr_freq}
cfgload: bootz 0x40008000 0x42000000 0x44000000
Kernel image @ 0x40008000 [ 0x000000 - 0x5c8180 ]
## Loading init Ramdisk from Legacy Image at 42000000 ...
   Image Name:   uInitrd
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    4091595 Bytes = 3.9 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
## Flattened Device Tree blob at 44000000
   Booting using the fdt blob at 0x44000000
   Using Device Tree in place at 44000000, end 44012111

Starting kernel ...

Loading, please wait...
Begin: Loading essential drivers ... done.
Begin: Running /scripts/init-premount ... done.
Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done.
Begin: Running /scripts/local-premount ... Scanning for Btrfs filesystems
done.
Begin: Waiting for root file system ... Begin: Running /scripts/local-block ... done.
done.
Begin: Will now check root file system ... fsck from util-linux 2.25.2
[/sbin/fsck.ext4 (1) -- /dev/sda1] fsck.ext4 -a -C0 /dev/sda1
/dev/sda1: clean, 37907/15269888 files, 1235827/61049633 blocks
done.
done.
Begin: Running /scripts/local-bottom ... done.
Begin: Running /scripts/init-bottom ... done.

Welcome to Debian GNU/Linux 8 (jessie)!

         Expecting device dev-ttySAC2.device...
[  OK  ] Reached target Remote File Systems (Pre).
[  OK  ] Reached target Encrypted Volumes.
[  OK  ] Reached target Paths.
[  OK  ] Set up automount Arbitrary Executable File Formats F...utomount Point.
         Expecting device dev-disk-by\x2duuid-0ad83cb2\x2dcc5...ad17c.device...
[  OK  ] Created slice Root Slice.
[  OK  ] Listening on /dev/initctl Compatibility Named Pipe.
[  OK  ] Listening on Delayed Shutdown Socket.
[  OK  ] Listening on Journal Socket (/dev/log).
[  OK  ] Created slice User and Session Slice.
[  OK  ] Listening on udev Control Socket.
[  OK  ] Listening on udev Kernel Socket.
[  OK  ] Listening on Journal Socket.
[  OK  ] Created slice System Slice.
[  OK  ] Created slice system-systemd\x2dfsck.slice.
         Starting Increase datagram queue length...
         Starting Restore / save the current clock...
         Starting Nameserver information manager...
         Mounting Debug File System...
         Starting udev Coldplug all Devices...
         Starting Create list of required static device nodes...rrent kernel...
         Mounting POSIX Message Queue File System...
[  OK  ] Created slice system-serial\x2dgetty.slice.
[  OK  ] Created slice system-getty.slice.
         Starting Load Kernel Modules...
[  OK  ] Reached target Slices.
[  OK  ] Mounted POSIX Message Queue File System.
[  OK  ] Mounted Debug File System.
[  OK  ] Started Increase datagram queue length.
[  OK  ] Started Restore / save the current clock.
[  OK  ] Started Create list of required static device nodes ...current kernel.
[  OK  ] Started Load Kernel Modules.
[  OK  ] Started Nameserver information manager.
[  OK  ] Started udev Coldplug all Devices.
         Mounting FUSE Control File System...
         Starting Apply Kernel Variables...
         Mounting Configuration File System...
         Starting Create Static Device Nodes in /dev...
[  OK  ] Listening on Syslog Socket.
[  OK  ] Mounted Configuration File System.
[  OK  ] Mounted FUSE Control File System.
[  OK  ] Started Apply Kernel Variables.
[  OK  ] Started Create Static Device Nodes in /dev.
         Starting udev Kernel Device Manager...
[  OK  ] Started udev Kernel Device Manager.
         Starting Copy rules generated while the root was ro...
         Starting LSB: Set preliminary keymap...
         Starting LSB: Tune IDE hard disks...
[  OK  ] Started Copy rules generated while the root was ro.
[  OK  ] Started LSB: Tune IDE hard disks.
[  OK  ] Found device /dev/ttySAC2.
[  OK  ] Found device /dev/disk/by-uuid/0ad83cb2-cc57-4b0e-bf45-b722be0ad17c.
         Starting File System Check on /dev/disk/by-uuid/0ad8...b722be0ad17c...
[  OK  ] Reached target Sound Card.
[  OK  ] Started LSB: Set preliminary keymap.
         Starting Remount Root and Kernel File Systems...
[  OK  ] Started Remount Root and Kernel File Systems.
         Activating swap /var/swap...
[  OK  ] Reached target Local File Systems (Pre).
         Mounting /tmp...
[   73.913360] EXT4-fs error (device sda1): __ext4_get_inode_loc:4363: inode #12976129: block 51904544: comm systemd: unable to read itable block
[   73.913398] EXT4-fs error (device sda1): ext4_find_entry:1469: inode #10879130: comm systemd-udevd: reading directory lblock 0
[   73.913654] EXT4-fs (sda1): Remounting filesystem read-only
[   73.942151] EXT4-fs error (device sda1): __ext4_get_inode_loc:4363: inode #12976129: block 51904544: comm systemd: unable to read itable block
         Starting Load/Save Random Seed...
[   73.984204] EXT4-fs error (device sda1): __ext4_get_inode_loc:4363: inode #12976129: block 51904544: comm mount: unable to read itable block
[   73.996366] EXT4-fs error (device sda1): __ext4_get_inode_loc:4363: inode #12976129: block 51904544: comm mount: unable to read itable block
[  OK  ] Started File System Check on /dev/disk/by-uuid/0ad83...5-b722be0ad17c.
[FAILED] Failed to activate swap /var/swap.
See 'systemctl status var-swap.swap' for details.
[DEPEND] Dependency failed for Swap.
[FAILED] Failed to mount /tmp.
See 'systemctl status tmp.mount' for details.
[DEPEND] Dependency failed for Local File Systems.
[FAILED] Failed to start Load/Save Random Seed.
See 'systemctl status systemd-random-seed.service' for details.
[  OK  ] Stopped Serial Getty on ttySAC2.
[  OK  ] Stopped Getty on tty1.
[  OK  ] Stopped getty on tty2-tty6 if dbus and logind are not available.
[  OK  ] Stopped target Graphical Interface.
[  OK  ] Stopped Entropy daemon using the HAVEGE algorithm.
[  OK  ] Stopped target Multi-User System.
[  OK  ] Stopped Regular background program processing daemon.
[  OK  ] Stopped OpenBSD Secure Shell server.
[  OK  ] Stopped Network Manager.
[  OK  ] Stopped /etc/rc.local Compatibility.
[  OK  ] Stopped Permit User Sessions.
[  OK  ] Stopped D-Bus System Message Bus.
[  OK  ] Stopped Login Service.
[  OK  ] Closed D-Bus System Message Bus Socket.
[  OK  ] Reached target Login Prompts.
[  OK  ] Stopped LSB: Start NTP daemon.
[  OK  ] Stopped LSB: Advanced IEEE 802.11 management daemon.
[  OK  ] Stopped LSB: Start/stop sysstat's sadc.
[  OK  ] Stopped LSB: Set sysfs variables from /etc/sysfs.conf.
[  OK  ] Stopped LSB: set CPUFreq kernel parameters.
[  OK  ] Stopped LSB: disk temperature monitoring daemon.
[  OK  ] Stopped LSB: start DirMngr daemon.
[  OK  ] Stopped LSB: Load kernel modules needed to enable cpufreq scaling.
[  OK  ] Reached target Remote File Systems.
[  OK  ] Stopped LSB: Armbian gathering hardware information.
[  OK  ] Stopped System Logging Service.
[  OK  ] Stopped target Basic System.
[  OK  ] Reached target Timers.
[  OK  ] Stopped target System Initialization.
         Starting Restore Sound Card State...
         Starting Create Volatile Files and Directories...
         Starting LSB: Prepare console...
         Starting LSB: Raise network interfaces....
[   74.861480] EXT4-fs error (device sda1): ext4_find_entry:1469: inode #14286890: comm kbd: reading directory lblock 0
[   74.870845] EXT4-fs error (device sda1): ext4_find_entry:1469: inode #14286890: comm kbd: reading directory lblock 0
         Starting Armbian enhanced Log2Ram...
[  OK  ] Closed Syslog Socket.
[  OK  ] Reached target Sockets.
         Starting Emergency Shell...
[  OK  ] Started Emergency Shell.
[  OK  ] Reached target Emergency Mode.
         Mounting /media/mmcboot...
[   75.027218] EXT4-fs error (device sda1): __ext4_get_inode_loc:4363: inode #1572865: block 6291488: comm systemd: unable to read itable block
[   75.038482] EXT4-fs error (device sda1): __ext4_get_inode_loc:4363: inode #1572865: block 6291488: comm systemd: unable to read itable block
[   75.051023] EXT4-fs error (device sda1): __ext4_get_inode_loc:4363: inode #1572865: block 6291488: comm systemd: unable to read itable block
[  OK  ] Started Restore Sound Card State.
[  OK  ] Started LSB: Prepare console.
[  OK  ] Started LSB: Raise network interfaces..
[FAILED] Failed to mount /media/mmcboot.
See 'systemctl status media-mmcboot.mount' for details.
[DEPEND] Dependency failed for /boot.
[  OK  ] Reached target Network.
[  OK  ] Reached target Network is Online.
         Starting LSB: Set console font and keymap...
[  OK  ] Started LSB: Set console font and keymap.
[   80.001231] EXT4-fs error (device sda1): __ext4_get_inode_loc:4363: inode #10616833: block 42467360: comm (plymouth): unable to read itable block
[   84.962063] EXT4-fs error (device sda1): ext4_find_entry:1469: inode #4456457: comm systemd-tmpfile: reading directory lblock 0
[   84.973012] EXT4-fs error (device sda1): __ext4_get_inode_loc:4363: inode #12976129: block 51904544: comm systemd-tmpfile: unable to read itable block
[   90.103613] EXT4-fs error (device sda1): __ext4_get_inode_loc:4363: inode #10616833: block 42467360: comm (echo): unable to read itable block
[   95.197807] EXT4-fs error (device sda1): __ext4_get_inode_loc:4363: inode #12976129: block 51904544: comm systemd-tmpfile: unable to read itable block
[   95.210996] EXT4-fs error (device sda1): __ext4_get_inode_loc:4363: inode #12976129: block 51904544: comm systemd-tmpfile: unable to read itable block
[  105.351764] EXT4-fs error (device sda1): __ext4_get_inode_loc:4363: inode #10616833: block 42467360: comm (sh): unable to read itable block
[  105.437956] EXT4-fs error (device sda1): ext4_find_entry:1469: inode #4456453: comm systemd-tmpfile: reading directory lblock 0
[FAILED] Failed to start Trigger Flushing of Journal to Persistent Storage.
See 'systemctl status systemd-journal-flush.service' for details.
[  OK  ] Stopped Trigger Flushing of Journal to Persistent Storage.
         Stopping Journal Service...
[  OK  ] Stopped Journal Service.
         Starting Journal Service...
[  OK  ] Started Journal Service.
         Starting Trigger Flushing of Journal to Persistent Storage...
[FAILED] Failed to start Trigger Flushing of Journal to Persistent Storage.
See 'systemctl status systemd-journal-flush.service' for details.
[  OK  ] Stopped Trigger Flushing of Journal to Persistent Storage.
         Stopping Journal Service...
[  OK  ] Stopped Journal Service.
         Starting Journal Service...
[  OK  ] Started Journal Service.
         Starting Trigger Flushing of Journal to Persistent Storage...
[   ***] (1 of 2) A start job is running for Create Volatile ... 8s / no limit)[  136.157903] EXT4-fs error (device sda1): ext4_find_entry:1469: inode #4456500: comm systemd-tmpfile: reading directory lblock 0
[FAILED] Failed to start Trigger Flushing of Journal to Persistent Storage.
See 'systemctl status systemd-journal-flush.service' for details.
[  OK  ] Stopped Trigger Flushing of Journal to Persistent Storage.
         Stopping Journal Service...
[  OK  ] Stopped Journal Service.
         Starting Journal Service...
[  OK  ] Started Journal Service.
         Starting Trigger Flushing of Journal to Persistent Storage...
[***   ] (1 of 2) A start job is running for Create Volatile ...19s / no limit)[  146.397826] EXT4-fs error (device sda1): ext4_find_entry:1469: inode #4456457: comm systemd-tmpfile: reading directory lblock 0
         Stopping Journal Service...
[  OK  ] Stopped Journal Service.
         Starting Journal Service...
[  OK  ] Started Journal Service.
[FAILED] Failed to start Trigger Flushing of Journal to Persistent Storage.
See 'systemctl status systemd-journal-flush.service' for details.
[***   ] A start job is running for Create Volatile Files and...29s / no limit)[  156.637790] EXT4-fs error (device sda1): ext4_find_entry:1469: inode #4456457: comm systemd-tmpfile: reading directory lblock 0
[  OK  ] Stopped Trigger Flushing of Journal to Persistent Storage.
         Stopping Journal Service...
[  OK  ] Stopped Journal Service.
         Starting Journal Service...
[  OK  ] Started Journal Service.
         Starting Trigger Flushing of Journal to Persistent Storage...
[FAILED] Failed to start Trigger Flushing of Journal to Persistent Storage.
See 'systemctl status systemd-journal-flush.service' for details.
[  OK  ] Stopped Trigger Flushing of Journal to Persistent Storage.
         Stopping Journal Service...
[  OK  ] Stopped Journal Service.
         Starting Journal Service...
[  OK  ] Started Journal Service.
         Starting Trigger Flushing of Journal to Persistent Storage...
[FAILED] Failed to start Trigger Flushing of Journal to Persistent Storage.
See 'systemctl status systemd-journal-flush.service' for details.
[  OK  ] Stopped Trigger Flushing of Journal to Persistent Storage.
         Stopping Journal Service...
[  OK  ] Stopped Journal Service.
         Starting Journal Service...
[  OK  ] Started Journal Service.
         Starting Trigger Flushing of Journal to Persistent Storage...
[**    ] (2 of 2) A start job is running for Trigger Flushing...(8s / no limit)[  187.357839] EXT4-fs error (device sda1): __ext4_get_inode_loc:4363: inode #12976129: block 51904544: comm systemd-tmpfile: unable to read itable block
[  187.370664] EXT4-fs error (device sda1): __ext4_get_inode_loc:4363: inode #12976129: block 51904544: comm systemd-tmpfile: unable to read itable block
[  187.384043] EXT4-fs error (device sda1): __ext4_get_inode_loc:4363: inode #12976129: block 51904544: comm systemd-tmpfile: unable to read itable block
         Stopping Journal Service...
[  OK  ] Stopped Journal Service.
         Starting Journal Service...
[  OK  ] Started Journal Service.
[FAILED] Failed to start Trigger Flushing of Journal to Persistent Storage.
See 'systemctl status systemd-journal-flush.service' for details.
[***   ] A start job is running for Create Volatile Files and...10s / no limit)[  197.597842] EXT4-fs error (device sda1): __ext4_get_inode_loc:4363: inode #12976129: block 51904544: comm systemd-tmpfile: unable to read itable block
[  197.610702] EXT4-fs error (device sda1): __ext4_get_inode_loc:4363: inode #12976129: block 51904544: comm systemd-tmpfile: unable to read itable block
[  197.624029] EXT4-fs error (device sda1): __ext4_get_inode_loc:4363: inode #12976129: block 51904544: comm systemd-tmpfile: unable to read itable block
[  OK  ] Stopped Trigger Flushing of Journal to Persistent Storage.
         Stopping Journal Service...
[  OK  ] Stopped Journal Service.
         Starting Journal Service...
[  OK  ] Started Journal Service.
         Starting Trigger Flushing of Journal to Persistent Storage...
[    **] (1 of 2) A start job is running for Create Volatile ...20s / no limit)[  207.837784] EXT4-fs error (device sda1): __ext4_get_inode_loc:4363: inode #12976129: block 51904544: comm systemd-tmpfile: unable to read itable block
[  207.850776] EXT4-fs error (device sda1): __ext4_get_inode_loc:4363: inode #12976129: block 51904544: comm systemd-tmpfile: unable to read itable block
[  207.863990] EXT4-fs error (device sda1): __ext4_get_inode_loc:4363: inode #12976129: block 51904544: comm systemd-tmpfile: unable to read itable block
[FAILED] Failed to start Trigger Flushing of Journal to Persistent Storage.
See 'systemctl status systemd-journal-flush.service' for details.
[  OK  ] Stopped Trigger Flushing of Journal to Persistent Storage.
         Stopping Journal Service...
[  OK  ] Stopped Journal Service.
         Starting Journal Service...
[  OK  ] Started Journal Service.
         Starting Trigger Flushing of Journal to Persistent Storage...
[  *** ] (1 of 2) A start job is running for Create Volatile ...30s / no limit)[  218.077811] EXT4-fs error (device sda1): __ext4_get_inode_loc:4363: inode #12976129: block 51904544: comm systemd-tmpfile: unable to read itable block
[  218.090819] EXT4-fs error (device sda1): __ext4_get_inode_loc:4363: inode #12976129: block 51904544: comm systemd-tmpfile: unable to read itable block
[  218.104003] EXT4-fs error (device sda1): __ext4_get_inode_loc:4363: inode #12976129: block 51904544: comm systemd-tmpfile: unable to read itable block
         Stopping Journal Service...
[  OK  ] Stopped Journal Service.
         Starting Journal Service...
[  OK  ] Started Journal Service.
[FAILED] Failed to start Trigger Flushing of Journal to Persistent Storage.
See 'systemctl status systemd-journal-flush.service' for details.
[**    ] A start job is running for Create Volatile Files and...41s / no limit)[  228.317952] EXT4-fs error (device sda1): __ext4_get_inode_loc:4363: inode #12976129: block 51904544: comm systemd-tmpfile: unable to read itable block
[  228.330734] EXT4-fs error (device sda1): __ext4_get_inode_loc:4363: inode #12976129: block 51904544: comm systemd-tmpfile: unable to read itable block
[  228.344238] EXT4-fs error (device sda1): __ext4_get_inode_loc:4363: inode #12976129: block 51904544: comm systemd-tmpfile: unable to read itable block
[  OK  ] Stopped Trigger Flushing of Journal to Persistent Storage.
         Stopping Journal Service...
[  OK  ] Stopped Journal Service.
         Starting Journal Service...
[  OK  ] Started Journal Service.
         Starting Trigger Flushing of Journal to Persistent Storage...
[  *** ] (1 of 2) A start job is running for Create Volatile ...50s / no limit)

Next I have re-installed a fresh image on the SDCard again after which I am able to apply some checks on the SSD.

# lsblk
NAME        MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
mmcblk1     179:0    0  29.7G  0 disk
└─mmcblk1p1 179:1    0  29.4G  0 part /
sda           8:0    0 232.9G  0 disk
└─sda1        8:1    0 232.9G  0 part
# fdisk /dev/sda

Welcome to fdisk (util-linux 2.25.2).
Changes will remain in memory only, until you decide to write them.
Be careful before using the write command.


Command (m for help): p
Disk /dev/sda: 232.9 GiB, 250059350016 bytes, 488397168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 33553920 bytes
Disklabel type: gpt
Disk identifier: 145892EA-EEA0-4E81-B3E6-1EE17BA3C428

Device     Start       End   Sectors   Size Type
/dev/sda1     64 488397134 488397071 232.9G Linux filesystem
# fsck -f /dev/sda1
fsck from util-linux 2.25.2
e2fsck 1.42.12 (29-Aug-2014)
/dev/sda1: recovering journal
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/sda1: 37907/15269888 files (0.1% non-contiguous), 1235827/61049633 blocks

 

Edited by Walker
Link to comment
Share on other sites

It doesn't seem to mount your sda drive? You're certain you can mount, read and write to that drive before the nand-sata install?

 

Using the above noted download, updating the system and setting my network info, when starting the nand-sata install from armbian-config I got a very quick message stating something was missing.  Then it went through what appeared a full install, then flashed another quick message with an error, then told me to reboot. I exited instead and ran armbianmonitor then rebooted and did it again.

 

armbianmonitor -u before reboot gave me 

http://ix.io/19NH

 

and after

http://ix.io/19NK

 

But even after all that ...

root@hc1:~# lsblk
NAME        MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
mmcblk1     179:0    0  29.8G  0 disk 
└─mmcblk1p1 179:1    0  29.5G  0 part /media/mmcboot
sda           8:0    0 111.8G  0 disk 
└─sda1        8:1    0 111.8G  0 part /
root@hc1:~# ls /
bin   dev  home  lost+found  mnt  proc  run   selinux  sys  usr
boot  etc  lib   media       opt  root  sbin  srv      tmp  var
root@hc1:~# 

So it seems to have worked fine for me. I can create directories and store data and copy it elsewhere.

 

The messages in your post show errors with the /dev/sda drive, sda1 not being mounted, etc. "unable to read itable block" points to data corruption or incompatibility? Have you deleted the partition and made a new one? ON the hc1?

 

I do believe armbian-config has its share of issues right now. For instance, on my hc1 I have to use nmtui to set a static address - the armbian-config entry for that always leaves me with a hanging network. Also I frequently get messages stating something is not a symbolic link to something else. Things seem to work, but error messages leave questions. These should be addressed in a different thread though.

 

Definitely get the serial uart adapter if you don't already have one. It's a world of difference from waiting for an ssh connection.

 

 

Link to comment
Share on other sites

I might be wrong but I don't think my SSD is bad. Reason therefore is as follows:

  • After I have tried  to install armbian to my SSD
    • The SSD is mountable and showing me the normal file structure (/bin,  /dev, /etc ...) and files that where present on the SDCard.
    • Files on the SSD are readable and writeable.
    • esfsck is not showing any issues
    • I'm able to copy a movie towards the SSD and back and the movie is still playable.

I suspect that there are hardlinks on the original SDCard which don't work once they are rsync'ed to the SSD. Could this be?

 

Link to comment
Share on other sites

I have my HC1 and have tried like mad to reproduce your problems, but what I keep finding is that I lose my NETWORK, not the boot ...

 

When you first log into the unit after install with 1234 and set up the user, try then nmtui and set a static local ip. My unit will also eventually fail to collect a dhcp address if I leave out this step.

 

@Walker I had a lot of problems like that with my clearfog board when I had the incorrect u-boot ... it forced the wrong device tree and caused all sorts of problems. Ensure you have the right uboot!

Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines