moose

Thanks for the detail kevinsyn. Very inventive solution! I like the idea, the only problem I would have is that my power supply (TX-850 V2) has an intake fan on top and I would be afraid to mount the HDD cage (or foam) atop that intake fan. I wonder how much clearance the PSU intake fan needs for airflow. Since the PC-A77F case has so many PCI brackets, I'm going to see if there is a internal case HDD bracket that might use 1-2 spare PCI brackets but allow suitable airflow for the power supply. This might work since the motherboard (X9SCM-F) is a microATX.

Can you please post a picture(s) of the "separate rack" and/or elaborate a bit of detail on how you mounted this inside the case? I am in-process of building a very similar setup, (same MB, case and SM cages) and would like to find a creative way to mount the SSD cache drive inside the case without taking up one of the 20 slots in the 4x Super Micro 5-in-3 cages.

You can purchase a Supermicro AOC-SASLP-MV8 8-Port SAS/SATA Add-on card for $83.29 at Superbizz if you enter the coupon code "HOMERUN", which gives you a $14.70 discount. If you purchase more than one card, the discount is spread among the multiple cards. http://www.superbiiz.com/detail.php?name=AOC-SASMV8

Should I hold in the power button to force the unRAID server to shut down? What is the worst that could happen as a consequence? A parity check on re-boot?

I issued the "lsof /mnt" command from telnet, no luck... Then went to the "Array Management" tab in unmenu and clicked "Stop Array", no luck... Results of "lsof /mnt" below: root@Tower:~# lsof /mnt lsof: WARNING: can't stat() fuse.shfs file system /mnt/user Output information may be incomplete.

Hi, I'm now attempting to power down the server but disk5 is stuck unmounting. I've searched the forum messages for examples and tried several commands to identify the process(es) that might be causing the problem but am stuck. Can someone please look at the ps ux_output file and/or the latest syslog (attached to this message) and help me out? I'm not sure what to do next. I'm running v4.7 Thank you. ps_ux_output.zip syslog-2012-04-03.zip smart_report_of_disk5.txt

This morning the web interface was unavailable however I was able to properly powerdown the server via console and reboot. After rebooting the web interface was working again. I looked at the syslog. I noted memory, unmenu and other errors. I may power down the server again and reseat all 4 memory modules. Can someone please take a look at my syslog (attached) and help me understand all the error messages? Thank you. unraid_syslog-2012-03-31.zip

Thank you. I could not get a smart report. The drive was definitely bad. Fortunately the Seagate drive was still under warranty (5 years) and I was able to RMA it. The replacement drive will be here next week. Before sending the drive back to Seagate I tried the "freezer trick" and Darik's Boot and Nuke, however the disk wiping process only completed about 30% before the drive warmed up and started failing again (clicking sound). Seagate's policy is that they destroy all data if they refurbish the drive for another user, so I was comfortable getting a warranty replacement drive.

I've added all my system details and attached the full syslog (zipped). I didn't notice the drive had failed until after I left for work this morning, however now that I'm home I went down to the basement where the server is kept (cooler in basement) and the drive is making a clicking sound ~ once a second, so it might appear the drive does indeed have mechanical failure. marcusone, disk #4 did show up during boot and I believe was good until the re-sync process started (I did not receive any automated emails indicating this drive failed until the re-sync). I just rebooted the server and now disk #4 is showing "not installed". Before this last reboot, I think disk #4 indicated "disabled". I'm attaching the new syslog since I rebooted. The drive has failed, correct? Since there is no further protection from a drive failure and I don't have enough free space to recover protection in the array, I should turn off the unRAID server until I get a replacement drive, correct? syslog-2012-03-01_b.zip

Hello, During the monthly parity resync process (last night), the resync process worked ok for the first two hours then I started to received notifications "unRaid Failure Notification - One or more disks are disabled or invalid". The disabled disk was disk #4. I also stopped the array this morning after receiving the disabled disk notification. First a bit of background and then my question. [*]On 2/6/12 I accidentally deleted files/folders in a unraid share (disk #4). After a bit of research on these boards, I found a discussion that explained how to recover the deleted files/folders. However, initially I started executing the undelete/recover commands below from console with the array stopped, then realizing that the array needed to be started for the commands to be executed, I started the array and successfully issued the commands. [*]I was able to recover the files/folders and the array (including disk#4) ran successfully until this morning when the monthly resync process started. From 2/6/12 through 2/29/12 I was able to read and write from disk #4 with no problems. Then I received the disabled disk message. [*]The only resyncs have been (2/1/12) - successful and (3/1/12) - unsuccessful. Questions Do I really have a failed disk (disk #4) or is this somehow related to the process I used to recover files on 2/6/12? Remember on 2/6/12 I started executed commands below and stopped the array before realizing that the array needed to be running for the commands to be executed. What steps do I take next and how do I ensure I don't lose any data? I've attached the syslog to this message...lots of repetitive information. If there is any other info needed, please let me know. I also am trying to run a smart report ("smartctl -a -d ata /dev/sdc") on drive #4 but am getting "Smartctl open device: /dev/sdc failed: No such device". Thanks, moose stop samba [all your shares will disappear from network] killall smbd nmbd un-mount the disk (md1=disk1, md2=disk2, md10-disk10, etc. Use the correct disk for your needs. this example is for disk1) umount /dev/md1 note the above command is umount, not unmount. run reiserfsck on the disk to rebuild the file tree. Any files that can be recovered will. This process could take many hours for a large disk as the entire disk will need to be scanned. reiserfsck --rebuild-tree -S /dev/md1 It will ask you to confirm the rebuild of the file tree. Make certain you answer Yes (three letters, Capital "Y", lower case "es") Anything else will be considered as "no" re-mount the disk (again, use the correct "md" and "disk" for your situation) mount /dev/md1 /mnt/disk1 re-start samba /usr/sbin/smbd -D /usr/sbin/nmbd -D your deleted files (any that could be recovered) will be in a lost+found folder on the disk. syslog-2012-03-01.zip

I apologize if this has already been answered. Two questions: 1. Once I recover the files in "lost+found" how to I effectively decrypt the original file name? 2. For some reason the "disk share" is still visible even though I copied the "lost+found" contents to a local pc , deleted the "lost+found" folder from the disk and set "Disk shares (SMB)" to "Don't export" Any ideas? Running unRAID Server Pro v4.7 Edit: Further research indicates there is no easy, straight-forward method to decipher the original file name. The date time stamp and file size seem to be the best clues. Also, I found out that stopping and restarting the array eliminated the "disk share" that was still visable. I answered my own questions.

Not trying to steal buxton's opportunity, however I have a ASH-1233 card for sale if anyone is interested...$10 obo.

I am running version 4.7. I installed a Supermicro CSE-M35T-1B 5-in-3 drive cage and inadvertently moved some drives to different sata ports, when I booted the server the I received a similar message regarding missing disks ("ERROR:TOO_MANY_MISSING_DISKS"). Once I reassigned the correct drive as the parity drive, the array worked properly again. I don't think it's your power supply.