March 5, 20206 yr So my home server is crashing I dont really know why. I changed all the sata cables, run through memory test and cpu loading test. I can't really find the reason why the server is rebooting. Today, one of the disk is showing "Unmountable: No file system". Can you help me with this situation? Edited March 7, 20206 yr by Dalto1
March 5, 20206 yr Community Expert https://wiki.unraid.net/Check_Disk_Filesystems#Checking_and_fixing_drives_in_the_webGui
March 5, 20206 yr Author I've run the test with the -n flag (XFS file system). This is the log Quote Phase 1 - find and verify superblock... Phase 2 - using internal log - zero log... - scan filesystem freespace and inode maps... - found root inode chunk Phase 3 - for each AG... - scan (but don't clear) agi unlinked lists... - process known inodes and perform inode discovery... - agno = 0 - agno = 1 - agno = 2 data fork in ino 4296080096 claims free block 537010022 bad nblocks 6697 for inode 4296080098, would reset to 6696 bad nblocks 2064 for inode 4296080101, would reset to 2063 - agno = 3 - agno = 4 - agno = 5 - process newly discovered inodes... Phase 4 - check for duplicate blocks... - setting up duplicate extent list... - check for inodes claiming duplicate blocks... - agno = 0 - agno = 2 - agno = 3 - agno = 1 - agno = 4 - agno = 5 bad nblocks 6697 for inode 4296080098, would reset to 6696 bad nblocks 2064 for inode 4296080101, would reset to 2063 No modify flag set, skipping phase 5 Phase 6 - check inode connectivity... - traversing filesystem ... - traversal finished ... - moving disconnected inodes to lost+found ... Phase 7 - verify link counts... No modify flag set, skipping filesystem flush and exiting. What should I do now?
March 5, 20206 yr Community Expert 1 hour ago, Dalto1 said: What should I do now? Run again without -n
March 5, 20206 yr Author 4 minutes ago, trurl said: Run again without -n I've repaired the filesystem. Do you see anything that could cause the server to crash in the logs?
March 5, 20206 yr Community Expert 3 minutes ago, Dalto1 said: I've repaired the filesystem. Do you see anything that could cause the server to crash in the logs? You should post new diagnostics with the array started in normal mode. Have you done memtest? Setup Syslog Server so you can keep syslog after a crash and reboot:
March 5, 20206 yr Author Mar 4 19:27:58 Poseidon-1 kern err kernel ata4.00: status: { DRDY } Mar 4 19:27:58 Poseidon-1 kern err kernel ata4.00: failed command: WRITE FPDMA QUEUED Mar 4 19:27:58 Poseidon-1 kern err kernel ata4.00: cmd 61/40:90:10:5b:4d/05:00:12:00:00/40 tag 18 ncq dma 688128 out Mar 4 19:27:58 Poseidon-1 kern err kernel res 40/00:90:10:5b:4d/00:00:12:00:00/40 Emask 0x10 (ATA bus error) Mar 4 19:27:58 Poseidon-1 kern err kernel ata4.00: status: { DRDY } Mar 4 19:27:58 Poseidon-1 kern err kernel ata4.00: failed command: READ FPDMA QUEUED Mar 4 19:27:58 Poseidon-1 kern err kernel ata4.00: cmd 60/08:c8:b0:75:4d/00:00:12:00:00/40 tag 25 ncq dma 4096 in Mar 4 19:27:58 Poseidon-1 kern err kernel res 40/00:90:10:5b:4d/00:00:12:00:00/40 Emask 0x10 (ATA bus error) Mar 4 19:27:58 Poseidon-1 kern err kernel ata4.00: status: { DRDY } Mar 4 19:27:58 Poseidon-1 kern err kernel ata4.00: failed command: READ FPDMA QUEUED Mar 4 19:27:58 Poseidon-1 kern err kernel ata4.00: cmd 60/08:d0:a8:75:4d/00:00:12:00:00/40 tag 26 ncq dma 4096 in Mar 4 19:27:58 Poseidon-1 kern err kernel res 40/00:90:10:5b:4d/00:00:12:00:00/40 Emask 0x10 (ATA bus error) Mar 4 19:27:58 Poseidon-1 kern err kernel ata4.00: status: { DRDY } Mar 4 19:27:58 Poseidon-1 kern err kernel ata4.00: failed command: READ FPDMA QUEUED Mar 4 19:27:58 Poseidon-1 kern err kernel ata4.00: cmd 60/58:e0:50:75:4d/00:00:12:00:00/40 tag 28 ncq dma 45056 in Mar 4 19:27:58 Poseidon-1 kern err kernel res 40/00:90:10:5b:4d/00:00:12:00:00/40 Emask 0x10 (ATA bus error) Mar 4 19:27:58 Poseidon-1 kern err kernel ata4.00: status: { DRDY } Mar 4 19:27:58 Poseidon-1 kern err kernel ata4.00: failed command: READ FPDMA QUEUED Mar 4 19:27:58 Poseidon-1 kern err kernel ata4.00: cmd 60/40:e8:10:70:4d/05:00:12:00:00/40 tag 29 ncq dma 688128 in Mar 4 19:27:58 Poseidon-1 kern err kernel res 40/00:90:10:5b:4d/00:00:12:00:00/40 Emask 0x10 (ATA bus error) Mar 4 19:27:58 Poseidon-1 kern err kernel ata4.00: status: { DRDY } Mar 4 19:27:58 Poseidon-1 kern err kernel ata4.00: failed command: READ FPDMA QUEUED Mar 4 19:27:58 Poseidon-1 kern err kernel ata4.00: cmd 60/40:f0:d0:6a:4d/05:00:12:00:00/40 tag 30 ncq dma 688128 in Mar 4 19:27:58 Poseidon-1 kern err kernel res 40/00:90:10:5b:4d/00:00:12:00:00/40 Emask 0x10 (ATA bus error) Mar 4 19:27:58 Poseidon-1 kern err kernel ata4.00: status: { DRDY } Mar 4 19:27:58 Poseidon-1 kern info kernel ata4: hard resetting link Mar 4 19:28:04 Poseidon-1 kern warning kernel ata6: link is slow to respond, please be patient (ready=0) Mar 4 19:28:04 Poseidon-1 kern warning kernel ata4: link is slow to respond, please be patient (ready=0) Mar 4 19:28:04 Poseidon-1 kern warning kernel ata3: link is slow to respond, please be patient (ready=0) Mar 4 19:28:06 Poseidon-1 kern info kernel ata6: SATA link up 3.0 Gbps (SStatus 123 SControl 300) Mar 4 19:28:06 Poseidon-1 kern info kernel ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 310) Mar 4 19:28:06 Poseidon-1 kern info kernel ata6.00: configured for UDMA/133 Mar 4 19:28:06 Poseidon-1 kern info kernel ata4.00: configured for UDMA/133 Mar 4 19:28:06 Poseidon-1 kern info kernel ata4: EH complete Mar 4 19:28:06 Poseidon-1 kern info kernel ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300) Mar 4 19:28:07 Poseidon-1 kern info kernel ata3.00: configured for UDMA/133 Mar 4 19:28:23 Poseidon-1 kern info kernel vetha3d9a7d: renamed from eth0 Mar 4 19:28:23 Poseidon-1 kern info kernel docker0: port 11(veth984cfc3) entered disabled state Mar 4 19:28:31 Poseidon-1 kern info kernel docker0: port 11(veth984cfc3) entered disabled state Mar 4 19:28:31 Poseidon-1 kern info kernel device veth984cfc3 left promiscuous mode Mar 4 19:28:31 Poseidon-1 kern info kernel docker0: port 11(veth984cfc3) entered disabled state Mar 4 19:28:32 Poseidon-1 kern info kernel eth0: renamed from vethe30e8f1 Mar 4 19:28:32 Poseidon-1 kern info kernel IPv6: ADDRCONF(NETDEV_CHANGE): veth440641d: link becomes ready Mar 4 19:28:32 Poseidon-1 kern info kernel docker0: port 12(veth440641d) entered blocking state Mar 4 19:28:32 Poseidon-1 kern info kernel docker0: port 12(veth440641d) entered forwarding state Mar 4 19:29:46 Poseidon-1 local7 err nginx 2020/03/04 19:29:46 [error] 9428#9428: *21325 upstream timed out (110: Connection timed out) while reading response header from upstream, client: , server: , request: "POST /plugins/dynamix.docker.manager/include/ContainerManager.php HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock", host: "", referrer: "http:///Docker" Mar 4 19:30:09 Poseidon-1 kern info kernel docker0: port 11(veth1477815) entered blocking state Mar 4 19:30:09 Poseidon-1 kern info kernel docker0: port 11(veth1477815) entered disabled state Mar 4 19:30:09 Poseidon-1 kern info kernel device veth1477815 entered promiscuous mode Mar 4 19:30:09 Poseidon-1 kern info kernel IPv6: ADDRCONF(NETDEV_UP): veth1477815: link is not ready Mar 4 19:30:09 Poseidon-1 kern info kernel docker0: port 11(veth1477815) entered blocking state Mar 4 19:30:09 Poseidon-1 kern info kernel docker0: port 11(veth1477815) entered forwarding state Mar 4 19:30:09 Poseidon-1 kern info kernel docker0: port 11(veth1477815) entered disabled state Mar 4 19:30:55 Poseidon-1 kern err kernel ata4.00: exception Emask 0x10 SAct 0x0 SErr 0x4090000 action 0xe frozen Mar 4 19:30:55 Poseidon-1 kern err kernel ata4.00: irq_stat 0x00400040, connection status changed Mar 4 19:30:55 Poseidon-1 kern err kernel ata4: SError: { PHYRdyChg 10B8B DevExch } Mar 4 19:30:55 Poseidon-1 kern err kernel ata4.00: failed command: FLUSH CACHE EXT Mar 4 19:30:55 Poseidon-1 kern err kernel ata4.00: cmd ea/00:00:00:00:00/00:00:00:00:00/a0 tag 4 Mar 4 19:30:55 Poseidon-1 kern err kernel res 50/00:00:00:00:00/00:00:00:00:00/a0 Emask 0x10 (ATA bus error) Mar 4 19:30:55 Poseidon-1 kern err kernel ata4.00: status: { DRDY } Mar 4 19:30:55 Poseidon-1 kern info kernel ata4: hard resetting link Mar 4 19:31:01 Poseidon-1 kern warning kernel ata4: link is slow to respond, please be patient (ready=0) Mar 4 19:31:04 Poseidon-1 kern info kernel ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 310) Mar 4 19:31:04 Poseidon-1 kern info kernel ata4.00: configured for UDMA/133 Mar 4 19:31:04 Poseidon-1 kern warning kernel ata4.00: retrying FLUSH 0xea Emask 0x10 Mar 4 19:31:04 Poseidon-1 kern warning kernel ata4.00: device reported invalid CHS sector 0 Mar 4 19:31:04 Poseidon-1 kern info kernel ata4: EH complete
March 6, 20206 yr Author On 3/5/2020 at 2:40 AM, johnnie.black said: Check/replace cables for parity. I changed some cables and i got this now, when im starting all my dockers. Maybe it is a powersupply issue? It's happenning when im starting all the dockers. Quote 2.168.0.120 Mar 6 08:19:40 Poseidon-1 kern err kernel ata6.00: status: { DRDY } Mar 6 08:19:40 Poseidon-1 kern err kernel ata6.00: failed command: READ FPDMA QUEUED Mar 6 08:19:40 Poseidon-1 kern err kernel ata6.00: cmd 60/20:d8:d8:42:6a/00:00:83:02:00/40 tag 27 ncq dma 16384 in Mar 6 08:19:40 Poseidon-1 kern err kernel res 40/00:88:60:df:77/00:00:01:00:00/40 Emask 0x10 (ATA bus error) Mar 6 08:19:40 Poseidon-1 kern err kernel ata6.00: status: { DRDY } Mar 6 08:19:40 Poseidon-1 kern err kernel ata6.00: failed command: READ FPDMA QUEUED Mar 6 08:19:40 Poseidon-1 kern err kernel ata6.00: cmd 60/20:e0:80:ab:19/00:00:02:02:00/40 tag 28 ncq dma 16384 in Mar 6 08:19:40 Poseidon-1 kern err kernel res 40/00:88:60:df:77/00:00:01:00:00/40 Emask 0x10 (ATA bus error) Mar 6 08:19:40 Poseidon-1 kern err kernel ata6.00: status: { DRDY } Mar 6 08:19:40 Poseidon-1 kern err kernel ata6.00: failed command: READ FPDMA QUEUED Mar 6 08:19:40 Poseidon-1 kern err kernel ata6.00: cmd 60/20:e8:a0:d5:77/00:00:01:00:00/40 tag 29 ncq dma 16384 in Mar 6 08:19:40 Poseidon-1 kern err kernel res 40/00:88:60:df:77/00:00:01:00:00/40 Emask 0x10 (ATA bus error) Mar 6 08:19:40 Poseidon-1 kern err kernel ata6.00: status: { DRDY } Mar 6 08:19:40 Poseidon-1 kern err kernel ata6.00: failed command: READ FPDMA QUEUED Mar 6 08:19:40 Poseidon-1 kern err kernel ata6.00: cmd 60/20:f0:e0:b3:19/00:00:02:02:00/40 tag 30 ncq dma 16384 in Mar 6 08:19:40 Poseidon-1 kern err kernel res 40/00:88:60:df:77/00:00:01:00:00/40 Emask 0x10 (ATA bus error) Mar 6 08:19:40 Poseidon-1 kern err kernel ata6.00: status: { DRDY } Mar 6 08:19:40 Poseidon-1 kern err kernel ata6.00: failed command: READ FPDMA QUEUED Mar 6 08:19:40 Poseidon-1 kern err kernel ata6.00: cmd 60/20:f8:a0:8a:19/00:00:02:02:00/40 tag 31 ncq dma 16384 in Mar 6 08:19:40 Poseidon-1 kern err kernel res 40/00:88:60:df:77/00:00:01:00:00/40 Emask 0x10 (ATA bus error) Mar 6 08:19:40 Poseidon-1 kern err kernel ata6.00: status: { DRDY } Mar 6 08:19:40 Poseidon-1 kern info kernel ata6: hard resetting link Mar 6 08:19:40 Poseidon-1 kern err kernel ata5.00: exception Emask 0x50 SAct 0xffffffff SErr 0x4090800 action 0xe frozen Mar 6 08:19:40 Poseidon-1 kern err kernel ata5.00: irq_stat 0x00400040, connection status changed Mar 6 08:19:40 Poseidon-1 kern err kernel ata5: SError: { HostInt PHYRdyChg 10B8B DevExch } Mar 6 08:19:40 Poseidon-1 kern err kernel ata5.00: failed command: READ FPDMA QUEUED Mar 6 08:19:40 Poseidon-1 kern err kernel ata5.00: cmd 60/40:00:28:a6:ec/00:00:85:01:00/40 tag 0 ncq dma 32768 in Mar 6 08:19:40 Poseidon-1 kern err kernel res 40/00:68:60:df:77/00:00:01:00:00/40 Emask 0x50 (ATA bus error) Mar 6 08:19:40 Poseidon-1 kern err kernel ata5.00: status: { DRDY } Mar 6 08:19:40 Poseidon-1 kern err kernel ata5.00: failed command: READ FPDMA QUEUED Mar 6 08:19:40 Poseidon-1 kern err kernel ata5.00: cmd 60/20:08:e0:a3:5d/00:00:00:02:00/40 tag 1 ncq dma 16384 in Mar 6 08:19:40 Poseidon-1 kern err kernel res 40/00:68:60:df:77/00:00:01:00:00/40 Emask 0x50 (ATA bus error) Mar 6 08:19:40 Poseidon-1 kern err kernel ata5.00: status: { DRDY } Mar 6 08:19:40 Poseidon-1 kern err kernel ata5.00: failed command: READ FPDMA QUEUED Mar 6 08:19:40 Poseidon-1 kern err kernel ata5.00: cmd 60/20:10:40:74:12/00:00:02:02:00/40 tag 2 ncq dma 16384 in Mar 6 08:19:40 Poseidon-1 kern err kernel res 40/00:68:60:df:77/00:00:01:00:00/40 Emask 0x50 (ATA bus error)
March 6, 20206 yr Author 12 minutes ago, Dalto1 said: I changed some cables and i got this now, when im starting all my dockers. Maybe it is a powersupply issue? It's happenning when im starting all the dockers. I think it's bad fans connectors that was messing up with my system.
March 6, 20206 yr Community Expert 26 minutes ago, Dalto1 said: Maybe it is a powersupply issue? Possibly, try a different one if available.
Archived
This topic is now archived and is closed to further replies.