October 14, 20205 yr Wanted to try unraid for Gaming VM. Build Array with 4 TB parity, 2 TB Array, 1TB SSD Cache. Installed VM and Windows. After fiddling with Windows VM and GPU Passthrough (didnt know my GPU Bios), i restarted my Server several times. Now it: - cant mount 2TB array anymore - libvirt failed (but thats a secondary/follow up problem, i think). To keep it simple, i wanted to start new, so tools > new config (as there are still no important data on all Disks). Assigned now only Array and Cache. Still unmountable. Formatting 2 TB... no error, but still unmountable. looked into Smart, telling me: 197 Current pending sector 0x0032 200 200 000 Old age Always Never 1 Smart short test and smart extended test fails, always with same error as above. I just dont get it, i just want to build simple array and start gaming on Windows VM.
October 14, 20205 yr Community Expert Please post the diagnostics after a format attempt: Tools -> Diagnostics
October 14, 20205 yr Author tower-diagnostics-20201014-1713.zip Diagnostics directly after formatting.
October 14, 20205 yr Community Expert That disk is failing: 197 Current_Pending_Sector -O--CK 200 200 000 - 1
October 14, 20205 yr Author As written in my first post. can i fix that? 2TB drive was in 2 other raids and never failed or had smart errors.
October 14, 20205 yr Community Expert Disks can fail at any time, you can write zeros to the entire disk, it might fix it, but possibly only temporarily, use for example pre-clear, then run a read test or and extended SMART test.
October 14, 20205 yr syslog is filled with errors, eg: Oct 14 07:19:08 Tower kernel: ata6.00: exception Emask 0x0 SAct 0x40000000 SErr 0x0 action 0x0 Oct 14 07:19:08 Tower kernel: ata6.00: irq_stat 0x40000008 Oct 14 07:19:08 Tower kernel: ata6.00: failed command: READ FPDMA QUEUED Oct 14 07:19:08 Tower kernel: ata6.00: cmd 60/08:f0:40:00:00/00:00:00:00:00/40 tag 30 ncq dma 4096 in Oct 14 07:19:08 Tower kernel: res 41/40:00:40:00:00/00:00:00:00:00/40 Emask 0x409 (media error) <F> Oct 14 07:19:08 Tower kernel: ata6.00: status: { DRDY ERR } Oct 14 07:19:08 Tower kernel: ata6.00: error: { UNC } Oct 14 07:19:08 Tower kernel: ata6.00: configured for UDMA/133 Oct 14 07:19:08 Tower kernel: sd 7:0:0:0: [sde] tag#30 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 Oct 14 07:19:08 Tower kernel: sd 7:0:0:0: [sde] tag#30 Sense Key : 0x3 [current] Oct 14 07:19:08 Tower kernel: sd 7:0:0:0: [sde] tag#30 ASC=0x11 ASCQ=0x4 Oct 14 07:19:08 Tower kernel: sd 7:0:0:0: [sde] tag#30 CDB: opcode=0x28 28 00 00 00 00 40 00 00 08 00 Oct 14 07:19:08 Tower kernel: print_req_error: I/O error, dev sde, sector 64 Oct 14 07:19:08 Tower kernel: Buffer I/O error on dev sde1, logical block 0, async page read Oct 14 07:19:08 Tower kernel: ata6: EH complete If this is a new build, check all your cabling, power, etc. Maybe move drive to a different controller or port.
October 14, 20205 yr Author detached the 2TB drive. Now it seems to work. libvirt online again, all shares now there again. VMs there and starting. i experiment a little longer and look for errors in diagnostics. Thanks.
Archived
This topic is now archived and is closed to further replies.