ctid

User on the server deleted and new one created and still no joy. Ran permissions again just to make sure and again, no joy. I'm not accessing via root, I have another user (new one too, see above!) The shares are set to public login, hence the strangeness of my problem. I can access them from other machines in the house, even on the machine with the troublesome account. I even set up a new account on my Windows 7 box, that too can access the shares. It is the account that had shares setup in v4 of unraid that now cannot access them. It can see the server but gets permission denied when clicking on the server. I can access \\tower no problem in the troublesome account.

On the windows box? Don't want to do this, there would be a large amount of work required to get the HTPC to a similar state. Did you run the new permissions script? Would this fix just a single login failing to access the shares?

I'm sure this is a windows issue, but you guys will probably know anyway! All was fine with my system until I upgraded to Unraid 5. Then the Unraid share on my Windows 7 HTPC stopped working. Browser access was fine, just the network shares wouldn't work. Other machines are fine, x3 Windows 7, 2x XP boxes, just the HTPC with the problem. So, I have read and read and have gone through all the suggestions, for example, set my master browser to unraid, turned off ip6 etc etc. Nothing worked. Then, by chance I set up another login on the HTPC. And whaya know, all shares are fine with this login!! Go back to my original login and no shares again. Unfortunatley, I need the original login as it is connected to my media centre and all the settings therein. I am sure this is something really simple, but I really can't get to the bottom of it. Does anybody have any suggestions?

I discovered it was an old unmenu installation. I have got rid of every plugin (I hope!) and have started the parity rebuild again. Interestingly, it seems to be completing significantly faster with all plugins disabled. I will update this thread with my results.

My saga upgrading my 2TB to 4TB continues... After problems with just adding a new disk, I took advice and precleared my disks. To do this, I used an old machine and a brand new installation of UNRAID, it had NO ADD ONs. Nothing but a fresh, vanilla, installation. Just to be clear, no add ons! Once finished, I turned off the array I was going to upgrade, powered down, swapped the 2TB parity disk for a 4TB. Powered up, assigned new disk to parity and UNRAID started to rebuild parity. Then at 51%, it fails. It has done this twice now on two different disks. Appropriate part of the SYSLOG is below. The important part is attempt to access beyond end of device UNRAID is not able to write over 2TB. Just to be clear, this is the SYSLOG below! I presume it was at the preclear stage that this has messed up. I used ver 1.4 of preclear. My server (proliant N54l) sees the disk as 4TB, as does UNRAID (sdf) Anyone got any ideas? Mar 14 18:55:46 Tower unmenu-status: Starting unmenu web-server Mar 14 19:10:00 Tower emhttp: shcmd (10): rmmod md-mod |& logger Mar 14 19:10:00 Tower emhttp: shcmd (11): modprobe md-mod super=/boot/config/super.dat slots=24 |& logger Mar 14 19:10:00 Tower kernel: md: unRAID driver removed Mar 14 19:10:00 Tower emhttp: shcmd (12): udevadm settle Mar 14 19:10:00 Tower emhttp: Device inventory: Mar 14 19:10:00 Tower emhttp: SAMSUNG_HD204UI_S2H7JD2B108427 (sdb) 1953513527 Mar 14 19:10:00 Tower emhttp: SAMSUNG_HD204UI_S2H7J9CB105081 (sdc) 1953514584 Mar 14 19:10:00 Tower emhttp: SAMSUNG_HD204UI_S2H7J9CB105079 (sdd) 1953514584 Mar 14 19:10:00 Tower kernel: md: unRAID driver 2.2.0 installed Mar 14 19:10:00 Tower emhttp: SAMSUNG_HD204UI_S2H7J9CB105083 (sde) 1953514584 Mar 14 19:10:00 Tower emhttp: WDC_WD40EFRX-68WT0N0_WD-WCC4E1140617 (sdf) 3907018584 Mar 14 19:10:00 Tower emhttp: shcmd (13): /usr/local/sbin/emhttp_event driver_loaded Mar 14 19:10:00 Tower kernel: mdcmd (1): import 0 0,0 Mar 14 19:10:00 Tower kernel: md: disk0 removed Mar 14 19:10:00 Tower kernel: mdcmd (2): import 1 8,32 1953514552 SAMSUNG_HD204UI_S2H7J9CB105081 Mar 14 19:10:00 Tower kernel: md: import disk1: [8,32] (sdc) SAMSUNG_HD204UI_S2H7J9CB105081 size: 1953514552 Mar 14 19:10:00 Tower kernel: mdcmd (3): import 2 8,48 1953514552 SAMSUNG_HD204UI_S2H7J9CB105079 Mar 14 19:10:00 Tower kernel: md: import disk2: [8,48] (sdd) SAMSUNG_HD204UI_S2H7J9CB105079 size: 1953514552 Mar 14 19:10:00 Tower kernel: mdcmd (4): import 3 8,64 1953514552 SAMSUNG_HD204UI_S2H7J9CB105083 Mar 14 19:10:00 Tower kernel: md: import disk3: [8,64] (sde) SAMSUNG_HD204UI_S2H7J9CB105083 size: 1953514552 Mar 14 19:10:00 Tower kernel: mdcmd (5): import 4 8,16 1953513496 SAMSUNG_HD204UI_S2H7JD2B108427 Mar 14 19:10:00 Tower kernel: md: import disk4: [8,16] (sdb) SAMSUNG_HD204UI_S2H7JD2B108427 size: 1953513496 Mar 14 19:10:00 Tower kernel: mdcmd (6): import 5 0,0 Mar 14 19:10:00 Tower kernel: mdcmd (7): import 6 0,0 Mar 14 19:10:00 Tower kernel: mdcmd (: import 7 0,0 Mar 14 19:10:00 Tower kernel: mdcmd (9): import 8 0,0 Mar 14 19:10:00 Tower kernel: mdcmd (10): import 9 0,0 Mar 14 19:10:00 Tower kernel: mdcmd (11): import 10 0,0 Mar 14 19:10:00 Tower kernel: mdcmd (12): import 11 0,0 Mar 14 19:10:00 Tower kernel: mdcmd (13): import 12 0,0 Mar 14 19:10:00 Tower kernel: mdcmd (14): import 13 0,0 Mar 14 19:10:00 Tower kernel: mdcmd (15): import 14 0,0 Mar 14 19:10:00 Tower kernel: mdcmd (16): import 15 0,0 Mar 14 19:10:00 Tower kernel: mdcmd (17): import 16 0,0 Mar 14 19:10:00 Tower kernel: mdcmd (18): import 17 0,0 Mar 14 19:10:00 Tower kernel: mdcmd (19): import 18 0,0 Mar 14 19:10:00 Tower kernel: mdcmd (20): import 19 0,0 Mar 14 19:10:00 Tower kernel: mdcmd (21): import 20 0,0 Mar 14 19:10:00 Tower kernel: mdcmd (22): import 21 0,0 Mar 14 19:10:00 Tower kernel: mdcmd (23): import 22 0,0 Mar 14 19:10:00 Tower kernel: mdcmd (24): import 23 0,0 Mar 14 19:10:00 Tower emhttp_event: driver_loaded Mar 14 19:10:06 Tower emhttp: shcmd (14): rmmod md-mod |& logger Mar 14 19:10:06 Tower emhttp: shcmd (15): modprobe md-mod super=/boot/config/super.dat slots=24 |& logger Mar 14 19:10:06 Tower kernel: md: unRAID driver removed Mar 14 19:10:06 Tower emhttp: shcmd (16): udevadm settle Mar 14 19:10:06 Tower kernel: md: unRAID driver 2.2.0 installed Mar 14 19:10:06 Tower emhttp: Device inventory: Mar 14 19:10:06 Tower emhttp: SAMSUNG_HD204UI_S2H7JD2B108427 (sdb) 1953513527 Mar 14 19:10:06 Tower emhttp: SAMSUNG_HD204UI_S2H7J9CB105081 (sdc) 1953514584 Mar 14 19:10:06 Tower emhttp: SAMSUNG_HD204UI_S2H7J9CB105079 (sdd) 1953514584 Mar 14 19:10:06 Tower emhttp: SAMSUNG_HD204UI_S2H7J9CB105083 (sde) 1953514584 Mar 14 19:10:06 Tower emhttp: WDC_WD40EFRX-68WT0N0_WD-WCC4E1140617 (sdf) 3907018584 Mar 14 19:10:06 Tower emhttp: shcmd (17): /usr/local/sbin/emhttp_event driver_loaded Mar 14 19:10:06 Tower kernel: mdcmd (1): import 0 8,80 3907018532 WDC_WD40EFRX-68WT0N0_WD-WCC4E1140617 Mar 14 19:10:06 Tower kernel: md: import disk0: [8,80] (sdf) WDC_WD40EFRX-68WT0N0_WD-WCC4E1140617 size: 3907018532 Mar 14 19:10:06 Tower kernel: md: disk0 replaced Mar 14 19:10:06 Tower kernel: mdcmd (2): import 1 8,32 1953514552 SAMSUNG_HD204UI_S2H7J9CB105081 Mar 14 19:10:06 Tower kernel: md: import disk1: [8,32] (sdc) SAMSUNG_HD204UI_S2H7J9CB105081 size: 1953514552 Mar 14 19:10:06 Tower kernel: mdcmd (3): import 2 8,48 1953514552 SAMSUNG_HD204UI_S2H7J9CB105079 Mar 14 19:10:06 Tower kernel: md: import disk2: [8,48] (sdd) SAMSUNG_HD204UI_S2H7J9CB105079 size: 1953514552 Mar 14 19:10:06 Tower kernel: mdcmd (4): import 3 8,64 1953514552 SAMSUNG_HD204UI_S2H7J9CB105083 Mar 14 19:10:06 Tower kernel: md: import disk3: [8,64] (sde) SAMSUNG_HD204UI_S2H7J9CB105083 size: 1953514552 Mar 14 19:10:06 Tower kernel: mdcmd (5): import 4 8,16 1953513496 SAMSUNG_HD204UI_S2H7JD2B108427 Mar 14 19:10:06 Tower kernel: md: import disk4: [8,16] (sdb) SAMSUNG_HD204UI_S2H7JD2B108427 size: 1953513496 Mar 14 19:10:06 Tower kernel: mdcmd (6): import 5 0,0 Mar 14 19:10:06 Tower kernel: mdcmd (7): import 6 0,0 Mar 14 19:10:06 Tower kernel: mdcmd (: import 7 0,0 Mar 14 19:10:06 Tower kernel: mdcmd (9): import 8 0,0 Mar 14 19:10:06 Tower kernel: mdcmd (10): import 9 0,0 Mar 14 19:10:06 Tower kernel: mdcmd (11): import 10 0,0 Mar 14 19:10:06 Tower kernel: mdcmd (12): import 11 0,0 Mar 14 19:10:06 Tower kernel: mdcmd (13): import 12 0,0 Mar 14 19:10:06 Tower kernel: mdcmd (14): import 13 0,0 Mar 14 19:10:06 Tower kernel: mdcmd (15): import 14 0,0 Mar 14 19:10:06 Tower kernel: mdcmd (16): import 15 0,0 Mar 14 19:10:06 Tower kernel: mdcmd (17): import 16 0,0 Mar 14 19:10:06 Tower kernel: mdcmd (18): import 17 0,0 Mar 14 19:10:06 Tower kernel: mdcmd (19): import 18 0,0 Mar 14 19:10:06 Tower kernel: mdcmd (20): import 19 0,0 Mar 14 19:10:06 Tower kernel: mdcmd (21): import 20 0,0 Mar 14 19:10:06 Tower kernel: mdcmd (22): import 21 0,0 Mar 14 19:10:06 Tower kernel: mdcmd (23): import 22 0,0 Mar 14 19:10:06 Tower kernel: mdcmd (24): import 23 0,0 Mar 14 19:10:06 Tower emhttp_event: driver_loaded Mar 14 19:10:19 Tower emhttp: shcmd (18): /usr/local/sbin/set_ncq sdf 1 &> /dev/null Mar 14 19:10:19 Tower kernel: mdcmd (25): set md_num_stripes 1280 Mar 14 19:10:19 Tower kernel: mdcmd (26): set md_write_limit 768 Mar 14 19:10:19 Tower kernel: mdcmd (27): set md_sync_window 384 Mar 14 19:10:19 Tower kernel: mdcmd (28): set spinup_group 0 0 Mar 14 19:10:19 Tower kernel: mdcmd (29): set spinup_group 1 0 Mar 14 19:10:19 Tower kernel: mdcmd (30): set spinup_group 2 0 Mar 14 19:10:19 Tower kernel: mdcmd (31): set spinup_group 3 0 Mar 14 19:10:19 Tower kernel: mdcmd (32): set spinup_group 4 0 Mar 14 19:10:19 Tower emhttp: shcmd (19): /usr/local/sbin/set_ncq sdc 1 &> /dev/null Mar 14 19:10:19 Tower emhttp: shcmd (20): /usr/local/sbin/set_ncq sdd 1 &> /dev/null Mar 14 19:10:19 Tower emhttp: shcmd (21): /usr/local/sbin/set_ncq sde 1 &> /dev/null Mar 14 19:10:19 Tower emhttp: shcmd (22): /usr/local/sbin/set_ncq sdb 1 &> /dev/null Mar 14 19:10:19 Tower emhttp: Spinning up all drives... Mar 14 19:10:19 Tower emhttp: writing GPT on disk (sdf), with partition 1 offset 64, erased: 0 Mar 14 19:10:19 Tower emhttp: shcmd (23): sgdisk -Z /dev/sdf &> /dev/null Mar 14 19:10:19 Tower emhttp: _shcmd: shcmd (23): exit status: 1 Mar 14 19:10:19 Tower emhttp: shcmd (24): sgdisk -o -a 64 -n 1:64:0 /dev/sdf |& logger Mar 14 19:10:19 Tower kernel: mdcmd (33): spinup 0 Mar 14 19:10:19 Tower kernel: mdcmd (34): spinup 1 Mar 14 19:10:19 Tower kernel: mdcmd (35): spinup 2 Mar 14 19:10:19 Tower kernel: mdcmd (36): spinup 3 Mar 14 19:10:19 Tower kernel: mdcmd (37): spinup 4 Mar 14 19:10:19 Tower logger: sgdisk: /usr/lib/libstdc++.so.6: version `GLIBCXX_3.4.11' not found (required by sgdisk) Mar 14 19:10:19 Tower emhttp: shcmd (25): udevadm settle Mar 14 19:10:19 Tower emhttp: Start array... Mar 14 19:10:19 Tower kernel: mdcmd (38): start RECON_DISK Mar 14 19:10:19 Tower kernel: unraid: allocating 28900K for 1280 stripes (5 disks) Mar 14 19:10:19 Tower kernel: md1: running, size: 1953514552 blocks Mar 14 19:10:19 Tower kernel: md2: running, size: 1953514552 blocks Mar 14 19:10:19 Tower kernel: md3: running, size: 1953514552 blocks Mar 14 19:10:19 Tower kernel: md4: running, size: 1953513496 blocks Mar 14 19:10:20 Tower emhttp: shcmd (26): udevadm settle Mar 14 19:10:20 Tower emhttp: shcmd (27): /usr/local/sbin/emhttp_event array_started Mar 14 19:10:20 Tower emhttp_event: array_started Mar 14 19:10:20 Tower emhttp: Mounting disks... Mar 14 19:10:20 Tower emhttp: shcmd (28): mkdir /mnt/disk1 Mar 14 19:10:20 Tower emhttp: shcmd (29): set -o pipefail ; mount -t reiserfs -o user_xattr,acl,noatime,nodiratime /dev/md1 /mnt/disk1 |& logger Mar 14 19:10:20 Tower kernel: REISERFS (device md1): found reiserfs format "3.6" with standard journal Mar 14 19:10:20 Tower kernel: REISERFS (device md1): using ordered data mode Mar 14 19:10:20 Tower kernel: reiserfs: using flush barriers Mar 14 19:10:20 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 Mar 14 19:10:20 Tower kernel: REISERFS (device md1): checking transaction log (md1) Mar 14 19:10:20 Tower kernel: REISERFS (device md1): Using r5 hash to sort names Mar 14 19:10:20 Tower emhttp: shcmd (30): mkdir /mnt/disk2 Mar 14 19:10:20 Tower emhttp: shcmd (31): set -o pipefail ; mount -t reiserfs -o user_xattr,acl,noatime,nodiratime /dev/md2 /mnt/disk2 |& logger Mar 14 19:10:20 Tower kernel: REISERFS (device md2): found reiserfs format "3.6" with standard journal Mar 14 19:10:20 Tower kernel: REISERFS (device md2): using ordered data mode Mar 14 19:10:20 Tower kernel: reiserfs: using flush barriers Mar 14 19:10:20 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 Mar 14 19:10:20 Tower kernel: REISERFS (device md2): checking transaction log (md2) Mar 14 19:10:20 Tower kernel: REISERFS (device md2): Using r5 hash to sort names Mar 14 19:10:21 Tower emhttp: shcmd (32): mkdir /mnt/disk3 Mar 14 19:10:21 Tower emhttp: shcmd (33): set -o pipefail ; mount -t reiserfs -o user_xattr,acl,noatime,nodiratime /dev/md3 /mnt/disk3 |& logger Mar 14 19:10:21 Tower kernel: REISERFS (device md3): found reiserfs format "3.6" with standard journal Mar 14 19:10:21 Tower kernel: REISERFS (device md3): using ordered data mode Mar 14 19:10:21 Tower kernel: reiserfs: using flush barriers Mar 14 19:10:21 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 Mar 14 19:10:21 Tower kernel: REISERFS (device md3): checking transaction log (md3) Mar 14 19:10:21 Tower kernel: REISERFS (device md3): Using r5 hash to sort names Mar 14 19:10:21 Tower emhttp: shcmd (34): mkdir /mnt/disk4 Mar 14 19:10:21 Tower emhttp: shcmd (35): set -o pipefail ; mount -t reiserfs -o user_xattr,acl,noatime,nodiratime /dev/md4 /mnt/disk4 |& logger Mar 14 19:10:21 Tower kernel: REISERFS (device md4): found reiserfs format "3.6" with standard journal Mar 14 19:10:21 Tower kernel: REISERFS (device md4): using ordered data mode Mar 14 19:10:21 Tower kernel: reiserfs: using flush barriers Mar 14 19:10:21 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 Mar 14 19:10:21 Tower kernel: REISERFS (device md4): checking transaction log (md4) Mar 14 19:10:21 Tower kernel: REISERFS (device md4): Using r5 hash to sort names Mar 14 19:10:22 Tower emhttp: shcmd (36): mkdir /mnt/user Mar 14 19:10:22 Tower emhttp: shcmd (37): /usr/local/sbin/shfs /mnt/user -disks 16777214 -o noatime,big_writes,allow_other -o remember=0 |& logger Mar 14 19:10:22 Tower emhttp: shcmd (38): crontab -c /etc/cron.d -d &> /dev/null Mar 14 19:10:22 Tower emhttp: shcmd (39): /usr/local/sbin/emhttp_event disks_mounted Mar 14 19:10:22 Tower emhttp_event: disks_mounted Mar 14 19:10:22 Tower kernel: mdcmd (39): check CORRECT Mar 14 19:10:22 Tower kernel: md: recovery thread woken up ... Mar 14 19:10:22 Tower kernel: md: recovery thread syncing parity disk ... Mar 14 19:10:22 Tower kernel: md: using 1536k window, over a total of 3907018532 blocks. Mar 14 19:10:23 Tower emhttp: shcmd (40): :>/etc/samba/smb-shares.conf Mar 14 19:10:23 Tower avahi-daemon[1638]: Files changed, reloading. Mar 14 19:10:23 Tower emhttp: get_config_idx: fopen /boot/config/shares/K.cfg: No such file or directory - assigning defaults Mar 14 19:10:23 Tower emhttp: get_config_idx: fopen /boot/config/shares/Recorded TV.cfg: No such file or directory - assigning defaults Mar 14 19:10:23 Tower emhttp: Restart SMB... Mar 14 19:10:23 Tower emhttp: shcmd (41): killall -HUP smbd Mar 14 19:10:23 Tower emhttp: shcmd (42): cp /etc/avahi/services/smb.service- /etc/avahi/services/smb.service Mar 14 19:10:23 Tower avahi-daemon[1638]: Files changed, reloading. Mar 14 19:10:23 Tower avahi-daemon[1638]: Service group file /services/smb.service changed, reloading. Mar 14 19:10:23 Tower emhttp: shcmd (43): ps axc | grep -q rpc.mountd Mar 14 19:10:23 Tower emhttp: _shcmd: shcmd (43): exit status: 1 Mar 14 19:10:23 Tower emhttp: shcmd (44): /usr/local/sbin/emhttp_event svcs_restarted Mar 14 19:10:23 Tower emhttp_event: svcs_restarted Mar 14 19:10:23 Tower emhttp: shcmd (45): /usr/local/sbin/emhttp_event started Mar 14 19:10:23 Tower emhttp_event: started Mar 14 19:10:24 Tower avahi-daemon[1638]: Service "Tower" (/services/smb.service) successfully established. Mar 16 14:18:57 Tower vsftpd[29293]: connect from 192.168.1.1 (192.168.1.1) Mar 16 14:18:57 Tower vsftpd[29295]: connect from 192.168.1.1 (192.168.1.1) Mar 16 16:27:38 Tower kernel: mdcmd (40): spindown 1 Mar 16 16:27:41 Tower kernel: mdcmd (41): spindown 2 Mar 16 16:27:43 Tower kernel: mdcmd (42): spindown 3 Mar 16 16:27:46 Tower kernel: mdcmd (43): spindown 4 Mar 16 20:01:09 Tower kernel: attempt to access beyond end of device Mar 16 20:01:09 Tower kernel: sdf1: rw=1, want=4294967296, limit=4294967295 Mar 16 20:01:09 Tower kernel: attempt to access beyond end of device Mar 16 20:01:09 Tower kernel: sdf1: rw=1, want=4294967304, limit=4294967295 Mar 16 20:01:09 Tower kernel: md: disk0 write error, sector=4294967288 Mar 16 20:01:09 Tower kernel: md: md_do_sync: got signal, exit... Mar 16 20:01:09 Tower kernel: md: disk0 write error, sector=4294967296 Mar 16 20:01:10 Tower kernel: md: recovery thread sync completion status: -4 Mar 16 20:01:10 Tower kernel: md: recovery thread woken up ... Mar 16 20:01:11 Tower kernel: md: recovery thread has nothing to resync Mar 16 20:38:33 Tower emhttp: shcmd (46): /usr/local/sbin/emhttp_event stopping_svcs Mar 16 20:38:33 Tower kernel: mdcmd (44): nocheck Mar 16 20:38:33 Tower kernel: md: nocheck_array: check not active Mar 16 20:38:33 Tower emhttp_event: stopping_svcs Mar 16 20:38:33 Tower emhttp: Stop AVAHI... Mar 16 20:38:33 Tower emhttp: shcmd (47): /etc/rc.d/rc.avahidaemon stop |& logger Mar 16 20:38:33 Tower logger: Stopping Avahi mDNS/DNS-SD Daemon: stopped Mar 16 20:38:33 Tower avahi-daemon[1638]: Got SIGTERM, quitting. Mar 16 20:38:33 Tower avahi-dnsconfd[1647]: read(): EOF Mar 16 20:38:33 Tower avahi-daemon[1638]: Leaving mDNS multicast group on interface eth0.IPv4 with address 192.168.1.85. Mar 16 20:38:33 Tower avahi-daemon[1638]: avahi-daemon 0.6.31 exiting. Mar 16 20:38:33 Tower emhttp: shcmd (48): /etc/rc.d/rc.avahidnsconfd stop |& logger Mar 16 20:38:33 Tower logger: Stopping Avahi mDNS/DNS-SD DNS Server Configuration Daemon: stopped Mar 16 20:38:33 Tower emhttp: shcmd (49): ps axc | grep -q rpc.mountd Mar 16 20:38:33 Tower emhttp: _shcmd: shcmd (49): exit status: 1 Mar 16 20:38:33 Tower emhttp: Stop SMB...

thank you. I have unmenu too so I can install via that.

I started a preclear session on a new disk. I logged on to my server via a windows PuTTY session and all was going swimmingly. The last time I checked prgrogress, it was in step 2, 93%. I went to check a little while later and the PuTTY session had crashed. I suspect my PC went into sleep mode which closed the network connection. So, is the process still running on the server and should I just wait? Or bite the bullet and start again? ta!

Good advice! The temptation to keep going back to the webgui is too strong though! I've got the N54. Tidy little thing, going to 4TB a drive will take me to 16TB with a potential of 20TB if I use the eSATA connector. I'm in no rush to be honest. I guess I could take the array off line and put all 4 in at once for a preclear after I complete the parity. I can live without the box for a few days. Then swap one at a time after that. It should be ready by the summer!

8%, it's like watching paint dry!

No, it is a vanilla install, so there was nothing to remove. My other complication in the run up to all this is that I have a HP microserver and all my slots are being used, hence why I needed to swap out the parity. In regards to consulting the FAQ, I did. It has a link to a forum post (http://lime-technology.com/forum/index.php?topic=2280.0) which states Hi All, I've a system with 6x 750 GB and 3x 500 GB drives; just received new 1 TB drive I would like to use as the parity drive. I think I understand the steps to replace the 750 GB parity with the new 1TB parity drive, but hoping for someone to tell me the following steps are correct. 1 - Ran parity check last night, no errors. This step not really required, but a sanity issue 2 - stop the array 3 - go to devices tab, remove parity drive from configuration 4 - power down system via "powerdown" button 5 - remove existing 750 GB parity drive, replace with new 1 TB drive 6 - power on unraid 7 - go to devices tab, assign 1TB drive as parity drive 8 - start the array with the "start" button 9 - wait for parity rebuild to complete 10 - power off array and system 11 - install 750 GB drive removed in step 5 12 - power on machine, start the array 13 - go to devices tab, add the new/old 750 GB as a data disk 14 - start the array - disk will be formatted and added to the array. I was stuck at point 8, the array would not start with the new disk. Once it had been put in a windows machine, voila, the array will start.

superloopy, I don't think you are quite understanding, but never mind. I'm up and running though. I wonder why unraind cannot deal with a fresh, out of the packet drive. Yes, I know there is preclear but this is not a prerequisite but good practice. Maybe there needs to be a way to create the partition so unraid can use a disk from the webgui.

Dumb question, but did you first click the checkbox for "Yes I want to do this" so that the "Start" button will change from Grayed-out to Normal? After clicking the box, you can then press the Start button to "bring the array on-line and begin Parity-Sync". Ha! I said I was a novice not a dim wit!!! Yes, I know how to start the array. Update time. I took the drive out and connected to my laptop with the esata connector. Set it up as an MBR partition, so only 2TB was seen, I didn't want to complicate things with GPT. Gave it a quick format and plugged it back into my server. Fired it up and lo and behold the array starts. It is also seen as 4TB too. Currently it is rebuilding the parity. I had to do it this way as I couldn't just add one of my 4TB's in a spare slot and preclear as they would be bigger than the parity and would have messed things up. So once I have the parity re-built I will then start pre-clearing my drives and adding them one by one.

I do have another WD red 4tb here that I am going to replace one of my data drives with. Another 3 are coming on Monday. I could try this other drive too as the parity drive. Not now though, it's bedtime in NL! I will try tomorrow, thanks everyone for the help thus far.

read the link, thanks superloopy. But the implication there is that it is for future security of your data that a preclear is good practice and not that it is needed to make the HDD work in the array from the off. Once I know this HDD is compatible I'm happy to set it going on a preclear, I just don't want to find out in three days time, that I still have a non compatible disk!

superloopy, did you try to start the array with your new drive or immediately go for a preclear? Was it a data or parity drive?