unRAID Server Release 5.0-beta12a Available

Joe L. · December 15, 2011

Hi,

Several weeks ago I moved from 4.7 to unRaid 12a. Shortly after I also moved onto a completely virtualised server using passthrough to access my disks from an LSI card.

I was about to replace my cache drive with a new SSD, and I suddenly discovered that most of my recent TV shows are still sitting on my cache disk. Looking in the logs, I discovered that my disk1 share, where all TV Shows had been copying until now, is full. Also the mover script has been failing for weeks due to the full disk.

It's been a while since I set up my user shares, so I had to quickly revise how things work in the wiki. I have checked the settings - it is set to a min free space of 5 GB and an allocation method of High Water, with split level set to 0, with no include or exclude disks. I tried manually creating a TVShows disk share on disk 2 (which has plenty of empty space) but when I run the mover script from the web GUI, it always appears to be trying to copy content to disk1 and fails. I've tried changing to "Most free" with no change, also added an include disk for "disk2" also with no luck.

I tried changing the min free space, but it won't "stick" when I apply the change. It always reverts to High water.

Syslog attached. Can anyone please help? I think the settings are correct, so I'm wondering if it is a beta issue?

Note I also checked the user permissions and ownsership on the new TVShows disk share on disk 2 that I created, and it looks the same as disk 1.

Thanks

No, it is a configuration error.

You must set the min-free-space on the user-share. (it is in kilobytes) It should be set to a value higher than the size of the largest file you will store on a disk.

You must set the split level to something other than 0 (0 indicates you will always manually create the directories needed on all the physical disks involved) You probably need something like 2 or higher.

You can leave the included disks, or excluded disks completely blank, but if you do use them, or change them, you will probably need to reboot to have them take effect.

Joe L.

AaronD · December 15, 2011

Thanks. I was just coming back to post that it must have been a configuration error. I found that if I set the split level to 99 (I don't care what it splits) then it started working.

Still not sure why it didn't work if I set it to 1 (I have a user share called TVShows and basically didn't care how it split it below this) but it's working which is the important thing.

Regards

pantner · February 9, 2012

phew, reading 24 pages takes a while!

looking at upgrading to this release, using my onbaord SATA, currently have an IBM BR10i (Rebranded LSI controller) and also have a M1015 (this is not installed yet).

From what i gather, this is the release to look at with LSI controllers and not the MV8 ones?

tr0910 · February 11, 2012

This may not be an unRaid issue but a brain freeze. On b12a just added a 3tb WD30EZRS drive after a successful preclear, and I didn't get a format option. In fact, unMenu shows status as

PROTECTED_EXPANSION, unRAID ARRAY is STOPPED 7 disks in array.    PARITY NOT VALID: DISK_NEW

When I try to restart the array after adding the new drive, and say yes, I want to do this, I get:

Spinning up all drives.......syncing

Then it just returns to the page listing all the empty disk slots in my pro server, and I have all other drives green balled, the new drive blue balled, and the server red-balled. If I give up, and unassign the new drive, and restart the array, every thing goes back to green-balled. Why am I not getting a format option?

Last few seconds from syslog below from when I tried to start the array with the new drive and full zipped syslog attached.


Feb 10 19:50:37 Server1 emhttp: shcmd (458): rmmod md-mod |$stuff$ logger (Other emhttp)
Feb 10 19:50:37 Server1 emhttp: shcmd (459): udevadm settle (Other emhttp)
Feb 10 19:50:37 Server1 emhttp: Device inventory: (Drive related)
Feb 10 19:50:37 Server1 emhttp: WDC_WD20EARS-00MVWB0_WD-WMAZA3919347 (sda) 1953514584 (Drive related)
Feb 10 19:50:37 Server1 emhttp: SAMSUNG_HD204UI_S2H7J90B713135 (sdc) 1953514584 (Drive related)
Feb 10 19:50:37 Server1 emhttp: Hitachi_HDS5C3030ALA630_MJ1313YNG28SGC (sdd) 2930266584 (Drive related)
Feb 10 19:50:37 Server1 emhttp: SAMSUNG_HD204UI_S2H7J1AZC09469 (sdb) 1953514584 (Drive related)
Feb 10 19:50:37 Server1 emhttp: WDC_WD30EZRS-00J99B0_WD-WCAWZ0361944 (sdf) 2930266584 (Drive related)
Feb 10 19:50:37 Server1 emhttp: SAMSUNG_HD204UI_S2H7J9JB706789 (sdg) 1953514584 (Drive related)
Feb 10 19:50:37 Server1 emhttp: Hitachi_HDS5C3030ALA630_MJ1313YNG290PC (sdh) 2930266584 (Drive related)
Feb 10 19:50:37 Server1 emhttp: shcmd (460): modprobe md-mod super=/boot/config/super.dat slots=21 |$stuff$ logger (unRAID engine)
Feb 10 19:50:37 Server1 kernel: md: unRAID driver removed (System)
Feb 10 19:50:37 Server1 kernel: md: unRAID driver 2.1.3 installed (System)
Feb 10 19:50:37 Server1 kernel: mdcmd (1): import 0 8,48 2930266532 Hitachi_HDS5C3030ALA630_MJ1313YNG28SGC (unRAID engine)
Feb 10 19:50:37 Server1 kernel: md: import disk0: [8,48] (sdd) Hitachi_HDS5C3030ALA630_MJ1313YNG28SGC size: 2930266532 (Drive related)
Feb 10 19:50:37 Server1 kernel: mdcmd (2): import 1 8,0 1953514552 WDC_WD20EARS-00MVWB0_WD-WMAZA3919347 (unRAID engine)
Feb 10 19:50:37 Server1 kernel: md: import disk1: [8,0] (sda) WDC_WD20EARS-00MVWB0_WD-WMAZA3919347 size: 1953514552 (Drive related)
Feb 10 19:50:37 Server1 kernel: mdcmd (3): import 2 8,16 1953514552 SAMSUNG_HD204UI_S2H7J1AZC09469 (unRAID engine)
Feb 10 19:50:37 Server1 kernel: md: import disk2: [8,16] (sdb) SAMSUNG_HD204UI_S2H7J1AZC09469 size: 1953514552 (Drive related)
Feb 10 19:50:37 Server1 kernel: mdcmd (4): import 3 8,32 1953514552 SAMSUNG_HD204UI_S2H7J90B713135 (unRAID engine)
Feb 10 19:50:37 Server1 kernel: md: import disk3: [8,32] (sdc) SAMSUNG_HD204UI_S2H7J90B713135 size: 1953514552 (Drive related)
Feb 10 19:50:37 Server1 emhttp: shcmd (461): /usr/local/sbin/emhttp_event driver_loaded (System)
Feb 10 19:50:37 Server1 emhttp_event: driver_loaded (System)
Feb 10 19:50:37 Server1 kernel: mdcmd (5): import 4 8,112 2930266532 Hitachi_HDS5C3030ALA630_MJ1313YNG290PC (unRAID engine)
Feb 10 19:50:37 Server1 kernel: md: import disk4: [8,112] (sdh) Hitachi_HDS5C3030ALA630_MJ1313YNG290PC size: 2930266532 (Drive related)
Feb 10 19:50:37 Server1 kernel: mdcmd (6): import 5 8,96 1953514552 SAMSUNG_HD204UI_S2H7J9JB706789 (unRAID engine)
Feb 10 19:50:37 Server1 kernel: md: import disk5: [8,96] (sdg) SAMSUNG_HD204UI_S2H7J9JB706789 size: 1953514552 (Drive related)
Feb 10 19:50:37 Server1 kernel: mdcmd (7): import 6 0,0 (unRAID engine)
Feb 10 19:50:37 Server1 kernel: mdcmd (: import 7 0,0 (unRAID engine)
Feb 10 19:50:37 Server1 kernel: mdcmd (9): import 8 0,0 (unRAID engine)
Feb 10 19:50:37 Server1 kernel: mdcmd (10): import 9 0,0 (unRAID engine)
Feb 10 19:50:37 Server1 kernel: mdcmd (11): import 10 0,0 (unRAID engine)
Feb 10 19:50:37 Server1 kernel: mdcmd (12): import 11 0,0 (unRAID engine)
Feb 10 19:50:37 Server1 kernel: mdcmd (13): import 12 0,0 (unRAID engine)
Feb 10 19:50:37 Server1 kernel: mdcmd (14): import 13 0,0 (unRAID engine)
Feb 10 19:50:37 Server1 kernel: mdcmd (15): import 14 0,0 (unRAID engine)
Feb 10 19:50:37 Server1 kernel: mdcmd (16): import 15 0,0 (unRAID engine)
Feb 10 19:50:37 Server1 kernel: mdcmd (17): import 16 0,0 (unRAID engine)
Feb 10 19:50:37 Server1 kernel: mdcmd (18): import 17 0,0 (unRAID engine)
Feb 10 19:50:37 Server1 kernel: mdcmd (19): import 18 0,0 (unRAID engine)
Feb 10 19:50:37 Server1 kernel: mdcmd (20): import 19 0,0 (unRAID engine)
Feb 10 19:50:37 Server1 kernel: mdcmd (21): import 20 8,80 2930266532 WDC_WD30EZRS-00J99B0_WD-WCAWZ0361944 (unRAID engine)
Feb 10 19:50:37 Server1 kernel: md: import disk20: [8,80] (sdf) WDC_WD30EZRS-00J99B0_WD-WCAWZ0361944 size: 2930266532 (Drive related)
Feb 10 19:50:37 Server1 kernel: md: disk20 new disk (unRAID engine)
Feb 10 19:50:49 Server1 emhttp: Spinning up all drives... (Other emhttp)
Feb 10 19:50:49 Server1 emhttp: shcmd (462): /usr/local/sbin/set_ncq sdd 1 $stuff$> /dev/null (Drive related)
Feb 10 19:50:49 Server1 emhttp: shcmd (463): /usr/local/sbin/set_ncq sda 1 $stuff$> /dev/null (Drive related)
Feb 10 19:50:49 Server1 emhttp: shcmd (464): /usr/local/sbin/set_ncq sdb 1 $stuff$> /dev/null (Drive related)
Feb 10 19:50:49 Server1 emhttp: shcmd (465): /usr/local/sbin/set_ncq sdc 1 $stuff$> /dev/null (Drive related)
Feb 10 19:50:49 Server1 kernel: mdcmd (22): set md_num_stripes 1280 (unRAID engine)
Feb 10 19:50:49 Server1 kernel: mdcmd (23): set md_write_limit 768 (unRAID engine)
Feb 10 19:50:49 Server1 kernel: mdcmd (24): set md_sync_window 384 (unRAID engine)
Feb 10 19:50:49 Server1 kernel: mdcmd (25): set spinup_group 0 0 (unRAID engine)
Feb 10 19:50:49 Server1 kernel: mdcmd (26): set spinup_group 1 0 (unRAID engine)
Feb 10 19:50:49 Server1 kernel: mdcmd (27): set spinup_group 2 0 (unRAID engine)
Feb 10 19:50:49 Server1 kernel: mdcmd (28): set spinup_group 3 0 (unRAID engine)
Feb 10 19:50:49 Server1 kernel: mdcmd (29): set spinup_group 4 0 (unRAID engine)
Feb 10 19:50:49 Server1 kernel: mdcmd (30): set spinup_group 5 0 (unRAID engine)
Feb 10 19:50:49 Server1 kernel: mdcmd (31): set spinup_group 20 0 (unRAID engine)
Feb 10 19:50:49 Server1 kernel: mdcmd (32): spinup 0 (Routine)
Feb 10 19:50:49 Server1 kernel: mdcmd (33): spinup 1 (Routine)
Feb 10 19:50:49 Server1 kernel: mdcmd (34): spinup 2 (Routine)
Feb 10 19:50:49 Server1 kernel: mdcmd (35): spinup 3 (Routine)
Feb 10 19:50:49 Server1 kernel: mdcmd (36): spinup 4 (Routine)
Feb 10 19:50:49 Server1 kernel: mdcmd (37): spinup 5 (Routine)
Feb 10 19:50:49 Server1 kernel: mdcmd (38): spinup 20 (Routine)
Feb 10 19:50:49 Server1 emhttp: shcmd (466): /usr/local/sbin/set_ncq sdh 1 $stuff$> /dev/null (Drive related)
Feb 10 19:50:49 Server1 emhttp: shcmd (467): /usr/local/sbin/set_ncq sdg 1 $stuff$> /dev/null (Drive related)
Feb 10 19:50:49 Server1 emhttp: shcmd (468): /usr/local/sbin/set_ncq sdf 1 $stuff$> /dev/null (Drive related)
Feb 10 19:50:49 Server1 emhttp: writing GPT on disk 20 (sdf) with partition 1 offset 64 (Drive related)
Feb 10 19:50:49 Server1 emhttp: shcmd (469): sgdisk -Z /dev/sdf $stuff$> /dev/null (Drive related)
Feb 10 19:50:49 Server1 emhttp: _shcmd: shcmd (469): exit status: 1 (Other emhttp)
Feb 10 19:50:49 Server1 emhttp: shcmd (470): sgdisk -o -a 64 -n 1:64:0 /dev/sdf |$stuff$ logger (Drive related)
Feb 10 19:50:49 Server1 logger: sgdisk: /usr/lib/libstdc++.so.6: version `GLIBCXX_3.4.11' not found (required by sgdisk) (System)
Feb 10 19:50:49 Server1 emhttp: shcmd (471): udevadm settle (Other emhttp)
Feb 10 19:50:49 Server1 emhttp: shcmd (472): rmmod md-mod |$stuff$ logger (Other emhttp)
Feb 10 19:50:49 Server1 emhttp: shcmd (473): udevadm settle (Other emhttp)
Feb 10 19:50:49 Server1 kernel: md: unRAID driver removed (System)
Feb 10 19:50:49 Server1 emhttp: Device inventory: (Drive related)
Feb 10 19:50:49 Server1 emhttp: WDC_WD20EARS-00MVWB0_WD-WMAZA3919347 (sda) 1953514584 (Drive related)
Feb 10 19:50:49 Server1 emhttp: SAMSUNG_HD204UI_S2H7J90B713135 (sdc) 1953514584 (Drive related)
Feb 10 19:50:49 Server1 emhttp: Hitachi_HDS5C3030ALA630_MJ1313YNG28SGC (sdd) 2930266584 (Drive related)
Feb 10 19:50:49 Server1 emhttp: SAMSUNG_HD204UI_S2H7J1AZC09469 (sdb) 1953514584 (Drive related)
Feb 10 19:50:49 Server1 emhttp: WDC_WD30EZRS-00J99B0_WD-WCAWZ0361944 (sdf) 2930266584 (Drive related)
Feb 10 19:50:49 Server1 emhttp: SAMSUNG_HD204UI_S2H7J9JB706789 (sdg) 1953514584 (Drive related)
Feb 10 19:50:49 Server1 emhttp: Hitachi_HDS5C3030ALA630_MJ1313YNG290PC (sdh) 2930266584 (Drive related)
Feb 10 19:50:49 Server1 emhttp: shcmd (474): modprobe md-mod super=/boot/config/super.dat slots=21 |$stuff$ logger (unRAID engine)
Feb 10 19:50:49 Server1 kernel: md: unRAID driver 2.1.3 installed (System)
Feb 10 19:50:49 Server1 kernel: mdcmd (1): import 0 8,48 2930266532 Hitachi_HDS5C3030ALA630_MJ1313YNG28SGC (unRAID engine)
Feb 10 19:50:49 Server1 kernel: md: import disk0: [8,48] (sdd) Hitachi_HDS5C3030ALA630_MJ1313YNG28SGC size: 2930266532 (Drive related)
Feb 10 19:50:49 Server1 kernel: mdcmd (2): import 1 8,0 1953514552 WDC_WD20EARS-00MVWB0_WD-WMAZA3919347 (unRAID engine)
Feb 10 19:50:49 Server1 kernel: md: import disk1: [8,0] (sda) WDC_WD20EARS-00MVWB0_WD-WMAZA3919347 size: 1953514552 (Drive related)
Feb 10 19:50:49 Server1 kernel: mdcmd (3): import 2 8,16 1953514552 SAMSUNG_HD204UI_S2H7J1AZC09469 (unRAID engine)
Feb 10 19:50:49 Server1 kernel: md: import disk2: [8,16] (sdb) SAMSUNG_HD204UI_S2H7J1AZC09469 size: 1953514552 (Drive related)
Feb 10 19:50:49 Server1 kernel: mdcmd (4): import 3 8,32 1953514552 SAMSUNG_HD204UI_S2H7J90B713135 (unRAID engine)
Feb 10 19:50:49 Server1 kernel: md: import disk3: [8,32] (sdc) SAMSUNG_HD204UI_S2H7J90B713135 size: 1953514552 (Drive related)
Feb 10 19:50:49 Server1 emhttp: shcmd (475): /usr/local/sbin/emhttp_event driver_loaded (System)
Feb 10 19:50:49 Server1 kernel: mdcmd (5): import 4 8,112 2930266532 Hitachi_HDS5C3030ALA630_MJ1313YNG290PC (unRAID engine)
Feb 10 19:50:49 Server1 kernel: md: import disk4: [8,112] (sdh) Hitachi_HDS5C3030ALA630_MJ1313YNG290PC size: 2930266532 (Drive related)
Feb 10 19:50:49 Server1 kernel: mdcmd (6): import 5 8,96 1953514552 SAMSUNG_HD204UI_S2H7J9JB706789 (unRAID engine)
Feb 10 19:50:49 Server1 kernel: md: import disk5: [8,96] (sdg) SAMSUNG_HD204UI_S2H7J9JB706789 size: 1953514552 (Drive related)
Feb 10 19:50:49 Server1 kernel: mdcmd (7): import 6 0,0 (unRAID engine)
Feb 10 19:50:49 Server1 kernel: mdcmd (: import 7 0,0 (unRAID engine)
Feb 10 19:50:49 Server1 kernel: mdcmd (9): import 8 0,0 (unRAID engine)
Feb 10 19:50:49 Server1 kernel: mdcmd (10): import 9 0,0 (unRAID engine)
Feb 10 19:50:49 Server1 kernel: mdcmd (11): import 10 0,0 (unRAID engine)
Feb 10 19:50:49 Server1 kernel: mdcmd (12): import 11 0,0 (unRAID engine)
Feb 10 19:50:49 Server1 kernel: mdcmd (13): import 12 0,0 (unRAID engine)
Feb 10 19:50:49 Server1 kernel: mdcmd (14): import 13 0,0 (unRAID engine)
Feb 10 19:50:49 Server1 kernel: mdcmd (15): import 14 0,0 (unRAID engine)
Feb 10 19:50:49 Server1 kernel: mdcmd (16): import 15 0,0 (unRAID engine)
Feb 10 19:50:49 Server1 kernel: mdcmd (17): import 16 0,0 (unRAID engine)
Feb 10 19:50:49 Server1 kernel: mdcmd (18): import 17 0,0 (unRAID engine)
Feb 10 19:50:49 Server1 kernel: mdcmd (19): import 18 0,0 (unRAID engine)
Feb 10 19:50:49 Server1 kernel: mdcmd (20): import 19 0,0 (unRAID engine)
Feb 10 19:50:49 Server1 kernel: mdcmd (21): import 20 8,80 2930266532 WDC_WD30EZRS-00J99B0_WD-WCAWZ0361944 (unRAID engine)
Feb 10 19:50:49 Server1 kernel: md: import disk20: [8,80] (sdf) WDC_WD30EZRS-00J99B0_WD-WCAWZ0361944 size: 2930266532 (Drive related)
Feb 10 19:50:49 Server1 kernel: md: disk20 new disk (unRAID engine)
Feb 10 19:50:49 Server1 emhttp_event: driver_loaded (System)
Feb 10 19:52:20 Server1 emhttp: shcmd (476): rmmod md-mod |$stuff$ logger (Other emhttp)
Feb 10 19:52:20 Server1 emhttp: shcmd (477): udevadm settle (Other emhttp)
Feb 10 19:52:20 Server1 emhttp: Device inventory: (Drive related)
Feb 10 19:52:20 Server1 emhttp: WDC_WD20EARS-00MVWB0_WD-WMAZA3919347 (sda) 1953514584 (Drive related)
Feb 10 19:52:20 Server1 emhttp: SAMSUNG_HD204UI_S2H7J90B713135 (sdc) 1953514584 (Drive related)
Feb 10 19:52:20 Server1 emhttp: Hitachi_HDS5C3030ALA630_MJ1313YNG28SGC (sdd) 2930266584 (Drive related)
Feb 10 19:52:20 Server1 emhttp: SAMSUNG_HD204UI_S2H7J1AZC09469 (sdb) 1953514584 (Drive related)
Feb 10 19:52:20 Server1 emhttp: WDC_WD30EZRS-00J99B0_WD-WCAWZ0361944 (sdf) 2930266584 (Drive related)
Feb 10 19:52:20 Server1 emhttp: SAMSUNG_HD204UI_S2H7J9JB706789 (sdg) 1953514584 (Drive related)
Feb 10 19:52:20 Server1 emhttp: Hitachi_HDS5C3030ALA630_MJ1313YNG290PC (sdh) 2930266584 (Drive related)
Feb 10 19:52:20 Server1 emhttp: shcmd (478): modprobe md-mod super=/boot/config/super.dat slots=21 |$stuff$ logger (unRAID engine)
Feb 10 19:52:20 Server1 kernel: md: unRAID driver removed (System)
Feb 10 19:52:20 Server1 kernel: md: unRAID driver 2.1.3 installed (System)
Feb 10 19:52:20 Server1 kernel: mdcmd (1): import 0 8,48 2930266532 Hitachi_HDS5C3030ALA630_MJ1313YNG28SGC (unRAID engine)
Feb 10 19:52:20 Server1 kernel: md: import disk0: [8,48] (sdd) Hitachi_HDS5C3030ALA630_MJ1313YNG28SGC size: 2930266532 (Drive related)
Feb 10 19:52:20 Server1 kernel: mdcmd (2): import 1 8,0 1953514552 WDC_WD20EARS-00MVWB0_WD-WMAZA3919347 (unRAID engine)
Feb 10 19:52:20 Server1 kernel: md: import disk1: [8,0] (sda) WDC_WD20EARS-00MVWB0_WD-WMAZA3919347 size: 1953514552 (Drive related)
Feb 10 19:52:20 Server1 kernel: mdcmd (3): import 2 8,16 1953514552 SAMSUNG_HD204UI_S2H7J1AZC09469 (unRAID engine)
Feb 10 19:52:20 Server1 kernel: md: import disk2: [8,16] (sdb) SAMSUNG_HD204UI_S2H7J1AZC09469 size: 1953514552 (Drive related)
Feb 10 19:52:20 Server1 kernel: mdcmd (4): import 3 8,32 1953514552 SAMSUNG_HD204UI_S2H7J90B713135 (unRAID engine)
Feb 10 19:52:20 Server1 kernel: md: import disk3: [8,32] (sdc) SAMSUNG_HD204UI_S2H7J90B713135 size: 1953514552 (Drive related)
Feb 10 19:52:20 Server1 emhttp: shcmd (479): /usr/local/sbin/emhttp_event driver_loaded (System)
Feb 10 19:52:20 Server1 emhttp_event: driver_loaded (System)
Feb 10 19:52:20 Server1 kernel: mdcmd (5): import 4 8,112 2930266532 Hitachi_HDS5C3030ALA630_MJ1313YNG290PC (unRAID engine)
Feb 10 19:52:20 Server1 kernel: md: import disk4: [8,112] (sdh) Hitachi_HDS5C3030ALA630_MJ1313YNG290PC size: 2930266532 (Drive related)
Feb 10 19:52:20 Server1 kernel: mdcmd (6): import 5 8,96 1953514552 SAMSUNG_HD204UI_S2H7J9JB706789 (unRAID engine)
Feb 10 19:52:20 Server1 kernel: md: import disk5: [8,96] (sdg) SAMSUNG_HD204UI_S2H7J9JB706789 size: 1953514552 (Drive related)
Feb 10 19:52:20 Server1 kernel: mdcmd (7): import 6 0,0 (unRAID engine)
Feb 10 19:52:20 Server1 kernel: mdcmd (: import 7 0,0 (unRAID engine)
Feb 10 19:52:20 Server1 kernel: mdcmd (9): import 8 0,0 (unRAID engine)
Feb 10 19:52:20 Server1 kernel: mdcmd (10): import 9 0,0 (unRAID engine)
Feb 10 19:52:20 Server1 kernel: mdcmd (11): import 10 0,0 (unRAID engine)
Feb 10 19:52:20 Server1 kernel: mdcmd (12): import 11 0,0 (unRAID engine)
Feb 10 19:52:20 Server1 kernel: mdcmd (13): import 12 0,0 (unRAID engine)
Feb 10 19:52:20 Server1 kernel: mdcmd (14): import 13 0,0 (unRAID engine)
Feb 10 19:52:20 Server1 kernel: mdcmd (15): import 14 0,0 (unRAID engine)
Feb 10 19:52:20 Server1 kernel: mdcmd (16): import 15 0,0 (unRAID engine)
Feb 10 19:52:20 Server1 kernel: mdcmd (17): import 16 0,0 (unRAID engine)
Feb 10 19:52:20 Server1 kernel: mdcmd (18): import 17 0,0 (unRAID engine)
Feb 10 19:52:20 Server1 kernel: mdcmd (19): import 18 0,0 (unRAID engine)
Feb 10 19:52:20 Server1 kernel: mdcmd (20): import 19 0,0 (unRAID engine)
Feb 10 19:52:20 Server1 kernel: mdcmd (21): import 20 0,0 (unRAID engine)

Have been running b12a on this machine since it was released and have had zero issues.

Supermicro X9SCM-F

Intel i3-2100 and 4 gig RAM

Supermicro AOC-SASLP-MV8 8-Port (only 1)

Norco 4224

mix of 3tb and 2tb drives

syslog-2012-02-10.zip

Joe L. · February 11, 2012

parity disk is never "formatted"

Are you adding a parity drive? or a data drive?

tr0910 · February 11, 2012

Data drive. I tried both drive6 and drive20

Server has drives 1-5, and I wanted this one to be 20.

jbartlett · February 12, 2012

On a side note, I can say that you can skip a slot of slots and assign drive 20. I've got 1-8 & added a SDD drive in slot #20 to hold non-movie media such as nfo files & cover images.

Joe L. · February 12, 2012

Data drive. I tried both drive6 and drive20

Server has drives 1-5, and I wanted this one to be 20.

I've got no idea then... perhaps it is an issue with beta12.

Joe L.

tr0910 · February 13, 2012

Updating to b14 didn't help anything. The only way I was able to add this disk as drive 20 was to comment out the line:

# cd /boot/packages && find . -name '*.auto_install' -type f -print | sort | xargs -n1 sh -c

that loads all my other goodies. Somehow one of these were interfering with the adding an extra disk, and interfering with allowing the format button to show up.

Wierd.....

Joe L. · February 13, 2012

Updating to b14 didn't help anything. The only way I was able to add this disk as drive 20 was to comment out the line:

# cd /boot/packages && find . -name '*.auto_install' -type f -print | sort | xargs -n1 sh -c

that loads all my other goodies. Somehow one of these were interfering with the adding an extra disk, and interfering with allowing the format button to show up.

Wierd.....

Time to rename the .auto_install lines in /boot/packages temporarily, to determine which one is causing your issue.

and let the remaining ones install by putting the line back in the "go" script.

Perhaps one of the added packages is attempting to access a disk when the array is stopped.

Joe L.

rsokoloff · February 13, 2012

I have been running 4.7 without difficulty for over a month and decided to upgrade to 5.0 so I could run Plex.

Following the upgrade instructions was uneventful and unRAID booted successfully; however, I am unable to find unRAID on my network. http://tower does not work nor does http://192.168.2.117 (its previous address). From unRAID I can not ping out and I can not ping unRAID. If I reinstall 4.7 everything is fine.

I started with 5.0b14 and then tried 5.0b8. Reformatting the flash drive results in the same outcome.

My syslog is attached. It seems to show that 192.168.2.117 is being used.

Could this be a NIC card issue?

Any advice would be greatly appreciated.

thanks,

ron

syslog.txt

Joe L. · February 14, 2012

The way it kept re-negotiating the speed, it might be a driver issue, or a cabling issue.

I've never seen anything like it in a syslog.

Is there more than one NIC in that server? (Initially I thought the later releases might supporting the NIC not supported in 4.7, and you were just plugged in the other LAN connector)

Joe L.

rsokoloff · February 14, 2012

Hi Joe,

Thanks for your advice.

I misspoke when I said NIC "card". The NIC is on the motherboard. I have a video card and a SATA port card but otherwise the machine is stock.

The way it kept re-negotiating the speed, it might be a driver issue, or a cabling issue. (Initially I thought the later releases might supporting the NIC not supported in 4.7, and you were just plugged in the other LAN connector)

How likely is it that 4.7 has a NIC driver not present in 5.0? Should I try a NIC card?

What sort of cabling issue are you thinking of since the machine is running fine with 4.7? I am using a crossover cable from the NIC but that has never been a problem before. I'll try swapping it with a regular cable.

thanks again,

ron

rsokoloff · February 14, 2012

Well swapping out the cable was not the answer.

Attempting to ping from the machine results in:

Connect: Network is unreachable.

I appreciate any advice regarding what I should try next.

thanks,

ron

kaiguy · February 14, 2012

Do you have an extra network card laying around? If not, it may not be a bad $20-25 test to go grab an Intel NIC and throw it in to see if that solves your problem.

pantner · February 14, 2012

Do you know what card your motherboard actually has?

Looking through the syslog it seems to mention the e100: Intel® PRO/100 Network Drive, e1000: Intel® PRO/1000 Network Driver and Broadcom NetXtreme II CNIC Driver.

If i read it right, the driver being used is the e1000, which may not be correct, the driver is crapping out and dropping the sync/link. Then it reconnects, renews it's IP Addy and changes the MTU.

I'm not 100% sure of the commands, but i've seen them around. I would try unloading those drivers that have loaded and just loading the one for your NIC

rsokoloff · February 14, 2012

Do you have an extra network card laying around? If not, it may not be a bad $20-25 test to go grab an Intel NIC and throw it in to see if that solves your problem.

That sounds good. Is there any concern that there will be a conflict from having two NIC's (see post from Joe L above)?

Do you know what card your motherboard actually has?

Looking through the syslog it seems to mention the e100: Intel® PRO/100 Network Drive, e1000: Intel® PRO/1000 Network Driver and Broadcom NetXtreme II CNIC Driver.

The recommended driver (from the dell website) is the Intel PRO/1000 Network Drivers http://support.dell.com/support/downloads/type.aspx?c=us&cs=19&l=en&s=dhs&SystemID=WRK_PNT_P4_360&category=5&os=WW1&osl=en&deviceid=4159&devlib=5Intel.

It gets fairly complicated as there are numerous drivers to choose from http://www.dell.com/support/drivers/us/en/19?c=us&l=en&s=dhs&~ck=anavml. These are not Linux drivers and I only point them out to try and figure out what NIC is on the MB.

I'm not 100% sure of the commands, but i've seen them around. I would try unloading those drivers that have loaded and just loading the one for your NIC

I like this idea but have no idea how to implement it.

ron

rsokoloff · February 15, 2012

I took the advice of kaiguy and put a NIC card into one of the PCI slots (Linksys/Cisco EG1032) and started the computer using 4.7. No problems.

I then put 5.0 on the flash and restarted. It appeared to boot normally but no network connection was made.

Here is the syslog from this boot. Hopefully comparing it with the earlier syslog will help someone figure out where I need to go from here.

ron

syslog.txt

pantner · February 15, 2012

I took the advice of kaiguy and put a NIC card into one of the PCI slots (Linksys/Cisco EG1032) and started the computer using 4.7. No problems.

I then put 5.0 on the flash and restarted. It appeared to boot normally but no network connection was made.

Here is the syslog from this boot. Hopefully comparing it with the earlier syslog will help someone figure out where I need to go from here.

ron

So, the new card appears to have a Realtek Chipset? (R8169?)

I'm not sure about the status of those cards, the 8168 and 8169 chipsets did have major issues with version 5 of UnRaid.

I can't even see the card negotiate a link speed.

I really don't understand enough about this to know what else to do im afraid

rsokoloff · February 15, 2012

Yep, I did some searching and the Realtek 8168/8169 chipsets are definite problems.

Intel chipsets are supposed to be fine. However, my MB NIC uses the Intel 8254 chipset so I suspect that not all Intel chipsets work.

Can somebody give me a PCI (not PCI-e) NIC model number known to work with 5.0?

ron

marcusone · February 15, 2012

Yep, I did some searching and the Realtek 8168/8169 chipsets are definite problems.

Intel chipsets are supposed to be fine. However, my MB NIC uses the Intel 8254 chipset so I suspect that not all Intel chipsets work.

Can somebody give me a PCI (not PCI-e) NIC model number known to work with 5.0?

ron

I've got these in one of my test machines that seems to work fine: NTEL 8390MT 1000 MT Gigabit Desktop PCI Network Card

get them off eBay for $10'ish

EDIT: I double checked the chipset of those, and they are the 82541GI - what is the ending number on your 8254?

as I've not had any issues with this card...or perhaps your motherboard one is dead, cable issue, or switch issue?

rsokoloff · February 15, 2012

Per Dell the MB NIC is Intel 8254OEM. And it is fine with 4.7.

Are you running 5.0 on your test machine?

ron

marcusone · February 16, 2012

Per Dell the MB NIC is Intel 8254OEM. And it is fine with 4.7.

Are you running 5.0 on your test machine?

ron

Beta 12a for the most part. but just did a test with Beta 14 and got full line speed on a 1GB file transfer.

rsokoloff · February 16, 2012

Thanks. That is the first evidence I have received that the Intel 8254 chipset works with 5.0. I have that card on order.

Optimally, however, I would like to get the MB NIC working with 5.0. I have my fingers crossed that someone with Linux knowledge can explain how to evaluate which driver loaded for my NIC and how I replace it with the correct driver.

I have tried this website http://www.basicconfig.com/ to learn some basic Linux but many of the things they suggest:

/etc/modprobe.d/modprobe.conf

and netconfig are not available on unRAID.

My problem is that I am not getting an IP address. Using ifconfig and route examples (not captures of my unRAID):

root@slackware:~# ifconfig
eth0 Link encap:Ethernet HWaddr 00:aa:11:bb:22:cc

inet addr:10.10.0.6 Bcast:10.21.35.255 Mask:255.255.0.0

UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1

RX packets:0 errors:0 dropped:0 overruns:0 frame:0

TX packets:0 errors:0 dropped:0 overruns:0 carrier:0

collisions:0 txqueuelen:1000

RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

Interrupt:11 Base address:0x1080

lo Link encap:Local Loopback

inet addr:127.0.0.1 Mask:255.0.0.0

UP LOOPBACK RUNNING MTU:16436 Metric:1

RX packets:0 errors:0 dropped:0 overruns:0 frame:0

TX packets:0 errors:0 dropped:0 overruns:0 carrier:0

collisions:0 txqueuelen:0

RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

root@slackware:~# route
Kernel IP routing table

Destination Gateway Genmask Flags Metric Ref Use Iface

192.168.1.0 * 255.255.255.0 U 0 0 0 eth0

loopback * 255.0.0.0 U 0 0 0 lo

default 192.168.1.1 0.0.0.0 UG 1 0 0 eth0

root@slackware:~#

the lines in red do not appear.

I tried this example

root@slackware:~# ifconfig eth0 192.168.1.5 netmask 255.255.255.0 up

without success.

Please, anybody with knowledge of NIC card driver installation, I would love a hint about where to go from here. :'(

ron

Joe L. · February 17, 2012

lsmod

will show you the loaded modules

rmmod

will unload (remove) a loaded module

insmod module_name

will load a module

unRAID Server Release 5.0-beta12a Available

Recommended Posts

Link to comment

Top Posters In This Topic

Popular Days

Top Posters In This Topic

Popular Days

Posted Images

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Join the conversation