comfox Posted March 6, 2015 Share Posted March 6, 2015 Hello, After some serious problems with my array I finally got the system stable only to find a drive Red Ball on me. I had a spare 3TB drive though so I threw it in and for some reason unRAID is detecting the drive at 0B. See the screen shot attached. I have run preclear on this drive it passed with flying colours. Any thoughts? When I try and put the 3TB WD Green in place of the Red Ball drive I get this error on the "Array Operations" tab: The replacement disk must be as big or bigger than the original. Quote Link to comment
comfox Posted March 6, 2015 Author Share Posted March 6, 2015 So just to try something I turned the array on and left the new drive unassigned. When I went to the unassigned tab the drive is showing up as 3TB now. So frustrating. What am I doing wrong here? Quote Link to comment
comfox Posted March 6, 2015 Author Share Posted March 6, 2015 My syslog is 60+MB. Is that normal? Compressed it is still 2+MB and it won't let me attach it. What should I do? Quote Link to comment
trurl Posted March 6, 2015 Share Posted March 6, 2015 Syslogs live in memory and so don't survive a reboot. Since your screenshot says you only have 2 minutes uptime it is not normal for your syslog to be so large. Are you sure you are getting the syslog correctly? Quote Link to comment
comfox Posted March 6, 2015 Author Share Posted March 6, 2015 i am following the article on the wiki page called "capturing a syslog" so yes very confident i am getting it correctly. when i tail the syslog to the telnet terminal the screen keeps scrolling. Quote Link to comment
Squid Posted March 6, 2015 Share Posted March 6, 2015 then you've got some issues. zip it up and post if possible, or use a free cloud service or something and post the link to it. Worst case, take a picture with your phone and post it up of the lines that are scrolling Quote Link to comment
comfox Posted March 7, 2015 Author Share Posted March 7, 2015 then you've got some issues. zip it up and post if possible, or use a free cloud service or something and post the link to it. Worst case, take a picture with your phone and post it up of the lines that are scrolling Thanks for the tip I have uploaded it to dropbox and here is the link to it. https://www.dropbox.com/s/kr631oqx7au6b35/syslog.zip?dl=0 Quote Link to comment
Squid Posted March 7, 2015 Share Posted March 7, 2015 Wow... Can't say that I've ever seen anything like that before. Your posted syslog is 60 Meg, has 750000 lines in it, covers a 4 hour window, and that's only a snippet of it. It's all just a continuing repeat of the same sections over and over again. Namely: Mar 6 04:40:02 NAS emhttp: shcmd (59800): rmmod md-mod |& logger Mar 6 04:40:02 NAS emhttp: shcmd (59801): modprobe md-mod super=/boot/config/super.dat slots=24 |& logger Mar 6 04:40:02 NAS emhttp: shcmd (59802): udevadm settle Mar 6 04:40:02 NAS kernel: md: unRAID driver removed Mar 6 04:40:02 NAS kernel: md: unRAID driver 2.2.0 installed Mar 6 04:40:02 NAS emhttp: Device inventory: Mar 6 04:40:02 NAS emhttp: WDC_WD20EARS-00MVWB0_WD-WCAZA4746883 (sdb) 1953514584 Mar 6 04:40:02 NAS emhttp: HGST_HDS5C4040ALE630_PL1331LAGJP3EH (sdc) 3907018584 Mar 6 04:40:02 NAS emhttp: WDC_WD30EZRX-00D8PB0_WD-WMC4N0F0Z00E (sdd) 2930233816 Mar 6 04:40:02 NAS emhttp: WDC_WD40EZRX-00SPEB0_WD-WMC4E0043633 (sde) 3906985816 Mar 6 04:40:02 NAS emhttp: WDC_WD20EARS-00S8B1_WD-WCAVY2471148 (sdf) 1953514584 Mar 6 04:40:02 NAS emhttp: WDC_WD30EZRX-00DC0B0_WD-WMC1T2028541 (sdg) 2930266584 Mar 6 04:40:02 NAS emhttp: WDC_WD20EARS-00S8B1_WD-WCAVY2474599 (sdh) 1953514584 Mar 6 04:40:02 NAS emhttp: WDC_WD20EARS-00S8B1_WD-WCAVY2471173 (sdi) 1953514584 Mar 6 04:40:02 NAS emhttp: HGST_HDS5C4040ALE630_PL2331LAGJ92AJ (sdj) 3907018584 Mar 6 04:40:02 NAS emhttp: WDC_WD20EARS-00S8B1_WD-WCAVY2472401 (sdk) 1953514584 Mar 6 04:40:02 NAS emhttp: WDC_WD20EARS-00MVWB0_WD-WMAZ20420852 (sdl) 1953514584 Mar 6 04:40:02 NAS emhttp: WDC_WD20EARS-00MVWB0_WD-WCAZA1279080 (sdm) 1953514584 Mar 6 04:40:02 NAS kernel: mdcmd (1): import 0 8,144 3907018532 HGST_HDS5C4040ALE630_PL2331LAGJ92AJ Mar 6 04:40:02 NAS kernel: md: import disk0: [8,144] (sdj) HGST_HDS5C4040ALE630_PL2331LAGJ92AJ size: 3907018532 Mar 6 04:40:02 NAS kernel: mdcmd (2): import 1 8,128 1953514552 WDC_WD20EARS-00S8B1_WD-WCAVY2471173 Mar 6 04:40:02 NAS kernel: md: import disk1: [8,128] (sdi) WDC_WD20EARS-00S8B1_WD-WCAVY2471173 size: 1953514552 Mar 6 04:40:02 NAS kernel: mdcmd (3): import 2 8,160 1953514552 WDC_WD20EARS-00S8B1_WD-WCAVY2472401 Mar 6 04:40:02 NAS kernel: md: import disk2: [8,160] (sdk) WDC_WD20EARS-00S8B1_WD-WCAVY2472401 size: 1953514552 Mar 6 04:40:02 NAS kernel: mdcmd (4): import 3 8,112 1953514552 WDC_WD20EARS-00S8B1_WD-WCAVY2474599 Mar 6 04:40:02 NAS kernel: md: import disk3: [8,112] (sdh) WDC_WD20EARS-00S8B1_WD-WCAVY2474599 size: 1953514552 Mar 6 04:40:02 NAS kernel: mdcmd (5): import 4 8,192 1953514552 WDC_WD20EARS-00MVWB0_WD-WCAZA1279080 Mar 6 04:40:02 NAS kernel: md: import disk4: [8,192] (sdm) WDC_WD20EARS-00MVWB0_WD-WCAZA1279080 size: 1953514552 Mar 6 04:40:02 NAS kernel: mdcmd (6): import 5 8,176 1953514552 WDC_WD20EARS-00MVWB0_WD-WMAZ20420852 Mar 6 04:40:02 NAS kernel: md: import disk5: [8,176] (sdl) WDC_WD20EARS-00MVWB0_WD-WMAZ20420852 size: 1953514552 Mar 6 04:40:02 NAS emhttp: shcmd (59803): /usr/local/sbin/emhttp_event driver_loaded Mar 6 04:40:02 NAS kernel: mdcmd (7): import 6 8,32 3907018532 HGST_HDS5C4040ALE630_PL1331LAGJP3EH Mar 6 04:40:02 NAS kernel: md: import disk6: [8,32] (sdc) HGST_HDS5C4040ALE630_PL1331LAGJP3EH size: 3907018532 Mar 6 04:40:02 NAS kernel: mdcmd (: import 7 8,16 1953514552 WDC_WD20EARS-00MVWB0_WD-WCAZA4746883 Mar 6 04:40:02 NAS kernel: md: import disk7: [8,16] (sdb) WDC_WD20EARS-00MVWB0_WD-WCAZA4746883 size: 1953514552 Mar 6 04:40:02 NAS kernel: mdcmd (9): import 8 8,96 2930266532 WDC_WD30EZRX-00DC0B0_WD-WMC1T2028541 Mar 6 04:40:02 NAS kernel: md: import disk8: [8,96] (sdg) WDC_WD30EZRX-00DC0B0_WD-WMC1T2028541 size: 2930266532 Mar 6 04:40:02 NAS kernel: mdcmd (10): import 9 8,48 2930233768 WDC_WD30EZRX-00D8PB0_WD-WMC4N0F0Z00E Mar 6 04:40:02 NAS kernel: md: import disk9: [8,48] (sdd) WDC_WD30EZRX-00D8PB0_WD-WMC4N0F0Z00E size: 2930233768 Mar 6 04:40:02 NAS kernel: md: disk9 replaced Mar 6 04:40:02 NAS kernel: mdcmd (11): import 10 8,64 3906985768 WDC_WD40EZRX-00SPEB0_WD-WMC4E0043633 Mar 6 04:40:02 NAS kernel: md: import disk10: [8,64] (sde) WDC_WD40EZRX-00SPEB0_WD-WMC4E0043633 size: 3906985768 Mar 6 04:40:02 NAS kernel: mdcmd (12): import 11 8,80 1953514552 WDC_WD20EARS-00S8B1_WD-WCAVY2471148 Mar 6 04:40:02 NAS kernel: md: import disk11: [8,80] (sdf) WDC_WD20EARS-00S8B1_WD-WCAVY2471148 size: 1953514552 Mar 6 04:40:02 NAS kernel: mdcmd (13): import 12 0,0 Mar 6 04:40:02 NAS kernel: mdcmd (14): import 13 0,0 Mar 6 04:40:02 NAS kernel: mdcmd (15): import 14 0,0 Mar 6 04:40:02 NAS kernel: mdcmd (16): import 15 0,0 Mar 6 04:40:02 NAS kernel: mdcmd (17): import 16 0,0 Mar 6 04:40:02 NAS kernel: mdcmd (18): import 17 0,0 Mar 6 04:40:02 NAS kernel: mdcmd (19): import 18 0,0 Mar 6 04:40:02 NAS kernel: mdcmd (20): import 19 0,0 Mar 6 04:40:02 NAS kernel: mdcmd (21): import 20 0,0 Mar 6 04:40:02 NAS kernel: mdcmd (22): import 21 0,0 Mar 6 04:40:02 NAS kernel: mdcmd (23): import 22 0,0 Mar 6 04:40:02 NAS kernel: mdcmd (24): import 23 0,0 Mar 6 04:40:02 NAS emhttp_event: driver_loaded Mar 6 04:40:03 NAS emhttp: shcmd (59804): rmmod md-mod |& logger Mar 6 04:40:03 NAS emhttp: shcmd (59805): modprobe md-mod super=/boot/config/super.dat slots=24 |& logger Under normal circumstances I would suggest wiping the flash drive and starting over, but with your one drive (disk 9) which you want to rebuild, I wouldn't do anything until you hear from somebody more knowledgeable than me as to why unRaid is doing this. I would PM limetech, jonp, and JoeL. / bjp999 and get their input before you do anything. Quote Link to comment
SSD Posted March 7, 2015 Share Posted March 7, 2015 Sorry, I'm pretty good from the command line but syslogs are not my specialty. Suggest a PM to RobJ as he's very good at reading these. It looks like unRaid is in some sort of a loop. Quote Link to comment
comfox Posted March 7, 2015 Author Share Posted March 7, 2015 Wow... Can't say that I've ever seen anything like that before. Your posted syslog is 60 Meg, has 75000 lines in it, covers a 4 hour window, and that's only a snippet of it. It's all just a continuing repeat of the same sections over and over again. Namely: Mar 6 04:40:02 NAS emhttp: shcmd (59800): rmmod md-mod |& logger Mar 6 04:40:02 NAS emhttp: shcmd (59801): modprobe md-mod super=/boot/config/super.dat slots=24 |& logger Mar 6 04:40:02 NAS emhttp: shcmd (59802): udevadm settle Mar 6 04:40:02 NAS kernel: md: unRAID driver removed Mar 6 04:40:02 NAS kernel: md: unRAID driver 2.2.0 installed Mar 6 04:40:02 NAS emhttp: Device inventory: Mar 6 04:40:02 NAS emhttp: WDC_WD20EARS-00MVWB0_WD-WCAZA4746883 (sdb) 1953514584 Mar 6 04:40:02 NAS emhttp: HGST_HDS5C4040ALE630_PL1331LAGJP3EH (sdc) 3907018584 Mar 6 04:40:02 NAS emhttp: WDC_WD30EZRX-00D8PB0_WD-WMC4N0F0Z00E (sdd) 2930233816 Mar 6 04:40:02 NAS emhttp: WDC_WD40EZRX-00SPEB0_WD-WMC4E0043633 (sde) 3906985816 Mar 6 04:40:02 NAS emhttp: WDC_WD20EARS-00S8B1_WD-WCAVY2471148 (sdf) 1953514584 Mar 6 04:40:02 NAS emhttp: WDC_WD30EZRX-00DC0B0_WD-WMC1T2028541 (sdg) 2930266584 Mar 6 04:40:02 NAS emhttp: WDC_WD20EARS-00S8B1_WD-WCAVY2474599 (sdh) 1953514584 Mar 6 04:40:02 NAS emhttp: WDC_WD20EARS-00S8B1_WD-WCAVY2471173 (sdi) 1953514584 Mar 6 04:40:02 NAS emhttp: HGST_HDS5C4040ALE630_PL2331LAGJ92AJ (sdj) 3907018584 Mar 6 04:40:02 NAS emhttp: WDC_WD20EARS-00S8B1_WD-WCAVY2472401 (sdk) 1953514584 Mar 6 04:40:02 NAS emhttp: WDC_WD20EARS-00MVWB0_WD-WMAZ20420852 (sdl) 1953514584 Mar 6 04:40:02 NAS emhttp: WDC_WD20EARS-00MVWB0_WD-WCAZA1279080 (sdm) 1953514584 Mar 6 04:40:02 NAS kernel: mdcmd (1): import 0 8,144 3907018532 HGST_HDS5C4040ALE630_PL2331LAGJ92AJ Mar 6 04:40:02 NAS kernel: md: import disk0: [8,144] (sdj) HGST_HDS5C4040ALE630_PL2331LAGJ92AJ size: 3907018532 Mar 6 04:40:02 NAS kernel: mdcmd (2): import 1 8,128 1953514552 WDC_WD20EARS-00S8B1_WD-WCAVY2471173 Mar 6 04:40:02 NAS kernel: md: import disk1: [8,128] (sdi) WDC_WD20EARS-00S8B1_WD-WCAVY2471173 size: 1953514552 Mar 6 04:40:02 NAS kernel: mdcmd (3): import 2 8,160 1953514552 WDC_WD20EARS-00S8B1_WD-WCAVY2472401 Mar 6 04:40:02 NAS kernel: md: import disk2: [8,160] (sdk) WDC_WD20EARS-00S8B1_WD-WCAVY2472401 size: 1953514552 Mar 6 04:40:02 NAS kernel: mdcmd (4): import 3 8,112 1953514552 WDC_WD20EARS-00S8B1_WD-WCAVY2474599 Mar 6 04:40:02 NAS kernel: md: import disk3: [8,112] (sdh) WDC_WD20EARS-00S8B1_WD-WCAVY2474599 size: 1953514552 Mar 6 04:40:02 NAS kernel: mdcmd (5): import 4 8,192 1953514552 WDC_WD20EARS-00MVWB0_WD-WCAZA1279080 Mar 6 04:40:02 NAS kernel: md: import disk4: [8,192] (sdm) WDC_WD20EARS-00MVWB0_WD-WCAZA1279080 size: 1953514552 Mar 6 04:40:02 NAS kernel: mdcmd (6): import 5 8,176 1953514552 WDC_WD20EARS-00MVWB0_WD-WMAZ20420852 Mar 6 04:40:02 NAS kernel: md: import disk5: [8,176] (sdl) WDC_WD20EARS-00MVWB0_WD-WMAZ20420852 size: 1953514552 Mar 6 04:40:02 NAS emhttp: shcmd (59803): /usr/local/sbin/emhttp_event driver_loaded Mar 6 04:40:02 NAS kernel: mdcmd (7): import 6 8,32 3907018532 HGST_HDS5C4040ALE630_PL1331LAGJP3EH Mar 6 04:40:02 NAS kernel: md: import disk6: [8,32] (sdc) HGST_HDS5C4040ALE630_PL1331LAGJP3EH size: 3907018532 Mar 6 04:40:02 NAS kernel: mdcmd (: import 7 8,16 1953514552 WDC_WD20EARS-00MVWB0_WD-WCAZA4746883 Mar 6 04:40:02 NAS kernel: md: import disk7: [8,16] (sdb) WDC_WD20EARS-00MVWB0_WD-WCAZA4746883 size: 1953514552 Mar 6 04:40:02 NAS kernel: mdcmd (9): import 8 8,96 2930266532 WDC_WD30EZRX-00DC0B0_WD-WMC1T2028541 Mar 6 04:40:02 NAS kernel: md: import disk8: [8,96] (sdg) WDC_WD30EZRX-00DC0B0_WD-WMC1T2028541 size: 2930266532 Mar 6 04:40:02 NAS kernel: mdcmd (10): import 9 8,48 2930233768 WDC_WD30EZRX-00D8PB0_WD-WMC4N0F0Z00E Mar 6 04:40:02 NAS kernel: md: import disk9: [8,48] (sdd) WDC_WD30EZRX-00D8PB0_WD-WMC4N0F0Z00E size: 2930233768 Mar 6 04:40:02 NAS kernel: md: disk9 replaced Mar 6 04:40:02 NAS kernel: mdcmd (11): import 10 8,64 3906985768 WDC_WD40EZRX-00SPEB0_WD-WMC4E0043633 Mar 6 04:40:02 NAS kernel: md: import disk10: [8,64] (sde) WDC_WD40EZRX-00SPEB0_WD-WMC4E0043633 size: 3906985768 Mar 6 04:40:02 NAS kernel: mdcmd (12): import 11 8,80 1953514552 WDC_WD20EARS-00S8B1_WD-WCAVY2471148 Mar 6 04:40:02 NAS kernel: md: import disk11: [8,80] (sdf) WDC_WD20EARS-00S8B1_WD-WCAVY2471148 size: 1953514552 Mar 6 04:40:02 NAS kernel: mdcmd (13): import 12 0,0 Mar 6 04:40:02 NAS kernel: mdcmd (14): import 13 0,0 Mar 6 04:40:02 NAS kernel: mdcmd (15): import 14 0,0 Mar 6 04:40:02 NAS kernel: mdcmd (16): import 15 0,0 Mar 6 04:40:02 NAS kernel: mdcmd (17): import 16 0,0 Mar 6 04:40:02 NAS kernel: mdcmd (18): import 17 0,0 Mar 6 04:40:02 NAS kernel: mdcmd (19): import 18 0,0 Mar 6 04:40:02 NAS kernel: mdcmd (20): import 19 0,0 Mar 6 04:40:02 NAS kernel: mdcmd (21): import 20 0,0 Mar 6 04:40:02 NAS kernel: mdcmd (22): import 21 0,0 Mar 6 04:40:02 NAS kernel: mdcmd (23): import 22 0,0 Mar 6 04:40:02 NAS kernel: mdcmd (24): import 23 0,0 Mar 6 04:40:02 NAS emhttp_event: driver_loaded Mar 6 04:40:03 NAS emhttp: shcmd (59804): rmmod md-mod |& logger Mar 6 04:40:03 NAS emhttp: shcmd (59805): modprobe md-mod super=/boot/config/super.dat slots=24 |& logger Under normal circumstances I would suggest wiping the flash drive and starting over, but with your one drive (disk 9) which you want to rebuild, I wouldn't do anything until you hear from somebody more knowledgeable than me as to why unRaid is doing this. I would PM limetech, jonp, and JoeL. / bjp999 and get their input before you do anything. Sorry, I'm pretty good from the command line but syslogs are not my specialty. Suggest a PM to RobJ as he's very good at reading these. It looks like unRaid is in some sort of a loop. Thanks for your thoughts. I have emailed Limetech a couple time about this but haven't heard a peep from them. I don't know the other folks but will see if I can get their attention. Quote Link to comment
limetech Posted March 7, 2015 Share Posted March 7, 2015 Reboot and get a fresh system log. Quote Link to comment
comfox Posted March 7, 2015 Author Share Posted March 7, 2015 Reboot and get a fresh system log. Done and done syslog-2015-03-07.txt Quote Link to comment
comfox Posted March 8, 2015 Author Share Posted March 8, 2015 Anyone able to review the new syslog I posted? Quote Link to comment
Squid Posted March 8, 2015 Share Posted March 8, 2015 It looks good. Is the same problem still happening? Are the same messages still continually being repeated? Quote Link to comment
comfox Posted March 8, 2015 Author Share Posted March 8, 2015 No the log isn't repeating now. But the original issue still persists where unRAID doesn't think my 3TB WD Green drive is big enough to replace my Red Balled Seageate 3TB drive. Quote Link to comment
comfox Posted March 8, 2015 Author Share Posted March 8, 2015 bump...still looking for advice. Quote Link to comment
SSD Posted March 9, 2015 Share Posted March 9, 2015 Often a slightly smaller disk means an HPA. I have explained it many times. Search for it. Quote Link to comment
garycase Posted March 9, 2015 Share Posted March 9, 2015 Agree it may be a Host Protected Area (HPA). There are several ways to resolve these. I prefer to simply boot to an HDAT2 CD (free) and use the "SetMax" function to automatically reset the drive to its native size. http://www.hdat2.com/ Quote Link to comment
jonp Posted March 10, 2015 Share Posted March 10, 2015 Remove all plugins, reboot your system, and please try again. If the issue occurs again, please post another syslog from that boot. Quote Link to comment
comfox Posted March 10, 2015 Author Share Posted March 10, 2015 Agree it may be a Host Protected Area (HPA). There are several ways to resolve these. I prefer to simply boot to an HDAT2 CD (free) and use the "SetMax" function to automatically reset the drive to its native size. http://www.hdat2.com/ I haven't had an oppertunity to look in to this, but will try to research it as soon as I can. Remove all plugins, reboot your system, and please try again. If the issue occurs again, please post another syslog from that boot. I don't have any plugins installed or if I do I don't know what they are. Quote Link to comment
trurl Posted March 10, 2015 Share Posted March 10, 2015 I don't have any plugins installed or if I do I don't know what they are. According to your syslog you have Dynamix installed and it's installing powerdown: Mar 7 08:20:31 NAS logger: Installing system plugins Mar 7 08:20:31 NAS logger: installing plugin: dynamix.webGui-2.2.7-noarch-bergware ... Mar 7 08:20:31 NAS logger: | Installing new package /boot/packages/powerdown-2.06-noarch-unRAID.tgz ... Mar 7 08:20:32 NAS logger: Installing user plugins Mar 7 08:20:32 NAS logger: Starting go script Mar 7 08:20:32 NAS emhttp: unRAID System Management Utility version 5.0.5 Quote Link to comment
comfox Posted March 10, 2015 Author Share Posted March 10, 2015 I don't have any plugins installed or if I do I don't know what they are. According to your syslog you have Dynamix installed and it's installing powerdown: Mar 7 08:20:31 NAS logger: Installing system plugins Mar 7 08:20:31 NAS logger: installing plugin: dynamix.webGui-2.2.7-noarch-bergware ... Mar 7 08:20:31 NAS logger: | Installing new package /boot/packages/powerdown-2.06-noarch-unRAID.tgz ... Mar 7 08:20:32 NAS logger: Installing user plugins Mar 7 08:20:32 NAS logger: Starting go script Mar 7 08:20:32 NAS emhttp: unRAID System Management Utility version 5.0.5 Thanks for pointing that out. I will take a look at how to remove that and do so! Quote Link to comment
trurl Posted March 10, 2015 Share Posted March 10, 2015 If you can get to the boot menu you can just boot in SAFE mode. Quote Link to comment
comfox Posted March 10, 2015 Author Share Posted March 10, 2015 If you can get to the boot menu you can just boot in SAFE mode. OK great, thanks for the tip. I didn't actually know what that did. 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.