12V/5A PS which I ordered together with other Pine NAS components
Create filesystem error communication failure
-
- OMV 4.x
- hemertje
-
-
I found at my computing stuff a WD 1TB Green Caviar HDD and tried it without the external power supply, similar like before with the 3TB WD Red HDD
Got the same errors as before , but it took a little longer before the system crashed
Code
Alles anzeigenCreating the file system, please wait ... ===== Wipe signatures from device ===== ===== Create partition ===== Creating new GPT entries. Disk /dev/sda: 1953525168 sectors, 931.5 GiB Model: WDC WD10EADS-00L Sector size (logical/physical): 512/512 bytes Disk identifier (GUID): 1E8AE397-E393-4A56-8835-5F9A81FA53CB Partition table holds up to 128 entries Main partition table begins at sector 2 and ends at sector 33 First usable sector is 34, last usable sector is 1953525134 Partitions will be aligned on 2048-sector boundaries Total free space is 2014 sectors (1007.0 KiB) Number Start (sector) End (sector) Size Code Name 1 2048 1953525134 931.5 GiB 8300 The operation has completed successfully. ===== Create file system ===== mke2fs 1.44.5 (15-Dec-2018) Creating filesystem with 244190385 4k blocks and 61054976 inodes Filesystem UUID: 88b18685-3bde-4609-99d8-539883efb79f Superblock backups stored on blocks: 32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208, 4096000, 7962624, 11239424, 20480000, 23887872, 71663616, 78675968, 102400000, 214990848 Allocating group tables: 0/7453 done Writing inode tables: 0/7453 45/7453 241/7453 317/7453 366/7453 414/7453 463/7453 511/7453 557/7453 600/7453 641/7453 680/7453 720/7453 759/7453 798/7453 838/7453 863/7453 871/7453 874/7453
Code
Alles anzeigen____ _ ____ __ _ _ | _ \ ___ ___| | _| _ \ _ __ ___ / /_ | || | | |_) / _ \ / __| |/ / |_) | '__/ _ \ | '_ \| || |_ | _ < (_) | (__| <| __/| | | (_) | | (_) |__ _| |_| \_\___/ \___|_|\_\_| |_| \___/ \___/ |_| Welcome to Armbian buster with Linux 4.4.208-rockchip64 System load: 0.11 0.07 0.02 Up time: 2:41 hours Memory usage: 5 % of 3874MB Zram usage: 2 % of 1937Mb IP: 192.168.2.3 CPU temp: 36°C Usage of /: 7% of 29G [ General system configuration (beta): armbian-config ] Last login: Wed Feb 5 17:21:39 2020 from 192.168.2.106 root@rockpro64:~# Message from syslogd@localhost at Feb 5 19:57:03 ... kernel:[ 9735.004750] Internal error: : 96000210 [#1] SMP Message from syslogd@localhost at Feb 5 19:57:10 ... kernel:[ 9742.274127] BUG: spinlock lockup suspected on CPU#0, scsi_eh_2/264 Message from syslogd@localhost at Feb 5 19:57:10 ... kernel:[ 9742.277966] lock: 0xffffff8009321870, .magic: dead4ead, .owner: scsi_eh_2/264, .owner_cpu: 0 Message from syslogd@localhost at Feb 5 19:58:48 ... kernel:[ 9840.525926] Kernel panic - not syncing: hung_task: blocked tasks
-
How to bring it down to the specific cause?
Power supply or PCI-SATA card or ?
Faulty hardware or caused by software?
-
-
Faulty hardware
Or failing hardware, or power.
-
I installed bionic-minimal-rockpro64-0.9.16-1163-armhf.img.xz from https://github.com/ayufan-rock…build/releases/tag/0.9.16
with the updates:
Codesudo apt-get update -y && sudo apt-get install linux-rockpro64-0.9 -y sudo apt-get update -y && sudo apt-get dist-upgrade -y
I opened a second ssh session with the command:
and did some debugging with the command:
-
here is the log:
Code
Alles anzeigenWelcome to Ubuntu 18.04.4 LTS (GNU/Linux 4.4.197-1236-rockchip-ayufan-g30faab37e339 aarch64) _ __ _ _ _ __ ___ | | ___ __ _ __ ___ / / | || | | '/ _ \ / | |/ / ' | '/ _ | '_ | || |_ | | | (_) | (| <| |) | | | () | (_) |_ | || _/ _||_\ .__/|| _/ _/ || || * Documentation: https://help.ubuntu.com * Management: https://landscape.canonical.com * Support: https://ubuntu.com/advantage System information as of Sun Feb 16 15:20:07 UTC 2020 System load: 0.14 Processes: 168 Usage of /: 5.3% of 28.42GB Users logged in: 1 Memory usage: 2% IP address for eth0: 192.168.2.3 Swap usage: 0% * Multipass 1.0 is out! Get Ubuntu VMs on demand on your Linux, Windows or Mac. Supports cloud-init for fast, local, cloud devops simulation. https://multipass.run/ Last login: Sun Feb 16 15:17:51 2020 from 192.168.2.106 rock64@rockpro64:~$ tail -f /var/log/syslog Feb 16 15:17:49 rockpro64 systemd[774]: Reached target Sockets. Feb 16 15:17:49 rockpro64 systemd[774]: Reached target Timers. Feb 16 15:17:49 rockpro64 systemd[774]: Reached target Basic System. Feb 16 15:17:49 rockpro64 systemd[774]: Reached target Default. Feb 16 15:17:49 rockpro64 systemd[774]: Startup finished in 184ms. Feb 16 15:17:49 rockpro64 systemd[1]: Started User Manager for UID 1000. Feb 16 15:18:01 rockpro64 CRON[830]: (root) CMD (for i in pgrep "ftpd|nfsiod|smbd|afpd|cnid" ; do ionice -c1 -p $i ${XU4_HMP_Fix}; done &>/dev/null) Feb 16 15:19:01 rockpro64 CRON[835]: (root) CMD (for i in pgrep "ftpd|nfsiod|smbd|afpd|cnid" ; do ionice -c1 -p $i ${XU4_HMP_Fix}; done &>/dev/null) Feb 16 15:20:01 rockpro64 CRON[842]: (root) CMD (for i in pgrep "ftpd|nfsiod|smbd|afpd|cnid" ; do ionice -c1 -p $i ${XU4_HMP_Fix}; done &>/dev/null) Feb 16 15:20:07 rockpro64 systemd[1]: Started Session 11 of user rock64. Feb 16 15:21:01 rockpro64 CRON[897]: (root) CMD (for i in pgrep "ftpd|nfsiod|smbd|afpd|cnid"; do ionice -c1 -p $i ${XU4_HMP_Fix}; done &>/dev/null) Feb 16 15:21:30 rockpro64 kernel: [ 410.987554] ata2.00: exception Emask 0x0 SAct 0x7effffff SErr 0x0 action 0x6 frozen Feb 16 15:21:30 rockpro64 kernel: [ 410.988489] ata2.00: failed command: WRITE FPDMA QUEUED Feb 16 15:21:30 rockpro64 kernel: [ 410.989238] ata2.00: cmd 61/40:00:40:e8:85/05:00:ae:00:00/40 tag 0 ncq 688128 out Feb 16 15:21:30 rockpro64 kernel: [ 410.989238] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Feb 16 15:21:30 rockpro64 kernel: [ 410.990973] ata2.00: status: { DRDY } Feb 16 15:21:30 rockpro64 kernel: [ 410.991420] ata2.00: failed command: WRITE FPDMA QUEUED Feb 16 15:21:30 rockpro64 kernel: [ 410.992056] ata2.00: cmd 61/40:08:80:ed:85/05:00:ae:00:00/40 tag 1 ncq 688128 out Feb 16 15:21:30 rockpro64 kernel: [ 410.992056] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Feb 16 15:21:30 rockpro64 kernel: [ 410.993900] ata2.00: status: { DRDY } Feb 16 15:21:30 rockpro64 kernel: [ 410.994359] ata2.00: failed command: WRITE FPDMA QUEUED Feb 16 15:21:30 rockpro64 kernel: [ 410.994995] ata2.00: cmd 61/40:10:c0:f2:85/05:00:ae:00:00/40 tag 2 ncq 688128 out Feb 16 15:21:30 rockpro64 kernel: [ 410.994995] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Feb 16 15:21:30 rockpro64 kernel: [ 410.996811] ata2.00: status: { DRDY } Feb 16 15:21:30 rockpro64 kernel: [ 410.997272] ata2.00: failed command: WRITE FPDMA QUEUED Feb 16 15:21:30 rockpro64 kernel: [ 410.997908] ata2.00: cmd 61/40:18:00:f8:85/05:00:ae:00:00/40 tag 3 ncq 688128 out Feb 16 15:21:30 rockpro64 kernel: [ 410.997908] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Feb 16 15:21:30 rockpro64 kernel: [ 410.999625] ata2.00: status: { DRDY } Feb 16 15:21:30 rockpro64 kernel: [ 411.000068] ata2.00: failed command: WRITE FPDMA QUEUED Feb 16 15:21:30 rockpro64 kernel: [ 411.000795] ata2.00: cmd 61/40:20:40:fd:85/05:00:ae:00:00/40 tag 4 ncq 688128 out Feb 16 15:21:30 rockpro64 kernel: [ 411.000795] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Feb 16 15:21:30 rockpro64 kernel: [ 411.002530] ata2.00: status: { DRDY } Feb 16 15:21:30 rockpro64 kernel: [ 411.002974] ata2.00: failed command: WRITE FPDMA QUEUED Feb 16 15:21:30 rockpro64 kernel: [ 411.003609] ata2.00: cmd 61/40:28:80:02:86/05:00:ae:00:00/40 tag 5 ncq 688128 out Feb 16 15:21:30 rockpro64 kernel: [ 411.003609] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Feb 16 15:21:30 rockpro64 kernel: [ 411.005431] ata2.00: status: { DRDY } Feb 16 15:21:30 rockpro64 kernel: [ 411.005879] ata2.00: failed command: WRITE FPDMA QUEUED
-
-
Code
Alles anzeigenFeb 16 15:21:30 rockpro64 kernel: [ 411.006514] ata2.00: cmd 61/40:30:c0:07:86/05:00:ae:00:00/40 tag 6 ncq 688128 out Feb 16 15:21:30 rockpro64 kernel: [ 411.006514] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Feb 16 15:21:30 rockpro64 kernel: [ 411.008022] ata2.00: status: { DRDY } Feb 16 15:21:30 rockpro64 kernel: [ 411.008403] ata2.00: failed command: WRITE FPDMA QUEUED Feb 16 15:21:30 rockpro64 kernel: [ 411.008968] ata2.00: cmd 61/40:38:00:0d:86/05:00:ae:00:00/40 tag 7 ncq 688128 out Feb 16 15:21:30 rockpro64 kernel: [ 411.008968] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Feb 16 15:21:30 rockpro64 kernel: [ 411.010471] ata2.00: status: { DRDY } Feb 16 15:21:30 rockpro64 kernel: [ 411.010852] ata2.00: failed command: WRITE FPDMA QUEUED Feb 16 15:21:30 rockpro64 kernel: [ 411.011395] ata2.00: cmd 61/40:40:40:12:86/05:00:ae:00:00/40 tag 8 ncq 688128 out Feb 16 15:21:30 rockpro64 kernel: [ 411.011395] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Feb 16 15:21:30 rockpro64 kernel: [ 411.012943] ata2.00: status: { DRDY } Feb 16 15:21:30 rockpro64 kernel: [ 411.013326] ata2.00: failed command: WRITE FPDMA QUEUED Feb 16 15:21:30 rockpro64 kernel: [ 411.013870] ata2.00: cmd 61/40:48:80:17:86/05:00:ae:00:00/40 tag 9 ncq 688128 out Feb 16 15:21:30 rockpro64 kernel: [ 411.013870] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Feb 16 15:21:30 rockpro64 kernel: [ 411.015371] ata2.00: status: { DRDY } Feb 16 15:21:30 rockpro64 kernel: [ 411.015751] ata2.00: failed command: WRITE FPDMA QUEUED Feb 16 15:21:30 rockpro64 kernel: [ 411.016295] ata2.00: cmd 61/40:50:c0:1c:86/05:00:ae:00:00/40 tag 10 ncq 688128 out Feb 16 15:21:30 rockpro64 kernel: [ 411.016295] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Feb 16 15:21:30 rockpro64 kernel: [ 411.017851] ata2.00: status: { DRDY } Feb 16 15:21:30 rockpro64 kernel: [ 411.021465] ata2.00: failed command: WRITE FPDMA QUEUED Feb 16 15:21:30 rockpro64 kernel: [ 411.025255] ata2.00: cmd 61/40:58:00:22:86/05:00:ae:00:00/40 tag 11 ncq 688128 out Feb 16 15:21:30 rockpro64 kernel: [ 411.025255] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Feb 16 15:21:30 rockpro64 kernel: [ 411.033208] ata2.00: status: { DRDY } Feb 16 15:21:30 rockpro64 kernel: [ 411.036768] ata2.00: failed command: WRITE FPDMA QUEUED Feb 16 15:21:30 rockpro64 kernel: [ 411.040422] ata2.00: cmd 61/40:60:40:27:86/05:00:ae:00:00/40 tag 12 ncq 688128 out Feb 16 15:21:30 rockpro64 kernel: [ 411.040422] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Feb 16 15:21:30 rockpro64 kernel: [ 411.048219] ata2.00: status: { DRDY } Feb 16 15:21:30 rockpro64 kernel: [ 411.051419] ata2.00: failed command: WRITE FPDMA QUEUED Feb 16 15:21:30 rockpro64 kernel: [ 411.054501] ata2.00: cmd 61/40:68:80:2c:86/05:00:ae:00:00/40 tag 13 ncq 688128 out Feb 16 15:21:30 rockpro64 kernel: [ 411.054501] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Feb 16 15:21:30 rockpro64 kernel: [ 411.061055] ata2.00: status: { DRDY } Feb 16 15:21:30 rockpro64 kernel: [ 411.063968] ata2.00: failed command: WRITE FPDMA QUEUED Feb 16 15:21:30 rockpro64 kernel: [ 411.067066] ata2.00: cmd 61/40:70:c0:31:86/05:00:ae:00:00/40 tag 14 ncq 688128 out Feb 16 15:21:30 rockpro64 kernel: [ 411.067066] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Feb 16 15:21:30 rockpro64 kernel: [ 411.073633] ata2.00: status: { DRDY } Feb 16 15:21:30 rockpro64 kernel: [ 411.076588] ata2.00: failed command: WRITE FPDMA QUEUED Feb 16 15:21:30 rockpro64 kernel: [ 411.079646] ata2.00: cmd 61/40:78:00:37:86/05:00:ae:00:00/40 tag 15 ncq 688128 out Feb 16 15:21:30 rockpro64 kernel: [ 411.079646] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Feb 16 15:21:30 rockpro64 kernel: [ 411.086228] ata2.00: status: { DRDY } Feb 16 15:21:30 rockpro64 kernel: [ 411.089029] ata2.00: failed command: WRITE FPDMA QUEUED Feb 16 15:21:30 rockpro64 kernel: [ 411.091678] ata2.00: cmd 61/40:80:40:3c:86/05:00:ae:00:00/40 tag 16 ncq 688128 out Feb 16 15:21:30 rockpro64 kernel: [ 411.091678] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Feb 16 15:21:30 rockpro64 kernel: [ 411.097416] ata2.00: status: { DRDY } Feb 16 15:21:30 rockpro64 kernel: [ 411.099930] ata2.00: failed command: WRITE FPDMA QUEUED Feb 16 15:21:30 rockpro64 kernel: [ 411.102607] ata2.00: cmd 61/40:88:80:41:86/05:00:ae:00:00/40 tag 17 ncq 688128 out Feb 16 15:21:30 rockpro64 kernel: [ 411.102607] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Feb 16 15:21:30 rockpro64 kernel: [ 411.108357] ata2.00: status: { DRDY } Feb 16 15:21:30 rockpro64 kernel: [ 411.110774] ata2.00: failed command: WRITE FPDMA QUEUED Feb 16 15:21:30 rockpro64 kernel: [ 411.113115] ata2.00: cmd 61/40:90:c0:46:86/05:00:ae:00:00/40 tag 18 ncq 688128 out Feb 16 15:21:30 rockpro64 kernel: [ 411.113115] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Feb 16 15:21:30 rockpro64 kernel: [ 411.118185] ata2.00: status: { DRDY } Feb 16 15:21:30 rockpro64 kernel: [ 411.120369] ata2.00: failed command: WRITE FPDMA QUEUED Feb 16 15:21:30 rockpro64 kernel: [ 411.122711] ata2.00: cmd 61/40:98:00:4c:86/05:00:ae:00:00/40 tag 19 ncq 688128 out Feb 16 15:21:30 rockpro64 kernel: [ 411.122711] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Feb 16 15:21:30 rockpro64 kernel: [ 411.127790] ata2.00: status: { DRDY } Feb 16 15:21:30 rockpro64 kernel: [ 411.130003] ata2.00: failed command: WRITE FPDMA QUEUED Feb 16 15:21:30 rockpro64 kernel: [ 411.132327] ata2.00: cmd 61/40:a0:40:51:86/05:00:ae:00:00/40 tag 20 ncq 688128 out Feb 16 15:21:30 rockpro64 kernel: [ 411.132327] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Feb 16 15:21:30 rockpro64 kernel: [ 411.137407] ata2.00: status: { DRDY } Feb 16 15:21:30 rockpro64 kernel: [ 411.139600] ata2.00: failed command: WRITE FPDMA QUEUED Feb 16 15:21:30 rockpro64 kernel: [ 411.141946] ata2.00: cmd 61/40:a8:80:56:86/05:00:ae:00:00/40 tag 21 ncq 688128 out Feb 16 15:21:30 rockpro64 kernel: [ 411.141946] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Feb 16 15:21:30 rockpro64 kernel: [ 411.147043] ata2.00: status: { DRDY } Feb 16 15:21:30 rockpro64 kernel: [ 411.149225] ata2.00: failed command: WRITE FPDMA QUEUED Feb 16 15:21:30 rockpro64 kernel: [ 411.151329] ata2.00: cmd 61/40:b0:c0:5b:86/05:00:ae:00:00/40 tag 22 ncq 688128 out Feb 16 15:21:30 rockpro64 kernel: [ 411.151329] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Feb 16 15:21:30 rockpro64 kernel: [ 411.155970] ata2.00: status: { DRDY } Feb 16 15:21:30 rockpro64 kernel: [ 411.157968] ata2.00: failed command: WRITE FPDMA QUEUED Feb 16 15:21:30 rockpro64 kernel: [ 411.160073] ata2.00: cmd 61/40:b8:00:61:86/05:00:ae:00:00/40 tag 23 ncq 688128 out Feb 16 15:21:30 rockpro64 kernel: [ 411.160073] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Feb 16 15:21:30 rockpro64 kernel: [ 411.164719] ata2.00: status: { DRDY } Feb 16 15:21:30 rockpro64 kernel: [ 411.166698] ata2.00: failed command: WRITE FPDMA QUEUED Feb 16 15:21:30 rockpro64 kernel: [ 411.168824] ata2.00: cmd 61/40:c8:c0:c8:85/05:00:ae:00:00/40 tag 25 ncq 688128 out Feb 16 15:21:30 rockpro64 kernel: [ 411.168824] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Feb 16 15:21:30 rockpro64 kernel: [ 411.173477] ata2.00: status: { DRDY } Feb 16 15:21:30 rockpro64 kernel: [ 411.175449] ata2.00: failed command: WRITE FPDMA QUEUED Feb 16 15:21:30 rockpro64 kernel: [ 411.177578] ata2.00: cmd 61/40:d0:00:ce:85/05:00:ae:00:00/40 tag 26 ncq 688128 out Feb 16 15:21:30 rockpro64 kernel: [ 411.177578] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Feb 16 15:21:30 rockpro64 kernel: [ 411.182221] ata2.00: status: { DRDY } Feb 16 15:21:30 rockpro64 kernel: [ 411.184195] ata2.00: failed command: WRITE FPDMA QUEUED Feb 16 15:21:30 rockpro64 kernel: [ 411.186336] ata2.00: cmd 61/40:d8:40:d3:85/05:00:ae:00:00/40 tag 27 ncq 688128 out Feb 16 15:21:30 rockpro64 kernel: [ 411.186336] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Feb 16 15:21:30 rockpro64 kernel: [ 411.190676] ata2.00: status: { DRDY } Feb 16 15:21:30 rockpro64 kernel: [ 411.192481] ata2.00: failed command: WRITE FPDMA QUEUED Feb 16 15:21:30 rockpro64 kernel: [ 411.194438] ata2.00: cmd 61/40:e0:80:d8:85/05:00:ae:00:00/40 tag 28 ncq 688128 out Feb 16 15:21:30 rockpro64 kernel: [ 411.194438] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Feb 16 15:21:30 rockpro64 kernel: [ 411.198734] ata2.00: status: { DRDY } Feb 16 15:21:30 rockpro64 kernel: [ 411.200553] ata2.00: failed command: WRITE FPDMA QUEUED Feb 16 15:21:30 rockpro64 kernel: [ 411.202490] ata2.00: cmd 61/40:e8:c0:dd:85/05:00:ae:00:00/40 tag 29 ncq 688128 out Feb 16 15:21:30 rockpro64 kernel: [ 411.202490] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Feb 16 15:21:30 rockpro64 kernel: [ 411.206798] ata2.00: status: { DRDY } Feb 16 15:21:30 rockpro64 kernel: [ 411.208615] ata2.00: failed command: WRITE FPDMA QUEUED Feb 16 15:21:30 rockpro64 kernel: [ 411.210414] ata2.00: cmd 61/40:f0:00:e3:85/05:00:ae:00:00/40 tag 30 ncq 688128 out Feb 16 15:21:30 rockpro64 kernel: [ 411.210414] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Feb 16 15:21:30 rockpro64 kernel: [ 411.214423] ata2.00: status: { DRDY } Feb 16 15:21:31 rockpro64 kernel: [ 411.216102] ata2: hard resetting link packet_write_wait: Connection to 192.168.2.3 port 22: Broken pipe
-
ATA controller:
Code
Alles anzeigenrock64@rockpro64:~$ lspci |grep ATA 01:00.0 SATA controller: ASMedia Technology Inc. ASM1062 Serial ATA Controller (rev 01) and this hard drive: rock64@rockpro64:~$ sudo smartctl -a /dev/sda |grep Model Model Family: Western Digital Red Device Model: WDC WD30EFRX-68EUZN0 here's the HDD's SMART report: rock64@rockpro64:~$ sudo smartctl -a /dev/sda smartctl 6.6 2016-05-31 r4324 [aarch64-linux-4.4.197-1236-rockchip-ayufan-g30faab37e339] (local build) Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Model Family: Western Digital Red Device Model: WDC WD30EFRX-68EUZN0 Serial Number: WD-WCC4N6JZS316 LU WWN Device Id: 5 0014ee 2111b9f23 Firmware Version: 82.00A82 User Capacity: 3,000,592,982,016 bytes [3.00 TB] Sector Sizes: 512 bytes logical, 4096 bytes physical Rotation Rate: 5400 rpm Device is: In smartctl database [for details use: -P show] ATA Version is: ACS-2 (minor revision not indicated) SATA Version is: SATA 3.0, 6.0 Gb/s (current: 6.0 Gb/s) Local Time is: Sun Feb 16 15:42:12 2020 UTC SMART support is: Available - device has SMART capability. SMART support is: Enabled === START OF READ SMART DATA SECTION === SMART overall-health self-assessment test result: PASSED General SMART Values: Offline data collection status: (0x82) Offline data collection activity was completed without error. Auto Offline Data Collection: Enabled. Self-test execution status: ( 0) The previous self-test routine completed without error or no self-test has ever been run. Total time to complete Offline data collection: (42420) seconds. Offline data collection capabilities: (0x7b) SMART execute Offline immediate. Auto Offline data collection on/off support. Suspend Offline collection upon new command. Offline surface scan supported. Self-test supported. Conveyance Self-test supported. Selective Self-test supported. SMART capabilities: (0x0003) Saves SMART data before entering power-saving mode. Supports SMART auto save timer. Error logging capability: (0x01) Error logging supported. General Purpose Logging supported. Short self-test routine recommended polling time: ( 2) minutes. Extended self-test routine recommended polling time: ( 425) minutes. Conveyance self-test routine recommended polling time: ( 5) minutes. SCT capabilities: (0x703d) SCT Status supported. SCT Error Recovery Control supported. SCT Feature Control supported. SCT Data Table supported. SMART Attributes Data Structure revision number: 16 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x002f 200 200 051 Pre-fail Always - 0 3 Spin_Up_Time 0x0027 185 176 021 Pre-fail Always - 5750 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 525 5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0 7 Seek_Error_Rate 0x002e 200 200 000 Old_age Always - 0 9 Power_On_Hours 0x0032 098 098 000 Old_age Always - 1808 10 Spin_Retry_Count 0x0032 100 100 000 Old_age Always - 0 11 Calibration_Retry_Count 0x0032 100 100 000 Old_age Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 469 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 48 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 590 194 Temperature_Celsius 0x0022 122 113 000 Old_age Always - 28 196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always - 0 197 Current_Pending_Sector 0x0032 200 200 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0030 200 200 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0 200 Multi_Zone_Error_Rate 0x0008 200 200 000 Old_age Offline - 0 SMART Error Log Version: 1 No Errors Logged SMART Self-test log structure revision number 1 Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error 1 Extended offline Completed without error 00% 1335 - 2 Extended offline Completed without error 00% 1187 - 3 Extended offline Completed without error 00% 1062 - 4 Extended offline Completed without error 00% 862 - 5 Extended offline Completed without error 00% 696 - 6 Extended offline Completed without error 00% 549 - 7 Extended offline Completed without error 00% 411 - 8 Extended offline Completed without error 00% 267 - 9 Extended offline Completed without error 00% 121 - SMART Selective self-test log data structure revision number 1 SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS 1 0 0 Not_testing 2 0 0 Not_testing 3 0 0 Not_testing 4 0 0 Not_testing 5 0 0 Not_testing Selective self-test flags (0x0): After scanning selected spans, do NOT read-scan remainder of disk. If Selective self-test is pending on power-up, resume after 0 minute delay.
-
As a layman myself, I see some "errors" with the dmesg command:
Code
Alles anzeigen[ 1.479161] vcc5v0_host: no parameters [ 1.479325] reg-fixed-voltage vcc5v0-host-regulator: vcc5v0_host supplying 0uV [ 1.479966] iommu: Adding device ff650000.vpu_service to group 0 [ 1.480069] iommu: Adding device ff660000.rkvdec to group 1 [ 1.480166] iommu: Adding device ff670000.iep to group 2 [ 1.480293] iommu: Adding device ff8f0000.vop to group 3 [ 1.480388] platform ff8f0000.vop: iommu /iommu@ff8f3f00 not found [ 1.480408] iommu: Removing device ff8f0000.vop from group 3 [ 1.480471] iommu: Adding device ff900000.vop to group 3 [ 1.480993] rk_iommu ff650800.iommu: can't get sclk [ 1.481295] rk_iommu ff660480.iommu: can't get sclk [ 1.481408] rk_iommu ff670800.iommu: can't get aclk [ 1.481432] rk_iommu ff670800.iommu: can't get hclk [ 1.481453] rk_iommu ff670800.iommu: can't get sclk [ 1.481655] rk_iommu ff903f00.iommu: can't get sclk [ 1.482036] SCSI subsystem initialized
Code
Alles anzeigen[ 1.851160] rockchip-pcie f8000000.pcie: Looking up vpcie3v3-supply from device tree [ 1.851268] rockchip-pcie f8000000.pcie: Looking up vpcie1v8-supply from device tree [ 1.851279] rockchip-pcie f8000000.pcie: Looking up vpcie1v8-supply property in node /pcie@f8000000 failed [ 1.851294] rockchip-pcie f8000000.pcie: no vpcie1v8 regulator found [ 1.851321] rockchip-pcie f8000000.pcie: Looking up vpcie0v9-supply from device tree [ 1.851331] rockchip-pcie f8000000.pcie: Looking up vpcie0v9-supply property in node /pcie@f8000000 failed [ 1.851343] rockchip-pcie f8000000.pcie: no vpcie0v9 regulator found [ 1.851367] rockchip-pcie f8000000.pcie: bus-scan-delay-ms in device tree is 1000 ms [ 1.851400] rockchip-pcie f8000000.pcie: missing "memory-region" property [ 1.851438] PCI host bridge /pcie@f8000000 ranges: [ 1.851472] MEM 0xfa000000..0xfbdfffff -> 0xfa000000 [ 1.851495] IO 0xfbe00000..0xfbefffff -> 0xfbe00000 [ 1.898676] rockchip-pcie f8000000.pcie: invalid power supply [ 1.935126] rockchip-pcie f8000000.pcie: wait 1000 ms (from device tree) before bus scan [ 2.938931] rockchip-pcie f8000000.pcie: PCI host bridge to bus 0000:00
-
-
Code
[ 3.946085] i2c i2c-10: of_i2c: modalias failure on /dp@fec00000/ports [ 3.947872] cdn-dp fec00000.dp: Direct firmware load for rockchip/dptx.bin failed with error -2
Code[ 4.132784] xhci-hcd xhci-hcd.9.auto: Host not halted after 16000 microseconds. [ 4.137214] xhci-hcd xhci-hcd.9.auto: Host controller not halted, aborting reset.
Code[ 4.951028] cdn-dp fec00000.dp: Direct firmware load for rockchip/dptx.bin failed with error -2
Code[ 14.382190] ff100000.saradc supply vref not found, using dummy regulator [ 14.382297] rockchip-saradc ff100000.saradc: failed to get voltage [ 14.386073] rockchip-saradc: probe of ff100000.saradc failed with error -22
Code[ 14.694857] FAT-fs (mmcblk0p6): utf8 is not a recommended IO charset for FAT filesystems, filesystem will be case sensitive! [ 14.706800] [BT_RFKILL]: DISABLE UART_RTS [ 14.706867] [BT_RFKILL]: bt turn on power [ 14.712323] FAT-fs (mmcblk0p6): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
Questions:
- I see many driver failures in de dmesg?
- Is this an incompatibility between the WD RED firmware and either the SATA Chipset and/or the mainboard it's self?
- How to be fixed?
Jetzt mitmachen!
Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!