Hoopster Posted November 6, 2012 Share Posted November 6, 2012 Just precleared two 3TB WD Red drives. I add them to the array (they show as blue balls) and it fails to start. If I unassign the drives, the array starts with no problem. This is with version 5 rc6 8168 test2. Any ideas? Quote Link to comment
dgaschk Posted November 6, 2012 Share Posted November 6, 2012 How does it "fail to start"? Attach a syslog. Quote Link to comment
Hoopster Posted November 6, 2012 Author Share Posted November 6, 2012 How does it "fail to start"? Attach a syslog. Clicking Start just greys out the Start button. Nothing happens. Status remains at "Stopped. Found 2 new disks." Array does not start. Check "Yes I want to do this", Click Start button again. Lather, rinse, repeat. Array does not start until I unassign the drives. Relevent lines of syslog: Nov 6 09:14:25 MediaNAS kernel: md: import disk1: [8,48] (sdd) WDC_WD30EZRX-00MMMB0_WD-WCAWZ2214923 size: 2930266532 Nov 6 09:14:25 MediaNAS kernel: mdcmd (3): import 2 8,80 1953514552 ST2000DL003-9VT166_5YD6GLZ4 Nov 6 09:14:25 MediaNAS kernel: md: import disk2: [8,80] (sdf) ST2000DL003-9VT166_5YD6GLZ4 size: 1953514552 Nov 6 09:14:25 MediaNAS kernel: mdcmd (4): import 3 8,0 1953514552 ST2000DL003-9VT166_6YD1Q84W Nov 6 09:14:25 MediaNAS kernel: md: import disk3: [8,0] (sda) ST2000DL003-9VT166_6YD1Q84W size: 1953514552 Nov 6 09:14:25 MediaNAS kernel: mdcmd (5): import 4 8,32 2930266532 WDC_WD30EFRX-68AX9N0_WD-WMC1T0529663 Nov 6 09:14:25 MediaNAS kernel: md: import disk4: [8,32] (sdc) WDC_WD30EFRX-68AX9N0_WD-WMC1T0529663 size: 2930266532 Nov 6 09:14:25 MediaNAS kernel: md: disk4 new disk Nov 6 09:14:25 MediaNAS kernel: mdcmd (6): import 5 8,64 2930266532 WDC_WD30EFRX-68AX9N0_WD-WMC1T0454239 Nov 6 09:14:25 MediaNAS kernel: md: import disk5: [8,64] (sde) WDC_WD30EFRX-68AX9N0_WD-WMC1T0454239 size: 2930266532 Nov 6 09:14:25 MediaNAS kernel: md: disk5 new disk Nov 6 09:14:25 MediaNAS emhttp: shcmd (743): /usr/local/sbin/emhttp_event driver_loaded Nov 6 09:14:25 MediaNAS emhttp_event: driver_loaded Nov 6 09:14:30 MediaNAS emhttp: shcmd (744): rmmod md-mod |& logger Nov 6 09:14:30 MediaNAS emhttp: shcmd (745): modprobe md-mod super=/boot/config/super.dat slots=6 |& logger Nov 6 09:14:30 MediaNAS emhttp: shcmd (746): udevadm settle Nov 6 09:14:30 MediaNAS emhttp: Device inventory: Nov 6 09:14:30 MediaNAS emhttp: ST2000DL003-9VT166_6YD1Q84W (sda) 1953514584 Nov 6 09:14:30 MediaNAS emhttp: Hitachi_HTS723232L9A360_090204FC1400NEGRASYC (sdb) 312571224 Nov 6 09:14:30 MediaNAS emhttp: WDC_WD30EFRX-68AX9N0_WD-WMC1T0529663 (sdc) 2930266584 Nov 6 09:14:30 MediaNAS emhttp: WDC_WD30EZRX-00MMMB0_WD-WCAWZ2214923 (sdd) 2930266584 Nov 6 09:14:30 MediaNAS emhttp: WDC_WD30EFRX-68AX9N0_WD-WMC1T0454239 (sde) 2930266584 Nov 6 09:14:30 MediaNAS kernel: md: unRAID driver removed Nov 6 09:14:30 MediaNAS kernel: md: unRAID driver 2.1.4 installed Nov 6 09:14:30 MediaNAS emhttp: ST2000DL003-9VT166_5YD6GLZ4 (sdf) 1953514584 Nov 6 09:14:30 MediaNAS emhttp: Hitachi_HDS723030ALA640_MK0331YHGWKPJA (sdg) 2930266584 Nov 6 09:14:30 MediaNAS kernel: mdcmd (1): import 0 8,96 2930266532 Hitachi_HDS723030ALA640_MK0331YHGWKPJA Nov 6 09:14:30 MediaNAS kernel: md: import disk0: [8,96] (sdg) Hitachi_HDS723030ALA640_MK0331YHGWKPJA size: 2930266532 Nov 6 09:14:30 MediaNAS kernel: mdcmd (2): import 1 8,48 2930266532 WDC_WD30EZRX-00MMMB0_WD-WCAWZ2214923 Nov 6 09:14:30 MediaNAS kernel: md: import disk1: [8,48] (sdd) WDC_WD30EZRX-00MMMB0_WD-WCAWZ2214923 size: 2930266532 Nov 6 09:14:30 MediaNAS kernel: mdcmd (3): import 2 8,80 1953514552 ST2000DL003-9VT166_5YD6GLZ4 Nov 6 09:14:30 MediaNAS kernel: md: import disk2: [8,80] (sdf) ST2000DL003-9VT166_5YD6GLZ4 size: 1953514552 Nov 6 09:14:30 MediaNAS kernel: mdcmd (4): import 3 8,0 1953514552 ST2000DL003-9VT166_6YD1Q84W Nov 6 09:14:30 MediaNAS kernel: md: import disk3: [8,0] (sda) ST2000DL003-9VT166_6YD1Q84W size: 1953514552 Nov 6 09:14:30 MediaNAS kernel: mdcmd (5): import 4 8,32 2930266532 WDC_WD30EFRX-68AX9N0_WD-WMC1T0529663 Nov 6 09:14:30 MediaNAS kernel: md: import disk4: [8,32] (sdc) WDC_WD30EFRX-68AX9N0_WD-WMC1T0529663 size: 2930266532 Nov 6 09:14:30 MediaNAS kernel: md: disk4 new disk Nov 6 09:14:30 MediaNAS kernel: mdcmd (6): import 5 8,64 2930266532 WDC_WD30EFRX-68AX9N0_WD-WMC1T0454239 Nov 6 09:14:30 MediaNAS kernel: md: import disk5: [8,64] (sde) WDC_WD30EFRX-68AX9N0_WD-WMC1T0454239 size: 2930266532 Nov 6 09:14:30 MediaNAS kernel: md: disk5 new disk Nov 6 09:14:30 MediaNAS emhttp: shcmd (747): /usr/local/sbin/emhttp_event driver_loaded Nov 6 09:14:30 MediaNAS emhttp_event: driver_loaded Nov 6 09:14:30 MediaNAS emhttp: shcmd (748): rmmod md-mod |& logger Nov 6 09:14:30 MediaNAS emhttp: shcmd (749): modprobe md-mod super=/boot/config/super.dat slots=6 |& logger Nov 6 09:14:30 MediaNAS kernel: md: unRAID driver removed Nov 6 09:14:30 MediaNAS emhttp: shcmd (750): udevadm settle Nov 6 09:14:30 MediaNAS emhttp: Device inventory: Nov 6 09:14:30 MediaNAS emhttp: ST2000DL003-9VT166_6YD1Q84W (sda) 1953514584 Nov 6 09:14:30 MediaNAS emhttp: Hitachi_HTS723232L9A360_090204FC1400NEGRASYC (sdb) 312571224 Nov 6 09:14:30 MediaNAS emhttp: WDC_WD30EFRX-68AX9N0_WD-WMC1T0529663 (sdc) 2930266584 Nov 6 09:14:30 MediaNAS emhttp: WDC_WD30EZRX-00MMMB0_WD-WCAWZ2214923 (sdd) 2930266584 Nov 6 09:14:30 MediaNAS emhttp: WDC_WD30EFRX-68AX9N0_WD-WMC1T0454239 (sde) 2930266584 Nov 6 09:14:30 MediaNAS emhttp: ST2000DL003-9VT166_5YD6GLZ4 (sdf) 1953514584 Nov 6 09:14:30 MediaNAS emhttp: Hitachi_HDS723030ALA640_MK0331YHGWKPJA (sdg) 2930266584 Nov 6 09:14:30 MediaNAS kernel: md: unRAID driver 2.1.4 installed Nov 6 09:14:30 MediaNAS kernel: mdcmd (1): import 0 8,96 2930266532 Hitachi_HDS723030ALA640_MK0331YHGWKPJA Nov 6 09:14:30 MediaNAS kernel: md: import disk0: [8,96] (sdg) Hitachi_HDS723030ALA640_MK0331YHGWKPJA size: 2930266532 Nov 6 09:14:30 MediaNAS kernel: mdcmd (2): import 1 8,48 2930266532 WDC_WD30EZRX-00MMMB0_WD-WCAWZ2214923 Nov 6 09:14:30 MediaNAS kernel: md: import disk1: [8,48] (sdd) WDC_WD30EZRX-00MMMB0_WD-WCAWZ2214923 size: 2930266532 Nov 6 09:14:30 MediaNAS kernel: mdcmd (3): import 2 8,80 1953514552 ST2000DL003-9VT166_5YD6GLZ4 Nov 6 09:14:30 MediaNAS kernel: md: import disk2: [8,80] (sdf) ST2000DL003-9VT166_5YD6GLZ4 size: 1953514552 Nov 6 09:14:30 MediaNAS kernel: mdcmd (4): import 3 8,0 1953514552 ST2000DL003-9VT166_6YD1Q84W Nov 6 09:14:30 MediaNAS kernel: md: import disk3: [8,0] (sda) ST2000DL003-9VT166_6YD1Q84W size: 1953514552 Nov 6 09:14:30 MediaNAS kernel: mdcmd (5): import 4 8,32 2930266532 WDC_WD30EFRX-68AX9N0_WD-WMC1T0529663 Nov 6 09:14:30 MediaNAS kernel: md: import disk4: [8,32] (sdc) WDC_WD30EFRX-68AX9N0_WD-WMC1T0529663 size: 2930266532 Nov 6 09:14:30 MediaNAS kernel: md: disk4 new disk Nov 6 09:14:30 MediaNAS kernel: mdcmd (6): import 5 8,64 2930266532 WDC_WD30EFRX-68AX9N0_WD-WMC1T0454239 Nov 6 09:14:30 MediaNAS kernel: md: import disk5: [8,64] (sde) WDC_WD30EFRX-68AX9N0_WD-WMC1T0454239 size: 2930266532 Nov 6 09:14:30 MediaNAS kernel: md: disk5 new disk Nov 6 09:14:30 MediaNAS emhttp: shcmd (751): /usr/local/sbin/emhttp_event driver_loaded Nov 6 09:14:30 MediaNAS emhttp_event: driver_loaded Nov 6 09:14:31 MediaNAS emhttp: shcmd (752): rmmod md-mod |& logger Nov 6 09:14:31 MediaNAS kernel: md: unRAID driver removed Nov 6 09:14:31 MediaNAS emhttp: shcmd (753): modprobe md-mod super=/boot/config/super.dat slots=6 |& logger Nov 6 09:14:31 MediaNAS emhttp: shcmd (754): udevadm settle Nov 6 09:14:31 MediaNAS kernel: md: unRAID driver 2.1.4 installed Nov 6 09:14:31 MediaNAS emhttp: Device inventory: Nov 6 09:14:31 MediaNAS emhttp: ST2000DL003-9VT166_6YD1Q84W (sda) 1953514584 Nov 6 09:14:31 MediaNAS emhttp: Hitachi_HTS723232L9A360_090204FC1400NEGRASYC (sdb) 312571224 Nov 6 09:14:31 MediaNAS emhttp: WDC_WD30EFRX-68AX9N0_WD-WMC1T0529663 (sdc) 2930266584 Nov 6 09:14:31 MediaNAS emhttp: WDC_WD30EZRX-00MMMB0_WD-WCAWZ2214923 (sdd) 2930266584 Nov 6 09:14:31 MediaNAS emhttp: WDC_WD30EFRX-68AX9N0_WD-WMC1T0454239 (sde) 2930266584 Nov 6 09:14:31 MediaNAS emhttp: ST2000DL003-9VT166_5YD6GLZ4 (sdf) 1953514584 Nov 6 09:14:31 MediaNAS emhttp: Hitachi_HDS723030ALA640_MK0331YHGWKPJA (sdg) 2930266584 Nov 6 09:14:31 MediaNAS kernel: mdcmd (1): import 0 8,96 2930266532 Hitachi_HDS723030ALA640_MK0331YHGWKPJA Nov 6 09:14:31 MediaNAS kernel: md: import disk0: [8,96] (sdg) Hitachi_HDS723030ALA640_MK0331YHGWKPJA size: 2930266532 Nov 6 09:14:31 MediaNAS kernel: mdcmd (2): import 1 8,48 2930266532 WDC_WD30EZRX-00MMMB0_WD-WCAWZ2214923 Nov 6 09:14:31 MediaNAS kernel: md: import disk1: [8,48] (sdd) WDC_WD30EZRX-00MMMB0_WD-WCAWZ2214923 size: 2930266532 Nov 6 09:14:31 MediaNAS kernel: mdcmd (3): import 2 8,80 1953514552 ST2000DL003-9VT166_5YD6GLZ4 Nov 6 09:14:31 MediaNAS kernel: md: import disk2: [8,80] (sdf) ST2000DL003-9VT166_5YD6GLZ4 size: 1953514552 Nov 6 09:14:31 MediaNAS kernel: mdcmd (4): import 3 8,0 1953514552 ST2000DL003-9VT166_6YD1Q84W Nov 6 09:14:31 MediaNAS kernel: md: import disk3: [8,0] (sda) ST2000DL003-9VT166_6YD1Q84W size: 1953514552 Nov 6 09:14:31 MediaNAS kernel: mdcmd (5): import 4 8,32 2930266532 WDC_WD30EFRX-68AX9N0_WD-WMC1T0529663 Nov 6 09:14:31 MediaNAS kernel: md: import disk4: [8,32] (sdc) WDC_WD30EFRX-68AX9N0_WD-WMC1T0529663 size: 2930266532 Nov 6 09:14:31 MediaNAS kernel: md: disk4 new disk Nov 6 09:14:31 MediaNAS kernel: mdcmd (6): import 5 8,64 2930266532 WDC_WD30EFRX-68AX9N0_WD-WMC1T0454239 Nov 6 09:14:31 MediaNAS kernel: md: import disk5: [8,64] (sde) WDC_WD30EFRX-68AX9N0_WD-WMC1T0454239 size: 2930266532 Nov 6 09:14:31 MediaNAS kernel: md: disk5 new disk Nov 6 09:14:31 MediaNAS emhttp: shcmd (755): /usr/local/sbin/emhttp_event driver_loaded Nov 6 09:14:31 MediaNAS emhttp_event: driver_loaded Quote Link to comment
Hoopster Posted November 7, 2012 Author Share Posted November 7, 2012 Hmmm, so no ideas on this one? Disable all plugins? It's really strange that the array won't start with these new precleared disks. I've never not been able to add/replace a disk in the array. Quote Link to comment
Frank1940 Posted November 7, 2012 Share Posted November 7, 2012 Hmmm, so no ideas on this one? Disable all plugins? It's really strange that the array won't start with these new precleared disks. I've never not been able to add/replace a disk in the array. When I upgraded a 1TB drive to a 3TB drive, I used the same procedure as you did. The process appeared to hang up for what seemed like forever. I was just about to panic when the array came up and everything was fine. The only thing I can think that was happening was that the disk had to be formatted and the base file system installed on it before the array could start. Quote Link to comment
bcbgboy13 Posted November 7, 2012 Share Posted November 7, 2012 Did you try one drive at a time? Quote Link to comment
Hoopster Posted November 7, 2012 Author Share Posted November 7, 2012 Did you try one drive at a time? Yep. One at a time makes no difference. Maybe it is just taking "forever" and I have not let it sit long enough to complete the process. Strange that it would take so long to add disks to the array, it's been very quick when I've done this with other drives. I've let it sit for up to 30 minutes and nothing happens. Quote Link to comment
Joe L. Posted November 7, 2012 Share Posted November 7, 2012 Did you try one drive at a time? Yep. One at a time makes no difference. Maybe it is just taking "forever" and I have not let it sit long enough to complete the process. Strange that it would take so long to add disks to the array, it's been very quick when I've done this with other drives. I've let it sit for up to 30 minutes and nothing happens. Did you pre-clear the drives you are adding? Quote Link to comment
Hoopster Posted November 7, 2012 Author Share Posted November 7, 2012 Did you try one drive at a time? Yep. One at a time makes no difference. Maybe it is just taking "forever" and I have not let it sit long enough to complete the process. Strange that it would take so long to add disks to the array, it's been very quick when I've done this with other drives. I've let it sit for up to 30 minutes and nothing happens. Did you pre-clear the drives you are adding? Yes, I did. Both passed preclear with no problems. Quote Link to comment
Joe L. Posted November 7, 2012 Share Posted November 7, 2012 Did you try one drive at a time? Yep. One at a time makes no difference. Maybe it is just taking "forever" and I have not let it sit long enough to complete the process. Strange that it would take so long to add disks to the array, it's been very quick when I've done this with other drives. I've let it sit for up to 30 minutes and nothing happens. Did you pre-clear the drives you are adding? Yes, I did. Both passed preclear with no problems. Do they still test as "precleared" preclear_disk.sh -t /dev/sdX (tests for a pre-clear signature, only takes a few seconds) The reason I ask is if the first attempt at using them wrote the the MBR they would now not be considered as pre-cleared, so unRAID will clear them. (and on a 2TB drive, that will take 5 or 6 hours or more, especially with two being cleared at the same time) Joe L. Quote Link to comment
Hoopster Posted November 7, 2012 Author Share Posted November 7, 2012 Did you try one drive at a time? Yep. One at a time makes no difference. Maybe it is just taking "forever" and I have not let it sit long enough to complete the process. Strange that it would take so long to add disks to the array, it's been very quick when I've done this with other drives. I've let it sit for up to 30 minutes and nothing happens. Did you pre-clear the drives you are adding? Yes, I did. Both passed preclear with no problems. Do they still test as "precleared" preclear_disk.sh -t /dev/sdX (tests for a pre-clear signature, only takes a few seconds) The reason I ask is if the first attempt at using them wrote the the MBR they would now not be considered as pre-cleared, so unRAID will clear them. (and on a 2TB drive, that will take 5 or 6 hours or more, especially with two being cleared at the same time) Joe L. I already started another preclear on both drives (took about 31 hours last time - they are both 3TB drives). A second preclear pass is not a bad idea on these large drives anyway. After this preclear cycle finishes, I will test preclear status as you suggest. BTW no format button appeared so I formatted them via unMenu Disk Management tab. Is that the proper procedure? Quote Link to comment
Frank1940 Posted November 7, 2012 Share Posted November 7, 2012 I already started another preclear on both drives (took about 31 hours last time - they are both 3TB drives). A second preclear pass is not a bad idea on these large drives anyway. After this preclear cycle finishes, I will test preclear status as you suggest. BTW no format button appeared so I formatted them via unMenu Disk Management tab. Is that the proper procedure? See the first post in this thread: http://lime-technology.com/forum/index.php?topic=2817.0 Quote Link to comment
Joe L. Posted November 7, 2012 Share Posted November 7, 2012 BTW no format button appeared so I formatted them via unMenu Disk Management tab. Is that the proper procedure? No, and in fact it completely negated the preclear. (in other words, the disk is no longer precleared, and if accidentally recognized as pre-cleared, will completely mess up any disk-re-construction. If not recognized, unRAID will clear it again, while you wait another 5 to 10 hours. During this time the array will be off-line and unusable. You NEVER EVER should format a disk outside of unRAID's web management screen if you are assigning it to an existing array. (I've occasionally regretted putting the format button in unMENU's screen) Quote Link to comment
Hoopster Posted November 7, 2012 Author Share Posted November 7, 2012 BTW no format button appeared so I formatted them via unMenu Disk Management tab. Is that the proper procedure? No, and in fact it completely negated the preclear. (in other words, the disk is no longer precleared, and if accidentally recognized as pre-cleared, will completely mess up any disk-re-construction. If not recognized, unRAID will clear it again, while you wait another 5 to 10 hours. During this time the array will be off-line and unusable. You NEVER EVER should format a disk outside of unRAID's web management screen if you are assigning it to an existing array. (I've occasionally regretted putting the format button in unMENU's screen) OK, thanks. That is certainly clear enough I only formatted in unMENU because I thought the drives needed to be formatted before being added and there was no format button in the main screen when I added them to the array. I'll certainly not make that mistake again. But, as I said, a second preclear pass is not a bad idea anyway. Quote Link to comment
Hoopster Posted November 9, 2012 Author Share Posted November 9, 2012 Did you try one drive at a time? Yep. One at a time makes no difference. Maybe it is just taking "forever" and I have not let it sit long enough to complete the process. Strange that it would take so long to add disks to the array, it's been very quick when I've done this with other drives. I've let it sit for up to 30 minutes and nothing happens. Did you pre-clear the drives you are adding? Yes, I did. Both passed preclear with no problems. Do they still test as "precleared" preclear_disk.sh -t /dev/sdX (tests for a pre-clear signature, only takes a few seconds) The reason I ask is if the first attempt at using them wrote the the MBR they would now not be considered as pre-cleared, so unRAID will clear them. (and on a 2TB drive, that will take 5 or 6 hours or more, especially with two being cleared at the same time) Joe L. OK, I just ran a second preclear pass on the drives. After completing preclear, I ran preclear_disk.sh -t /dev/sdX on each drive. Both reported they were precleared with a valid GPT. I stopped the array and added the disks to new slots that had previously been unassigned as I am expanding the array not replacing drives. I clicked "Yes, I want to do this" to enable the Start button. I clicked the Start button. So far nothing has happened (I have been waiting 15 minutes). The array remains at a status of "Stopped. Found 2 new disk(s)" Quote Link to comment
JonathanM Posted November 9, 2012 Share Posted November 9, 2012 Zip the current session's entire syslog in the state it's in now and attach it here. Quote Link to comment
Joe L. Posted November 9, 2012 Share Posted November 9, 2012 Did you try one drive at a time? Yep. One at a time makes no difference. Maybe it is just taking "forever" and I have not let it sit long enough to complete the process. Strange that it would take so long to add disks to the array, it's been very quick when I've done this with other drives. I've let it sit for up to 30 minutes and nothing happens. Did you pre-clear the drives you are adding? Yes, I did. Both passed preclear with no problems. Do they still test as "precleared" preclear_disk.sh -t /dev/sdX (tests for a pre-clear signature, only takes a few seconds) The reason I ask is if the first attempt at using them wrote the the MBR they would now not be considered as pre-cleared, so unRAID will clear them. (and on a 2TB drive, that will take 5 or 6 hours or more, especially with two being cleared at the same time) Joe L. OK, I just ran a second preclear pass on the drives. After completing preclear, I ran preclear_disk.sh -t /dev/sdX on each drive. Both reported they were precleared with a valid GPT. I stopped the array and added the disks to new slots that had previously been unassigned as I am expanding the array not replacing drives. I clicked "Yes, I want to do this" to enable the Start button. I clicked the Start button. So far nothing has happened (I have been waiting 15 minutes). The array remains at a status of "Stopped. Found 2 new disk(s)" Post a syslog while you wait. Joe L. Quote Link to comment
Hoopster Posted November 9, 2012 Author Share Posted November 9, 2012 Zip the current session's entire syslog in the state it's in now and attach it here. Zipped Syslog attached; sdc and sde are the two drives I am trying to to add - the 3TB WD30EFRX drives. When I unassign them, the array starts with no problem. The disks still show as precleared with a GPT protective MBR after attempting to add them to the array and then unassigning them when the array fails to start. Syslog.zip Quote Link to comment
Hoopster Posted November 9, 2012 Author Share Posted November 9, 2012 Just passed two hours; array is still stopped. I'll let it sit all night if nothing happens in a few hours, although, I don't expect anything will change. If anyone but me downloads the syslog (I downloaded to test attachment) and sees anything interesting, I'd be grateful for any light you can shed on this issue. The array simply refuses to start with the new precleared drives assigned. Quote Link to comment
dgaschk Posted November 9, 2012 Share Posted November 9, 2012 The beginning of the syslog is missing. Quote Link to comment
Influencer Posted November 9, 2012 Share Posted November 9, 2012 This is an absolute shot in the dark, but adding those two disks unraid will add them to its database, which I believe is the super.dat file you see mentioned in your first syslog excerpt. Verify that the super.dat has appropriate permissions to be written to. Edit: the super.dat file should be owned by root:root and have permissions of 777, or rwxrwxrwx Quote Link to comment
Hoopster Posted November 9, 2012 Author Share Posted November 9, 2012 This is an absolute shot in the dark, but adding those two disks unraid will add them to its database, which I believe is the super.dat file you see mentioned in your first syslog excerpt. Verify that the super.dat has appropriate permissions to be written to. Edit: the super.dat file should be owned by root:root and have permissions of 777, or rwxrwxrwx I did an ls -l on /boot/config and the permissions on super.dat are rwxrwxrwx and it is owned by root root. Quote Link to comment
Hoopster Posted November 9, 2012 Author Share Posted November 9, 2012 The beginning of the syslog is missing. The latest complete syslog.zip exceeds the 192 KB attachment limit - attached is part 1 Syslog_part_1.zip Quote Link to comment
Hoopster Posted November 9, 2012 Author Share Posted November 9, 2012 The beginning of the syslog is missing. Attached is the second half of the zipped syslog. Syslog_part_2.zip Quote Link to comment
Hoopster Posted November 9, 2012 Author Share Posted November 9, 2012 What exactly happens when disks are added to an array and the array is started? What files are modified, what processes are run, etc.? Maybe I should start troubleshooting the individual steps. As mentioned earlier, the appropriate permissions seem to exist on super.dat which needs to be modified with the new disk info. 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.