Eisi2005

Hi together, the topic says it all, but let me say some words to my situation. Maybe it could help. I run Unraid 4.7 for the last 2 years without any problems. I start with a Asrock G785GXH with 6 sata ports. As all ports are full i bought a 2 port SIL3132 controller and as this hdds are full i bought a SIL3124 4 port controller with pci-express. All went fine at this time. My write speed to array was about 25MB/s. Only my parity check was slow. i have 25MB/S speed at parity check. So i ask me what can i do to increase my parity check speed. I dont know why but my hope was unraid 5.0. So the day comes and i install unraid 5.0 but the speed was bad again, but i have no parity sync errors. So a friend give me a 8 port SAS 3082E-R Controller. It´s only a controller for hdds with max 2 TB but i only have 1,5 TB hdds. I switch in the controller and the speed from parity check goes to 40 MB/s. Ok i thought that was better but others have 80MB/s and more. so what can i do next. then i found in the forum the "unraid-tunables-tester". The scripter says only with 4GB RAM and more it make sense to use this. So i bought 2 GB RAM to come on 4GB RAM. I start the script and it gives me for best performance these values "4728, 2128,2128" I use this values and my parity speed increase to 75 MB/s. Now i was satisfied with the parity check speed. But what was with write speed to the array ? To increase this speed i bought a small 250 GB cache disc. But now the trouble begins, i hope you understand the next words with my bad english. After insert the cache disk, unraid wont boot anymore. The bios shows me all hdds but when unraid should boot from usb stick i become the message to insert a boot medium. So i disable the cache disk from power and then unraid boot. Ok i thought my power supply was to small for all the hardware and i bought a bigger power supply but i have the same situation. Then i tested and switch of a data disk from power, to see if the problem was the new hdd. But if a switch of a data hdd and switch on the new cache disk unraid starts. so it could not be a power problem and not a hdd problem. Long words it was the "new" SAS controller if i take out this controller and switch in my 2 old SIL Controller unraid boot. I´m happy and begin a parity check to see how the speed was. And there i become 1717 parity sync errors. This was a long story and hope someone read it although. As i have insert the SAS Controller the parity disc was on the SAS Controller. So my hope is that there is no corrupt data and only the parrity disc was not ok while the SAS Controller has a defect. But how could i check if the data is ok ? I could make a parrity check and correct the errors but is this the rigth way ? Thanks for any help, if my english was not readable please ask if you need other informations. Eisi syslog-2013-09-15.zip

@Joe thanks for your answer, but to the times where cache_dirs started, the array was not offline. Eisi

@Joe L. sine tonight i have this entries in my logfile. Running unraid 5.0 Sep 13 23:26:25 Server cache_dirs: scheduling via at ./cache_dirs -w -m 1 -M 10 -d 9999 -p 10 -a "-noleaf" Sep 13 23:27:00 Server cache_dirs: ============================================== Sep 13 23:27:00 Server cache_dirs: command-args=-w -m 1 -M 10 -d 9999 -p 10 -a -noleaf Sep 13 23:27:00 Server cache_dirs: vfs_cache_pressure=10 Sep 13 23:27:00 Server cache_dirs: max_seconds=10, min_seconds=1 Sep 13 23:27:00 Server cache_dirs: max_depth=9999 Sep 13 23:27:00 Server cache_dirs: command=find -noleaf Sep 13 23:27:00 Server cache_dirs: version=1.6.7 Sep 13 23:27:00 Server cache_dirs: ---------- caching directories --------------- Sep 13 23:27:00 Server cache_dirs: server Sep 13 23:27:00 Server cache_dirs: ---------------------------------------------- Sep 13 23:27:00 Server cache_dirs: cache_dirs process ID 24124 started, To terminate it, type: cache_dirs -q From where did these entries come ? I have only normaly started cache_dirs -w at startup ? Eisi syslog-2013-09-14.zip

Thanks for your answers Cache is enabled for the share. Without cache i have 25 mb/s write speed. Eisi

Hmmm, when i copy direct to the cache disk i have write speed about 60 mb/s If i write to the cache over the array i have write speed about 40mb/s. Is there anything i can do to become the same speed ? Eisi

Hi, thanks, life could be so easy. Eisi

Hi, thanks for your answer. Maybe i dont understand the function of the mover. But if i put a new movie on the cache drive i must create the folder structe i have on my share to see the movie just in time in my "secure" raid. If i dont create the file structure i didnt see the movie in my protected server and mover could not move the movie to the right direction. So i must every day create new the dirs /server/Filme/A-C as example. For my personaly use i found it better when mover only move the files in these directories Eisi

Hi, since yesterday i have installed a cache drive. All works fine for me, tonight all files got moved to the array. But then i saw that my dir structure on the cache disk get deleted also. I search in the forum and found this thread, but i could not read the code, sorry i´m not a scripter Here is my code of the mover script: if [ ! -d /mnt/cache -o ! -d /mnt/user0 ]; then exit 0 fi # If a previous invokation of this script is already running, exit if [ -f /var/run/mover.pid ]; then if ps h `cat /var/run/mover.pid` | grep mover ; then echo "mover already running" exit 0 fi fi echo $$ >/var/run/mover.pid echo "mover started" cd /mnt/cache for Share in */ ; do if [ -d "/mnt/user0/$Share" ]; then echo "moving $Share" find "./$Share" -depth \( \( -type f ! -exec fuser -s {} \; \) -o \( -type d -empty \) \) -print \ -exec rsync -i -dIWRpEAXogtO --numeric-ids --inplace {} /mnt/user0/ \; -delete else echo "skipping $Share" fi done rm /var/run/mover.pid echo "mover finished" if [ -f /tmp/mover.sync ] then for i in `grep disk /proc/mdcmd | grep diskNumber | sed 's/.*=//'` do /root/mdcmd spindown $i done rm /tmp/mover.sync fi My dir structure on my parrity is: server/Filme/A-C server/Filme 3D/A-C server/Bilder/ So i make dirs on my cache disc called: server/Filme/A-C server/Filme 3D/A-C . . Now i want that the script dont delete these "Top-Level" dirs after moving. Could anyone help me with the code ? Thanks Eisi

Hi, reiserfsck shows me some errors, after reiserfsck --fix-fixable all seems fine again, the array started normaly. Should i do now a parity check ? Eisi

Hi, i´m running unraid 4.7. after an reboot at the morning i have many many red entries in my systemlog for md9. Is there something i can do ? I must say that i´m a total linux noob, but unraid run the last year without any problems. This is my first problem with one drive ? Edit: Should i run a check disk ? reiserfsck --check /dev/md9 ?? At the moment i copy my files from md9 to a usb drive, n hope to get all files from disk Thanks for your help. Eisi syslog-2013-09-01.zip

Thanks for you help

@dgaschk thanks for your answer and help. Where in which line did you see that it seems disk 9 ? Greet Eisi

Sorry for the forgotten logfile I´m running unraid 4.7 Greet Eisi syslog-2013-08-09.txt

Hi, i found this entrys today in my logfile. Aug 8 14:31:16 Server kernel: ata2.00: exception Emask 0x10 SAct 0x0 SErr 0x80000 action 0xe frozen (Errors) Aug 8 14:31:16 Server kernel: ata2.00: irq_stat 0x01100010, PHY RDY changed (Drive related) Aug 8 14:31:16 Server kernel: ata2: SError: { 10B8B } (Errors) Aug 8 14:31:16 Server kernel: ata2.00: failed command: READ DMA (Minor Issues) Aug 8 14:31:16 Server kernel: ata2.00: cmd c8/00:08:3f:00:54/00:00:00:00:00/ea tag 0 dma 4096 in (Drive related) Aug 8 14:31:16 Server kernel: res 4c/04:00:00:00:00/00:00:00:00:4c/00 Emask 0x12 (ATA bus error) (Errors) Aug 8 14:31:16 Server kernel: ata2.00: status: { DRDY DRQ } (Drive related) Aug 8 14:31:16 Server kernel: ata2.00: error: { ABRT } (Errors) Aug 8 14:31:16 Server kernel: ata2: hard resetting link (Minor Issues) Aug 8 14:31:23 Server kernel: ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 0) (Drive related) Aug 8 14:31:23 Server kernel: ata2.00: configured for UDMA/100 (Drive related) Aug 8 14:31:23 Server kernel: ata2: EH complete (Drive related) How could i find out which harddrive makes the problem ? Greets Eisi

Release 5.0 but give an exact instruction to fall back to 4.7. so every people could test 5.0. If it is ok fine, if not people could go back to 4.7

@dgaschk you are rigth, no new errors after checking again, thanks. Greets Eisi

@jonathanm the parity check has finished and the super.dat has a new time stamp. No error message with write access on super.dat. This is the good news. The parity check says the following: Last parity check < 1 day ago . Parity updated 3 times to address sync errors The parity check start from alone after rebooting the server, so i don´t know if the check correct the parity or not ? I have make a short smart test for all my disc, the reports and the syslog are in the attachment. All disc seems to be fine what i could see, only Datadisc 1 seems to have a problem. The smart status report for disc 1 says that the check was aborted after 90%. I have started the check 4 times and every time the same message. Is this a problem ? Must i do anything ? Could you give me a hint again ? Greets and many many thanks Eisi Logfiles.zip

@jonathanm yes i have a backup of my config folder. I have now make the filecheck on my win7 pc. The check deleted the complete custom folder and correct some files. Now i have boot the unraid again, i dont have anymore the fat filesystem errors. Nov 1 14:38:02 Server kernel: fat_bmap_cluster: request beyond EOF (i_pos 1793675) Nov 1 14:38:02 Server kernel: FAT: Filesystem error (dev sdb1) (Errors) Now a new parity check has started. Is this ok ? If the parrity check writes the super.dat. Could i then use the version of unraid that is on my stick now ? What should i do with the 3 errors from last parrity check ? Should i do a smart check ? Greets and thanks for your help Eisi

@jonathanm first the parity check have finished so i could test your hint in the afternoon. But now is parity finished and i got these error msg in log. Nov 2 08:45:18 Server kernel: md: parity incorrect: 2930275568 (Errors) Nov 2 08:45:18 Server kernel: md: parity incorrect: 2930276080 (Errors) Nov 2 08:45:18 Server kernel: md: parity incorrect: 2930276592 (Errors) Nov 2 08:45:18 Server kernel: md: sync done. time=58307sec rate=25128K/sec (unRAID engine) Nov 2 08:45:18 Server kernel: write_file: error 30 opening /boot/config/super.dat (Errors) Nov 2 08:45:18 Server kernel: md: could not write superblock from /boot/config/super.dat (unRAID engine) Nov 2 08:45:18 Server kernel: md: recovery thread sync completion status: 0 (unRAID engine) Is this important ? Greets Eisi

@jonathanm Thanks for your answer. Could i try the file system check with a normal win 7 pc ? Greets Eisi

Something that i noticed. I dont have any rights on the flash dir. With root i could not delte anythin in these dir. Greets Eisi

Hi all, i have added today a new 4 port controller from silicon image 3124, with one new 1,5 tb disk. I´m running unraid 4.7. After Starting server , i must add the new disk and all was fine, after formatting the server share comes back and i could see all my files. Then i want to start my cache dirs and see in my /boot/custom folder many dirs and files with crypted signs. And my sh files i have put there where gone. In the log file i have massiv errors with : Nov 1 14:38:02 Server kernel: fat_bmap_cluster: request beyond EOF (i_pos 1793675) Nov 1 14:38:02 Server kernel: FAT: Filesystem error (dev sdb1) (Errors) Could someone help what to do ? Could i delete these files ? Could i install cache_dirs new ? These are the files in the custom folfer: Greets Eisi syslog-2012-11-01.zip

@ljh89 Thanks for your answer. sometime could the solution so easy. Greets Eisi

Hi, i have one share called server (\\server\server) Is there a way to give 2 different user control on this share ? I want one share for me to have write access and one share for my kids with read only access ? Greets Eisi

@Joe L. Thanks for your hint, but it did not work mount: mounting //192.168.xxx.xx/server on /storage/server failed: Invalid argument Greets Eisi