dikkiedirk

I have 3 disks inside a CSE-M35T and those lights just flash on/off ever 1-2 seconds. With no SATA cables attached at the moment. The other thwo are out with a disk inside. Is that normal behaviour?

What I find strange when looking at the syslog is that at 14:52:32 I see Drive inventory and subsequent lines and that this sequence of lines is repeated several times. The entire boot takes 8 minutes!!

Happened to me too, but was a RMA from Western Digital Germany.

I experience long boot times on my server at the moment and sometimes it just hangs on the attached screen. Can someone help me to find what is wrong? Or in which direction to search? The system specs are: X9SCM-F, 16 GB Kingston RAM, E3-1240, M1015 controller, Areca ARC 1200 controller. The system finally booted, I attach a syslog after boot. syslog-2012-12-10.zip

Has the error underneath in red got something to do with the mover? what does it mean, why does it happen. Untaid version is 5.0 beta12a. Dec 9 22:03:52 Tower1 logger: .d..t...... videos/ Dec 9 22:03:52 Tower1 logger: .d..t...... videos/Blu-Ray/ Dec 9 22:03:52 Tower1 logger: .d..t...... videos/Blu-Ray/They Live/BDMV/STREAM/ Dec 9 22:03:52 Tower1 logger: >f+++++++++ videos/Blu-Ray/They Live/BDMV/STREAM/00004.m2ts Dec 9 22:04:22 Tower1 kernel: CIFS VFS: did not end path lookup where expected namelen is 0 Dec 9 22:05:08 Tower1 last message repeated 5 times

What broken? Then how do I access it? Maybe not entirely broken, but there seems to be something wrong with it. See earlier in this thread, some users are upgrading Samba to 3.6.8.

I want to upgrade to RC8a coming from beta12a. I was told and read in this thread that Samba is broken in this release. What is the correct way to upgrade Samba? Is there gonna be a RC9 with fixed Samba?

Thanks Joe, is there gonna be a RC9 with updated Samba? I rather wait for that. Is the samba fix as described in the thread persistent?

I made an additional step: I transferred my setup,which was housed in a HP EX490 homeserver housing and Sans Digital eSATA tower to a new Lian Li case with Supermicro drive cages. The transfer went OK so far, server booted with all drives assigned correctly and array started. Now running a parity check at 112 MB/s. I still use 5.0 beta12A is there a urgent reason to upgrade to 5.0 RC8a? I use a X9SCM-F with a flashed M1015.

Data rebuild in progress now, going at a low speed of approx. 35 MB/s. One of the drawbacks of an eSATA tower. Time to build all drives in one case. A lot less clutter and less prone to errors. And faster off course.

Thanks Joe, I knew I missed something. Will the rebuild automatically start after reassigning the drive? When I now play a file that is on this drive, will it in fact be "reconstructed" from the parity disk?

Can someone pls help?

Probably due to a power outage early this morning . My server is behind a UPS, but I have an eSATA tower with some drives attached which are part of the array, and this tower wasn't behind the UPS . I saw it in the log of the UPS.

Just an hour ago I rebooted my unraid 5.12a server because I couldn't write to my shares. When the reboot finished I noticed a red-balled drive (disk7 sdf). This drive is mounted in a eSATA tower and there was a power-outage. This tower wasn't on a UPS, while the server where it is connected to is. What is the best thing to do now? Can I just stop the array-unassign the drive-start the array-stop the array-reassign the drive-start the array? Do I risk that the drive is getting cleared and formatted in this sitation? Is it better to unassign the Parity disk too? Syslog is attached. syslog-2012-12-02.zip

When i go to a share on my unraid server with a Windows 7 laptop I cant create a new folder. I can acces all folders and read from them but writing is not possible ISecurity is set to public

Today I stumbled upon problem. I tried to delete a directory from my server with an attached Windows 7 laptop. I got a message that it could not be deleted because it was open in another program. I then tried to delete the file in a telnet session with MC. I still can't delete the directory because it is not empty. There is indeed a file like shown in the attachment. Where does this file come from and how to delete it? It's over 38 GByte.

U live in Europe? I would say DEVOLO AV 500 Or Netgear. But if you have coax cable all through the house I recommend MOKA 16 from Hirschmann.

How well is NFS implemented in unraraid 5.0. RC8? Does it offer better speeds for streaming to mediaplayers than SMB? What is the correct way to set it up, is just enabling NFS enough? After enabling it, I see this in the syslog: Nov 24 19:44:56 Hal emhttp: Start NFS... Nov 24 19:44:56 Hal emhttp: shcmd (80): /etc/rc.d/rc.nfsd start |& logger Nov 24 19:44:56 Hal logger: Starting NFS server daemons: Nov 24 19:44:56 Hal logger: /usr/sbin/exportfs -r Nov 24 19:44:56 Hal logger: /usr/sbin/rpc.nfsd 8 Nov 24 19:44:56 Hal logger: /usr/sbin/rpc.mountd Nov 24 19:44:56 Hal mountd[6278]: Kernel does not have pseudo root support. Nov 24 19:44:56 Hal mountd[6278]: NFS v4 mounts will be disabled unless fsid=0 Nov 24 19:44:56 Hal mountd[6278]: is specfied in /etc/exports file. Is this OK? How to check the NFS mounts?

I also wouldn't trust a disk with pending sectors. I had some bad experiences with some WD20EARS: started with a few pending sectors, but like an avalanche their count grew till the disk was RMA'd. The disk that I now have has been added to the array. The last time I checked there are still no pending sectors and the other values stay the same. Keeping an eye on it though.

These are the reports of the drive. Please give me your opinion. Can it still serve as an array-drive? preclear_start__JK1121YAG7SHTS_2012-11-17.zip

I understand, that is why I said "If ever" .

Would you put such a drive in an array? It's a Hitachi 7k2000 out of warranty.

Do you have a link to those enclosures? Are they eSATA or USB? unraid is booted of a USB stick and can work with eSATA enclosures.

Go ahead, try it. It doesn't hurt. If you want to add 3 TB disks I recommend to start with version 5.0 RC8.

Thanks Joe, I'll report back later with full results incl. SMART report. This is a problem disk where SMART showed 15 reallocated sectors before doing the preclear. See if this has worsened.