johnny121b Posted October 15, 2011 Posted October 15, 2011 Update: It seems my concern was premature. I copied about 10Gb into the array last night, and the system utilized drive #5 for the first time. I've watched the other 4 drives alternately fill over time. None of them ever seemed to sit idle for quite this long. It seems every time I think I have those distribution choices figured out, it does something that seems random to me. Anyways, please disregard my call for help- seems there was nothing to see here. I added a 5th drive to my array about a month ago. It shows up as green in main menu, but no files have ever been written to it. I didn't think much of it because the other drives weren't nearly full. Well, they're approaching full- and still nothing's being written to this drive. Looking in the syslog file, I see some errors listed, but don't know what they mean. Any help appreciated. (A clip of the log is below) Aug 31 22:47:35 Tower kernel: md: import disk5: [8,80] (sdf) Hitachi_HDS5C3020ALA632_ML2220F30Z3MPE size: 1953514552 Aug 31 22:47:35 Tower kernel: md: disk5 new disk Aug 31 22:47:35 Tower kernel: mdcmd (7): import 6 0,0 Aug 31 22:47:35 Tower kernel: mdcmd (: import 7 0,0 Aug 31 22:47:35 Tower kernel: mdcmd (9): import 8 0,0 Aug 31 22:47:35 Tower kernel: mdcmd (10): import 9 0,0 Aug 31 22:47:35 Tower kernel: mdcmd (11): import 10 0,0 Aug 31 22:47:35 Tower kernel: mdcmd (12): import 11 0,0 Aug 31 22:47:35 Tower kernel: mdcmd (13): import 12 0,0 Aug 31 22:47:35 Tower kernel: mdcmd (14): import 13 0,0 Aug 31 22:47:35 Tower kernel: mdcmd (15): import 14 0,0 Aug 31 22:47:35 Tower kernel: mdcmd (16): import 15 0,0 Aug 31 22:47:35 Tower kernel: mdcmd (17): import 16 0,0 Aug 31 22:47:35 Tower kernel: mdcmd (18): import 17 0,0 Aug 31 22:47:35 Tower kernel: mdcmd (19): import 18 0,0 Aug 31 22:47:35 Tower kernel: mdcmd (20): import 19 0,0 Aug 31 22:47:35 Tower kernel: mdcmd (21): import 20 0,0 Aug 31 22:47:35 Tower emhttp: shcmd (225): /usr/local/sbin/emhttp_event driver_loaded Aug 31 22:47:35 Tower emhttp_event: driver_loaded Aug 31 22:47:58 Tower emhttp: Spinning up all drives... Aug 31 22:47:58 Tower emhttp: shcmd (226): /usr/local/sbin/set_ncq sda 1 &> /dev/null Aug 31 22:47:58 Tower emhttp: shcmd (227): /usr/local/sbin/set_ncq sdb 1 &> /dev/null Aug 31 22:47:58 Tower emhttp: shcmd (228): /usr/local/sbin/set_ncq sdc 1 &> /dev/null Aug 31 22:47:58 Tower emhttp: shcmd (229): /usr/local/sbin/set_ncq sdd 1 &> /dev/null Aug 31 22:47:58 Tower kernel: mdcmd (22): set md_num_stripes 1280 Aug 31 22:47:58 Tower kernel: mdcmd (23): set md_write_limit 768 Aug 31 22:47:58 Tower kernel: mdcmd (24): set md_sync_window 288 Aug 31 22:47:58 Tower kernel: mdcmd (25): set spinup_group 0 0 Aug 31 22:47:58 Tower kernel: mdcmd (26): set spinup_group 1 0 Aug 31 22:47:58 Tower kernel: mdcmd (27): set spinup_group 2 0 Aug 31 22:47:58 Tower kernel: mdcmd (28): set spinup_group 3 0 Aug 31 22:47:58 Tower kernel: mdcmd (29): set spinup_group 4 0 Aug 31 22:47:58 Tower kernel: mdcmd (30): set spinup_group 5 0 Aug 31 22:47:58 Tower kernel: mdcmd (31): spinup 0 Aug 31 22:47:58 Tower kernel: mdcmd (32): spinup 1 Aug 31 22:47:58 Tower kernel: mdcmd (33): spinup 2 Aug 31 22:47:58 Tower kernel: mdcmd (34): spinup 3 Aug 31 22:47:58 Tower kernel: mdcmd (35): spinup 4 Aug 31 22:47:58 Tower kernel: mdcmd (36): spinup 5 Aug 31 22:47:58 Tower emhttp: shcmd (230): /usr/local/sbin/set_ncq sde 1 &> /dev/null Aug 31 22:47:58 Tower emhttp: shcmd (231): /usr/local/sbin/set_ncq sdf 1 &> /dev/null Aug 31 22:47:58 Tower emhttp: writing MBR on disk 5 (sdf) with partition 1 offset 64 Aug 31 22:47:58 Tower emhttp: re-reading (sdf) partition table Aug 31 22:47:58 Tower emhttp: shcmd (232): udevadm settle Aug 31 22:47:58 Tower kernel: sdf: sdf1 Aug 31 22:47:58 Tower emhttp: clearing disk5*... Aug 31 22:47:58 Tower emhttp: Start array... Aug 31 22:47:58 Tower kernel: mdcmd (37): start PROTECTED_EXPANSION Aug 31 22:47:58 Tower kernel: unraid: allocating 33720K for 1280 stripes (6 disks) Aug 31 22:47:58 Tower kernel: md1: running, size: 1953514552 blocks Aug 31 22:47:58 Tower kernel: md2: running, size: 1953514552 blocks Aug 31 22:47:58 Tower kernel: md3: running, size: 1953514552 blocks Aug 31 22:47:58 Tower kernel: md4: running, size: 1953514552 blocks Aug 31 22:47:58 Tower kernel: md5: running, size: 1953514552 blocks Aug 31 22:47:59 Tower emhttp: shcmd (233): udevadm settle Aug 31 22:47:59 Tower emhttp: shcmd (234): /usr/local/sbin/emhttp_event array_started Aug 31 22:47:59 Tower emhttp_event: array_started Aug 31 22:47:59 Tower emhttp: Mounting disks... Aug 31 22:47:59 Tower emhttp: shcmd (235): mkdir /mnt/disk5 Aug 31 22:47:59 Tower emhttp: shcmd (236): mkdir /mnt/disk4 Aug 31 22:47:59 Tower emhttp: shcmd (237): mkdir /mnt/disk3 Aug 31 22:47:59 Tower emhttp: shcmd (238): mkdir /mnt/disk2 Aug 31 22:47:59 Tower emhttp: shcmd (239): set -o pipefail ; mount -t reiserfs -o acl,user_xattr,noatime,nodiratime /dev/md4 /mnt/disk4 |& logger Aug 31 22:47:59 Tower emhttp: shcmd (240): set -o pipefail ; mount -t reiserfs -o acl,user_xattr,noatime,nodiratime /dev/md5 /mnt/disk5 |& logger Aug 31 22:47:59 Tower kernel: mdcmd (38): check CORRECT Aug 31 22:47:59 Tower kernel: md: recovery thread woken up ... Aug 31 22:47:59 Tower emhttp: shcmd (241): set -o pipefail ; mount -t reiserfs -o acl,user_xattr,noatime,nodiratime /dev/md3 /mnt/disk3 |& logger Aug 31 22:47:59 Tower emhttp: shcmd (242): mkdir /mnt/disk1 Aug 31 22:47:59 Tower emhttp: shcmd (243): set -o pipefail ; mount -t reiserfs -o acl,user_xattr,noatime,nodiratime /dev/md2 /mnt/disk2 |& logger Aug 31 22:47:59 Tower emhttp: shcmd (244): set -o pipefail ; mount -t reiserfs -o acl,user_xattr,noatime,nodiratime /dev/md1 /mnt/disk1 |& logger Aug 31 22:47:59 Tower kernel: md: recovery thread has nothing to resync Aug 31 22:47:59 Tower kernel: REISERFS (device md4): found reiserfs format "3.6" with standard journal Aug 31 22:47:59 Tower kernel: REISERFS (device md4): using ordered data mode Aug 31 22:47:59 Tower kernel: REISERFS (device md4): journal params: device md4, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30 Aug 31 22:47:59 Tower kernel: REISERFS (device md4): checking transaction log (md4) Aug 31 22:47:59 Tower kernel: REISERFS (device md3): found reiserfs format "3.6" with standard journal Aug 31 22:47:59 Tower kernel: REISERFS (device md3): using ordered data mode Aug 31 22:47:59 Tower kernel: REISERFS (device md3): journal params: device md3, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30 Aug 31 22:47:59 Tower kernel: REISERFS (device md3): checking transaction log (md3) Aug 31 22:47:59 Tower kernel: REISERFS (device md2): found reiserfs format "3.6" with standard journal Aug 31 22:47:59 Tower kernel: REISERFS (device md2): using ordered data mode Aug 31 22:47:59 Tower kernel: REISERFS (device md2): journal params: device md2, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30 Aug 31 22:47:59 Tower kernel: REISERFS (device md2): checking transaction log (md2) Aug 31 22:47:59 Tower kernel: REISERFS warning (device md5): sh-2021 reiserfs_fill_super: can not find reiserfs on md5 Aug 31 22:47:59 Tower kernel: REISERFS (device md1): found reiserfs format "3.6" with standard journal Aug 31 22:47:59 Tower kernel: REISERFS (device md1): using ordered data mode Aug 31 22:47:59 Tower logger: mount: wrong fs type, bad option, bad superblock on /dev/md5, Aug 31 22:47:59 Tower logger: missing codepage or helper program, or other error Aug 31 22:47:59 Tower logger: In some cases useful info is found in syslog - try Aug 31 22:47:59 Tower logger: dmesg | tail or so Aug 31 22:47:59 Tower logger: Aug 31 22:47:59 Tower emhttp: _shcmd: shcmd (240): exit status: 32 Aug 31 22:47:59 Tower emhttp: disk5 mount error: 32 Aug 31 22:47:59 Tower emhttp: shcmd (245): rmdir /mnt/disk5 Aug 31 22:47:59 Tower kernel: REISERFS (device md1): journal params: device md1, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30 Aug 31 22:47:59 Tower kernel: REISERFS (device md1): checking transaction log (md1) Aug 31 22:47:59 Tower kernel: REISERFS (device md2): Using r5 hash to sort names Aug 31 22:47:59 Tower kernel: REISERFS (device md4): Using r5 hash to sort names Aug 31 22:47:59 Tower kernel: REISERFS (device md3): Using r5 hash to sort names Aug 31 22:47:59 Tower kernel: REISERFS (device md1): Using r5 hash to sort names Aug 31 22:47:59 Tower emhttp: shcmd (246): chmod 770 '/mnt/disk2' Aug 31 22:47:59 Tower emhttp: shcmd (247): chown nobody:users '/mnt/disk2' Aug 31 22:48:00 Tower emhttp: shcmd (248): chmod 770 '/mnt/disk3' Aug 31 22:48:00 Tower emhttp: shcmd (249): chmod 770 '/mnt/disk4' Aug 31 22:48:00 Tower emhttp: shcmd (250): chown nobody:users '/mnt/disk3' Aug 31 22:48:00 Tower emhttp: shcmd (251): chown nobody:users '/mnt/disk4' Aug 31 22:48:00 Tower emhttp: shcmd (252): chmod 770 '/mnt/disk1' Aug 31 22:48:00 Tower emhttp: shcmd (253): chown nobody:users '/mnt/disk1' Aug 31 22:48:00 Tower emhttp: shcmd (254): mkdir /mnt/user Aug 31 22:48:00 Tower emhttp: shcmd (255): /usr/local/sbin/shfs /mnt/user -disks 30 -o noatime,big_writes,allow_other,default_permissions,use_ino Aug 31 22:48:00 Tower emhttp: shcmd (256): /usr/local/sbin/emhttp_event disks_mounted Aug 31 22:48:00 Tower emhttp_event: disks_mounted Aug 31 22:48:00 Tower emhttp: shcmd (257): :>/etc/samba/smb-shares.conf Aug 31 22:48:00 Tower emhttp: shcmd (258): cp /etc/exports- /etc/exports Aug 31 22:48:00 Tower emhttp: Restart SMB... Aug 31 22:48:00 Tower emhttp: shcmd (259): killall -HUP smbd Aug 31 22:48:00 Tower emhttp: Restart NFS... Aug 31 22:48:00 Tower emhttp: shcmd (260): exportfs -ra |& logger Aug 31 22:48:00 Tower emhttp: shcmd (261): /usr/local/sbin/emhttp_event svcs_restarted Aug 31 22:48:00 Tower emhttp_event: svcs_restarted Aug 31 22:50:14 Tower emhttp: shcmd (262): set -o pipefail ; mkreiserfs -q /dev/md5 |& logger Aug 31 22:50:14 Tower logger: mkreiserfs 3.6.21 (2009 www.namesys.com) Aug 31 22:50:14 Tower logger: Aug 31 22:53:31 Tower emhttp: shcmd (263): mkdir /mnt/disk5 Aug 31 22:53:31 Tower emhttp: shcmd (264): set -o pipefail ; mount -t reiserfs -o acl,user_xattr,noatime,nodiratime /dev/md5 /mnt/disk5 |& logger Aug 31 22:53:31 Tower kernel: REISERFS (device md5): found reiserfs format "3.6" with standard journal Aug 31 22:53:31 Tower kernel: REISERFS (device md5): using ordered data mode Aug 31 22:53:31 Tower kernel: REISERFS (device md5): journal params: device md5, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30 Aug 31 22:53:31 Tower kernel: REISERFS (device md5): checking transaction log (md5) Aug 31 22:53:32 Tower kernel: REISERFS (device md5): Using r5 hash to sort names Aug 31 22:53:32 Tower kernel: REISERFS (device md5): Created .reiserfs_priv - reserved for xattr storage. Aug 31 22:53:32 Tower emhttp: resized: /mnt/disk5 Aug 31 22:53:32 Tower emhttp: shcmd (265): chmod 770 '/mnt/disk5' Aug 31 22:53:32 Tower emhttp: shcmd (266): chown nobody:users '/mnt/disk5' Aug 31 22:53:33 Tower emhttp: shcmd (267): :>/etc/samba/smb-shares.conf Aug 31 22:53:33 Tower emhttp: shcmd (268): cp /etc/exports- /etc/exports Aug 31 22:53:33 Tower emhttp: Restart SMB... Aug 31 22:53:33 Tower emhttp: shcmd (269): killall -HUP smbd Aug 31 22:53:33 Tower emhttp: Restart NFS...
revco Posted October 15, 2011 Posted October 15, 2011 I think you may need to provide a little more info about the drive in question. Are these the errors you're referring to? Aug 31 22:47:59 Tower kernel: REISERFS warning (device md5): sh-2021 reiserfs_fill_super: can not find reiserfs on md5 Aug 31 22:47:59 Tower logger: mount: wrong fs type, bad option, bad superblock on /dev/md5, Aug 31 22:47:59 Tower logger: missing codepage or helper program, or other error Aug 31 22:47:59 Tower logger: In some cases useful info is found in syslog - try Aug 31 22:47:59 Tower logger: dmesg | tail or so Aug 31 22:47:59 Tower logger: Aug 31 22:47:59 Tower emhttp: _shcmd: shcmd (240): exit status: 32 Aug 31 22:47:59 Tower emhttp: disk5 mount error: 32 Aug 31 22:47:59 Tower emhttp: shcmd (245): rmdir /mnt/disk5 What's the history on this drive? Did you preclear it? Presumably it was formatted by unRAID, but it's a little concerning that it's saying it's not seeing reiserfs. Can you provide more detail about the procedures you used to add this drive to the array? I see that later in the log it does see the reiserfs on that same drive, which to me seems like odd behavior. Aug 31 22:53:31 Tower emhttp: shcmd (263): mkdir /mnt/disk5 Aug 31 22:53:31 Tower emhttp: shcmd (264): set -o pipefail ; mount -t reiserfs -o acl,user_xattr,noatime,nodiratime /dev/md5 /mnt/disk5 |& logger Aug 31 22:53:31 Tower kernel: REISERFS (device md5): found reiserfs format "3.6" with standard journal Aug 31 22:53:31 Tower kernel: REISERFS (device md5): using ordered data mode Aug 31 22:53:31 Tower kernel: REISERFS (device md5): journal params: device md5, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30 Aug 31 22:53:31 Tower kernel: REISERFS (device md5): checking transaction log (md5) Aug 31 22:53:32 Tower kernel: REISERFS (device md5): Using r5 hash to sort names Aug 31 22:53:32 Tower kernel: REISERFS (device md5): Created .reiserfs_priv - reserved for xattr storage. Can you write files directly to the drive, without using a share? This will isolate a potential issue with your share configuration. Do you have any declared includes/excludes in your share configuration?
johnny121b Posted October 16, 2011 Author Posted October 16, 2011 It's a 2Tb Hitachi. Precleared: Yes. One pass. Formatted by UnRAID upon addition, as I recall. Like I said, it's been several weeks ago that I added it. I can copy a file directly TO it via Windows Explorer. All my copying to/from server is normally done via shares. The drive has been added to the shares' "included disk(s)" field.
revco Posted October 16, 2011 Posted October 16, 2011 Well, it may just be some weirdness in your logs...but it seems like it's recognizing and mounting the drive fine. How do you have your share allocation set? Most free, high water or fill-up? You may want to re-read this link: http://lime-technology.com/wiki/index.php?title=Un-Official_UnRAID_Manual#Allocation_method The way I understand it, with high water using all the same size drives...it will basically act like fill-up since the high water mark would basically be the same for all drives. If the case is the same size drives, you might want to try most free since that would definitely force files to your new drive. Also, just double check that you haven't added the new disk as an exclusion for any shares as well. Probably not likely, but something to check anyway.
Recommended Posts
Archived
This topic is now archived and is closed to further replies.