snowmirage Posted August 19, 2018 Share Posted August 19, 2018 I have a fresh trial installation of unraid 6.5.3. I have a total of 8 Sata drives connected to the two different onboard sata controllers on my EVGA SR-2 motherboard (nothing overclocked). Also a LOT of 2 TB HDD on a IBM M1015 + HP SAS expander but those drives are all showing up in unraid 4 x 250 GB Samsung Evo SSDs 2 x 240GB SSDs (two different brands can't remember the names off the top of my head) 1 x 60GB SSD 1 x ~320 GB 2.5" mechanical hard disk. Before installing unraid I installed a fresh copy of windows 10 on the 60 GB SSD to test the system. In windows I was able to verify ALL the disk were available to the OS *in windows* wmic diskdrive get Name, Manufacturer, Model, InterfaceType, MediaType, SerialNumber 5 IDE (Standard disk drives) Fixed hard disk media Samsung SSD 840 EVO 250GB ATA Device \\.\PHYSICALDRIVE18 S1DBNSADB51559P 11 SCSI (Standard disk drives) Fixed hard disk media KingDian S280-240GB SCSI Disk Device \\.\PHYSICALDRIVE24 2016052500135 14 IDE (Standard disk drives) Fixed hard disk media Samsung SSD 840 EVO 250GB ATA Device \\.\PHYSICALDRIVE21 S1DBNSADB51553V 16 IDE (Standard disk drives) Fixed hard disk media SPCC Solid State Disk ATA Device \\.\PHYSICALDRIVE22 P1601544000000009646 19 IDE (Standard disk drives) Fixed hard disk media Samsung SSD 840 EVO 250GB ATA Device \\.\PHYSICALDRIVE20 S1DBNSADB51570A 21 SCSI (Standard disk drives) Fixed hard disk media Samsung SSD 840 EVO 250G SCSI Disk Device \\.\PHYSICALDRIVE23 S1DBNSADB51567R 24 IDE (Standard disk drives) Fixed hard disk media Patriot Torch ATA Device \\.\PHYSICALDRIVE19 DA5A075A06EE02149192 There I have the 4x Samsung Evo SSDS, 2x 240GB SSDs, and the 60 GB SSD However when I boot into unraid not all of them show up. SCSI Devices section under tools in the GUI [0:0:0:0] disk Corsair Voyager SliderX1 000E /dev/sda 15.5GB [3:0:0:0] disk ATA HITACHI HTS72323 C50B /dev/sdb 320GB [4:0:0:0] disk ATA Patriot Torch 02.6 /dev/sdx 60.0GB [5:0:0:0] disk ATA Samsung SSD 840 BB0Q /dev/sdy 250GB [6:0:0:0] disk ATA Samsung SSD 840 BB0Q /dev/sdz 250GB [7:0:0:0] disk ATA Samsung SSD 840 BB0Q /dev/sdaa 250GB [8:0:0:0] disk ATA SPCC Solid State V2.7 /dev/sdab 240GB [17:0:0:0] disk ATA ST2000DM001-1CH1 CC24 /dev/sdc 2.00TB [17:0:1:0] disk ATA WL2000GSA6472E 1E.5 /dev/sdd 2.00TB [17:0:2:0] disk ATA WL2000GSA6472E 1KX0 /dev/sde 2.00TB [17:0:3:0] disk ATA SAMSUNG HD204UI 0001 /dev/sdf 2.00TB [17:0:4:0] disk ATA WL2000GSA6472E 1DH2 /dev/sdg 2.00TB [17:0:5:0] disk ATA ST2000DM001-1CH1 CC24 /dev/sdh 2.00TB [17:0:6:0] disk ATA ST32000646NS G008 /dev/sdi 2.00TB [17:0:7:0] disk ATA ST32000644NS SN12 /dev/sdj 2.00TB [17:0:8:0] disk ATA WL2000GSA6472E 1D02 /dev/sdk 2.00TB [17:0:9:0] disk ATA WL2000GSA6472E NQ70 /dev/sdl 2.00TB [17:0:10:0] disk ATA WDC WD20EURS-63S AB51 /dev/sdm 2.00TB [17:0:11:0] disk ATA ST32000644NS SN12 /dev/sdn 2.00TB [17:0:12:0] disk ATA WDC WD20EADS-00S 5G04 /dev/sdo 2.00TB [17:0:13:0] disk ATA WDC WD20EADS-00S 5G04 /dev/sdp 2.00TB [17:0:14:0] disk ATA ST32000644NS GG15 /dev/sdq 2.00TB [17:0:15:0] disk ATA ST2000VN001-1T41 SC60 /dev/sdr 2.00TB [17:0:16:0] disk ATA ST32000644NS GG15 /dev/sds 2.00TB [17:0:17:0] disk ATA WL2000GSA6472E 1D01 /dev/sdt 2.00TB [17:0:18:0] disk ATA SAMSUNG HD204UI 0001 /dev/sdu 2.00TB [17:0:19:0] disk ATA WDC WD10EACS-00D 1A01 /dev/sdv 1.00TB [17:0:20:0] disk ATA WDC WD20EARS-00M AB51 /dev/sdw 2.00TB I can't seem to figure out why 1 of the Samsung EVO SSDs and the one KingDian 240 GB SSD are not showing up in unraid. I've attached the full diagnostic file from Tools > Diagnostics I would have thought I had bad drives, cables or such but if so they wouldn't show up in windows. I'd greatly appreciate any suggestions, I can't think of or find anything obvious I may have over looked. phoenix-diagnostics-20180819-1113.zip Link to comment
Squid Posted August 19, 2018 Share Posted August 19, 2018 I'd try reseating the cabling to the drives. 6 minutes ago, snowmirage said: I would have thought I had bad drives, cables or such but if so they wouldn't show up in windows The one thing about Windows is that it doesn't particularly care about how many times it has to reset / reinitialize a drive if a problem occurs with it. It'll just keep going and going until it works. MS philosophy is that its better to keep trying (and failing) than to notify the user that something is wrong. Link to comment
snowmirage Posted August 19, 2018 Author Share Posted August 19, 2018 I have tried reseating the cables and drives a few times still seeing the same results Good point regarding windows, I started trying to setup a few other parts of the system including grabbing the Fix Common Problems plugin That alerted me about some errors Machine Check Events detected on your server Looking through the logs (attached in first post but here's the .log file from that .zip) the only things jumping out at me are Many of these "failed to IDENTIFY (I/O error " messages Aug 19 11:07:01 phoenix kernel: ata10.00: qc timeout (cmd 0xec) Aug 19 11:07:01 phoenix kernel: ata10.00: failed to IDENTIFY (I/O error, err_mask=0x4) Aug 19 11:07:01 phoenix kernel: ata16.00: qc timeout (cmd 0xa1) Aug 19 11:07:01 phoenix kernel: ata16.00: failed to IDENTIFY (I/O error, err_mask=0x4) Aug 19 11:07:01 phoenix kernel: ata9.00: qc timeout (cmd 0xec) Aug 19 11:07:01 phoenix kernel: ata16: SATA link up 1.5 Gbps (SStatus 113 SControl 300) Aug 19 11:07:01 phoenix kernel: ata10: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Don't know what that means yet I'll try to keep searching but it looks like I'm not seeing that error for just the two drives that aren't showing up in unraid so that kinda leads me to believe its not directly related. The 2nd thing I see is this Hardware Error Aug 19 11:07:01 phoenix kernel: x86: Booting SMP configuration: Aug 19 11:07:01 phoenix kernel: .... node #0, CPUs: #1 #2 #3 #4 #5 Aug 19 11:07:01 phoenix kernel: .... node #1, CPUs: #6 Aug 19 11:07:01 phoenix kernel: mce: [Hardware Error]: Machine check events logged Aug 19 11:07:01 phoenix kernel: mce: [Hardware Error]: CPU 6: Machine Check: 0 Bank 8: ea106d80008000b1 Aug 19 11:07:01 phoenix kernel: mce: [Hardware Error]: TSC 0 MISC 40000 Aug 19 11:07:01 phoenix kernel: mce: [Hardware Error]: PROCESSOR 0:206c2 TIME 1534701952 SOCKET 1 APIC 20 microcode c Aug 19 11:07:01 phoenix kernel: #7 #8 #9 #10 #11 Aug 19 11:07:01 phoenix kernel: .... node #0, CPUs: #12 #13 #14 #15 #16 #17 Aug 19 11:07:01 phoenix kernel: .... node #1, CPUs: #18 #19 #20 #21 #22 #23 Don't know whats going on there either so the search continues ! syslog.txt Link to comment
John_M Posted August 20, 2018 Share Posted August 20, 2018 You have a hardware fault. It might be a faulty memory module or socket or it might be a bent pin on the relevant CPU socket. I'd reseat or swap around DIMMs and run memtest first because it's easier than reseating a CPU. I always make sure that SSDs are connected to motherboard SATA ports. Link to comment
snowmirage Posted August 20, 2018 Author Share Posted August 20, 2018 All the SSDs are connected directly to the motherboard. I'll run memtest, thanks for the advise. Link to comment
Recommended Posts
Archived
This topic is now archived and is closed to further replies.