tr0910

Members
  • Posts

    1449
  • Joined

  • Last visited

Everything posted by tr0910

  1. @Frank1940 The rebuild completed successfully, but another drive showed 200 errors during the rebuild process. Does this mean that errors were replicated into the newly built drive and it is not fully perfect? I have 2 parity drives, so that other WDC EZRS can go bad without further issue...
  2. Here part of the syslog on the old server just before it locked up. Nov 27 20:06:54 Robin root: Starting Avahi mDNS/DNS-SD Daemon: /usr/sbin/avahi-daemon -D Nov 27 20:06:54 Robin avahi-daemon[9235]: Found user 'avahi' (UID 61) and group 'avahi' (GID 214). Nov 27 20:06:54 Robin avahi-daemon[9235]: Successfully dropped root privileges. Nov 27 20:06:54 Robin avahi-daemon[9235]: avahi-daemon 0.7 starting up. Nov 27 20:06:54 Robin avahi-daemon[9235]: WARNING: No NSS support for mDNS detected, consider installing nss-mdns! Nov 27 20:06:54 Robin avahi-daemon[9235]: Successfully called chroot(). Nov 27 20:06:54 Robin avahi-daemon[9235]: Successfully dropped remaining capabilities. Nov 27 20:06:54 Robin avahi-daemon[9235]: Loading service file /services/sftp-ssh.service. Nov 27 20:06:54 Robin avahi-daemon[9235]: Loading service file /services/smb.service. Nov 27 20:06:54 Robin avahi-daemon[9235]: Loading service file /services/ssh.service. Nov 27 20:06:54 Robin avahi-daemon[9235]: Joining mDNS multicast group on interface br0.IPv6 with address 2605:a601:ae0f:2700:230:48ff:fe7d:3760. Nov 27 20:06:54 Robin avahi-daemon[9235]: New relevant interface br0.IPv6 for mDNS. Nov 27 20:06:54 Robin avahi-daemon[9235]: Joining mDNS multicast group on interface br0.IPv4 with address 192.168.13.75. Nov 27 20:06:54 Robin avahi-daemon[9235]: New relevant interface br0.IPv4 for mDNS. Nov 27 20:06:54 Robin avahi-daemon[9235]: Joining mDNS multicast group on interface bond0.IPv6 with address fe80::230:48ff:fe7d:3760. Nov 27 20:06:54 Robin avahi-daemon[9235]: New relevant interface bond0.IPv6 for mDNS. Nov 27 20:06:54 Robin avahi-daemon[9235]: Network interface enumeration completed. Nov 27 20:06:54 Robin avahi-daemon[9235]: Registering new address record for 2605:a601:ae0f:2700:230:48ff:fe7d:3760 on br0.*. Nov 27 20:06:54 Robin avahi-daemon[9235]: Registering new address record for 192.168.13.75 on br0.IPv4. Nov 27 20:06:54 Robin avahi-daemon[9235]: Registering new address record for fe80::230:48ff:fe7d:3760 on bond0.*. Nov 27 20:06:54 Robin emhttpd: shcmd (20): /etc/rc.d/rc.avahidnsconfd start Nov 27 20:06:54 Robin root: Starting Avahi mDNS/DNS-SD DNS Server Configuration Daemon: /usr/sbin/avahi-dnsconfd -D Nov 27 20:06:54 Robin avahi-dnsconfd[9245]: Successfully connected to Avahi daemon. Nov 27 20:06:54 Robin emhttpd: shcmd (25): /etc/rc.d/rc.php-fpm start Nov 27 20:06:54 Robin root: Starting php-fpm done Nov 27 20:06:54 Robin emhttpd: shcmd (26): /etc/rc.d/rc.nginx start Nov 27 20:06:54 Robin root: Starting Nginx server daemon... Nov 27 20:06:54 Robin emhttpd: stale configuration Nov 27 20:06:54 Robin root: error: /plugins/preclear.disk/Preclear.php: wrong csrf_token Nov 27 20:06:55 Robin avahi-daemon[9235]: Server startup complete. Host name is Robin.local. Local service cookie is 3056464356. Nov 27 20:06:56 Robin avahi-daemon[9235]: Service "Robin" (/services/ssh.service) successfully established. Nov 27 20:06:56 Robin avahi-daemon[9235]: Service "Robin" (/services/smb.service) successfully established. Nov 27 20:06:56 Robin avahi-daemon[9235]: Service "Robin" (/services/sftp-ssh.service) successfully established. Nov 27 20:07:00 Robin login[9505]: ROOT LOGIN on '/dev/pts/0' Nov 27 20:07:48 Robin kernel: ata20: link is slow to respond, please be patient (ready=0) Nov 27 20:07:52 Robin kernel: ata20: SRST failed (errno=-16) Nov 27 20:07:57 Robin kernel: ata20: SATA link up 3.0 Gbps (SStatus 123 SControl 300) Nov 27 20:07:57 Robin kernel: ata20.00: ATA-8: WDC WD30EZRX-00MMMB0, WD-WCAWZ2389747, 80.00A80, max UDMA/133 Nov 27 20:07:57 Robin kernel: ata20.00: 5860533168 sectors, multi 0: LBA48 NCQ (depth 31/32) Nov 27 20:07:58 Robin kernel: ata20.00: configured for UDMA/133 Nov 27 20:07:58 Robin kernel: scsi 21:0:0:0: Direct-Access ATA WDC WD30EZRX-00M 0A80 PQ: 0 ANSI: 5 Nov 27 20:07:58 Robin kernel: sd 21:0:0:0: [sdh] 5860533168 512-byte logical blocks: (3.00 TB/2.73 TiB) Nov 27 20:07:58 Robin kernel: sd 21:0:0:0: [sdh] 4096-byte physical blocks Nov 27 20:07:58 Robin kernel: sd 21:0:0:0: [sdh] Write Protect is off Nov 27 20:07:58 Robin kernel: sd 21:0:0:0: [sdh] Mode Sense: 00 3a 00 00 Nov 27 20:07:58 Robin kernel: sd 21:0:0:0: [sdh] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Nov 27 20:07:58 Robin kernel: sd 21:0:0:0: Attached scsi generic sg8 type 0 Nov 27 20:07:58 Robin kernel: sdh: sdh1 Nov 27 20:07:58 Robin kernel: sd 21:0:0:0: [sdh] Attached SCSI disk Nov 27 20:07:58 Robin rc.diskinfo[7275]: SIGHUP received, forcing refresh of disks info. Nov 27 20:07:58 Robin unassigned.devices: Disk with serial 'WDC_WD30EZRX-00MMMB0_WD-WCAWZ2389747', mountpoint 'WDC_WD30EZRX-00MMMB0_WD-WCAWZ2389747' is not set to auto mount and will not be mounted... Nov 27 20:07:58 Robin emhttpd: shcmd (93): rmmod md-mod Nov 27 20:07:58 Robin kernel: md: unRAID driver removed Nov 27 20:07:58 Robin emhttpd: shcmd (94): modprobe md-mod super=/boot/config/super.dat Nov 27 20:07:58 Robin kernel: md: unRAID driver 2.9.4 installed Nov 27 20:07:58 Robin emhttpd: Device inventory: Nov 27 20:07:58 Robin emhttpd: WDC_WD30EZRX-00MMMB0_WD-WCAWZ2389747 (sdh) 512 5860533168 Nov 27 20:07:58 Robin emhttpd: WDC_WD30EURS-63R8UY0_WD-WCAWZ1111556 (sdg) 512 5860533168 Nov 27 20:07:58 Robin emhttpd: ST3000DM001-9YN166_W1F0N4JK (sdd) 512 5860533168 Nov 27 20:07:58 Robin emhttpd: ST3000DM001-9YN166_W1F0ZVBK (sde) 512 5860533168 Nov 27 20:07:58 Robin emhttpd: ST3000DM001-9YN166_Z1F0YAZG (sdb) 512 5860533168 Nov 27 20:07:58 Robin emhttpd: WDC_WD30EZRS-00J99B0_WD-WCAWZ0361944 (sdf) 512 5860533168 Nov 27 20:07:58 Robin emhttpd: WDC_WD30EZRS-00J99B0_WD-WCAWZ2007804 (sdc) 512 5860533168 Nov 27 20:07:58 Robin emhttpd: SanDisk_Cruzer_Fit_4C532000060115109422-0:0 (sda) 512 31266816 Nov 27 20:07:58 Robin kernel: mdcmd (1): import 0 sde 64 2930266532 0 ST3000DM001-9YN166_W1F0ZVBK Nov 27 20:07:58 Robin kernel: md: import disk0: (sde) ST3000DM001-9YN166_W1F0ZVBK size: 2930266532 Nov 27 20:07:58 Robin kernel: mdcmd (2): import 1 sdb 64 2930266532 0 ST3000DM001-9YN166_Z1F0YAZG Nov 27 20:07:58 Robin kernel: md: import disk1: (sdb) ST3000DM001-9YN166_Z1F0YAZG size: 2930266532 Nov 27 20:07:58 Robin kernel: mdcmd (3): import 2 sdd 64 2930266532 0 ST3000DM001-9YN166_W1F0N4JK Nov 27 20:07:58 Robin kernel: md: import disk2: (sdd) ST3000DM001-9YN166_W1F0N4JK size: 2930266532 Nov 27 20:07:58 Robin kernel: mdcmd (4): import 3 Nov 27 20:07:58 Robin kernel: mdcmd (5): import 4 Nov 27 20:07:58 Robin kernel: md: import_slot: 4 missing Nov 27 20:07:58 Robin kernel: mdcmd (6): import 5 sdf 64 2930266532 0 WDC_WD30EZRS-00J99B0_WD-WCAWZ0361944 Nov 27 20:07:58 Robin kernel: md: import disk5: (sdf) WDC_WD30EZRS-00J99B0_WD-WCAWZ0361944 size: 2930266532 Nov 27 20:07:58 Robin kernel: mdcmd (7): import 6 sdg 64 2930266532 0 WDC_WD30EURS-63R8UY0_WD-WCAWZ1111556 Nov 27 20:07:58 Robin kernel: md: import disk6: (sdg) WDC_WD30EURS-63R8UY0_WD-WCAWZ1111556 size: 2930266532 Nov 27 20:07:58 Robin kernel: mdcmd (8): import 7 sdh 64 2930266532 0 WDC_WD30EZRX-00MMMB0_WD-WCAWZ2389747 Nov 27 20:07:58 Robin kernel: md: import disk7: (sdh) WDC_WD30EZRX-00MMMB0_WD-WCAWZ2389747 size: 2930266532 Nov 27 20:07:58 Robin kernel: mdcmd (9): import 8 Nov 27 20:07:58 Robin kernel: mdcmd (10): import 9 Nov 27 20:07:58 Robin kernel: md: import_slot: 9 missing Nov 27 20:07:58 Robin kernel: mdcmd (11): import 10 Nov 27 20:07:58 Robin kernel: mdcmd (12): import 11 Nov 27 20:07:58 Robin kernel: mdcmd (13): import 12 Nov 27 20:07:58 Robin kernel: mdcmd (14): import 13 Nov 27 20:07:58 Robin kernel: mdcmd (15): import 14 sdc 64 2930266532 0 WDC_WD30EZRS-00J99B0_WD-WCAWZ2007804 Nov 27 20:07:58 Robin kernel: md: import disk14: (sdc) WDC_WD30EZRS-00J99B0_WD-WCAWZ2007804 size: 2930266532 Nov 27 20:07:58 Robin kernel: mdcmd (16): import 15 Nov 27 20:07:58 Robin kernel: mdcmd (17): import 16 Nov 27 20:07:58 Robin kernel: mdcmd (18): import 17 Nov 27 20:07:58 Robin kernel: mdcmd (19): import 18 Nov 27 20:07:58 Robin kernel: mdcmd (20): import 19 Nov 27 20:07:58 Robin kernel: mdcmd (21): import 20 Nov 27 20:07:58 Robin kernel: mdcmd (22): import 21 Nov 27 20:07:58 Robin kernel: mdcmd (23): import 22 Nov 27 20:07:58 Robin kernel: mdcmd (24): import 23 Nov 27 20:07:58 Robin kernel: mdcmd (25): import 24 Nov 27 20:07:58 Robin kernel: mdcmd (26): import 25 Nov 27 20:07:58 Robin kernel: mdcmd (27): import 26 Nov 27 20:07:58 Robin kernel: mdcmd (28): import 27 Nov 27 20:07:58 Robin kernel: mdcmd (29): import 28 Nov 27 20:07:58 Robin kernel: mdcmd (30): import 29 Nov 27 20:07:58 Robin kernel: md: import_slot: 29 empty Nov 27 20:07:58 Robin emhttpd: import 30 cache device: no device Nov 27 20:07:58 Robin emhttpd: import flash device: sda Nov 27 20:08:42 Robin login[12726]: ROOT LOGIN on '/dev/pts/1' Nov 27 20:09:56 Robin kernel: ata17: link is slow to respond, please be patient (ready=0) Nov 27 20:09:59 Robin kernel: ata17: SATA link up 3.0 Gbps (SStatus 123 SControl 300) Nov 27 20:09:59 Robin kernel: ata17.00: ATA-9: WDC WD30EZRX-00DC0B0, WD-WMC1T0416128, 80.00A80, max UDMA/133 Nov 27 20:09:59 Robin kernel: ata17.00: 5860533168 sectors, multi 0: LBA48 NCQ (depth 31/32) Nov 27 20:09:59 Robin kernel: ata17.00: configured for UDMA/133 Nov 27 20:09:59 Robin kernel: scsi 18:0:0:0: Direct-Access ATA WDC WD30EZRX-00D 0A80 PQ: 0 ANSI: 5 Nov 27 20:09:59 Robin kernel: sd 18:0:0:0: [sdi] 5860533168 512-byte logical blocks: (3.00 TB/2.73 TiB) Nov 27 20:09:59 Robin kernel: sd 18:0:0:0: [sdi] 4096-byte physical blocks Nov 27 20:09:59 Robin kernel: sd 18:0:0:0: [sdi] Write Protect is off Nov 27 20:09:59 Robin kernel: sd 18:0:0:0: [sdi] Mode Sense: 00 3a 00 00 Nov 27 20:09:59 Robin kernel: sd 18:0:0:0: [sdi] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Nov 27 20:09:59 Robin kernel: sd 18:0:0:0: Attached scsi generic sg9 type 0 Nov 27 20:10:00 Robin kernel: sdi: sdi1 Nov 27 20:10:00 Robin kernel: sd 18:0:0:0: [sdi] Attached SCSI disk Nov 27 20:10:02 Robin kernel: ------------[ cut here ]------------ Nov 27 20:10:02 Robin kernel: kernel BUG at drivers/ata/sata_mv.c:2118! Nov 27 20:10:02 Robin kernel: invalid opcode: 0000 [#1] SMP PTI Nov 27 20:10:02 Robin kernel: CPU: 1 PID: 1223 Comm: scsi_eh_18 Not tainted 4.18.20-unRAID #1 Nov 27 20:10:02 Robin kernel: Hardware name: Supermicro X7DB8-X/X7DB8-X, BIOS 6.00 08/13/2007 Nov 27 20:10:02 Robin kernel: RIP: 0010:mv_qc_prep+0x153/0x1c4 [sata_mv] Nov 27 20:10:02 Robin kernel: Code: 66 89 48 0a eb 26 0f b6 57 2a 80 ce 11 66 89 50 0a 0f b6 4f 2f 48 8d 50 0e 80 cd 11 66 89 48 0c eb 0a 48 8d 50 0a 84 c9 74 02 <0f> 0b 0f b6 47 30 80 cc 12 66 89 02 0f b6 47 2c 80 cc 13 66 89 42 Nov 27 20:10:02 Robin kernel: RSP: 0018:ffffc90000f83a90 EFLAGS: 00010006 Nov 27 20:10:02 Robin kernel: RAX: ffff880222c59060 RBX: ffff880222b9df30 RCX: 0000000000000047 Nov 27 20:10:02 Robin kernel: RDX: ffff880222c5906a RSI: ffff880222c59000 RDI: ffff880222b9df30 Nov 27 20:10:02 Robin kernel: RBP: ffff880222b9c000 R08: 0000000000000002 R09: 0000000000000001 Nov 27 20:10:02 Robin kernel: R10: 0000000000000002 R11: 0000000000000200 R12: ffff880222b9e040 Nov 27 20:10:02 Robin kernel: R13: ffffc90000f83bd0 R14: ffff880222b9c000 R15: 0000000000000000 Nov 27 20:10:02 Robin kernel: FS: 0000000000000000(0000) GS:ffff88022fd00000(0000) knlGS:0000000000000000 Nov 27 20:10:02 Robin kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Nov 27 20:10:02 Robin kernel: CR2: 000015239dfe7480 CR3: 0000000222768000 CR4: 00000000000006e0 Nov 27 20:10:02 Robin kernel: Call Trace: Nov 27 20:10:02 Robin kernel: ata_qc_issue+0x162/0x194 Nov 27 20:10:02 Robin kernel: ata_exec_internal_sg+0x2b1/0x4c9 Nov 27 20:10:02 Robin kernel: ata_exec_internal+0x6a/0x89 Nov 27 20:10:02 Robin kernel: ata_read_log_page+0x11a/0x16b Nov 27 20:10:02 Robin kernel: ata_eh_analyze_ncq_error+0xad/0x282 Nov 27 20:10:02 Robin kernel: ata_eh_link_autopsy+0x126/0x83c Nov 27 20:10:02 Robin kernel: ? ata_set_mode+0xdc/0xe5 Nov 27 20:10:02 Robin kernel: ? __accumulate_pelt_segments+0x1d/0x2a Nov 27 20:10:02 Robin kernel: ? __update_load_avg_se.isra.1+0xe9/0x19c Nov 27 20:10:02 Robin kernel: ata_eh_autopsy+0x23/0xbe Nov 27 20:10:02 Robin kernel: sata_pmp_error_handler+0x3a/0x7a9 Nov 27 20:10:02 Robin kernel: ? __switch_to_asm+0x40/0x70 Nov 27 20:10:02 Robin kernel: ? __switch_to_asm+0x34/0x70 Nov 27 20:10:02 Robin kernel: ? __switch_to_asm+0x40/0x70 Nov 27 20:10:02 Robin kernel: ? __switch_to_asm+0x34/0x70 Nov 27 20:10:02 Robin kernel: ? __switch_to_asm+0x40/0x70 Nov 27 20:10:02 Robin kernel: ? __switch_to_asm+0x34/0x70 Nov 27 20:10:02 Robin kernel: ? __switch_to_asm+0x40/0x70 Nov 27 20:10:02 Robin kernel: ? lock_timer_base+0x4b/0x71 Nov 27 20:10:02 Robin kernel: ata_scsi_port_error_handler+0x221/0x53c Nov 27 20:10:02 Robin kernel: ? scsi_eh_get_sense+0xda/0xda Nov 27 20:10:02 Robin kernel: ata_scsi_error+0x8c/0xb5 Nov 27 20:10:02 Robin kernel: ? scsi_try_target_reset+0x74/0x74 Nov 27 20:10:02 Robin kernel: scsi_error_handler+0x9d/0x36c Nov 27 20:10:02 Robin kernel: kthread+0x10b/0x113 Nov 27 20:10:02 Robin kernel: ? kthread_flush_work_fn+0x9/0x9 Nov 27 20:10:02 Robin kernel: ret_from_fork+0x35/0x40 Nov 27 20:10:02 Robin kernel: Modules linked in: md_mod nfsd lockd grace sunrpc bonding e1000e coretemp kvm sr_mod ipmi_si i2c_i801 i2c_core cdrom i5000_edac i5k_amb ata_piix sata_mv button pcc_cpufreq acpi_cpufreq [last unloaded: md_mod] Nov 27 20:10:02 Robin kernel: ---[ end trace 0ba3e512db1142cf ]--- Nov 27 20:10:02 Robin kernel: RIP: 0010:mv_qc_prep+0x153/0x1c4 [sata_mv] Nov 27 20:10:02 Robin kernel: Code: 66 89 48 0a eb 26 0f b6 57 2a 80 ce 11 66 89 50 0a 0f b6 4f 2f 48 8d 50 0e 80 cd 11 66 89 48 0c eb 0a 48 8d 50 0a 84 c9 74 02 <0f> 0b 0f b6 47 30 80 cc 12 66 89 02 0f b6 47 2c 80 cc 13 66 89 42 Nov 27 20:10:02 Robin kernel: RSP: 0018:ffffc90000f83a90 EFLAGS: 00010006 Nov 27 20:10:02 Robin kernel: RAX: ffff880222c59060 RBX: ffff880222b9df30 RCX: 0000000000000047 Nov 27 20:10:02 Robin kernel: RDX: ffff880222c5906a RSI: ffff880222c59000 RDI: ffff880222b9df30 Nov 27 20:10:02 Robin kernel: RBP: ffff880222b9c000 R08: 0000000000000002 R09: 0000000000000001 Nov 27 20:10:02 Robin kernel: R10: 0000000000000002 R11: 0000000000000200 R12: ffff880222b9e040 Nov 27 20:10:02 Robin kernel: R13: ffffc90000f83bd0 R14: ffff880222b9c000 R15: 0000000000000000 Nov 27 20:10:02 Robin kernel: FS: 0000000000000000(0000) GS:ffff88022fd00000(0000) knlGS:0000000000000000 Nov 27 20:10:02 Robin kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Nov 27 20:10:02 Robin kernel: CR2: 000015239dfe7480 CR3: 0000000222768000 CR4: 00000000000006e0 Nov 27 20:12:00 Robin emhttpd: device /dev/sdi problem getting id Nov 27 20:13:00 Robin kernel: INFO: rcu_sched detected stalls on CPUs/tasks: Nov 27 20:13:00 Robin kernel: 0-...!: (0 ticks this GP) idle=c06/1/4611686018427387904 softirq=46628/46628 fqs=0 Nov 27 20:13:00 Robin kernel: (detected by 1, t=60002 jiffies, g=19733, c=19732, q=1927) Nov 27 20:13:00 Robin kernel: Sending NMI from CPU 1 to CPUs 0: Nov 27 20:13:00 Robin kernel: NMI backtrace for cpu 0 Nov 27 20:13:00 Robin kernel: CPU: 0 PID: 1253 Comm: kworker/u4:20 Tainted: G D 4.18.20-unRAID #1 Nov 27 20:13:00 Robin kernel: Hardware name: Supermicro X7DB8-X/X7DB8-X, BIOS 6.00 08/13/2007 Nov 27 20:13:00 Robin kernel: Workqueue: events_freezable_power_ disk_events_workfn Nov 27 20:13:00 Robin kernel: RIP: 0010:native_queued_spin_lock_slowpath+0x15f/0x16d Nov 27 20:13:00 Robin kernel: Code: 00 f0 0f b1 37 75 eb eb 13 48 8b 0a 48 85 c9 75 04 f3 90 eb f4 c7 41 08 01 00 00 00 65 ff 0d a6 da f9 7e c3 85 d2 74 0a 8b 07 <84> c0 74 04 f3 90 eb f6 66 c7 07 01 00 c3 49 b8 eb 83 b5 80 46 86
  3. Disk shows up in unassigned devices but the mount button is greyed out. I am doing a rebuild on a spare drive which should bring everything back again. Likely this will only be an exercise in curiosity. Do you think this XFS disk is salvageable?? This disk was in an old 6.6.7 server and if installed, the server will completely lock up. Removing the disk and installing in a newer server with 6.9b25 gives us this data.
  4. Full diagnostics syslog from the newer server with the bad drive inserted. cara-diagnostics-20201128-0946.zip
  5. Drive is WDC - 6128 Here is the unassigned devices log showing some error from that drive. Is there any hope for this one? ErrorWarningSystemArray Sep 8 04:57:59 Cara kernel: ata1: SATA max UDMA/133 abar m2048@0xd1200000 port 0xd1200100 irq 33 Sep 8 04:57:59 Cara kernel: ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Sep 8 04:57:59 Cara kernel: ata1.00: ATA-8: ST33000651AS, 9XK0NC4Q, CC45, max UDMA/133 Sep 8 04:57:59 Cara kernel: ata1.00: 5860533168 sectors, multi 16: LBA48 NCQ (depth 32) Sep 8 04:57:59 Cara kernel: ata1.00: configured for UDMA/133 Sep 8 04:57:59 Cara kernel: sd 5:0:0:0: [sdf] 5860533168 512-byte logical blocks: (3.00 TB/2.73 TiB) Sep 8 04:57:59 Cara kernel: sd 5:0:0:0: [sdf] 4096-byte physical blocks Sep 8 04:57:59 Cara kernel: sd 5:0:0:0: [sdf] Write Protect is off Sep 8 04:57:59 Cara kernel: sd 5:0:0:0: [sdf] Mode Sense: 00 3a 00 00 Sep 8 04:57:59 Cara kernel: sd 5:0:0:0: [sdf] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Sep 8 04:57:59 Cara kernel: sdf: sdf1 Sep 8 04:57:59 Cara kernel: sd 5:0:0:0: [sdf] Attached SCSI disk Sep 8 04:58:18 Cara emhttpd: ST3000DM001-9YN166_W1F115AC (sdf) 512 5860533168 Sep 8 04:58:24 Cara unassigned.devices: Issue spin down timer for device '/dev/sdf'. Nov 27 22:33:07 Cara kernel: ata1: SATA link down (SStatus 0 SControl 300) Nov 27 22:33:12 Cara kernel: ata1: SATA link down (SStatus 0 SControl 300) Nov 27 22:33:18 Cara kernel: ata1: SATA link down (SStatus 0 SControl 300) Nov 27 22:33:18 Cara kernel: ata1.00: disabled Nov 27 22:33:18 Cara kernel: ata1.00: detaching (SCSI 1:0:0:0) Nov 27 22:33:30 Cara kernel: sd 5:0:0:0: [sdf] Synchronizing SCSI cache Nov 27 22:33:30 Cara kernel: sd 5:0:0:0: [sdf] Synchronize Cache(10) failed: Result: hostbyte=0x04 driverbyte=0x00 Nov 27 22:33:30 Cara kernel: sd 5:0:0:0: [sdf] Stopping disk Nov 27 22:33:30 Cara kernel: sd 5:0:0:0: [sdf] Start/Stop Unit failed: Result: hostbyte=0x04 driverbyte=0x00 Nov 27 22:38:23 Cara kernel: ata1: link is slow to respond, please be patient (ready=0) Nov 27 22:38:27 Cara kernel: ata1: COMRESET failed (errno=-16) Nov 27 22:38:29 Cara kernel: ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Nov 27 22:38:29 Cara kernel: ata1.00: ATA-8: ST3000DM001-9YN166, W1F115DE, CC9F, max UDMA/133 Nov 27 22:38:29 Cara kernel: ata1.00: 5860533168 sectors, multi 0: LBA48 NCQ (depth 32), AA Nov 27 22:38:29 Cara kernel: ata1.00: configured for UDMA/133 Nov 27 22:42:12 Cara kernel: ata1: SATA link down (SStatus 0 SControl 300) Nov 27 22:42:17 Cara kernel: ata1: SATA link down (SStatus 0 SControl 300) Nov 27 22:42:23 Cara kernel: ata1: SATA link down (SStatus 0 SControl 300) Nov 27 22:42:23 Cara kernel: ata1.00: disabled Nov 27 22:42:23 Cara kernel: ata1.00: detaching (SCSI 1:0:0:0) Nov 27 22:42:57 Cara kernel: ata1: link is slow to respond, please be patient (ready=0) Nov 27 22:43:01 Cara kernel: ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Nov 27 22:43:01 Cara kernel: ata1.00: ATA-9: WDC WD30EZRX-00DC0B0, WD-WMC1T0416128, 80.00A80, max UDMA/133 Nov 27 22:43:01 Cara kernel: ata1.00: 5860533168 sectors, multi 0: LBA48 NCQ (depth 32), AA Nov 27 22:43:01 Cara kernel: ata1.00: configured for UDMA/133 Nov 27 22:43:04 Cara kernel: ata1.00: exception Emask 0x0 SAct 0x1000 SErr 0x0 action 0x0 Nov 27 22:43:04 Cara kernel: ata1.00: irq_stat 0x40000008 Nov 27 22:43:04 Cara kernel: ata1.00: failed command: READ FPDMA QUEUED Nov 27 22:43:04 Cara kernel: ata1.00: cmd 60/08:60:40:00:00/00:00:00:00:00/40 tag 12 ncq dma 4096 in Nov 27 22:43:04 Cara kernel: ata1.00: status: { DRDY ERR } Nov 27 22:43:04 Cara kernel: ata1.00: error: { UNC } Nov 27 22:43:04 Cara kernel: ata1.00: configured for UDMA/133 Nov 27 22:43:04 Cara kernel: ata1: EH complete Nov 27 22:43:07 Cara kernel: ata1.00: exception Emask 0x0 SAct 0x200000 SErr 0x0 action 0x0 Nov 27 22:43:07 Cara kernel: ata1.00: irq_stat 0x40000008 Nov 27 22:43:07 Cara kernel: ata1.00: failed command: READ FPDMA QUEUED Nov 27 22:43:07 Cara kernel: ata1.00: cmd 60/08:a8:40:00:00/00:00:00:00:00/40 tag 21 ncq dma 4096 in Nov 27 22:43:07 Cara kernel: ata1.00: status: { DRDY ERR } Nov 27 22:43:07 Cara kernel: ata1.00: error: { UNC } Nov 27 22:43:07 Cara kernel: ata1.00: configured for UDMA/133 Nov 27 22:43:07 Cara kernel: ata1: EH complete Nov 27 22:43:10 Cara kernel: ata1.00: exception Emask 0x0 SAct 0x8000 SErr 0x0 action 0x0 Nov 27 22:43:10 Cara kernel: ata1.00: irq_stat 0x40000008 Nov 27 22:43:10 Cara kernel: ata1.00: failed command: READ FPDMA QUEUED Nov 27 22:43:10 Cara kernel: ata1.00: cmd 60/08:78:40:00:00/00:00:00:00:00/40 tag 15 ncq dma 4096 in Nov 27 22:43:10 Cara kernel: ata1.00: status: { DRDY ERR } Nov 27 22:43:10 Cara kernel: ata1.00: error: { UNC } Nov 27 22:43:10 Cara kernel: ata1.00: configured for UDMA/133 Nov 27 22:43:10 Cara kernel: ata1: EH complete Nov 27 22:43:13 Cara kernel: ata1.00: exception Emask 0x0 SAct 0x10700 SErr 0x0 action 0x0 Nov 27 22:43:13 Cara kernel: ata1.00: irq_stat 0x40000008 Nov 27 22:43:13 Cara kernel: ata1.00: failed command: READ FPDMA QUEUED Nov 27 22:43:13 Cara kernel: ata1.00: cmd 60/01:80:40:00:00/00:00:00:00:00/40 tag 16 ncq dma 512 in Nov 27 22:43:13 Cara kernel: ata1.00: status: { DRDY ERR } Nov 27 22:43:13 Cara kernel: ata1.00: error: { UNC } Nov 27 22:43:13 Cara kernel: ata1.00: configured for UDMA/133 Nov 27 22:43:13 Cara kernel: ata1: EH complete Nov 27 22:43:15 Cara kernel: ata1.00: exception Emask 0x0 SAct 0x40000003 SErr 0x0 action 0x0 Nov 27 22:43:15 Cara kernel: ata1.00: irq_stat 0x40000008 Nov 27 22:43:15 Cara kernel: ata1.00: failed command: READ FPDMA QUEUED Nov 27 22:43:15 Cara kernel: ata1.00: cmd 60/01:08:41:00:00/00:00:00:00:00/40 tag 1 ncq dma 512 in Nov 27 22:43:15 Cara kernel: ata1.00: status: { DRDY ERR } Nov 27 22:43:15 Cara kernel: ata1.00: error: { UNC } Nov 27 22:43:15 Cara kernel: ata1.00: configured for UDMA/133 Nov 27 22:43:15 Cara kernel: ata1: EH complete Nov 27 22:43:18 Cara kernel: ata1.00: exception Emask 0x0 SAct 0xc SErr 0x0 action 0x0 Nov 27 22:43:18 Cara kernel: ata1.00: irq_stat 0x40000008 Nov 27 22:43:18 Cara kernel: ata1.00: failed command: READ FPDMA QUEUED Nov 27 22:43:18 Cara kernel: ata1.00: cmd 60/03:18:42:00:00/00:00:00:00:00/40 tag 3 ncq dma 1536 in Nov 27 22:43:18 Cara kernel: ata1.00: status: { DRDY ERR } Nov 27 22:43:18 Cara kernel: ata1.00: error: { UNC } Nov 27 22:43:18 Cara kernel: ata1.00: configured for UDMA/133 Nov 27 22:43:18 Cara kernel: ata1: EH complete Nov 27 22:43:21 Cara kernel: ata1.00: exception Emask 0x0 SAct 0x800000 SErr 0x0 action 0x0 Nov 27 22:43:21 Cara kernel: ata1.00: irq_stat 0x40000008 Nov 27 22:43:21 Cara kernel: ata1.00: failed command: READ FPDMA QUEUED Nov 27 22:43:21 Cara kernel: ata1.00: cmd 60/03:b8:45:00:00/00:00:00:00:00/40 tag 23 ncq dma 1536 in Nov 27 22:43:21 Cara kernel: ata1.00: status: { DRDY ERR } Nov 27 22:43:21 Cara kernel: ata1.00: error: { UNC } Nov 27 22:43:21 Cara kernel: ata1.00: configured for UDMA/133 Nov 27 22:43:21 Cara kernel: ata1: EH complete Nov 27 22:43:32 Cara kernel: sd 5:0:0:0: [sdf] 5860533168 512-byte logical blocks: (3.00 TB/2.73 TiB) Nov 27 22:43:32 Cara kernel: sd 5:0:0:0: [sdf] 4096-byte physical blocks Nov 27 22:43:32 Cara kernel: sd 5:0:0:0: [sdf] Write Protect is off Nov 27 22:43:32 Cara kernel: sd 5:0:0:0: [sdf] Mode Sense: 00 3a 00 00 Nov 27 22:43:32 Cara kernel: sd 5:0:0:0: [sdf] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Nov 27 22:43:32 Cara kernel: sdf: sdf1 Nov 27 22:43:32 Cara kernel: sd 5:0:0:0: [sdf] Attached SCSI disk Nov 27 22:43:32 Cara unassigned.devices: Issue spin down timer for device '/dev/sdf'. Nov 27 22:44:02 Cara kernel: sd 5:0:0:0: [sdf] Synchronizing SCSI cache Nov 27 22:44:02 Cara kernel: sd 5:0:0:0: [sdf] Synchronize Cache(10) failed: Result: hostbyte=0x04 driverbyte=0x00 Nov 27 22:44:02 Cara kernel: sd 5:0:0:0: [sdf] Stopping disk Nov 27 22:44:02 Cara kernel: sd 5:0:0:0: [sdf] Start/Stop Unit failed: Result: hostbyte=0x04 driverbyte=0x00 Nov 27 22:44:07 Cara kernel: sd 2:0:0:0: [sdf] 5860533168 512-byte logical blocks: (3.00 TB/2.73 TiB) Nov 27 22:44:07 Cara kernel: sd 2:0:0:0: [sdf] 4096-byte physical blocks Nov 27 22:44:07 Cara kernel: sd 2:0:0:0: [sdf] Write Protect is off Nov 27 22:44:07 Cara kernel: sd 2:0:0:0: [sdf] Mode Sense: 00 3a 00 00 Nov 27 22:44:07 Cara kernel: sd 2:0:0:0: [sdf] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Nov 27 22:44:07 Cara kernel: sdf: sdf1 Nov 27 22:44:07 Cara kernel: sd 2:0:0:0: [sdf] Attached SCSI disk Nov 27 22:44:07 Cara unassigned.devices: Issue spin down timer for device '/dev/sdf'. Nov 27 22:47:25 Cara kernel: ata1: SATA link down (SStatus 0 SControl 300) Nov 27 22:47:31 Cara kernel: ata1: SATA link down (SStatus 0 SControl 300) Nov 27 22:47:36 Cara kernel: ata1: SATA link down (SStatus 0 SControl 300) Nov 27 22:47:36 Cara kernel: ata1.00: disabled Nov 27 22:47:36 Cara kernel: ata1.00: detaching (SCSI 1:0:0:0) Nov 27 22:50:59 Cara kernel: sd 2:0:0:0: [sdf] Synchronizing SCSI cache Nov 27 22:50:59 Cara kernel: sd 2:0:0:0: [sdf] Synchronize Cache(10) failed: Result: hostbyte=0x04 driverbyte=0x00 Nov 27 22:50:59 Cara kernel: sd 2:0:0:0: [sdf] Stopping disk Nov 27 22:50:59 Cara kernel: sd 2:0:0:0: [sdf] Start/Stop Unit failed: Result: hostbyte=0x04 driverbyte=0x00 Nov 28 08:32:37 Cara kernel: sd 5:0:0:0: [sdf] 5860533168 512-byte logical blocks: (3.00 TB/2.73 TiB) Nov 28 08:32:37 Cara kernel: sd 5:0:0:0: [sdf] 4096-byte physical blocks Nov 28 08:32:37 Cara kernel: sd 5:0:0:0: [sdf] Write Protect is off Nov 28 08:32:37 Cara kernel: sd 5:0:0:0: [sdf] Mode Sense: 00 3a 00 00 Nov 28 08:32:37 Cara kernel: sd 5:0:0:0: [sdf] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Nov 28 08:32:37 Cara kernel: sdf: sdf1 Nov 28 08:32:37 Cara kernel: sd 5:0:0:0: [sdf] Attached SCSI disk Nov 28 08:32:40 Cara kernel: sd 5:0:0:0: [sdf] tag#6 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 cmd_age=2s Nov 28 08:32:40 Cara kernel: sd 5:0:0:0: [sdf] tag#6 Sense Key : 0x3 [current] Nov 28 08:32:40 Cara kernel: sd 5:0:0:0: [sdf] tag#6 ASC=0x11 ASCQ=0x4 Nov 28 08:32:40 Cara kernel: sd 5:0:0:0: [sdf] tag#6 CDB: opcode=0x88 88 00 00 00 00 00 00 00 00 40 00 00 00 08 00 00 Nov 28 08:32:40 Cara kernel: blk_update_request: I/O error, dev sdf, sector 64 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0 Nov 28 08:32:43 Cara kernel: sd 5:0:0:0: [sdf] tag#16 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 cmd_age=2s Nov 28 08:32:43 Cara kernel: sd 5:0:0:0: [sdf] tag#16 Sense Key : 0x3 [current] Nov 28 08:32:43 Cara kernel: sd 5:0:0:0: [sdf] tag#16 ASC=0x11 ASCQ=0x4 Nov 28 08:32:43 Cara kernel: sd 5:0:0:0: [sdf] tag#16 CDB: opcode=0x88 88 00 00 00 00 00 00 00 00 40 00 00 00 08 00 00 Nov 28 08:32:43 Cara kernel: blk_update_request: I/O error, dev sdf, sector 64 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 Nov 28 08:32:43 Cara kernel: Buffer I/O error on dev sdf, logical block 8, async page read Nov 28 08:32:46 Cara kernel: sd 5:0:0:0: [sdf] tag#9 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 cmd_age=2s Nov 28 08:32:46 Cara kernel: sd 5:0:0:0: [sdf] tag#9 Sense Key : 0x3 [current] Nov 28 08:32:46 Cara kernel: sd 5:0:0:0: [sdf] tag#9 ASC=0x11 ASCQ=0x4 Nov 28 08:32:46 Cara kernel: sd 5:0:0:0: [sdf] tag#9 CDB: opcode=0x88 88 00 00 00 00 00 00 00 00 40 00 00 00 08 00 00 Nov 28 08:32:46 Cara kernel: blk_update_request: I/O error, dev sdf, sector 64 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0 Nov 28 08:32:48 Cara kernel: sd 5:0:0:0: [sdf] tag#7 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 cmd_age=2s Nov 28 08:32:48 Cara kernel: sd 5:0:0:0: [sdf] tag#7 Sense Key : 0x3 [current] Nov 28 08:32:48 Cara kernel: sd 5:0:0:0: [sdf] tag#7 ASC=0x11 ASCQ=0x4 Nov 28 08:32:48 Cara kernel: sd 5:0:0:0: [sdf] tag#7 CDB: opcode=0x88 88 00 00 00 00 00 00 00 00 40 00 00 00 01 00 00 Nov 28 08:32:48 Cara kernel: blk_update_request: I/O error, dev sdf, sector 64 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 Nov 28 08:32:48 Cara kernel: Buffer I/O error on dev sdf1, logical block 0, async page read Nov 28 08:32:51 Cara kernel: sd 5:0:0:0: [sdf] tag#6 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 cmd_age=5s Nov 28 08:32:51 Cara kernel: sd 5:0:0:0: [sdf] tag#6 Sense Key : 0x3 [current] Nov 28 08:32:51 Cara kernel: sd 5:0:0:0: [sdf] tag#6 ASC=0x11 ASCQ=0x4 Nov 28 08:32:51 Cara kernel: sd 5:0:0:0: [sdf] tag#6 CDB: opcode=0x88 88 00 00 00 00 00 00 00 00 41 00 00 00 06 00 00 Nov 28 08:32:51 Cara kernel: blk_update_request: I/O error, dev sdf, sector 65 op 0x0:(READ) flags 0x0 phys_seg 6 prio class 0 Nov 28 08:32:51 Cara kernel: Buffer I/O error on dev sdf1, logical block 1, async page read Nov 28 08:32:51 Cara kernel: Buffer I/O error on dev sdf1, logical block 2, async page read Nov 28 08:32:51 Cara kernel: Buffer I/O error on dev sdf1, logical block 3, async page read Nov 28 08:32:51 Cara kernel: Buffer I/O error on dev sdf1, logical block 4, async page read Nov 28 08:32:51 Cara kernel: Buffer I/O error on dev sdf1, logical block 5, async page read Nov 28 08:32:51 Cara kernel: Buffer I/O error on dev sdf1, logical block 6, async page read Nov 28 08:32:54 Cara kernel: sd 5:0:0:0: [sdf] tag#28 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 cmd_age=8s Nov 28 08:32:54 Cara kernel: sd 5:0:0:0: [sdf] tag#28 Sense Key : 0x3 [current] Nov 28 08:32:54 Cara kernel: sd 5:0:0:0: [sdf] tag#28 ASC=0x11 ASCQ=0x4 Nov 28 08:32:54 Cara kernel: sd 5:0:0:0: [sdf] tag#28 CDB: opcode=0x88 88 00 00 00 00 00 00 00 00 47 00 00 00 01 00 00 Nov 28 08:32:54 Cara kernel: blk_update_request: I/O error, dev sdf, sector 71 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 Nov 28 08:32:54 Cara kernel: Buffer I/O error on dev sdf1, logical block 7, async page read Nov 28 08:32:54 Cara unassigned.devices: Issue spin down timer for device '/dev/sdf'. Nov 28 08:37:28 Cara kernel: sd 5:0:0:0: [sdf] Synchronizing SCSI cache Nov 28 08:37:28 Cara kernel: sd 5:0:0:0: [sdf] Synchronize Cache(10) failed: Result: hostbyte=0x04 driverbyte=0x00 Nov 28 08:37:28 Cara kernel: sd 5:0:0:0: [sdf] Stopping disk Nov 28 08:37:28 Cara kernel: sd 5:0:0:0: [sdf] Start/Stop Unit failed: Result: hostbyte=0x04 driverbyte=0x00 Nov 28 08:37:34 Cara kernel: ata1: link is slow to respond, please be patient (ready=0) Nov 28 08:37:34 Cara kernel: ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Nov 28 08:37:34 Cara kernel: ata1.00: ATA-9: WDC WD30EZRX-00DC0B0, WD-WMC1T0416128, 80.00A80, max UDMA/133 Nov 28 08:37:34 Cara kernel: ata1.00: 5860533168 sectors, multi 0: LBA48 NCQ (depth 32), AA Nov 28 08:37:34 Cara kernel: ata1.00: configured for UDMA/133 Nov 28 08:37:34 Cara kernel: sd 1:0:0:0: [sdf] 5860533168 512-byte logical blocks: (3.00 TB/2.73 TiB) Nov 28 08:37:34 Cara kernel: sd 1:0:0:0: [sdf] 4096-byte physical blocks Nov 28 08:37:34 Cara kernel: sd 1:0:0:0: [sdf] Write Protect is off Nov 28 08:37:34 Cara kernel: sd 1:0:0:0: [sdf] Mode Sense: 00 3a 00 00 Nov 28 08:37:34 Cara kernel: sd 1:0:0:0: [sdf] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Nov 28 08:37:34 Cara kernel: sdf: sdf1 Nov 28 08:37:34 Cara kernel: sd 1:0:0:0: [sdf] Attached SCSI disk Nov 28 08:37:37 Cara kernel: ata1.00: exception Emask 0x0 SAct 0x20 SErr 0x0 action 0x0 Nov 28 08:37:37 Cara kernel: ata1.00: irq_stat 0x40000008 Nov 28 08:37:37 Cara kernel: ata1.00: failed command: READ FPDMA QUEUED Nov 28 08:37:37 Cara kernel: ata1.00: cmd 60/08:28:40:00:00/00:00:00:00:00/40 tag 5 ncq dma 4096 in Nov 28 08:37:37 Cara kernel: ata1.00: status: { DRDY ERR } Nov 28 08:37:37 Cara kernel: ata1.00: error: { UNC } Nov 28 08:37:37 Cara kernel: ata1.00: configured for UDMA/133 Nov 28 08:37:37 Cara kernel: sd 1:0:0:0: [sdf] tag#5 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 cmd_age=2s Nov 28 08:37:37 Cara kernel: sd 1:0:0:0: [sdf] tag#5 Sense Key : 0x3 [current] Nov 28 08:37:37 Cara kernel: sd 1:0:0:0: [sdf] tag#5 ASC=0x11 ASCQ=0x4 Nov 28 08:37:37 Cara kernel: sd 1:0:0:0: [sdf] tag#5 CDB: opcode=0x88 88 00 00 00 00 00 00 00 00 40 00 00 00 08 00 00 Nov 28 08:37:37 Cara kernel: blk_update_request: I/O error, dev sdf, sector 64 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0 Nov 28 08:37:37 Cara kernel: ata1: EH complete Nov 28 08:37:40 Cara kernel: ata1.00: exception Emask 0x0 SAct 0x10 SErr 0x0 action 0x0 Nov 28 08:37:40 Cara kernel: ata1.00: irq_stat 0x40000008 Nov 28 08:37:40 Cara kernel: ata1.00: failed command: READ FPDMA QUEUED Nov 28 08:37:40 Cara kernel: ata1.00: cmd 60/08:20:40:00:00/00:00:00:00:00/40 tag 4 ncq dma 4096 in Nov 28 08:37:40 Cara kernel: ata1.00: status: { DRDY ERR } Nov 28 08:37:40 Cara kernel: ata1.00: error: { UNC } Nov 28 08:37:40 Cara kernel: ata1.00: configured for UDMA/133 Nov 28 08:37:40 Cara kernel: sd 1:0:0:0: [sdf] tag#4 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 cmd_age=2s Nov 28 08:37:40 Cara kernel: sd 1:0:0:0: [sdf] tag#4 Sense Key : 0x3 [current] Nov 28 08:37:40 Cara kernel: sd 1:0:0:0: [sdf] tag#4 ASC=0x11 ASCQ=0x4 Nov 28 08:37:40 Cara kernel: sd 1:0:0:0: [sdf] tag#4 CDB: opcode=0x88 88 00 00 00 00 00 00 00 00 40 00 00 00 08 00 00 Nov 28 08:37:40 Cara kernel: blk_update_request: I/O error, dev sdf, sector 64 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 Nov 28 08:37:40 Cara kernel: Buffer I/O error on dev sdf, logical block 8, async page read Nov 28 08:37:40 Cara kernel: ata1: EH complete Nov 28 08:37:43 Cara kernel: ata1.00: exception Emask 0x0 SAct 0x8 SErr 0x0 action 0x0 Nov 28 08:37:43 Cara kernel: ata1.00: irq_stat 0x40000008 Nov 28 08:37:43 Cara kernel: ata1.00: failed command: READ FPDMA QUEUED Nov 28 08:37:43 Cara kernel: ata1.00: cmd 60/08:18:40:00:00/00:00:00:00:00/40 tag 3 ncq dma 4096 in Nov 28 08:37:43 Cara kernel: ata1.00: status: { DRDY ERR } Nov 28 08:37:43 Cara kernel: ata1.00: error: { UNC } Nov 28 08:37:43 Cara kernel: ata1.00: configured for UDMA/133 Nov 28 08:37:43 Cara kernel: sd 1:0:0:0: [sdf] tag#3 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 cmd_age=2s Nov 28 08:37:43 Cara kernel: sd 1:0:0:0: [sdf] tag#3 Sense Key : 0x3 [current] Nov 28 08:37:43 Cara kernel: sd 1:0:0:0: [sdf] tag#3 ASC=0x11 ASCQ=0x4 Nov 28 08:37:43 Cara kernel: sd 1:0:0:0: [sdf] tag#3 CDB: opcode=0x88 88 00 00 00 00 00 00 00 00 40 00 00 00 08 00 00 Nov 28 08:37:43 Cara kernel: blk_update_request: I/O error, dev sdf, sector 64 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0 Nov 28 08:37:43 Cara kernel: ata1: EH complete Nov 28 08:37:46 Cara kernel: ata1.00: exception Emask 0x0 SAct 0x8000000 SErr 0x0 action 0x0 Nov 28 08:37:46 Cara kernel: ata1.00: irq_stat 0x40000008 Nov 28 08:37:46 Cara kernel: ata1.00: failed command: READ FPDMA QUEUED Nov 28 08:37:46 Cara kernel: ata1.00: cmd 60/08:d8:40:00:00/00:00:00:00:00/40 tag 27 ncq dma 4096 in Nov 28 08:37:46 Cara kernel: ata1.00: status: { DRDY ERR } Nov 28 08:37:46 Cara kernel: ata1.00: error: { UNC } Nov 28 08:37:46 Cara kernel: ata1.00: configured for UDMA/133 Nov 28 08:37:46 Cara kernel: sd 1:0:0:0: [sdf] tag#27 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 cmd_age=2s Nov 28 08:37:46 Cara kernel: sd 1:0:0:0: [sdf] tag#27 Sense Key : 0x3 [current] Nov 28 08:37:46 Cara kernel: sd 1:0:0:0: [sdf] tag#27 ASC=0x11 ASCQ=0x4 Nov 28 08:37:46 Cara kernel: sd 1:0:0:0: [sdf] tag#27 CDB: opcode=0x88 88 00 00 00 00 00 00 00 00 40 00 00 00 08 00 00 Nov 28 08:37:46 Cara kernel: blk_update_request: I/O error, dev sdf, sector 64 op 0x0:(READ) flags 0x0 phys_seg 8 prio class 0 Nov 28 08:37:46 Cara kernel: Buffer I/O error on dev sdf1, logical block 0, async page read Nov 28 08:37:46 Cara kernel: Buffer I/O error on dev sdf1, logical block 1, async page read Nov 28 08:37:46 Cara kernel: Buffer I/O error on dev sdf1, logical block 2, async page read Nov 28 08:37:46 Cara kernel: Buffer I/O error on dev sdf1, logical block 3, async page read Nov 28 08:37:46 Cara kernel: Buffer I/O error on dev sdf1, logical block 4, async page read Nov 28 08:37:46 Cara kernel: Buffer I/O error on dev sdf1, logical block 5, async page read Nov 28 08:37:46 Cara kernel: Buffer I/O error on dev sdf1, logical block 6, async page read Nov 28 08:37:46 Cara kernel: Buffer I/O error on dev sdf1, logical block 7, async page read Nov 28 08:37:46 Cara kernel: ata1: EH complete Nov 28 08:37:46 Cara unassigned.devices: Issue spin down timer for device '/dev/sdf'.
  6. ISP admits to blocking these ports but for an additional fee they can give me a static IP (which I already have) and ports 80 and 443 will be unblocked. The additional fee is not desirable, so now I need to find a different way around this blockage.
  7. Here is the router page: Going to 192.168.13.142:1880 from inside the local lan brings me to the congratulations page for NPM. Does it look ok to you for the normal suggested port forwarding logic for NPM? Googling around led me to believe that ISP blocking of 80 and 443 was quite normal and to be expected. Your response makes me question this. You haven't had to deal with blocked ports? It does seem that others have had to deal with this. There is even a SpaceInvaderOne unRaid video about port 80 blockage with Lets Encrypt setup. And sorry, this particular area where I am testing at present does not have other ISP options. If they are blocking, we will have to either ask nicely, or just work around it. I'll dig some more and see what I find. Thanks for the pointers...
  8. From my cell phone with WiFi shut off, both my external IP address and my domain forwarded to this IP respond with the same thing. Yes IP is fixed. This site cannot be reached. ERR_Connection_Refused Router is forwarding 80 and 443 to unRaid 1880 and 18443 as per a default NPM recommended install.
  9. @Kru-x NPM is installed and available. But when I attempt to request a cert for a private domain already forwarded to my ip address, I get interenal error from NPM. I suspect that I may have port 80 and 443 being blocked by my no name ISP. I have those ports forwarded in my router, and the NPM congratulations page is never displayed. I can torrent (with unRaid Transmission docker) over this ISP, so not everything is blocked. Is this likely my problem?
  10. Ah OK, thanks for pointing me in the right direction. Once I can spin up a WP site repeatedly without error, I'll move on to getting NPM to work.
  11. Ok, I just deleted the mariaDB passwords from the WP container setup and suddenly it works. WP is installed and the dashboard is up now. Is that what you do with passwords for setup. Ignore them?
  12. I am just trying to get it to communicate in any way. Maybe something else is wrong? What is your normal way to get it to work?
  13. Ok, I have installed WP and MariaDB multiple times to try and get connection going. I assume this is the best way to start and then bring NPM along later. I keep getting "Error establishing a database connection" I have the following in MariaDB Host Port 1 :3306 Key1 : 99 Key2 : 100 Key3 : 0 And in WP Container port: 8080 WORDPRESS_DB_HOST: 192.168.13.142:3306 WORDPRESS_DB_USER: 99 WORDPRESS_DB_PASSWORD: 0 I've created and recreated the containers multiple times without getting past the database error. It seems editing the container is no good as that takes me to a http://192.168.13.142:8080/ "Problem with the connection error" Each time I create a new mariaDB container and WP container, I call it a new name Wordpress2 and store it in a new appdata folder etc... What stupid thing am I doing wrong?
  14. Hey, @Kru-xthis has me tempted to play with your tools. I have 3 Wordpress sites in mind that I would run. All 3 are at different domains. One is a simple site with minimal data, traffic, and plugins. Site 2 has several GB of image files in the media folder but still has minimal traffic. Site 3 is a WooCommerce site with 100GB of image files and paypal and credit card processing and the goodies. Can I run all 3 on my unRaid server? I have Gigibit ethernet from Google Fiber with a single IP address. The unRaid server is Xeon 2670 based with 64GB ram.
  15. ... and there is some possibility that unRaid may include ZFS as a supported file system out of the box. Developer has been ranting about btrfs and dropping ZFS hints. We will just have to wait and see. The plugin has been working with unRaid for over a year, and we can thank steini84 for his dedication. Getting Tom to bake it in to unRaid and have it be more thoroughly tested will be even better yet.
  16. Remote snapshot replication using SSH?? I wrote up a rsync ssh guide that has been very solid, but ZFS and snapshot replication was never part of that.
  17. What is your use case for Sanoid that you cannot already do with above ZFS tools?? Yes, we are always interested in new shiny things.. Is there any issues with it?
  18. Followup on the 6.9.0 b22 with Win10 ZFS problems. If a Win10 VM is started and stopped, the server will shutdown successfully. The attempt to restart a shutdown Win10 VM will fail and this is what is bringing ZFS and unRaid to a bad place where unRaid will not shutdown.
  19. Followup on the 6.9.0 b22 with Win10 ZFS install problems. When the VM is shut down, and then attempt is made to restart it, the VM tab on the server will lock up. Other than this, the server will continue to operate normally. When the server is shut down from the GUI, to attempt to bring the VM back online, unRaid reports that shutdown is successful with system powered off. A putty telnet window open gets the expected "The system is going down for system halt NOW!" message, but after unRaid reports the system is powered off, a press of the enter key shows putty still connected with a telnet session active. Even the unRaid array remains mounted. I don't know if this is unRaid's fault or ZFS? I look forward to somebody else attempting to replicate this issue with 6.9.0 b22 and a Win10 vm. Syslog entries after initating shutdown from GUI - It should be off, but its still live. Jul 2 09:33:08 Cara shutdown[140908]: shutting down for system halt Jul 2 09:33:08 Cara init: Switching to runlevel: 0 Jul 2 09:33:08 Cara init: Trying to re-exec init Jul 2 09:33:12 Cara kernel: mdcmd (44): nocheck cancel Jul 2 09:33:13 Cara emhttpd: Spinning up all drives... Jul 2 09:33:13 Cara kernel: mdcmd (45): spinup 1 Jul 2 09:33:14 Cara emhttpd: Stopping services... Jul 2 09:33:14 Cara emhttpd: shcmd (791): /etc/rc.d/rc.libvirt stop Jul 2 09:34:42 Cara root: Status of all loop devices Jul 2 09:34:42 Cara root: /dev/loop1: [2049]:4 (/boot/bzfirmware) Jul 2 09:34:42 Cara root: /dev/loop2: [0044]:264 (/mnt/disk1/system/libvirt/libvirt.img) Jul 2 09:34:42 Cara root: /dev/loop0: [0044]:260 (/mnt/disk1/system/docker/docker.img) Jul 2 09:34:42 Cara root: Active pids left on /mnt/* Jul 2 09:34:42 Cara root: USER PID ACCESS COMMAND Jul 2 09:34:42 Cara root: /mnt/MFS: root kernel mount /mnt/MFS Jul 2 09:34:42 Cara root: /mnt/disk1: root kernel mount /mnt/disk1 Jul 2 09:34:42 Cara root: /mnt/disks: root kernel mount /mnt/disks Jul 2 09:34:42 Cara root: /mnt/user: root kernel mount /mnt/user Jul 2 09:34:42 Cara root: root 54064 f.c.. smbd Jul 2 09:34:42 Cara root: /mnt/user0: root kernel mount /mnt/user0 Jul 2 09:34:42 Cara root: Active pids left on /dev/md* Jul 2 09:34:42 Cara root: Generating diagnostics... Jul 2 09:34:47 Cara avahi-daemon[4244]: Interface docker0.IPv4 no longer relevant for mDNS. Jul 2 09:34:47 Cara avahi-daemon[4244]: Leaving mDNS multicast group on interface docker0.IPv4 with address 172.17.0.1. Jul 2 09:34:47 Cara avahi-daemon[4244]: Withdrawing address record for 172.17.0.1 on docker0.
  20. At 10:26 there are a few zfs entries, but it is now 13:30 and the start VM icon is still spinning away. About 12:00 would be the time that the VM was shut down. Other than for this, the server continues to work normally. ZFS list commands return expected results nothing seems broken, except the VM doesn't start. On shutting down the server, unRaid claims the server is down, but a putty window shows the server is still live, and will respond to ZFS list etc. What it will not do is ZPOOL export -a This comes back with. cannot unmount '/mnt/MFS/VM/Win10ZFS': umount failed cara-diagnostics-20200701-1327.zip
  21. I have been testing on 6.9.0 b22 and have a ZFS mirror created on 2 spinners. On this mirror, I have a Win10 VM created, and now twice unRaid has refused to start the VM after a VM shutdown. The VM start command in unRaid just sits with the VM stopped and the red spinning arrows going in a circle attempting to restart the VM. UnRaid is still reponsive as you can create another tab, and work with unRaid normally. The VM had been running successfully after a fresh unRaid boot, but shutting down a Win10 VM and restarting the VM causes this issue.
  22. Hey, thanks for the report. ZFS is very cool, but @steini84maybe we should update post1 with "Where not to use ZFS" It would appear that using ZFS to mount USB devices is not a good use case, (or should only be done in cases where you are aware that ZFS is not plug and play with USB). For normal disk maintenance, unRaid leads us to believe that we can safely do this with the array stopped. ZFS is a totally different animal. Would best practice be to put a "zpool export" command into Squid's awesome user scripts plugin and set it to happen on array stop, and "zpool import" on array start? On first startup of array, you should not need this as ZFS will automatically do the zpool import. It would seem that user scripts supports all this and could make ZFS behave like the unRaid array. Would this make sense?
  23. So the conclusion is that ZFS is extremely sensitive to disconnections and does not recover on reconnection. Have you ever seen data corruption as a result of these issues??
  24. ZFS lockup Array stop and restart I have a 6.8.3 production server that has ZFS installed recently. I took a single disk and set it up with ZFS for testing as follows. root@Tower:/# zpool create -m /mnt/ZFS1 ZFS1 sde The server behaved as expected and the ZFS1 pool was active. I then took the unRaid array offline and performed some disk maintenance. I didn't do anything to unmount ZFS1. By mistake, the ZFS disk was also pulled from the server and reinserted into the hotbay. Bringing the server back online resulted in ZFS being locked up. The ZFS and ZPOOL commands would execute, but a ZFS list command would result in a hung terminal window. ZFS import also locked the terminal window. The unRaid server was working fine, but to recover ZFS, the only thing I could do was reboot the server. The ZFS pool came back online after reboot. I expect that I needed to perform some ZFS commands on array stop and restart? What should I have done? Is there any way to recover a locked up ZFS without reboot?