gaikokujinkyofusho Posted March 28, 2015 Share Posted March 28, 2015 I wanted to use a 3tb drive as a parity drive on a system I am building so I installed the drive and went into the interface and noticed that under main, when i go to the list of drives in the pull down menu in the identification column the drive shows up as "0 B" sdc (as opposed to 3tb). All the other drives show up properly except this one. Just for the heck of it i tried to select it anyway (I am still experimenting so don't have anything important on this server) and unraid will not let me select it as a parity or data disk but at first would let me select it as a cache disk. After fiddling around it later disappeared from the pull down menu and dashboard all together. This drive worked fine in windows like 30 minutes before i put it into the unraid box so I don't think anything is wrong with the drive but I can't think of much else, beta bug perhaps? (hopefully not as i would really like to get this working). Any thoughts would be appreciated! Link to comment
Squid Posted March 28, 2015 Share Posted March 28, 2015 I wanted to use a 3tb drive as a parity drive on a system I am building so I installed the drive and went into the interface and noticed that under main, when i go to the list of drives in the pull down menu in the identification column the drive shows up as "0 B" sdc (as opposed to 3tb). All the other drives show up properly except this one. Just for the heck of it i tried to select it anyway (I am still experimenting so don't have anything important on this server) and unraid will not let me select it as a parity or data disk but at first would let me select it as a cache disk. After fiddling around it later disappeared from the pull down menu and dashboard all together. This drive worked fine in windows like 30 minutes before i put it into the unraid box so I don't think anything is wrong with the drive but I can't think of much else, beta bug perhaps? (hopefully not as i would really like to get this working). Any thoughts would be appreciated! Post a syslog when that drive is installed Link to comment
gaikokujinkyofusho Posted March 28, 2015 Author Share Posted March 28, 2015 Ah Right, shoulda thought of that, thanks! /usr/bin/tail -n 42 -f /var/log/syslog 2>&1 Mar 28 15:43:14 Tower emhttp: shcmd (21): udevadm settle Mar 28 15:43:14 Tower emhttp: shcmd (22): /sbin/btrfs device scan |& logger Mar 28 15:43:15 Tower logger: Scanning for Btrfs filesystems Mar 28 15:43:15 Tower emhttp: Device inventory: Mar 28 15:43:15 Tower emhttp: Hitachi_HDS722020ALA330_JK1171YAG3Y7HS (sdb) 1953514584 Mar 28 15:43:15 Tower emhttp: Hitachi_HDS722020ALA330_JK1171YAG3Y7VS (sdc) 1953514584 Mar 28 15:43:15 Tower emhttp: Hitachi_HDS722020ALA330_JK1171YAG5EGDS (sdd) 1953514584 Mar 28 15:43:15 Tower emhttp: WDC_WD20EADS-00R6B0_WD-WCAVY0356481 (sde) 1953514584 Mar 28 15:43:15 Tower emhttp: WDC_WD20EADS-00R6B0_WD-WCAVY0350749 (sdf) 1953514584 Mar 28 15:43:15 Tower emhttp: Hitachi_HUA723020ALA641_YFG3XBLA (sdg) 1953514584 Mar 28 15:43:15 Tower emhttp: shcmd (23): modprobe md-mod super=/boot/config/super.dat slots=24 |& logger Mar 28 15:43:15 Tower kernel: md: unRAID driver 2.4.0 installed Mar 28 15:43:15 Tower kernel: mdcmd (1): import 0 0,0 Mar 28 15:43:15 Tower kernel: md: disk0 missing Mar 28 15:43:15 Tower kernel: mdcmd (2): import 1 8,32 1953514552 Hitachi_HDS722020ALA330_JK1171YAG3Y7VS Mar 28 15:43:15 Tower kernel: md: import disk1: [8,32] (sdc) Hitachi_HDS722020ALA330_JK1171YAG3Y7VS size: 1953514552 Mar 28 15:43:15 Tower kernel: mdcmd (3): import 2 8,16 1953514552 Hitachi_HDS722020ALA330_JK1171YAG3Y7HS Mar 28 15:43:15 Tower kernel: md: import disk2: [8,16] (sdb) Hitachi_HDS722020ALA330_JK1171YAG3Y7HS size: 1953514552 Mar 28 15:43:15 Tower kernel: mdcmd (4): import 3 0,0 Mar 28 15:43:15 Tower kernel: mdcmd (5): import 4 0,0 Mar 28 15:43:15 Tower kernel: mdcmd (6): import 5 0,0 Mar 28 15:43:15 Tower kernel: mdcmd (7): import 6 0,0 Mar 28 15:43:15 Tower emhttp: import 24 cache device: no device Mar 28 15:43:15 Tower kernel: mdcmd (: import 7 0,0 Mar 28 15:43:15 Tower kernel: mdcmd (9): import 8 0,0 Mar 28 15:43:15 Tower kernel: mdcmd (10): import 9 0,0 Mar 28 15:43:15 Tower kernel: mdcmd (11): import 10 0,0 Mar 28 15:43:15 Tower kernel: mdcmd (12): import 11 0,0 Mar 28 15:43:15 Tower kernel: mdcmd (13): import 12 0,0 Mar 28 15:43:15 Tower kernel: mdcmd (14): import 13 0,0 Mar 28 15:43:15 Tower kernel: mdcmd (15): import 14 0,0 Mar 28 15:43:15 Tower kernel: mdcmd (16): import 15 0,0 Mar 28 15:43:15 Tower kernel: mdcmd (17): import 16 0,0 Mar 28 15:43:15 Tower kernel: mdcmd (18): import 17 0,0 Mar 28 15:43:15 Tower kernel: mdcmd (19): import 18 0,0 Mar 28 15:43:15 Tower kernel: mdcmd (20): import 19 0,0 Mar 28 15:43:15 Tower kernel: mdcmd (21): import 20 0,0 Mar 28 15:43:15 Tower kernel: mdcmd (22): import 21 0,0 Mar 28 15:43:15 Tower kernel: mdcmd (23): import 22 0,0 Mar 28 15:43:15 Tower kernel: mdcmd (24): import 23 0,0 Mar 28 15:43:15 Tower emhttp: import flash device: sda Mar 28 15:43:20 Tower emhttp: read_line: client closed the connection Mar 28 15:44:03 Tower emhttp: shcmd (25): rmmod md-mod |& logger Mar 28 15:44:03 Tower kernel: md: unRAID driver removed Mar 28 15:44:03 Tower emhttp: Unregistered Mar 28 15:44:03 Tower emhttp: array slots: 24 Mar 28 15:44:03 Tower emhttp: cache slots: 1 Mar 28 15:44:03 Tower emhttp: shcmd (26): udevadm settle Mar 28 15:44:03 Tower emhttp: shcmd (27): /sbin/btrfs device scan |& logger Mar 28 15:44:03 Tower logger: Scanning for Btrfs filesystems Mar 28 15:44:03 Tower emhttp: Device inventory: Mar 28 15:44:03 Tower emhttp: Hitachi_HDS722020ALA330_JK1171YAG3Y7HS (sdb) 1953514584 Mar 28 15:44:03 Tower emhttp: Hitachi_HDS722020ALA330_JK1171YAG3Y7VS (sdc) 1953514584 Mar 28 15:44:03 Tower emhttp: Hitachi_HDS722020ALA330_JK1171YAG5EGDS (sdd) 1953514584 Mar 28 15:44:03 Tower emhttp: WDC_WD20EADS-00R6B0_WD-WCAVY0356481 (sde) 1953514584 Mar 28 15:44:03 Tower emhttp: WDC_WD20EADS-00R6B0_WD-WCAVY0350749 (sdf) 1953514584 Mar 28 15:44:03 Tower emhttp: Hitachi_HUA723020ALA641_YFG3XBLA (sdg) 1953514584 Mar 28 15:44:03 Tower emhttp: shcmd (28): modprobe md-mod super=/boot/config/super.dat slots=24 |& logger Mar 28 15:44:03 Tower kernel: md: unRAID driver 2.4.0 installed Mar 28 15:44:03 Tower kernel: mdcmd (1): import 0 0,0 Mar 28 15:44:03 Tower kernel: md: disk0 missing Mar 28 15:44:03 Tower kernel: mdcmd (2): import 1 8,32 1953514552 Hitachi_HDS722020ALA330_JK1171YAG3Y7VS Mar 28 15:44:03 Tower kernel: md: import disk1: [8,32] (sdc) Hitachi_HDS722020ALA330_JK1171YAG3Y7VS size: 1953514552 Mar 28 15:44:03 Tower kernel: mdcmd (3): import 2 8,16 1953514552 Hitachi_HDS722020ALA330_JK1171YAG3Y7HS Mar 28 15:44:03 Tower kernel: md: import disk2: [8,16] (sdb) Hitachi_HDS722020ALA330_JK1171YAG3Y7HS size: 1953514552 Mar 28 15:44:03 Tower kernel: mdcmd (4): import 3 0,0 Mar 28 15:44:03 Tower kernel: mdcmd (5): import 4 0,0 Mar 28 15:44:03 Tower kernel: mdcmd (6): import 5 0,0 Mar 28 15:44:03 Tower kernel: mdcmd (7): import 6 0,0 Mar 28 15:44:03 Tower kernel: mdcmd (: import 7 0,0 Mar 28 15:44:03 Tower kernel: mdcmd (9): import 8 0,0 Mar 28 15:44:03 Tower kernel: mdcmd (10): import 9 0,0 Mar 28 15:44:03 Tower kernel: mdcmd (11): import 10 0,0 Mar 28 15:44:03 Tower kernel: mdcmd (12): import 11 0,0 Mar 28 15:44:03 Tower emhttp: import 24 cache device: no device Mar 28 15:44:03 Tower emhttp: import flash device: sda Mar 28 15:44:03 Tower kernel: mdcmd (13): import 12 0,0 Mar 28 15:44:03 Tower kernel: mdcmd (14): import 13 0,0 Mar 28 15:44:03 Tower kernel: mdcmd (15): import 14 0,0 Mar 28 15:44:03 Tower kernel: mdcmd (16): import 15 0,0 Mar 28 15:44:03 Tower kernel: mdcmd (17): import 16 0,0 Mar 28 15:44:03 Tower kernel: mdcmd (18): import 17 0,0 Mar 28 15:44:03 Tower kernel: mdcmd (19): import 18 0,0 Mar 28 15:44:03 Tower kernel: mdcmd (20): import 19 0,0 Mar 28 15:44:03 Tower kernel: mdcmd (21): import 20 0,0 Mar 28 15:44:03 Tower kernel: mdcmd (22): import 21 0,0 Mar 28 15:44:03 Tower kernel: mdcmd (23): import 22 0,0 Mar 28 15:44:03 Tower kernel: mdcmd (24): import 23 0,0 I noticed here that this time the 3tb drive doesn't even seem to be showing up (its a hitachi hds5c3030ala630) Link to comment
gaikokujinkyofusho Posted March 29, 2015 Author Share Posted March 29, 2015 Nuts. Ok, just for sh*ts and giggles I switched the data cables from one card/2tb drive to the 3tb drive and the 3tb's data cable to the 2tb drive and rebooted and now the 3tb drive shows up just fine! ... aaaaand I can't get the log window to come up... even after restarting twice (in any of the browsers, not quite sure how to do it from the shell). sigh, not sure what to make of it, 3tb is usable now but would love to know if this going to happen again (or if i did something to create the afore situation). Link to comment
garycase Posted March 29, 2015 Share Posted March 29, 2015 The cables may not have been securely seated; or you may have a marginal cable. Are all of your SATA cables latching cables? If not, I'd replace them with new latching cables. Link to comment
gaikokujinkyofusho Posted March 29, 2015 Author Share Posted March 29, 2015 They are latching cables, its totally possible they were still loose but I like triple checked it before, anywho I am starting to think that was it. I guess I will continue trying things out and see if i can recreate the issue and consider myself lucky if i don't Link to comment
Recommended Posts
Archived
This topic is now archived and is closed to further replies.