[MicroServer N36L/N40L/N54L - 6 Drive Edition]

Ok, yep... will do that.  Just got it yesterday.  I've got an SSD to use as the write cache but I may have to hold off a bit until I can get those drives.

[MicroServer N36L/N40L/N54L - 6 Drive Edition]

So I am looking to replace my 4224 with a smaller setup and less drives... snagged a N54L off Ebay for a decent price.  I know it only holds 4 drives out of the box, I really want those 8TB drives to come out   I wanted expansibility (albeit with external boxes) and the ability to try 6.0 and move all my old stuff off

[Wow things have changed ;)]

So it's been a number of years since I logged in... once I got 4.7 up and running and my 20 bay case fully populated with 2TB cards I kind of just let my unRaid run.  Frankly it has never failed me although I am closing in on the final few TB of space   But I've been thinking hey, I should check out what upgrades are out there now and WOW things are different.  Docker containers, running as a guest OS, etc;  Very impressive!  Now I have to figure out how to upgrade my poor system to at least 5 and what I can take advantage of.  Since the new 8TB drive announcement today I'm chuckling at jumping from 40TB to 160TB usable.  Not even sure my controller cards for instance can handle that drive size without a flash or something, and I am terrified of losing everything I have.

 

-MP

[Can't unmount cache drive]

All drives in the arry say stopped.  The Cache drive still says Unmounting and the status says Stopping.  Sooo... I can't add a device.  Not sure what to do at this point.  Reboot from the command line?  If I do that it will kicj off a parity check, and I will have to wait for that to finish before trying to stop the array again.

[Can't unmount cache drive]

I'm trying to add 4 more drives that have been precleared but when I run unmount from the web page the cache drive won't unmount.  I am guessing it's because of the modules I have installed.  Is there a manual way to shut it down so I can add the drive?  Even after all these years with UnRaid my Linux skills suck

[UnRaid not visible in "Network" on Win7]

On a Win7 PC I need to be able to see Tower displayed through the Network browser with all my other PCs.  Got an application that requires I be able to select it like that rather than typing in the path \\tower\share path.  Any ideas where the heck I make that work?

 

Thanks!

[Hitachi 3TB 5400RPM $109.99 w/Free Shipping @ NewEgg]

Now if only we could use them to their full capacity.

[[SOLVED] Recovering after the hurricane... something is badly wrong.]

Whew!  I pulled the USB and ran chkdisk, no errors.  Reseated it firmly and it restarted fine.  No idea what happened, but everything is back.  Thanks for the help in my moment of panick

[[SOLVED] Recovering after the hurricane... something is badly wrong.]

Ah ok.  Thanks, I'll try that this morning.

[[SOLVED] Recovering after the hurricane... something is badly wrong.]

Do you think I need to completely replace it or just pull it, pop it back, and try again?

[[SOLVED] Recovering after the hurricane... something is badly wrong.]

So any suggestions on what I should do?  I don't understand what's up with my shares or how to stitch it all back together

[[SOLVED] Recovering after the hurricane... something is badly wrong.]

If I browse to the individual disks they all have the Videos folder.  On some the directory list is a few, on others its a bunch, on some it appears to maybe be all.

[[SOLVED] Recovering after the hurricane... something is badly wrong.]

I stopped it and started it again and am still missing all my data

 

Aug 30 19:23:48 Tower mountd[3446]: Caught signal 15, un-registering and exiting.

Aug 30 19:23:49 Tower kernel: nfsd: last server has exited, flushing export cache

Aug 30 19:23:49 Tower emhttp: Spinning up all drives...

Aug 30 19:23:49 Tower emhttp: shcmd (62): /usr/sbin/hdparm -S0 /dev/sdd >/dev/null

Aug 30 19:23:49 Tower kernel: mdcmd (39): spinup 0

Aug 30 19:23:49 Tower kernel: mdcmd (40): spinup 1

Aug 30 19:23:49 Tower kernel: mdcmd (41): spinup 2

Aug 30 19:23:49 Tower kernel: mdcmd (42): spinup 3

Aug 30 19:23:49 Tower kernel: mdcmd (43): spinup 4

Aug 30 19:23:49 Tower kernel: mdcmd (44): spinup 5

Aug 30 19:23:49 Tower kernel: mdcmd (45): spinup 6

Aug 30 19:23:49 Tower kernel: mdcmd (46): spinup 7

Aug 30 19:23:49 Tower kernel: mdcmd (47): spinup 8

Aug 30 19:23:49 Tower kernel: mdcmd (48): spinup 9

Aug 30 19:23:57 Tower kernel: sas: command 0xf53ef3c0, task 0xf53faa00, timed out: BLK_EH_NOT_HANDLED

Aug 30 19:24:02 Tower emhttp: _shcmd: shcmd (62): exit status: 5

Aug 30 19:24:02 Tower emhttp: shcmd (63): sync

Aug 30 19:24:02 Tower kernel: sas: Enter sas_scsi_recover_host

Aug 30 19:24:02 Tower kernel: sas: trying to find task 0xf53faa00

Aug 30 19:24:02 Tower kernel: sas: sas_scsi_find_task: aborting task 0xf53faa00

Aug 30 19:24:02 Tower kernel: sas: sas_scsi_find_task: task 0xf53faa00 is done

Aug 30 19:24:02 Tower kernel: sas: sas_eh_handle_sas_errors: task 0xf53faa00 is done

Aug 30 19:24:02 Tower kernel: sas: sas_ata_task_done: SAS error 8d

Aug 30 19:24:02 Tower kernel: ata3: translated ATA stat/err 0x01/04 to SCSI SK/ASC/ASCQ 0xb/00/00

Aug 30 19:24:02 Tower kernel: ata3: status=0x01 { Error }

Aug 30 19:24:02 Tower kernel: ata3: error=0x04 { DriveStatusError }

Aug 30 19:24:02 Tower kernel: sas: --- Exit sas_scsi_recover_host

Aug 30 19:24:04 Tower emhttp: shcmd (64): umount /mnt/user >/dev/null 2>&1

Aug 30 19:24:04 Tower emhttp: shcmd (65): rmdir /mnt/user >/dev/null 2>&1

Aug 30 19:24:04 Tower emhttp: shcmd (66): umount /mnt/user0 >/dev/null 2>&1

Aug 30 19:24:04 Tower emhttp: shcmd (67): rmdir /mnt/user0 >/dev/null 2>&1

Aug 30 19:24:04 Tower emhttp: shcmd (68): umount /mnt/disk1 >/dev/null 2>&1

Aug 30 19:24:05 Tower emhttp: shcmd (69): rmdir /mnt/disk1 >/dev/null 2>&1

Aug 30 19:24:05 Tower emhttp: shcmd (70): umount /mnt/disk2 >/dev/null 2>&1

Aug 30 19:24:05 Tower emhttp: shcmd (71): rmdir /mnt/disk2 >/dev/null 2>&1

Aug 30 19:24:05 Tower emhttp: shcmd (72): umount /mnt/disk3 >/dev/null 2>&1

Aug 30 19:24:06 Tower emhttp: shcmd (73): rmdir /mnt/disk3 >/dev/null 2>&1

Aug 30 19:24:06 Tower emhttp: shcmd (74): umount /mnt/disk4 >/dev/null 2>&1

Aug 30 19:24:06 Tower emhttp: shcmd (75): rmdir /mnt/disk4 >/dev/null 2>&1

Aug 30 19:24:06 Tower emhttp: shcmd (76): umount /mnt/disk5 >/dev/null 2>&1

Aug 30 19:24:06 Tower emhttp: shcmd (77): rmdir /mnt/disk5 >/dev/null 2>&1

Aug 30 19:24:06 Tower emhttp: shcmd (78): umount /mnt/disk6 >/dev/null 2>&1

Aug 30 19:24:06 Tower emhttp: shcmd (79): rmdir /mnt/disk6 >/dev/null 2>&1

Aug 30 19:24:06 Tower emhttp: shcmd (80): umount /mnt/disk7 >/dev/null 2>&1

Aug 30 19:24:07 Tower emhttp: shcmd (81): rmdir /mnt/disk7 >/dev/null 2>&1

Aug 30 19:24:07 Tower emhttp: shcmd (82): umount /mnt/disk8 >/dev/null 2>&1

Aug 30 19:24:07 Tower emhttp: shcmd (83): rmdir /mnt/disk8 >/dev/null 2>&1

Aug 30 19:24:07 Tower emhttp: shcmd (84): umount /mnt/disk9 >/dev/null 2>&1

Aug 30 19:24:08 Tower emhttp: shcmd (85): rmdir /mnt/disk9 >/dev/null 2>&1

Aug 30 19:24:08 Tower emhttp: shcmd (86): umount /mnt/cache >/dev/null 2>&1

Aug 30 19:24:08 Tower emhttp: shcmd (87): rmdir /mnt/cache >/dev/null 2>&1

Aug 30 19:24:08 Tower kernel: mdcmd (49): stop

Aug 30 19:24:08 Tower kernel: md1: stopping

Aug 30 19:24:08 Tower kernel: md2: stopping

Aug 30 19:24:08 Tower kernel: md3: stopping

Aug 30 19:24:08 Tower kernel: md4: stopping

Aug 30 19:24:08 Tower kernel: md5: stopping

Aug 30 19:24:08 Tower kernel: md6: stopping

Aug 30 19:24:08 Tower kernel: md7: stopping

Aug 30 19:24:08 Tower kernel: md8: stopping

Aug 30 19:24:08 Tower kernel: md9: stopping

Aug 30 19:24:08 Tower kernel: write_file: error 2 opening /boot/config/super.dat

Aug 30 19:24:08 Tower kernel: md: could not write superblock from /boot/config/super.dat

Aug 30 19:24:09 Tower emhttp: shcmd (88): rm /etc/samba/smb-shares.conf >/dev/null 2>&1

Aug 30 19:24:09 Tower emhttp: shcmd (89): cp /etc/exports- /etc/exports

Aug 30 19:24:09 Tower emhttp: shcmd (90): /etc/rc.d/rc.samba start | logger

Aug 30 19:24:09 Tower logger: Starting Samba:  /usr/sbin/nmbd -D

Aug 30 19:24:09 Tower logger:                  /usr/sbin/smbd -D

Aug 30 19:24:09 Tower emhttp: shcmd (91): /etc/rc.d/rc.nfsd start | logger

Aug 30 19:24:22 Tower emhttp: shcmd (92): /usr/local/sbin/set_ncq sdg 1 >/dev/null

Aug 30 19:24:22 Tower emhttp: shcmd (93): /usr/local/sbin/set_ncq sdl 1 >/dev/null

Aug 30 19:24:22 Tower emhttp: shcmd (94): /usr/local/sbin/set_ncq sdk 1 >/dev/null

Aug 30 19:24:22 Tower emhttp: shcmd (95): /usr/local/sbin/set_ncq sdm 1 >/dev/null

Aug 30 19:24:22 Tower emhttp: shcmd (96): /usr/local/sbin/set_ncq sdf 1 >/dev/null

Aug 30 19:24:22 Tower emhttp: shcmd (97): /usr/local/sbin/set_ncq sdc 1 >/dev/null

Aug 30 19:24:22 Tower emhttp: shcmd (98): /usr/local/sbin/set_ncq sdj 1 >/dev/null

Aug 30 19:24:22 Tower emhttp: shcmd (99): /usr/local/sbin/set_ncq sde 1 >/dev/null

Aug 30 19:24:22 Tower emhttp: shcmd (100): /usr/local/sbin/set_ncq sdh 1 >/dev/null

Aug 30 19:24:22 Tower emhttp: shcmd (101): /usr/local/sbin/set_ncq sdi 1 >/dev/null

Aug 30 19:24:22 Tower emhttp: shcmd (102): /usr/local/sbin/set_ncq sdd 1 >/dev/null

Aug 30 19:24:22 Tower kernel: mdcmd (50): start STOPPED

Aug 30 19:24:22 Tower kernel: unraid: allocating 54200K for 1280 stripes (10 disks)

Aug 30 19:24:22 Tower kernel: md1: running, size: 1953514552 blocks

Aug 30 19:24:22 Tower kernel: md2: running, size: 1953514552 blocks

Aug 30 19:24:22 Tower kernel: md3: running, size: 1953514552 blocks

Aug 30 19:24:22 Tower kernel: md4: running, size: 1953514552 blocks

Aug 30 19:24:22 Tower kernel: md5: running, size: 1953514552 blocks

Aug 30 19:24:22 Tower kernel: md6: running, size: 1953514552 blocks

Aug 30 19:24:22 Tower kernel: md7: running, size: 1953514552 blocks

Aug 30 19:24:22 Tower kernel: md8: running, size: 1953514552 blocks

Aug 30 19:24:22 Tower kernel: md9: running, size: 1953514552 blocks

Aug 30 19:24:23 Tower emhttp: shcmd (103): udevadm settle

Aug 30 19:24:23 Tower emhttp: shcmd (104): mkdir /mnt/disk1

Aug 30 19:24:23 Tower emhttp: shcmd (104): mkdir /mnt/disk2

Aug 30 19:24:23 Tower emhttp: shcmd (104): mkdir /mnt/disk5

Aug 30 19:24:23 Tower emhttp: shcmd (104): mkdir /mnt/disk3

Aug 30 19:24:23 Tower emhttp: shcmd (104): mkdir /mnt/disk7

Aug 30 19:24:23 Tower emhttp: shcmd (104): mkdir /mnt/cache

Aug 30 19:24:23 Tower emhttp: shcmd (104): mkdir /mnt/disk8

Aug 30 19:24:23 Tower emhttp: shcmd (104): mkdir /mnt/disk6

Aug 30 19:24:23 Tower emhttp: shcmd (104): mkdir /mnt/disk4

Aug 30 19:24:23 Tower emhttp: shcmd (104): mkdir /mnt/disk9

Aug 30 19:24:23 Tower emhttp: shcmd (105): set -o pipefail ; mount -t reiserfs -o noacl,nouser_xattr,noatime,nodiratime /dev/md1 /mnt/disk1 2>&1 | logger

Aug 30 19:24:23 Tower kernel: mdcmd (51): check

Aug 30 19:24:23 Tower kernel: md: recovery thread woken up ...

Aug 30 19:24:23 Tower kernel: write_file: error 2 opening /boot/config/super.dat

Aug 30 19:24:23 Tower kernel: md: could not write superblock from /boot/config/super.dat

Aug 30 19:24:23 Tower kernel: md: recovery thread has nothing to resync

Aug 30 19:24:23 Tower emhttp: shcmd (106): set -o pipefail ; mount -t reiserfs -o noacl,nouser_xattr,noatime,nodiratime /dev/md5 /mnt/disk5 2>&1 | logger

Aug 30 19:24:23 Tower emhttp: shcmd (107): set -o pipefail ; mount -t reiserfs -o noacl,nouser_xattr,noatime,nodiratime /dev/md3 /mnt/disk3 2>&1 | logger

Aug 30 19:24:23 Tower emhttp: shcmd (108): set -o pipefail ; mount -t reiserfs -o noacl,nouser_xattr,noatime,nodiratime /dev/md2 /mnt/disk2 2>&1 | logger

Aug 30 19:24:23 Tower emhttp: shcmd (109): set -o pipefail ; mount -t reiserfs -o noacl,nouser_xattr,noatime,nodiratime /dev/md9 /mnt/disk9 2>&1 | logger

Aug 30 19:24:23 Tower emhttp: shcmd (109): set -o pipefail ; mount -t reiserfs -o noacl,nouser_xattr,noatime,nodiratime /dev/md4 /mnt/disk4 2>&1 | logger

Aug 30 19:24:23 Tower emhttp: shcmd (110): set -o pipefail ; mount -t reiserfs -o noacl,nouser_xattr,noatime,nodiratime /dev/md7 /mnt/disk7 2>&1 | logger

Aug 30 19:24:23 Tower emhttp: shcmd (111): set -o pipefail ; mount -t reiserfs -o noacl,nouser_xattr,noatime,nodiratime /dev/sdd1 /mnt/cache 2>&1 | logger

Aug 30 19:24:23 Tower emhttp: shcmd (112): set -o pipefail ; mount -t reiserfs -o noacl,nouser_xattr,noatime,nodiratime /dev/md6 /mnt/disk6 2>&1 | logger

Aug 30 19:24:23 Tower emhttp: shcmd (113): set -o pipefail ; mount -t reiserfs -o noacl,nouser_xattr,noatime,nodiratime /dev/md8 /mnt/disk8 2>&1 | logger

Aug 30 19:24:23 Tower kernel: REISERFS (device sdd1): found reiserfs format "3.6" with standard journal

Aug 30 19:24:23 Tower kernel: REISERFS (device sdd1): using ordered data mode

Aug 30 19:24:23 Tower kernel: REISERFS (device sdd1): journal params: device sdd1, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30

Aug 30 19:24:23 Tower kernel: REISERFS (device sdd1): checking transaction log (sdd1)

Aug 30 19:24:23 Tower kernel: REISERFS (device md7): found reiserfs format "3.6" with standard journal

Aug 30 19:24:23 Tower kernel: REISERFS (device md7): using ordered data mode

Aug 30 19:24:23 Tower kernel: REISERFS (device md5): found reiserfs format "3.6" with standard journal

Aug 30 19:24:23 Tower kernel: REISERFS (device md5): using ordered data mode

Aug 30 19:24:23 Tower kernel: REISERFS (device md6): found reiserfs format "3.6" with standard journal

Aug 30 19:24:23 Tower kernel: REISERFS (device md6): using ordered data mode

Aug 30 19:24:23 Tower kernel: REISERFS (device md8): found reiserfs format "3.6" with standard journal

Aug 30 19:24:23 Tower kernel: REISERFS (device md8): using ordered data mode

Aug 30 19:24:23 Tower kernel: REISERFS (device md2): found reiserfs format "3.6" with standard journal

Aug 30 19:24:23 Tower kernel: REISERFS (device md2): using ordered data mode

Aug 30 19:24:23 Tower kernel: REISERFS (device md9): found reiserfs format "3.6" with standard journal

Aug 30 19:24:23 Tower kernel: REISERFS (device md9): using ordered data mode

Aug 30 19:24:23 Tower kernel: REISERFS (device md4): found reiserfs format "3.6" with standard journal

Aug 30 19:24:23 Tower kernel: REISERFS (device md4): using ordered data mode

Aug 30 19:24:23 Tower kernel: REISERFS (device md3): found reiserfs format "3.6" with standard journal

Aug 30 19:24:23 Tower kernel: REISERFS (device md3): using ordered data mode

Aug 30 19:24:23 Tower kernel: REISERFS (device md1): found reiserfs format "3.6" with standard journal

Aug 30 19:24:23 Tower kernel: REISERFS (device md1): using ordered data mode

Aug 30 19:24:23 Tower kernel: REISERFS (device md9): journal params: device md9, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30

Aug 30 19:24:23 Tower kernel: REISERFS (device md9): checking transaction log (md9)

Aug 30 19:24:23 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 30 19:24:23 Tower kernel: REISERFS (device md5): checking transaction log (md5)

Aug 30 19:24:23 Tower kernel: REISERFS (device md7): journal params: device md7, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30

Aug 30 19:24:23 Tower kernel: REISERFS (device md7): checking transaction log (md7)

Aug 30 19:24:23 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 30 19:24:23 Tower kernel: REISERFS (device md3): checking transaction log (md3)

Aug 30 19:24:23 Tower kernel: REISERFS (device sdd1): Using r5 hash to sort names

Aug 30 19:24:23 Tower kernel: REISERFS (device md6): journal params: device md6, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30

Aug 30 19:24:23 Tower kernel: REISERFS (device md6): checking transaction log (md6)

Aug 30 19:24:23 Tower kernel: REISERFS (device md8): journal params: device md8, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30

Aug 30 19:24:23 Tower kernel: REISERFS (device md8): checking transaction log (md8)

Aug 30 19:24:23 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 30 19:24:23 Tower kernel: REISERFS (device md2): checking transaction log (md2)

Aug 30 19:24:23 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 30 19:24:23 Tower kernel: REISERFS (device md1): checking transaction log (md1)

Aug 30 19:24:23 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 30 19:24:23 Tower kernel: REISERFS (device md4): checking transaction log (md4)

Aug 30 19:24:23 Tower kernel: REISERFS (device md9): Using r5 hash to sort names

Aug 30 19:24:23 Tower kernel: REISERFS (device md1): Using r5 hash to sort names

Aug 30 19:24:23 Tower kernel: REISERFS (device md6): Using r5 hash to sort names

Aug 30 19:24:23 Tower kernel: REISERFS (device md5): Using r5 hash to sort names

Aug 30 19:24:23 Tower kernel: REISERFS (device md3): Using r5 hash to sort names

Aug 30 19:24:23 Tower kernel: REISERFS (device md2): Using r5 hash to sort names

Aug 30 19:24:23 Tower kernel: REISERFS (device md7): Using r5 hash to sort names

Aug 30 19:24:23 Tower kernel: REISERFS (device md8): Using r5 hash to sort names

Aug 30 19:24:23 Tower kernel: REISERFS (device md4): Using r5 hash to sort names

Aug 30 19:24:25 Tower emhttp: shcmd (123): rm /etc/samba/smb-shares.conf >/dev/null 2>&1

Aug 30 19:24:25 Tower emhttp: shcmd (124): cp /etc/exports- /etc/exports

Aug 30 19:24:25 Tower emhttp: shcmd (125): echo \"/mnt/disk1\" '-async,no_subtree_check,anongid=0,anonuid=0,all_squash,fsid=11' 'Videos' >>/etc/exports

Aug 30 19:24:25 Tower emhttp: shcmd (126): echo \"/mnt/disk2\" '-async,no_subtree_check,anongid=0,anonuid=0,all_squash,fsid=12' 'Videos' >>/etc/exports

Aug 30 19:24:25 Tower emhttp: shcmd (127): echo \"/mnt/disk3\" '-async,no_subtree_check,anongid=0,anonuid=0,all_squash,fsid=13' 'Videos' >>/etc/exports

Aug 30 19:24:25 Tower emhttp: shcmd (128): echo \"/mnt/disk4\" '-async,no_subtree_check,anongid=0,anonuid=0,all_squash,fsid=14' 'Videos' >>/etc/exports

Aug 30 19:24:25 Tower emhttp: shcmd (129): echo \"/mnt/disk5\" '-async,no_subtree_check,anongid=0,anonuid=0,all_squash,fsid=15' 'Videos' >>/etc/exports

Aug 30 19:24:25 Tower emhttp: shcmd (130): echo \"/mnt/disk6\" '-async,no_subtree_check,anongid=0,anonuid=0,all_squash,fsid=16' 'Videos' >>/etc/exports

Aug 30 19:24:25 Tower emhttp: shcmd (131): echo \"/mnt/disk7\" '-async,no_subtree_check,anongid=0,anonuid=0,all_squash,fsid=17' 'Videos' >>/etc/exports

Aug 30 19:24:25 Tower emhttp: shcmd (132): echo \"/mnt/disk8\" '-async,no_subtree_check,anongid=0,anonuid=0,all_squash,fsid=18' 'Videos' >>/etc/exports

Aug 30 19:24:25 Tower emhttp: shcmd (133): echo \"/mnt/disk9\" '-async,no_subtree_check,anongid=0,anonuid=0,all_squash,fsid=19' 'Videos' >>/etc/exports

Aug 30 19:24:25 Tower emhttp: shcmd (134): echo \"/mnt/cache\" '-async,no_subtree_check,anongid=0,anonuid=0,all_squash,fsid=10' 'Videos' >>/etc/exports

Aug 30 19:24:25 Tower emhttp: shcmd (135): mkdir /mnt/user

Aug 30 19:24:25 Tower emhttp: shcmd (136): /usr/local/sbin/shfs /mnt/user -cache 1 -floor 2000000  -o noatime,big_writes,allow_other,default_permissions

Aug 30 19:24:25 Tower emhttp: shcmd (137): mkdir /mnt/user0

Aug 30 19:24:25 Tower kernel: FAT: Directory bread(block 16384) failed

Aug 30 19:24:25 Tower kernel: FAT: Directory bread(block 16385) failed

Aug 30 19:24:25 Tower kernel: FAT: Directory bread(block 16386) failed

Aug 30 19:24:25 Tower kernel: FAT: Directory bread(block 16387) failed

Aug 30 19:24:25 Tower kernel: FAT: Directory bread(block 16388) failed

Aug 30 19:24:25 Tower kernel: FAT: Directory bread(block 16389) failed

Aug 30 19:24:25 Tower kernel: FAT: Directory bread(block 16390) failed

Aug 30 19:24:25 Tower kernel: FAT: Directory bread(block 16391) failed

Aug 30 19:24:25 Tower emhttp: shcmd (138): /usr/local/sbin/shfs /mnt/user0 -cache 0  -o noatime,big_writes,allow_other,default_permissions

Aug 30 19:24:25 Tower kernel: FAT: Directory bread(block 16384) failed

Aug 30 19:24:25 Tower kernel: FAT: Directory bread(block 16385) failed

Aug 30 19:24:25 Tower kernel: FAT: Directory bread(block 16386) failed

Aug 30 19:24:25 Tower kernel: FAT: Directory bread(block 16387) failed

Aug 30 19:24:25 Tower kernel: FAT: Directory bread(block 16388) failed

Aug 30 19:24:25 Tower kernel: FAT: Directory bread(block 16389) failed

Aug 30 19:24:25 Tower kernel: FAT: Directory bread(block 16390) failed

Aug 30 19:24:25 Tower kernel: FAT: Directory bread(block 16391) failed

Aug 30 19:24:26 Tower emhttp: get_config_idx: fopen /boot/config/shares/Home Movies.cfg: No such file or directory - assigning defaults

Aug 30 19:24:26 Tower emhttp: get_config_idx: fopen /boot/config/shares/Music.cfg: No such file or directory - assigning defaults

Aug 30 19:24:26 Tower emhttp: get_config_idx: fopen /boot/config/shares/TV Shows.cfg: No such file or directory - assigning defaults

Aug 30 19:24:26 Tower emhttp: get_config_idx: fopen /boot/config/shares/Videos.cfg: No such file or directory - assigning defaults

Aug 30 19:24:26 Tower emhttp: shcmd (139): killall -HUP smbd

Aug 30 19:24:26 Tower emhttp: shcmd (140): /etc/rc.d/rc.nfsd restart | logger

Aug 30 19:24:28 Tower logger: Starting NFS server daemons:

Aug 30 19:24:28 Tower logger:   /usr/sbin/exportfs -r

Aug 30 19:24:28 Tower logger:   /usr/sbin/rpc.nfsd 8

Aug 30 19:24:28 Tower logger:   /usr/sbin/rpc.mountd

 

[[SOLVED] Recovering after the hurricane... something is badly wrong.]

I lost power on Sunday from Irene and my UPS shut my server down (I thought) gracefully.  Got it back this morning and noticed my server had booted up but I hadn't had time to check it out before I went to work.  I came home tonight though and am about to vomit.  I am running 4.7 pro.  All drives show green, no errors, parity check finished successfully.  But over half my data is just gone.  My syslog has some really weird errors, and I'm freaking out about what to do.  Hoping someone can talk me off the ledge, I'm talking terrabytes of data.  I am just leaving it as is for now, I don't know what to try.

syslog.txt

[Hit my first hard drive failure]

So I'm still confused... the array rebuild finished and the drive still says unformatted.  Do I just format it it?  What happened to the data that was on it?  I thought when I rebuilt the array it was supposed to rebuild that drive with whatever it had before...

[Hit my first hard drive failure]

Well, I was brave and swapped everything back to the way it was supposed to be and it seems to be rebuilding now   Question though, shouldn't it format the drive before rebuilding the array?  Still says unformatted.

[Hit my first hard drive failure]

Something seems to have gone bad   I replaced the old drive with a new Seagate.  It spun up and assigned my old parity drive as my new Drive 6 with the blue ball, and assigned the new drive as parity with a red ball.  And in the logs I have this:

 

May  7 15:26:09 Tower kernel: md: import disk0: [8,144] (sdj) ST2000DL003-9VT1 5YD2AG1H size: 1953514552

May  7 15:26:09 Tower kernel: md: disk0 wrong

May  7 15:26:09 Tower kernel: md: import disk1: [8,176] (sdl) SAMSUNG HD204UI  S2HGJDWZ807150      size: 1953514552

May  7 15:26:09 Tower kernel: md: import disk2: [8,160] (sdk) SAMSUNG HD204UI  S2HGJDWZ807152      size: 1953514552

May  7 15:26:09 Tower kernel: md: import disk3: [8,192] (sdm) SAMSUNG HD204UI  S2HGJDWZ807155      size: 1953514552

May  7 15:26:09 Tower kernel: md: import disk4: [8,80] (sdf) SAMSUNG HD204UI  S2HGJDWZ807151      size: 1953514552

May  7 15:26:09 Tower kernel: md: import disk5: [8,32] (sdc) Hitachi HDS5C302 ML0220F30A30PD size: 1953514552

May  7 15:26:09 Tower kernel: md: import disk6: [8,48] (sdd) SAMSUNG HD103SJ  S246JD2Z931515      size: 976762552

May  7 15:26:09 Tower kernel: md: disk6 replaced

May  7 15:26:09 Tower kernel: md: import disk7: [8,64] (sde) Hitachi HDS5C302 ML0220F309HPMD size: 1953514552

May  7 15:26:09 Tower kernel: md: import disk8: [8,112] (sdh) Hitachi HDS5C302 ML0220F30A1DZD size: 1953514552

May  7 15:26:09 Tower kernel: md: import disk9: [8,128] (sdi) WDC WD20EARS-00M WD-WMAZA1148665 size: 1953514552

 

 

Can I just swap them back?  I thought it was just supposed to assign the new drive to the missing slot and rebuild the array from there.

[SUPERMICRO AOC-SASLP-MV8 Issue]

Just screenshot your assigned drives so when you replace the controller you can reassign your drives in the correct order.

[SUPERMICRO AOC-SASLP-MV8 Issue]

Honestly I just consider it the price of having an array with 22 hard drives.  I don't boot unless I REALLY have to

[Hit my first hard drive failure]

I'll be honest, I only preclear one cycle... guess I need to start doing more   Good idea on a different PC, I need to do firmware upgrade anyway.

[SUPERMICRO AOC-SASLP-MV8 Issue]

Mine seems to freeze as well, but if I walk away and leave them for 15 minutes my unRaid system finally boots all the way.  I have no idea what takes it so freaking long but it is the SASLPs that it seems to wait on.

[Hit my first hard drive failure]

Well, it finally happened... I lost a drive somehow.  It passed all the preclear, but blew up when unRaid went to write to it.  I am going to follow the steps here:

 

http://lime-technology.com/wiki/index.php?title=Replacing_a_Data_Drive

 

But I wanted to check first whether I should precelar the replacement disk first?  I am nervous about running too long without a functioing array

[New unMENU packages for SABnzbd, Sick Beard and Couch Potato]

So I'm trying to get SAB and Sickbeard up and running.  I followed the directions and the packages show as installed and reinstall on restart.  I didn't change any variables so they should be on 8081 and 8082.  I've tried the start buttons for both, but I'm not getting any response on either port.

 

I telnet'd in and looked around for it.  I found the directories in the /user folder rather than /cache, so I'm not sure what's up with that.  I was able to start them from the command line pointed at the User folder but I'm not sure the implications of that...

[Hitachi 2TB 5K3000 Green drive for $69.99 shipped (Amazon)]

Forgot we had that one now

[Hitachi 2TB 5K3000 Green drive for $69.99 shipped (Amazon)]

I ordered 4 more on Friday and they shipped yesterday, so that's good.  Are these AF drives?  Trying to figure out how I need to preclear them.