caseyparsons

Oh, I didn't realize I was looking at the tags for the wrong version. But got it now. Thanks! Unfortunately, my son likes to play on his amazon fire tablet sometimes and wants to be able to use his PC other times, but I guess I'm gathering that the two clients can't coexist on a server.

Oh. So on his tablet he can connect to this server, but to play from his PC he has to connect to a different server? Well that stinks. But thank you for the reply!

Oops, you're right. Thanks for pointing me to the right thread. I re-posted over there.

Sorry for the noob question. Current server version is 1.19.10-beta20. My son's PC client version is 1.19.0. When he tries to log in, he gets the error "Could not connect: outdated client!". How do I specify a server version that matches his client version? How do you keep these in sync? I saw this tags page so I tried to input 1.19-01 as part of the repo. So I entered "binhex/arch-minecraftbedrockserver:1.19-01" as the repository, but then the docker fails. I get this error in the Update Container page: "docker: Error response from daemon: manifest for binhex/arch-minecraftbedrockserver:1.19-01 not found: manifest unknown: manifest unknown." Is my syntax wrong? Is this not the right way to specify a specific version? I searched (a bunch) for the answers but just couldn't find what I needed. Thanks! Or should I not be using Bedrock version?

Sorry for the noob question. Current server version is 1.19.10-beta20. My son's PC client version is 1.19.0. When he tries to log in, he gets the error "Could not connect: outdated client!". How do I specify a server version that matches his client version? How do you keep these in sync? I saw this tags page so I tried to input 1.19-01 as part of the repo. So I entered "binhex/arch-minecraftbedrockserver:1.19-01" as the repository, but then the docker fails. I get this error in the Update Container page: "docker: Error response from daemon: manifest for binhex/arch-minecraftbedrockserver:1.19-01 not found: manifest unknown: manifest unknown." Is my syntax wrong? Is this not the right way to specify a specific version? I searched (a bunch) for the answers but just couldn't find what I needed. Thanks!

Well look at that. I needed to REBOOT. After the reboot the server started responding to network on the port that I was not originally connected to. Yep, I had some stuff passed through for plex. Already working on cleaning all that up, but I can handle. Thank you for the help! Really appreciate it.

OK good call on this. The motherboard actually has two integrated NICs. One is a 1Gb and one is 2.5Gb. I was only cabled to the 1Gb, but am now cabled to both - but no improvement yet. Thanks for the idea.

Hi friends, I've been very happy with my unraid server for many years. Today I upgraded my motherboard to the MSI B560 Torpedo, CPU to i5-11400, and new RAM. These replaced a Ryzen 5 1500af and GTX 960 GPU. After fiddling with the UEFI boot settings in the BIOS I can finally get unRaid to boot but not get to a good running state. I get all the way through the scrolling loading stuff and to the login prompt. The server states that the IPv4 address is 192.168.10.10, which is what I had previously configured in the GUI. However, the server is not available on the network. I can't ping to it, and I can't ping out of it from the console. It will ping itself, but nothing outside the NIC. I tried to boot into GUI (and safe mode with GUI) but the GUI never loads, I just get a flashing cursor. I do see some modprobe errors, which I assume temp sensor errors because I switched CPU and no longer using nvidia, but all those plugins are still installed. I figured I would clean that up after, but hopefully not causing the error. What can I try now? Attached is a diagnostics file that I initiated from console then pulled off the USB. For some reason the date says yesterday but I definitely ran it today. Thank you! tower-diagnostics-20211220-2324.zip

Hmm I tried this but didn't work for me. Just got new errors. This seems to be the important part: {"t":{"$date":"2021-02-18T12:35:47.675-05:00"},"s":"W", "c":"STORAGE", "id":22347, "ctx":"initandlisten","msg":"Failed to start up WiredTiger under any compatibility version. This may be due to an unsupported upgrade or downgrade."}

Having the same problem after update.

Is this docker container still being maintained? I enjoy using it, but can't be running an unmaintained container without security patches.

I'm quoting this old comment because that's how I found this thread from a Google search. I'm just posting to help searchers in the future. After installing the unraid-nvidia plug-in, visiting the settings page, and then clicking the Unraid Nividia link, I would get stuck at "Updating available builds". To resolve this, I did nothing else but changed my MTU to 1500. I had previously changed it to 9214 to accomplish something different. Changing it to 1500 let the process to update the page complete after about a minute. Hope that helps someone!

Hi all, I need some help with this issue. I bought a brand new Kingston A400 240GB SSD to use as my cache drive, replacing an old spinner. After the install and bootup, the Fix Common Problems plug-in is throwing the error "Unable to write to cache. Drive mounted read-only or completely full." I'm running Unraid 6.6.6. Here is the disk log: Feb 19 21:49:06 Tower kernel: ata8: SATA max UDMA/133 abar m512@0xfeaffc00 port 0xfeaffd80 irq 37 Feb 19 21:49:06 Tower kernel: ata8: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Feb 19 21:49:06 Tower kernel: ata8.00: ATA-10: KINGSTON SA400S37240G, 50026B76827F3C5D, SBFKB1D2, max UDMA/133 Feb 19 21:49:06 Tower kernel: ata8.00: 468862128 sectors, multi 1: LBA48 NCQ (depth 32), AA Feb 19 21:49:06 Tower kernel: ata8.00: configured for UDMA/133 Feb 19 21:49:06 Tower kernel: sd 8:0:0:0: [sdi] 468862128 512-byte logical blocks: (240 GB/224 GiB) Feb 19 21:49:06 Tower kernel: sd 8:0:0:0: [sdi] Write Protect is off Feb 19 21:49:06 Tower kernel: sd 8:0:0:0: [sdi] Mode Sense: 00 3a 00 00 Feb 19 21:49:06 Tower kernel: sd 8:0:0:0: [sdi] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Feb 19 21:49:06 Tower kernel: sdi: sdi1 Feb 19 21:49:06 Tower kernel: sd 8:0:0:0: [sdi] Attached SCSI disk Feb 19 21:49:24 Tower emhttpd: KINGSTON_SA400S37240G_50026B76827F3C5D (sdi) 512 468862128 Feb 19 21:49:24 Tower emhttpd: import 30 cache device: (sdi) KINGSTON_SA400S37240G_50026B76827F3C5D Feb 19 21:49:59 Tower emhttpd: shcmd (102): mount -t xfs -o noatime,nodiratime /dev/sdi1 /mnt/cache Feb 19 21:49:59 Tower kernel: XFS (sdi1): Mounting V5 Filesystem Feb 19 21:49:59 Tower kernel: XFS (sdi1): Ending clean mount Feb 19 21:52:48 Tower kernel: ata8.00: exception Emask 0x11 SAct 0xffffffff SErr 0x400000 action 0x6 frozen Feb 19 21:52:48 Tower kernel: ata8.00: irq_stat 0x48000008, interface fatal error Feb 19 21:52:48 Tower kernel: ata8: SError: { Handshk } Feb 19 21:52:48 Tower kernel: ata8.00: failed command: WRITE FPDMA QUEUED Feb 19 21:52:48 Tower kernel: ata8.00: cmd 61/00:00:20:82:ca/0a:00:08:00:00/40 tag 0 ncq dma 1310720 ou Feb 19 21:52:48 Tower kernel: ata8.00: status: { DRDY } Feb 19 21:52:48 Tower kernel: ata8.00: failed command: WRITE FPDMA QUEUED Feb 19 21:52:48 Tower kernel: ata8.00: cmd 61/00:08:20:8c:ca/06:00:08:00:00/40 tag 1 ncq dma 786432 out Feb 19 21:52:48 Tower kernel: ata8.00: status: { DRDY } Feb 19 21:52:48 Tower kernel: ata8.00: failed command: WRITE FPDMA QUEUED Feb 19 21:52:48 Tower kernel: ata8.00: cmd 61/00:10:20:92:ca/0a:00:08:00:00/40 tag 2 ncq dma 1310720 ou Feb 19 21:52:48 Tower kernel: ata8.00: status: { DRDY } Feb 19 21:52:48 Tower kernel: ata8.00: failed command: WRITE FPDMA QUEUED Feb 19 21:52:48 Tower kernel: ata8.00: cmd 61/00:18:20:9c:ca/06:00:08:00:00/40 tag 3 ncq dma 786432 out Feb 19 21:52:48 Tower kernel: ata8.00: status: { DRDY } Feb 19 21:52:48 Tower kernel: ata8.00: failed command: WRITE FPDMA QUEUED Feb 19 21:52:48 Tower kernel: ata8.00: cmd 61/00:20:20:a2:ca/0a:00:08:00:00/40 tag 4 ncq dma 1310720 ou Feb 19 21:52:48 Tower kernel: ata8.00: status: { DRDY } Feb 19 21:52:48 Tower kernel: ata8.00: failed command: WRITE FPDMA QUEUED Feb 19 21:52:48 Tower kernel: ata8.00: cmd 61/00:28:20:ac:ca/06:00:08:00:00/40 tag 5 ncq dma 786432 out Feb 19 21:52:48 Tower kernel: ata8.00: status: { DRDY } Feb 19 21:52:48 Tower kernel: ata8.00: failed command: WRITE FPDMA QUEUED Feb 19 21:52:48 Tower kernel: ata8.00: cmd 61/00:30:20:b2:ca/0a:00:08:00:00/40 tag 6 ncq dma 1310720 ou Feb 19 21:52:48 Tower kernel: ata8.00: status: { DRDY } Feb 19 21:52:48 Tower kernel: ata8.00: failed command: WRITE FPDMA QUEUED Feb 19 21:52:48 Tower kernel: ata8.00: cmd 61/00:38:20:bc:ca/06:00:08:00:00/40 tag 7 ncq dma 786432 out Feb 19 21:52:48 Tower kernel: ata8.00: status: { DRDY } Feb 19 21:52:48 Tower kernel: ata8.00: failed command: WRITE FPDMA QUEUED Feb 19 21:52:48 Tower kernel: ata8.00: cmd 61/00:40:20:c2:ca/0a:00:08:00:00/40 tag 8 ncq dma 1310720 ou Feb 19 21:52:48 Tower kernel: ata8.00: status: { DRDY } Feb 19 21:52:48 Tower kernel: ata8.00: failed command: WRITE FPDMA QUEUED Feb 19 21:52:48 Tower kernel: ata8.00: cmd 61/00:48:20:cc:ca/06:00:08:00:00/40 tag 9 ncq dma 786432 out Feb 19 21:52:48 Tower kernel: ata8.00: status: { DRDY } Feb 19 21:52:48 Tower kernel: ata8.00: failed command: WRITE FPDMA QUEUED Feb 19 21:52:48 Tower kernel: ata8.00: cmd 61/00:50:20:d2:ca/0a:00:08:00:00/40 tag 10 ncq dma 1310720 ou Feb 19 21:52:48 Tower kernel: ata8.00: status: { DRDY } Feb 19 21:52:48 Tower kernel: ata8.00: failed command: WRITE FPDMA QUEUED Feb 19 21:52:48 Tower kernel: ata8.00: cmd 61/00:58:20:dc:ca/06:00:08:00:00/40 tag 11 ncq dma 786432 out Feb 19 21:52:48 Tower kernel: ata8.00: status: { DRDY } Feb 19 21:52:48 Tower kernel: ata8.00: failed command: WRITE FPDMA QUEUED Feb 19 21:52:48 Tower kernel: ata8.00: cmd 61/00:60:20:e2:ca/0a:00:08:00:00/40 tag 12 ncq dma 1310720 ou Feb 19 21:52:48 Tower kernel: ata8.00: status: { DRDY } Feb 19 21:52:48 Tower kernel: ata8.00: failed command: WRITE FPDMA QUEUED Feb 19 21:52:48 Tower kernel: ata8.00: cmd 61/00:68:20:f2:c9/0a:00:08:00:00/40 tag 13 ncq dma 1310720 ou Feb 19 21:52:48 Tower kernel: ata8.00: status: { DRDY } Feb 19 21:52:48 Tower kernel: ata8.00: failed command: WRITE FPDMA QUEUED Feb 19 21:52:48 Tower kernel: ata8.00: cmd 61/00:70:20:fc:c9/06:00:08:00:00/40 tag 14 ncq dma 786432 out Feb 19 21:52:48 Tower kernel: ata8.00: status: { DRDY } Feb 19 21:52:48 Tower kernel: ata8.00: failed command: WRITE FPDMA QUEUED Feb 19 21:52:48 Tower kernel: ata8.00: cmd 61/00:78:20:02:ca/0a:00:08:00:00/40 tag 15 ncq dma 1310720 ou Feb 19 21:52:48 Tower kernel: ata8.00: status: { DRDY } Feb 19 21:52:48 Tower kernel: ata8.00: failed command: WRITE FPDMA QUEUED Feb 19 21:52:48 Tower kernel: ata8.00: cmd 61/00:80:20:0c:ca/06:00:08:00:00/40 tag 16 ncq dma 786432 out Feb 19 21:52:48 Tower kernel: ata8.00: status: { DRDY } Feb 19 21:52:48 Tower kernel: ata8.00: failed command: WRITE FPDMA QUEUED Feb 19 21:52:48 Tower kernel: ata8.00: cmd 61/00:88:20:12:ca/0a:00:08:00:00/40 tag 17 ncq dma 1310720 ou Feb 19 21:52:48 Tower kernel: ata8.00: status: { DRDY } Feb 19 21:52:48 Tower kernel: ata8.00: failed command: WRITE FPDMA QUEUED Feb 19 21:52:48 Tower kernel: ata8.00: cmd 61/00:90:20:1c:ca/06:00:08:00:00/40 tag 18 ncq dma 786432 out Feb 19 21:52:48 Tower kernel: ata8.00: status: { DRDY } Feb 19 21:52:48 Tower kernel: ata8.00: failed command: WRITE FPDMA QUEUED Feb 19 21:52:48 Tower kernel: ata8.00: cmd 61/00:98:20:22:ca/0a:00:08:00:00/40 tag 19 ncq dma 1310720 ou Feb 19 21:52:48 Tower kernel: ata8.00: status: { DRDY } Feb 19 21:52:48 Tower kernel: ata8.00: failed command: READ FPDMA QUEUED Feb 19 21:52:48 Tower kernel: ata8.00: cmd 60/08:a0:90:22:f9/00:00:0d:00:00/40 tag 20 ncq dma 4096 in Feb 19 21:52:48 Tower kernel: ata8.00: status: { DRDY } Feb 19 21:52:48 Tower kernel: ata8.00: failed command: WRITE FPDMA QUEUED Feb 19 21:52:48 Tower kernel: ata8.00: cmd 61/00:a8:20:2c:ca/06:00:08:00:00/40 tag 21 ncq dma 786432 out Feb 19 21:52:48 Tower kernel: ata8.00: status: { DRDY } Feb 19 21:52:48 Tower kernel: ata8.00: failed command: WRITE FPDMA QUEUED Feb 19 21:52:48 Tower kernel: ata8.00: cmd 61/00:b0:20:32:ca/0a:00:08:00:00/40 tag 22 ncq dma 1310720 ou Feb 19 21:52:48 Tower kernel: ata8.00: status: { DRDY } Feb 19 21:52:48 Tower kernel: ata8.00: failed command: WRITE FPDMA QUEUED Feb 19 21:52:48 Tower kernel: ata8.00: cmd 61/00:b8:20:3c:ca/06:00:08:00:00/40 tag 23 ncq dma 786432 out Feb 19 21:52:48 Tower kernel: ata8.00: status: { DRDY } Feb 19 21:52:48 Tower kernel: ata8.00: failed command: WRITE FPDMA QUEUED Feb 19 21:52:48 Tower kernel: ata8.00: cmd 61/00:c0:20:42:ca/0a:00:08:00:00/40 tag 24 ncq dma 1310720 ou Feb 19 21:52:48 Tower kernel: ata8.00: status: { DRDY } Feb 19 21:52:48 Tower kernel: ata8.00: failed command: WRITE FPDMA QUEUED Feb 19 21:52:48 Tower kernel: ata8.00: cmd 61/00:c8:20:4c:ca/06:00:08:00:00/40 tag 25 ncq dma 786432 out Feb 19 21:52:48 Tower kernel: ata8.00: status: { DRDY } Feb 19 21:52:48 Tower kernel: ata8.00: failed command: WRITE FPDMA QUEUED Feb 19 21:52:48 Tower kernel: ata8.00: cmd 61/00:d0:20:52:ca/0a:00:08:00:00/40 tag 26 ncq dma 1310720 ou Feb 19 21:52:48 Tower kernel: ata8.00: status: { DRDY } Feb 19 21:52:48 Tower kernel: ata8.00: failed command: WRITE FPDMA QUEUED Feb 19 21:52:48 Tower kernel: ata8.00: cmd 61/00:d8:20:5c:ca/06:00:08:00:00/40 tag 27 ncq dma 786432 out Feb 19 21:52:48 Tower kernel: ata8.00: status: { DRDY } Feb 19 21:52:48 Tower kernel: ata8.00: failed command: WRITE FPDMA QUEUED Feb 19 21:52:48 Tower kernel: ata8.00: cmd 61/00:e0:20:62:ca/0a:00:08:00:00/40 tag 28 ncq dma 1310720 ou Feb 19 21:52:48 Tower kernel: ata8.00: status: { DRDY } Feb 19 21:52:48 Tower kernel: ata8.00: failed command: WRITE FPDMA QUEUED Feb 19 21:52:48 Tower kernel: ata8.00: cmd 61/00:e8:20:6c:ca/06:00:08:00:00/40 tag 29 ncq dma 786432 out Feb 19 21:52:48 Tower kernel: ata8.00: status: { DRDY } Feb 19 21:52:48 Tower kernel: ata8.00: failed command: WRITE FPDMA QUEUED Feb 19 21:52:48 Tower kernel: ata8.00: cmd 61/00:f0:20:72:ca/0a:00:08:00:00/40 tag 30 ncq dma 1310720 ou Feb 19 21:52:48 Tower kernel: ata8.00: status: { DRDY } Feb 19 21:52:48 Tower kernel: ata8.00: failed command: WRITE FPDMA QUEUED Feb 19 21:52:48 Tower kernel: ata8.00: cmd 61/00:f8:20:7c:ca/06:00:08:00:00/40 tag 31 ncq dma 786432 out Feb 19 21:52:48 Tower kernel: ata8.00: status: { DRDY } Feb 19 21:52:48 Tower kernel: ata8: hard resetting link Feb 19 21:52:48 Tower kernel: ata8: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Feb 19 21:52:48 Tower kernel: ata8.00: configured for UDMA/133 Feb 19 21:52:48 Tower kernel: ata8: EH complete Feb 19 21:56:50 Tower kernel: ata8.00: exception Emask 0x10 SAct 0xffffbfff SErr 0x400000 action 0x6 frozen Feb 19 21:56:50 Tower kernel: ata8.00: irq_stat 0x08000000, interface fatal error Feb 19 21:56:50 Tower kernel: ata8: SError: { Handshk } Feb 19 21:56:50 Tower kernel: ata8.00: failed command: WRITE FPDMA QUEUED Feb 19 21:56:50 Tower kernel: ata8.00: cmd 61/00:00:90:eb:0b/06:00:00:00:00/40 tag 0 ncq dma 786432 out Feb 19 21:56:50 Tower kernel: ata8.00: status: { DRDY } Feb 19 21:56:50 Tower kernel: ata8.00: failed command: WRITE FPDMA QUEUED Feb 19 21:56:50 Tower kernel: ata8.00: cmd 61/00:08:90:f1:0b/0a:00:00:00:00/40 tag 1 ncq dma 1310720 ou Feb 19 21:56:50 Tower kernel: ata8.00: status: { DRDY } Feb 19 21:56:50 Tower kernel: ata8.00: failed command: WRITE FPDMA QUEUED Feb 19 21:56:50 Tower kernel: ata8.00: cmd 61/00:10:90:fb:0b/06:00:00:00:00/40 tag 2 ncq dma 786432 out Feb 19 21:56:50 Tower kernel: ata8.00: status: { DRDY } Feb 19 21:56:50 Tower kernel: ata8.00: failed command: WRITE FPDMA QUEUED Feb 19 21:56:50 Tower kernel: ata8.00: cmd 61/00:18:90:01:0c/0a:00:00:00:00/40 tag 3 ncq dma 1310720 ou Feb 19 21:56:50 Tower kernel: ata8.00: status: { DRDY } Feb 19 21:56:50 Tower kernel: ata8.00: failed command: WRITE FPDMA QUEUED Feb 19 21:56:50 Tower kernel: ata8.00: cmd 61/00:20:90:0b:0c/06:00:00:00:00/40 tag 4 ncq dma 786432 out Feb 19 21:56:50 Tower kernel: ata8.00: status: { DRDY } Feb 19 21:56:50 Tower kernel: ata8.00: failed command: WRITE FPDMA QUEUED Feb 19 21:56:50 Tower kernel: ata8.00: cmd 61/00:28:90:11:0c/0a:00:00:00:00/40 tag 5 ncq dma 1310720 ou Feb 19 21:56:50 Tower kernel: ata8.00: status: { DRDY } Feb 19 21:56:50 Tower kernel: ata8.00: failed command: WRITE FPDMA QUEUED Feb 19 21:56:50 Tower kernel: ata8.00: cmd 61/00:30:90:1b:0c/06:00:00:00:00/40 tag 6 ncq dma 786432 out Feb 19 21:56:50 Tower kernel: ata8.00: status: { DRDY } Feb 19 21:56:50 Tower kernel: ata8.00: failed command: WRITE FPDMA QUEUED Feb 19 21:56:50 Tower kernel: ata8.00: cmd 61/00:38:90:21:0c/0a:00:00:00:00/40 tag 7 ncq dma 1310720 ou Feb 19 21:56:50 Tower kernel: ata8.00: status: { DRDY } Feb 19 21:56:50 Tower kernel: ata8.00: failed command: WRITE FPDMA QUEUED Feb 19 21:56:50 Tower kernel: ata8.00: cmd 61/00:40:90:2b:0c/06:00:00:00:00/40 tag 8 ncq dma 786432 out Feb 19 21:56:50 Tower kernel: ata8.00: status: { DRDY } Feb 19 21:56:50 Tower kernel: ata8.00: failed command: WRITE FPDMA QUEUED Feb 19 21:56:50 Tower kernel: ata8.00: cmd 61/00:48:90:31:0c/0a:00:00:00:00/40 tag 9 ncq dma 1310720 ou Feb 19 21:56:50 Tower kernel: ata8.00: status: { DRDY } Feb 19 21:56:50 Tower kernel: ata8.00: failed command: WRITE FPDMA QUEUED Feb 19 21:56:50 Tower kernel: ata8.00: cmd 61/00:50:90:3b:0c/06:00:00:00:00/40 tag 10 ncq dma 786432 out Feb 19 21:56:50 Tower kernel: ata8.00: status: { DRDY } Feb 19 21:56:50 Tower kernel: ata8.00: failed command: WRITE FPDMA QUEUED Feb 19 21:56:50 Tower kernel: ata8.00: cmd 61/00:58:90:41:0c/0a:00:00:00:00/40 tag 11 ncq dma 1310720 ou Feb 19 21:56:50 Tower kernel: ata8.00: status: { DRDY } Feb 19 21:56:50 Tower kernel: ata8.00: failed command: WRITE FPDMA QUEUED Feb 19 21:56:50 Tower kernel: ata8.00: cmd 61/58:60:90:4b:0c/09:00:00:00:00/40 tag 12 ncq dma 1224704 ou Feb 19 21:56:50 Tower kernel: ata8.00: status: { DRDY } Feb 19 21:56:50 Tower kernel: ata8.00: failed command: WRITE FPDMA QUEUED Feb 19 21:56:50 Tower kernel: ata8.00: cmd 61/f0:68:e8:54:0c/04:00:00:00:00/40 tag 13 ncq dma 647168 out Feb 19 21:56:50 Tower kernel: ata8.00: status: { DRDY } Feb 19 21:56:50 Tower kernel: ata8.00: failed command: WRITE FPDMA QUEUED Feb 19 21:56:50 Tower kernel: ata8.00: cmd 61/00:78:90:61:0b/0a:00:00:00:00/40 tag 15 ncq dma 1310720 ou Feb 19 21:56:50 Tower kernel: ata8.00: status: { DRDY } Feb 19 21:56:50 Tower kernel: ata8.00: failed command: WRITE FPDMA QUEUED Feb 19 21:56:50 Tower kernel: ata8.00: cmd 61/00:80:90:6b:0b/06:00:00:00:00/40 tag 16 ncq dma 786432 out Feb 19 21:56:50 Tower kernel: ata8.00: status: { DRDY } Feb 19 21:56:50 Tower kernel: ata8.00: failed command: WRITE FPDMA QUEUED Feb 19 21:56:50 Tower kernel: ata8.00: cmd 61/00:88:90:71:0b/0a:00:00:00:00/40 tag 17 ncq dma 1310720 ou Feb 19 21:56:50 Tower kernel: ata8.00: status: { DRDY } Feb 19 21:56:50 Tower kernel: ata8.00: failed command: WRITE FPDMA QUEUED Feb 19 21:56:50 Tower kernel: ata8.00: cmd 61/00:90:90:7b:0b/06:00:00:00:00/40 tag 18 ncq dma 786432 out Feb 19 21:56:50 Tower kernel: ata8.00: status: { DRDY } Feb 19 21:56:50 Tower kernel: ata8.00: failed command: WRITE FPDMA QUEUED Feb 19 21:56:50 Tower kernel: ata8.00: cmd 61/00:98:90:81:0b/0a:00:00:00:00/40 tag 19 ncq dma 1310720 ou Feb 19 21:56:50 Tower kernel: ata8.00: status: { DRDY } Feb 19 21:56:50 Tower kernel: ata8.00: failed command: WRITE FPDMA QUEUED Feb 19 21:56:50 Tower kernel: ata8.00: cmd 61/00:a0:90:8b:0b/06:00:00:00:00/40 tag 20 ncq dma 786432 out Feb 19 21:56:50 Tower kernel: ata8.00: status: { DRDY } Feb 19 21:56:50 Tower kernel: ata8.00: failed command: WRITE FPDMA QUEUED Feb 19 21:56:50 Tower kernel: ata8.00: cmd 61/00:a8:90:91:0b/0a:00:00:00:00/40 tag 21 ncq dma 1310720 ou Feb 19 21:56:50 Tower kernel: ata8.00: status: { DRDY } Feb 19 21:56:50 Tower kernel: ata8.00: failed command: WRITE FPDMA QUEUED Feb 19 21:56:50 Tower kernel: ata8.00: cmd 61/00:b0:90:9b:0b/06:00:00:00:00/40 tag 22 ncq dma 786432 out Feb 19 21:56:50 Tower kernel: ata8.00: status: { DRDY } Feb 19 21:56:50 Tower kernel: ata8.00: failed command: WRITE FPDMA QUEUED Feb 19 21:56:50 Tower kernel: ata8.00: cmd 61/00:b8:90:a1:0b/0a:00:00:00:00/40 tag 23 ncq dma 1310720 ou Feb 19 21:56:50 Tower kernel: ata8.00: status: { DRDY } Feb 19 21:56:50 Tower kernel: ata8.00: failed command: WRITE FPDMA QUEUED Feb 19 21:56:50 Tower kernel: ata8.00: cmd 61/00:c0:90:ab:0b/06:00:00:00:00/40 tag 24 ncq dma 786432 out Feb 19 21:56:50 Tower kernel: ata8.00: status: { DRDY } Feb 19 21:56:50 Tower kernel: ata8.00: failed command: WRITE FPDMA QUEUED Feb 19 21:56:50 Tower kernel: ata8.00: cmd 61/00:c8:90:b1:0b/0a:00:00:00:00/40 tag 25 ncq dma 1310720 ou Feb 19 21:56:50 Tower kernel: ata8.00: status: { DRDY } Feb 19 21:56:50 Tower kernel: ata8.00: failed command: WRITE FPDMA QUEUED Feb 19 21:56:50 Tower kernel: ata8.00: cmd 61/00:d0:90:bb:0b/06:00:00:00:00/40 tag 26 ncq dma 786432 out Feb 19 21:56:50 Tower kernel: ata8.00: status: { DRDY } Feb 19 21:56:50 Tower kernel: ata8.00: failed command: WRITE FPDMA QUEUED Feb 19 21:56:50 Tower kernel: ata8.00: cmd 61/00:d8:90:c1:0b/0a:00:00:00:00/40 tag 27 ncq dma 1310720 ou Feb 19 21:56:50 Tower kernel: ata8.00: status: { DRDY } Feb 19 21:56:50 Tower kernel: ata8.00: failed command: WRITE FPDMA QUEUED Feb 19 21:56:50 Tower kernel: ata8.00: cmd 61/00:e0:90:cb:0b/06:00:00:00:00/40 tag 28 ncq dma 786432 out Feb 19 21:56:50 Tower kernel: ata8.00: status: { DRDY } Feb 19 21:56:50 Tower kernel: ata8.00: failed command: WRITE FPDMA QUEUED Feb 19 21:56:50 Tower kernel: ata8.00: cmd 61/00:e8:90:d1:0b/0a:00:00:00:00/40 tag 29 ncq dma 1310720 ou Feb 19 21:56:50 Tower kernel: ata8.00: status: { DRDY } Feb 19 21:56:50 Tower kernel: ata8.00: failed command: WRITE FPDMA QUEUED Feb 19 21:56:50 Tower kernel: ata8.00: cmd 61/00:f0:90:db:0b/06:00:00:00:00/40 tag 30 ncq dma 786432 out Feb 19 21:56:50 Tower kernel: ata8.00: status: { DRDY } Feb 19 21:56:50 Tower kernel: ata8.00: failed command: WRITE FPDMA QUEUED Feb 19 21:56:50 Tower kernel: ata8.00: cmd 61/00:f8:90:e1:0b/0a:00:00:00:00/40 tag 31 ncq dma 1310720 ou Feb 19 21:56:50 Tower kernel: ata8.00: status: { DRDY } Feb 19 21:56:50 Tower kernel: ata8: hard resetting link Feb 19 21:57:00 Tower kernel: ata8: softreset failed (1st FIS failed) Feb 19 21:57:00 Tower kernel: ata8: hard resetting link Feb 19 21:57:10 Tower kernel: ata8: softreset failed (1st FIS failed) Feb 19 21:57:10 Tower kernel: ata8: hard resetting link Feb 19 21:57:45 Tower kernel: ata8: softreset failed (1st FIS failed) Feb 19 21:57:45 Tower kernel: ata8: limiting SATA link speed to 3.0 Gbps Feb 19 21:57:45 Tower kernel: ata8: hard resetting link Feb 19 21:57:50 Tower kernel: ata8: softreset failed (1st FIS failed) Feb 19 21:57:50 Tower kernel: ata8: reset failed, giving up Feb 19 21:57:50 Tower kernel: ata8.00: disabled Feb 19 21:57:50 Tower kernel: ata8: EH complete Feb 19 21:57:50 Tower kernel: sd 8:0:0:0: [sdi] tag#14 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00 Feb 19 21:57:50 Tower kernel: sd 8:0:0:0: [sdi] tag#14 CDB: opcode=0x2a 2a 00 00 0b e1 90 00 0a 00 00 Feb 19 21:57:50 Tower kernel: print_req_error: I/O error, dev sdi, sector 778640 Feb 19 21:57:50 Tower kernel: sd 8:0:0:0: [sdi] tag#15 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00 Feb 19 21:57:50 Tower kernel: sd 8:0:0:0: [sdi] tag#15 CDB: opcode=0x2a 2a 00 00 0b db 90 00 06 00 00 Feb 19 21:57:50 Tower kernel: print_req_error: I/O error, dev sdi, sector 777104 Feb 19 21:57:50 Tower kernel: sd 8:0:0:0: [sdi] tag#16 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00 Feb 19 21:57:50 Tower kernel: sd 8:0:0:0: [sdi] tag#16 CDB: opcode=0x2a 2a 00 00 0b d1 90 00 0a 00 00 Feb 19 21:57:50 Tower kernel: print_req_error: I/O error, dev sdi, sector 774544 Feb 19 21:57:50 Tower kernel: sd 8:0:0:0: [sdi] tag#17 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00 Feb 19 21:57:50 Tower kernel: sd 8:0:0:0: [sdi] tag#17 CDB: opcode=0x2a 2a 00 00 0b cb 90 00 06 00 00 Feb 19 21:57:50 Tower kernel: print_req_error: I/O error, dev sdi, sector 773008 Feb 19 21:57:50 Tower kernel: sd 8:0:0:0: [sdi] tag#18 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00 Feb 19 21:57:50 Tower kernel: sd 8:0:0:0: [sdi] tag#18 CDB: opcode=0x2a 2a 00 00 0b c1 90 00 0a 00 00 Feb 19 21:57:50 Tower kernel: print_req_error: I/O error, dev sdi, sector 770448 Feb 19 21:57:50 Tower kernel: sd 8:0:0:0: [sdi] tag#19 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00 Feb 19 21:57:50 Tower kernel: sd 8:0:0:0: [sdi] tag#19 CDB: opcode=0x2a 2a 00 00 0b bb 90 00 06 00 00 Feb 19 21:57:50 Tower kernel: print_req_error: I/O error, dev sdi, sector 768912 Feb 19 21:57:50 Tower kernel: sd 8:0:0:0: [sdi] tag#20 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00 Feb 19 21:57:50 Tower kernel: sd 8:0:0:0: [sdi] tag#20 CDB: opcode=0x2a 2a 00 00 0b b1 90 00 0a 00 00 Feb 19 21:57:50 Tower kernel: print_req_error: I/O error, dev sdi, sector 766352 Feb 19 21:57:50 Tower kernel: sd 8:0:0:0: [sdi] tag#21 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00 Feb 19 21:57:50 Tower kernel: sd 8:0:0:0: [sdi] tag#21 CDB: opcode=0x2a 2a 00 00 0b ab 90 00 06 00 00 Feb 19 21:57:50 Tower kernel: print_req_error: I/O error, dev sdi, sector 764816 Feb 19 21:57:50 Tower kernel: sd 8:0:0:0: [sdi] tag#22 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00 Feb 19 21:57:50 Tower kernel: sd 8:0:0:0: [sdi] tag#22 CDB: opcode=0x2a 2a 00 00 0b a1 90 00 0a 00 00 Feb 19 21:57:50 Tower kernel: print_req_error: I/O error, dev sdi, sector 762256 Feb 19 21:57:50 Tower kernel: sd 8:0:0:0: [sdi] tag#23 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00 Feb 19 21:57:50 Tower kernel: sd 8:0:0:0: [sdi] tag#23 CDB: opcode=0x2a 2a 00 00 0b 9b 90 00 06 00 00 Feb 19 21:57:50 Tower kernel: print_req_error: I/O error, dev sdi, sector 760720 Feb 19 21:57:50 Tower kernel: XFS (sdi1): metadata I/O error in "xlog_iodone" at daddr 0xdf9512f len 64 error 5 Feb 19 21:57:50 Tower kernel: XFS (sdi1): xfs_do_force_shutdown(0x2) called from line 1250 of file fs/xfs/xfs_log.c. Return address = 00000000f7c65300 Feb 19 21:57:50 Tower kernel: XFS (sdi1): Log I/O Error Detected. Shutting down filesystem Feb 19 21:57:50 Tower kernel: XFS (sdi1): Please umount the filesystem and rectify the problem(s) Feb 19 21:57:50 Tower kernel: XFS (sdi1): metadata I/O error in "xlog_iodone" at daddr 0xdf9516f len 64 error 5 Feb 19 21:57:50 Tower kernel: XFS (sdi1): xfs_do_force_shutdown(0x2) called from line 1250 of file fs/xfs/xfs_log.c. Return address = 00000000f7c65300 Feb 19 21:57:50 Tower kernel: XFS (sdi1): metadata I/O error in "xlog_iodone" at daddr 0xdf951af len 64 error 5 Feb 19 21:57:50 Tower kernel: XFS (sdi1): xfs_do_force_shutdown(0x2) called from line 1250 of file fs/xfs/xfs_log.c. Return address = 00000000f7c65300 Feb 19 21:57:50 Tower kernel: XFS (sdi1): metadata I/O error in "xlog_iodone" at daddr 0xdf951ef len 64 error 5 Feb 19 21:57:50 Tower kernel: XFS (sdi1): xfs_do_force_shutdown(0x2) called from line 1250 of file fs/xfs/xfs_log.c. Return address = 00000000f7c65300 Feb 19 21:57:50 Tower kernel: XFS (sdi1): metadata I/O error in "xlog_iodone" at daddr 0xdf9522f len 64 error 5 Feb 19 21:57:50 Tower kernel: XFS (sdi1): xfs_do_force_shutdown(0x2) called from line 1250 of file fs/xfs/xfs_log.c. Return address = 00000000f7c65300 Feb 19 21:57:50 Tower kernel: XFS (sdi1): metadata I/O error in "xlog_iodone" at daddr 0xdf9526f len 64 error 5 Feb 19 21:57:50 Tower kernel: XFS (sdi1): xfs_do_force_shutdown(0x2) called from line 1250 of file fs/xfs/xfs_log.c. Return address = 00000000f7c65300 Feb 19 21:57:50 Tower kernel: XFS (sdi1): metadata I/O error in "xlog_iodone" at daddr 0xdf952af len 64 error 5 Feb 19 21:57:50 Tower kernel: XFS (sdi1): xfs_do_force_shutdown(0x2) called from line 1250 of file fs/xfs/xfs_log.c. Return address = 00000000f7c65300 Feb 19 21:57:50 Tower kernel: XFS (sdi1): metadata I/O error in "xlog_iodone" at daddr 0xdf952ef len 64 error 5 Feb 19 21:57:50 Tower kernel: XFS (sdi1): xfs_do_force_shutdown(0x2) called from line 1250 of file fs/xfs/xfs_log.c. Return address = 00000000f7c65300 Feb 19 21:57:50 Tower kernel: XFS (sdi1): writeback error on sector 808744 Feb 19 21:57:50 Tower kernel: XFS (sdi1): writeback error on sector 808808 Feb 19 21:57:50 Tower kernel: XFS (sdi1): writeback error on sector 809432 Feb 19 21:57:50 Tower kernel: XFS (sdi1): writeback error on sector 808032 Feb 19 21:57:50 Tower kernel: XFS (sdi1): writeback error on sector 808168 Feb 19 21:57:50 Tower kernel: XFS (sdi1): writeback error on sector 733584 Feb 19 21:57:50 Tower kernel: XFS (sdi1): writeback error on sector 810056 Feb 19 21:57:50 Tower kernel: XFS (sdi1): writeback error on sector 1049728 Feb 19 21:57:50 Tower kernel: XFS (sdi1): writeback error on sector 887784 Feb 19 21:57:50 Tower kernel: XFS (sdi1): writeback error on sector 814152 Feb 19 22:02:11 Tower kernel: sd 8:0:0:0: [sdi] tag#6 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00 Feb 19 22:02:11 Tower kernel: sd 8:0:0:0: [sdi] tag#6 CDB: opcode=0x85 85 06 20 00 00 00 00 00 00 00 00 00 00 40 e5 00 Feb 19 22:02:11 Tower kernel: sd 8:0:0:0: [sdi] tag#8 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00 Feb 19 22:02:11 Tower kernel: sd 8:0:0:0: [sdi] tag#8 CDB: opcode=0x85 85 06 20 00 00 00 00 00 00 00 00 00 00 40 98 00 Feb 19 22:02:16 Tower kernel: sd 8:0:0:0: [sdi] tag#16 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00 Feb 19 22:02:16 Tower kernel: sd 8:0:0:0: [sdi] tag#16 CDB: opcode=0x85 85 06 20 00 00 00 00 00 00 00 00 00 00 40 e5 00 Feb 19 22:02:16 Tower kernel: sd 8:0:0:0: [sdi] tag#18 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00 Feb 19 22:02:16 Tower kernel: sd 8:0:0:0: [sdi] tag#18 CDB: opcode=0x85 85 06 20 00 00 00 00 00 00 00 00 00 00 40 98 00 Feb 19 22:09:29 Tower kernel: sd 8:0:0:0: [sdi] tag#24 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00 Feb 19 22:09:29 Tower kernel: sd 8:0:0:0: [sdi] tag#24 CDB: opcode=0x85 85 06 20 00 00 00 00 00 00 00 00 00 00 40 e5 00 Feb 19 22:09:29 Tower kernel: sd 8:0:0:0: [sdi] tag#26 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00 Feb 19 22:09:29 Tower kernel: sd 8:0:0:0: [sdi] tag#26 CDB: opcode=0x85 85 06 20 00 00 00 00 00 00 00 00 00 00 40 98 00 Feb 19 22:09:30 Tower kernel: sd 8:0:0:0: [sdi] tag#29 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00 Feb 19 22:09:30 Tower kernel: sd 8:0:0:0: [sdi] tag#29 CDB: opcode=0x85 85 06 20 00 00 00 00 00 00 00 00 00 00 40 e5 00 Feb 19 22:09:30 Tower kernel: sd 8:0:0:0: [sdi] tag#31 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00 Feb 19 22:09:30 Tower kernel: sd 8:0:0:0: [sdi] tag#31 CDB: opcode=0x85 85 06 20 00 00 00 00 00 00 00 00 00 00 40 98 00 Feb 19 22:12:51 Tower emhttpd: shcmd (129): /usr/sbin/hdparm -y /dev/sdi Feb 19 22:12:51 Tower root: /dev/sdi: Feb 19 22:12:51 Tower kernel: sd 8:0:0:0: [sdi] tag#14 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00 Feb 19 22:12:51 Tower kernel: sd 8:0:0:0: [sdi] tag#14 CDB: opcode=0x85 85 06 20 00 00 00 00 00 00 00 00 00 00 40 e0 00 Feb 19 22:12:51 Tower kernel: sd 8:0:0:0: [sdi] tag#16 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00 Feb 19 22:12:51 Tower kernel: sd 8:0:0:0: [sdi] tag#16 CDB: opcode=0x85 85 06 20 00 00 00 00 00 00 00 00 00 00 40 94 0 Thanks for any help. Planning to swap cables just in case, but have already re-seated the sata cable with no luck.

The utility is showing all of my disks except for one. On the right side at the top it says "1 new drive detected. (sdb)", which is the drive that is missing. I have re-scanned controllers multiple times but it keeps showing the same. The missing drive (sdb) is a WD Red 3TB WDC_WD30EFRX-68EUZN0. I have three of this identical drive and it's finding the others, just not this one. The missing drive is seen in the array, storaing data, no errors, passing SMART, and appears healthy. I have six drives plugged into the motherboad sata ports, including the one missing sbd. I also have a PCI sata card with 1 drive that is showing up fine.

Thanks! Is the key file the only file that needs saved? Everything else can be blown away? By disk assignment, do you mean to correlate which serial equals disk 1, disk 2, etc? Any link to simple instructions on that? I'm technical and can do, just not familiar with the process.

Loaded and it boots, but now it takes around 30 minutes to load bzimage and bzroot. Was running fine before upgrade.

My upgrade went smoothly. But now my server will become unresponsive every day or two. Lights are on, fans spinning, but no response to ping or web.

http://en.community.dell.com/techcenter/extras/w/wiki/2837.hdd-support-for-2-5tb-3tb-drives-and-beyond

Details! Pics!

I've attached my notes on setting up rsync. This should be a fairly complete "how-to". Cool! Thanks.

Care to do a detailed write-up? Many other users could benefit from your experience.

This is $109 now.

Back up to $121 already.

Amazon currently has the WD Red 3TB for $109. Pretty good price...I've been tracking on Camel Camel Camel.

This script worked well on my unRaid box and I found it interesting to see the speed info per drive. Thanks for creating the script.