voldak Posted January 14, 2017 Share Posted January 14, 2017 Hello, I logged into my server yesterday because Plex wasn't working. Upon investigation, Plex and some other dockers were stopped and I couldn't start them. I tried to remove the dockers to remake them and I was given an error that the docker didn't exist. I restarted the server and the cache drive wasn't there. I had the drive for a while so I figured it may be having issues. I replaced the drive today with another SSD, turned the server back on and the drive still isn't an option as a cache drive. The drive shows up when I use "preclear_disk.sh -l", but it fails almost immediately whenever I try to actually preclear it. I then shut the server off and swapped locations in my icydock...same story. Attached are my diagnostic files. tower-diagnostics-20170113-2111.zip Quote Link to comment
John_M Posted January 14, 2017 Share Posted January 14, 2017 Check your BIOS to make sure that the port (ata2) to which you have your Intel SSD connected is in AHCI mode. It looks as though it's in legacy IDE mode. Tell us more about the ICYDOCK and how you use it. Quote Link to comment
voldak Posted January 16, 2017 Author Share Posted January 16, 2017 John_M, Thank you for the reply. I went into the bios and changed all drives from "integrated IDE" to AHCI mode. Same story with the SSD. I actually have 2 IcyDocks in my server. My primary use is for ease of drive swaps. I ended up swapping the cache drive to one empty slot in my other IcyDock. FYI, my first IcyDock has all slots going straight into my motherboard, my second icy dock has 4 slots from a PCI-Express card that I use for expansion. Anyway, after swapping it still didn't show up. I also tried to swap the old cache drive with another drive. In doing this, the drive didn't show up, but it also made a data drive show up as missing. Quote Link to comment
John_M Posted January 16, 2017 Share Posted January 16, 2017 Are you saying that disks connected to the motherboard SATA sockets are recognised but ones connected to the PCIe card are not? Quote Link to comment
voldak Posted January 17, 2017 Author Share Posted January 17, 2017 No. They aren't all connected to the motherboard SATA sockets when the problem arises. I have my original SSD back in the server now, and it's only showing up as a total of 32.8kb drive. It isn't mountable, and I can't preclear or format the drive. I will be trying a SSD tomorrow evening that is known to be good and will report back. Thanks again for the help! Quote Link to comment
voldak Posted January 17, 2017 Author Share Posted January 17, 2017 Ok. So, I just booted the server back up with a brand new SSD to test out the Cache drive slot (this slot is plugged in straight to my mother board). I assigned the drive as cache, then I tried to format it. It didn't format. After checking the syslog, the following errors where in the syslog. Jan 17 11:16:22 Tower kernel: blk_update_request: I/O error, dev sdd, sector 0 Jan 17 11:16:22 Tower kernel: sd 7:0:1:0: [sdd] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00 Jan 17 11:16:22 Tower kernel: sd 7:0:1:0: [sdd] tag#0 CDB: opcode=0x28 28 00 00 00 00 00 00 00 08 00 Jan 17 11:16:22 Tower kernel: blk_update_request: I/O error, dev sdd, sector 0 Jan 17 11:16:22 Tower kernel: Buffer I/O error on dev sdd, logical block 0, async page read Jan 17 11:16:22 Tower kernel: sd 7:0:1:0: [sdd] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00 Jan 17 11:16:22 Tower kernel: sd 7:0:1:0: [sdd] tag#0 CDB: opcode=0x28 28 00 00 00 00 08 00 00 08 00 Jan 17 11:16:22 Tower kernel: blk_update_request: I/O error, dev sdd, sector 8 Jan 17 11:16:22 Tower kernel: Buffer I/O error on dev sdd, logical block 1, async page read Jan 17 11:16:22 Tower kernel: sd 7:0:1:0: [sdd] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00 Jan 17 11:16:22 Tower kernel: sd 7:0:1:0: [sdd] tag#0 CDB: opcode=0x28 28 00 1b f2 44 a8 00 00 08 00 Jan 17 11:16:22 Tower kernel: blk_update_request: I/O error, dev sdd, sector 468862120 Jan 17 11:16:22 Tower kernel: Buffer I/O error on dev sdd, logical block 58607765, async page read Jan 17 11:16:22 Tower kernel: Buffer I/O error on dev sdd, logical block 58607765, async page read Jan 17 11:16:22 Tower kernel: Buffer I/O error on dev sdd, logical block 58607765, async page read Jan 17 11:16:22 Tower kernel: Buffer I/O error on dev sdd, logical block 58607765, async page read Jan 17 11:16:22 Tower kernel: Buffer I/O error on dev sdd, logical block 58607765, async page read Jan 17 11:16:22 Tower emhttp: shcmd (175): set -o pipefail ; mount -t auto -o noatime,nodiratime /dev/sdd1 /mnt/cache |& logger Jan 17 11:16:22 Tower logger: mount: special device /dev/sdd1 does not exist Jan 17 11:16:22 Tower emhttp: shcmd: shcmd (175): exit status: 32 Jan 17 11:16:22 Tower emhttp: mount error: No file system (32) Quote Link to comment
voldak Posted January 17, 2017 Author Share Posted January 17, 2017 I swapped the drive to another slot (connected to my PCI-Express Add-on card) and the drive was mountable and looks functional. I'm going to keep it here to check it over the next few days. It seems that I may be having issues with only the slots on the motherboard, since the issue follows across two IcyDocks and only happens with motherboard ports. I may look at replacement to try. I'll keep this open and post updates just in case anyone else has similar issues. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.