tony013
Members-
Posts
62 -
Joined
-
Last visited
Recent Profile Visitors
The recent visitors block is disabled and is not being shown to other users.
-
No, that is no acceptable solution. apart from that, it's about the first impression during installation. I have two NAS (rockpi4) both running armbian. The installation of the first one was a few years ago. I invested a lot of time to be able to control the fan of the tower. When I installed the second NAS, I found that the newer armbian prohibits PWM fan control. I then decided to use an external fan controller and stayed with armbian. Recently I had to install a raspberry4 (for the company). Armbian was of course my first choice. But the new installation routine frustrated me so much that I threw armbian in the garbage can and switched to raspi os. Raspi OS allows one to switch the keyboard to language in use before having to enter a password. With the password, everything is accepted. You just get a hint that the password may be too insecure to operate on the internet. With Armbian, the first thing you have to do is enter a strong password. With a keyboard setting that you don't even know! And even after the installation it is still very very difficult to switch the keyboard. At least for someone who doesn't know Linux that well. If you compare the impression the first installation leaves on the user, a raspi os says: Welcome. Thank you for using raspi os. The message of armbian on the other hand is: fuck off! Armbian is not for you!
-
Hm, the default power supply of the sata tower package has 60W and the old PC power supply has 500W According to rockpi-wiki a ssd needs about 5W - so about 25W should already be enuf ... I suspect that the problem is more likely to be voltage spikes that could be transmitted from one part to the other via the power supply line. That's why I would have thought of diodes rather than capacitors. What do you think?
-
Hi, I built a second nas from rockpi4 and as I used the 12V plug to power the tower, I thought, I could use an old pc power supply to drive both. But when I start both nas from the same power supply, both will crash. Any idea, how I could avoid that crash and stil use only one power supply? Maybe add some electronic components?
-
disks not spinning up - schematics for power supply?
tony013 replied to Alexander Eiblinger's topic in Rockchip
I used to have a real linux-server with raid-systems and there I had regular failures of this kind. The problem is that the hard disks that are sold as single disks are getting worse and worse. I had a few times even the case that a newly purchased disk was already defective. Well, I could exchange it via RMA, but that costs time and is annoying. A while ago I discarded the server and built a NAS based on rockpi4 with sata-extension. 4x 2.5" SSD - and since then there is peace on the disk front. Everything works as desired. -
Hi, I installed a fresh Armbian_22.05.4_Rockpi-4a_sid_edge_5.18.0 first on SD-card, then I used nand-sata-install to copy system to emmc. After that I rebooted and set up the nas (rockpi-4a with 4 ssd-drives). I already used ssh remote shell to perform apt dist-upgrade and copying of about 6TB ... When all setup was finished, I shutdown the system, closed the tower and restarted again. On that restart, the network came up without inet-address. ifconfig showed eth0 and l0, but eth0 had a mac-address (not the one, I configured in armbianEnv.txt) but no ip-address. Here are some lines from syslog: Aug 28 15:57:01 mynas NetworkManager[1659]: <info> [1661695021.5656] device (eth0): state change: disconnected -> unavailable (reason 'carrier-changed', sys-iface-state: 'managed') Aug 28 15:57:02 mynas NetworkManager[1659]: <info> [1661695022.7361] device (eth0): carrier: link connected Aug 28 15:57:02 mynas NetworkManager[1659]: <info> [1661695022.7370] device (eth0): state change: unavailable -> disconnected (reason 'carrier-changed', sys-iface-state: 'managed') Aug 28 15:57:02 mynas kernel: [ 327.420987] rk_gmac-dwmac fe300000.ethernet eth0: Link is Up - 100Mbps/Full - flow control rx/tx Aug 28 15:57:02 mynas kernel: [ 327.421037] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready Aug 28 15:57:02 mynas NetworkManager[1659]: <info> [1661695022.7393] policy: auto-activating connection 'Armbian ethernet' (9362e2eb-3533-439f-acd4-3804f33c01a5) Aug 28 15:57:02 mynas NetworkManager[1659]: <info> [1661695022.7409] device (eth0): Activation: starting connection 'Armbian ethernet' (9362e2eb-3533-439f-acd4-3804f33c01a5) Aug 28 15:57:02 mynas NetworkManager[1659]: <info> [1661695022.7413] device (eth0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed') Aug 28 15:57:02 mynas NetworkManager[1659]: <info> [1661695022.7425] manager: NetworkManager state is now CONNECTING Aug 28 15:57:02 mynas NetworkManager[1659]: <warn> [1661695022.7434] platform-linux: do-change-link[2]: failure changing link: failure 16 (Device or resource busy) Aug 28 15:57:02 mynas kernel: [ 327.429651] rk_gmac-dwmac fe300000.ethernet eth0: Link is Down Aug 28 15:57:02 mynas NetworkManager[1659]: <warn> [1661695022.7460] platform-linux: do-change-link[2]: failure changing link: failure 99 (Cannot assign requested address) Aug 28 15:57:02 mynas NetworkManager[1659]: <warn> [1661695022.7461] device (eth0): set-hw-addr: failed to set-cloned MAC address to AB:CD:47:11:FE:D0 (AB:CD:47:11:FE:D0) (NME_UNSPEC) Aug 28 15:57:02 mynas kernel: [ 327.433545] rk_gmac-dwmac fe300000.ethernet eth0: PHY [stmmac-0:00] driver [RTL8211E Gigabit Ethernet] (irq=POLL) Aug 28 15:57:02 mynas kernel: [ 327.484253] rk_gmac-dwmac fe300000.ethernet eth0: Register MEM_TYPE_PAGE_POOL RxQ-0 Aug 28 15:57:02 mynas kernel: [ 327.495328] rk_gmac-dwmac fe300000.ethernet eth0: No Safety Features support found Aug 28 15:57:02 mynas kernel: [ 327.495354] rk_gmac-dwmac fe300000.ethernet eth0: PTP not supported by HW Aug 28 15:57:02 mynas kernel: [ 327.495370] rk_gmac-dwmac fe300000.ethernet eth0: configuring for phy/rgmii link mode Aug 28 15:57:02 mynas NetworkManager[1659]: <info> [1661695022.8109] device (eth0): state change: prepare -> failed (reason 'config-failed', sys-iface-state: 'managed') Aug 28 15:57:02 mynas NetworkManager[1659]: <info> [1661695022.8121] manager: NetworkManager state is now DISCONNECTED Aug 28 15:57:02 mynas NetworkManager[1659]: <warn> [1661695022.8128] device (eth0): Activation: failed for connection 'Armbian ethernet' Aug 28 15:57:02 mynas NetworkManager[1659]: <info> [1661695022.8139] device (eth0): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed') Aug 28 15:57:08 mynas NetworkManager[1659]: <info> [1661695028.8165] device (eth0): state change: disconnected -> unavailable (reason 'carrier-changed', sys-iface-state: 'managed') I see the error, but I have no idea, what to do.