SR-G Posted May 26, 2021 Share Posted May 26, 2021 Hello, HELIOS4 system was running (and doing nothing), when it suddenly crashed. After restart, nothing automatically loaded (system stuck in emergency mode), once USB cable plugged i managed to log only once into the system, and discovered that no disks where mounted anymore (not even available / detect by the board) (it's not so easy as it seems there are some freezes, maybe due to the hardware errors related to he missing hdd links) 13:00 root@helios4 ~# ll /dev/sd* zsh: no matches found: /dev/sd* Is this a failing PSU (like in other threads) ? To be noted : the PSU has a blinking green light ... i can't remember if it was like that before ? In journalctl : May 26 12:57:03 helios4 kernel: ata1: SATA link down (SStatus 0 SControl 300) May 26 12:57:04 helios4 kernel: ata1: SATA link down (SStatus 0 SControl 300) May 26 12:57:06 helios4 kernel: ata1: COMRESET failed (errno=-32) May 26 12:57:06 helios4 kernel: ata1: reset failed (errno=-32), retrying in 8 se May 26 12:57:06 helios4 kernel: ata2: SATA link down (SStatus 0 SControl 300) May 26 12:57:07 helios4 kernel: ata2: SATA link down (SStatus 0 SControl 300) May 26 12:57:08 helios4 kernel: ata2: SATA link down (SStatus 0 SControl 300) May 26 12:57:11 helios4 kernel: ata2: COMRESET failed (errno=-32) May 26 12:57:11 helios4 kernel: ata2: reset failed (errno=-32), retrying in 8 se May 26 12:57:12 helios4 kernel: ata3: SATA link down (SStatus 0 SControl 300) May 26 12:57:12 helios4 kernel: ata4: COMRESET failed (errno=-32) May 26 12:57:12 helios4 kernel: ata4: reset failed (errno=-32), retrying in 8 se May 26 12:57:13 helios4 kernel: ata3: SATA link down (SStatus 0 SControl 300) May 26 12:57:14 helios4 kernel: ata3: SATA link down (SStatus 0 SControl 300) May 26 12:57:15 helios4 kernel: ata3: SATA link down (SStatus 0 SControl 300) May 26 12:57:15 helios4 kernel: ata1: SATA link down (SStatus 0 SControl 300) May 26 12:57:16 helios4 kernel: ata3: SATA link down (SStatus 0 SControl 300) May 26 12:57:16 helios4 kernel: ata3: SATA link down (SStatus 0 SControl 300) May 26 12:57:17 helios4 kernel: ata1: SATA link down (SStatus 0 SControl 300) May 26 12:57:17 helios4 kernel: ata3: SATA link down (SStatus 0 SControl 300) May 26 12:57:17 helios4 kernel: ata1: SATA link down (SStatus 0 SControl 300) May 26 12:57:18 helios4 kernel: ata3: SATA link down (SStatus 0 SControl 300) May 26 12:57:19 helios4 kernel: ata3: SATA link down (SStatus 0 SControl 300) May 26 12:57:19 helios4 kernel: ata3: SATA link down (SStatus 0 SControl 300) Full boot log : Quote U-Boot SPL 2019.04-armbian (Nov 23 2020 - 16:19:37 +0100) High speed PHY - Version: 2.0 Detected Device ID 6828 board SerDes lanes topology details: | Lane # | Speed | Type | -------------------------------- | 0 | 6 | SATA0 | | 1 | 5 | USB3 HOST0 | | 2 | 6 | SATA1 | | 3 | 6 | SATA3 | | 4 | 6 | SATA2 | | 5 | 5 | USB3 HOST1 | -------------------------------- High speed PHY - Ended Successfully mv_ddr: mv_ddr-armada-18.09.2 DDR3 Training Sequence - Switching XBAR Window to FastPath Window DDR Training Sequence - Start scrubbing DDR3 Training Sequence - End scrubbing mv_ddr: completed successfully Trying to boot from MMC1 U-Boot 2019.04-armbian (Nov 23 2020 - 16:19:37 +0100) SoC: MV88F6828-A0 at 1600 MHz DRAM: 2 GiB (800 MHz, 32-bit, ECC enabled) MMC: mv_sdh: 0 Loading Environment from EXT4... ** File not found /boot/boot.env ** ** Unable to read "/boot/boot.env" from mmc0:1 ** Model: Helios4 Board: Helios4 SCSI: MVEBU SATA INIT Target spinup took 0 ms. Target spinup took 0 ms. AHCI 0001.0000 32 slots 2 ports 6 Gbps 0x3 impl SATA mode flags: 64bit ncq led only pmp fbss pio slum part sxs No Link on this port! Can not start port 1 Net: Warning: ethernet@70000 (eth1) using random MAC address - 8a:1e:dc:26:d7:9a eth1: ethernet@70000 Hit any key to stop autoboot: 0 switch to partitions #0, OK mmc0 is current device Scanning mmc 0:1... Found U-Boot script /boot/boot.scr 2996 bytes read in 214 ms (13.7 KiB/s) ## Executing script at 03000000 Boot script loaded from mmc 120 bytes read in 182 ms (0 Bytes/s) 27241 bytes read in 627 ms (42 KiB/s) 9448011 bytes read in 1878 ms (4.8 MiB/s) 6607552 bytes read in 1379 ms (4.6 MiB/s) ## Loading init Ramdisk from Legacy Image at 02880000 ... Image Name: uInitrd Created: 2021-05-14 13:15:56 UTC Image Type: ARM Linux RAMDisk Image (gzip compressed) Data Size: 9447947 Bytes = 9 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Flattened Device Tree blob at 02040000 Booting using the fdt blob at 0x2040000 Loading Ramdisk to 0f6fd000, end 0ffffa0b ... OK ERROR: reserving fdt memory region failed (addr=2040000 size=6c000) Loading Device Tree to 0f68e000, end 0f6fcfff ... OK Starting kernel ... Uncompressing Linux... done, booting the kernel. Loading, please wait... Starting version 241 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: Will now check root file system ... fsck from util-linux 2.33.1 [/sbin/fsck.ext4 (1) -- /dev/mmcblk0p1] fsck.ext4 -a -C0 /dev/mmcblk0p1 /dev/mmcblk0p1: recovering journal /dev/mmcblk0p1: clean, 75903/1818432 files, 933326/7567200 blocks done. done. Begin: Running /scripts/local-bottom ... done. Begin: Running /scripts/init-bottom ... done. Welcome to Debian GNU/Linux 10 (buster)! [ OK ] Started Forward Password R…uests to Wall Directory Watch. [ OK ] Created slice User and Session Slice. [ OK ] Listening on fsck to fsckd communication Socket. [ OK ] Created slice system-serial\x2dgetty.slice. [ OK ] Listening on udev Control Socket. [ OK ] Listening on Syslog Socket. [ OK ] Listening on Journal Socket (/dev/log). [ OK ] Reached target Slices. [ OK ] Set up automount Arbitrary…s File System Automount Point. [ OK ] Listening on RPCbind Server Activation Socket. [ OK ] Listening on initctl Compatibility Named Pipe. [ OK ] Listening on udev Kernel Socket. [ OK ] Reached target System Time Synchronized. [ OK ] Listening on Journal Socket. Mounting RPC Pipe File System... Starting udev Coldplug all Devices... Starting Load Kernel Modules... Starting Set the console keyboard layout... Mounting Kernel Debug File System... Mounting POSIX Message Queue File System... Starting Create list of re…odes for the current kernel... Starting Remount Root and Kernel File Systems... Starting Nameserver information manager... [ OK ] Reached target Swap. [ OK ] Created slice system-getty.slice. [ OK ] Listening on Journal Audit Socket. [ OK ] Reached target Local Encrypted Volumes. [ OK ] Reached target Paths. [ OK ] Mounted RPC Pipe File System. [ OK ] Started Load Kernel Modules. [ OK ] Mounted Kernel Debug File System. [ OK ] Mounted POSIX Message Queue File System. [ OK ] Started Create list of req… nodes for the current kernel. [ OK ] Started Remount Root and Kernel File Systems. [ OK ] Started Set the console keyboard layout. Starting Create System Users... Starting Load/Save Random Seed... Starting Apply Kernel Variables... Mounting FUSE Control File System... [ OK ] Started udev Coldplug all Devices. [ OK ] Started Nameserver information manager. [ OK ] Started Create System Users. [ OK ] Started Load/Save Random Seed. [ OK ] Started Apply Kernel Variables. [ OK ] Mounted FUSE Control File System. Starting Create Static Device Nodes in /dev... Starting Helper to synchronize boot up for ifupdown... [ OK ] Started Helper to synchronize boot up for ifupdown. [ OK ] Started Create Static Device Nodes in /dev. Starting udev Kernel Device Manager... [ OK ] Reached target Local File Systems (Pre). Mounting /tmp... [ OK ] Mounted /tmp. [ OK ] Started udev Kernel Device Manager. [ OK ] Found device /dev/ttyS0. [ TIME ] Timed out waiting for device /dev/md/helios4:0. [DEPEND] Dependency failed for /mnt/internal/raid. [DEPEND] Dependency failed for Local File Systems. [DEPEND] Dependency failed for Mark… need to relabel after reboot. Starting Raise network interfaces... Starting Set console font and keymap... Starting Preprocess NFS configuration... Starting Armbian ZRAM config... [ OK ] Stopped Forward Password R…uests to Wall Directory Watch. [ OK ] Closed Syslog Socket. [ OK ] Reached target Login Prompts. [ OK ] Reached target Timers. [ OK ] Reached target Sockets. Starting Armbian hardware monitoring... Starting Armbian hardware optimization... [ OK ] Started Emergency Shell. [ OK ] Reached target Emergency Mode. [ OK ] Started Set console font and keymap. [ OK ] Started Preprocess NFS configuration. [ OK ] Started Armbian hardware monitoring. [ OK ] Started Armbian hardware optimization. [ OK ] Reached target NFS client services. [ OK ] Started Raise network interfaces. [ OK ] Reached target Network. [ OK ] Reached target Network is Online. [ OK ] Started Armbian ZRAM config. Starting Armbian memory supported logging... [ OK ] Started Armbian memory supported logging. Starting Journal Service... [ OK ] Started Journal Service. Starting Flush Journal to Persistent Storage... [ OK ] Started Flush Journal to Persistent Storage. Starting Create Volatile Files and Directories... [ OK ] Started Create Volatile Files and Directories. [ OK ] Started Entropy daemon using the HAVEGE algorithm. Starting RPC bind portmap service... Starting Update UTMP about System Boot/Shutdown... [ OK ] Started Update UTMP about System Boot/Shutdown. Starting Update UTMP about System Runlevel Changes... [ OK ] Started RPC bind portmap service. [ OK ] Reached target Remote File Systems (Pre). [ OK ] Reached target Remote File Systems. [ OK ] Reached target RPC Port Mapper. [ OK ] Started Update UTMP about System Runlevel Changes. You are in emergency mode. After logging in, type "journalctl -xb" to view system logs, "systemctl reboot" to reboot, "systemctl default" or "eGive root password for maintenance (or press Control-D to continue): Reloading system manager configuration Starting default target 0 Quote Link to comment Share on other sites More sharing options...
Mangix Posted May 27, 2021 Share Posted May 27, 2021 Sounds like a failing PSU. 4 3.5 inch HDDs? 0 Quote Link to comment Share on other sites More sharing options...
SR-G Posted May 27, 2021 Author Share Posted May 27, 2021 Correct, 4 x 3.5" HDD in the NAS 0 Quote Link to comment Share on other sites More sharing options...
SR-G Posted June 2, 2021 Author Share Posted June 2, 2021 So with a new PSU (30€ on amazon) my HELIOS4 NAS is working again. 0 Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.