papnikol

Hallo, everyone I have messed too much with some settings with my array USB stick and I want to start completely clean. I have not found anywhere a mention of the location of array configuration regarding the disks. I mean, a file where the position of each disk is saved, e.g. which disk is parity, which is disk1 etc. This would allow me to perform a clean install without having to validate parity again. Could you please help?

Hi everyone, I am currently building a new server and I will soon have to buy a new PSU since the one I have is non-modular. I would like a few suggestions for a PSU that is not too expensive. Bear in mind that I live in Europe (Greece), although I think that PSUs do not vary as much as some other components between various continents. Some extra info: 1. The Server will ultimately have at least 15 HDDs (mostly WD Green, although the parity and 1 or 2 other drives might be WD Red) 2. Ideally the PSU will have as many as possible SATA cables 3. The main system specs: Asus P5Q Deluxe Mobo, Intel Core Quad CPU Q9550 (2.83GHz), 8GB RAM, primitive PCI graphics card and soon 1 or 2 SAS2LP-MV8 cards Thanks in advance for your input

Yes, that's a nasty Catch-22 ... guess you just need to live with it until Brian updates MyMain. I vaguely recall a discussion about this a few months ago ... are you sure you're using the most current version of MyMain in UnMenu? It MAY have already been resolved. On the User Scripts page in UnMenu, click on the "Check for UnMenu Updates" button ... then scroll to the bottom of that page and see what it found. For some reason, it was not fully updated, but I performed an update, and a few packages were updated except for 3: 5a0630afc49c196a23db71a5d02bf18f != a5d02879e3d52eb0dffda20f12d0111c or 7799da8e46bf08d7a328617cb1a48442, /tmp/unmenu_tmp/myMain_local.conf not installed d0b27d3a4d9a936a384ec34bb24f85e6 != d41d8cd98f00b204e9800998ecf8427e or d41d8cd98f00b204e9800998ecf8427e, /tmp/unmenu_tmp/powerdown-1.02_ctlaltdel-unmenu-package.conf not installed 9c1682566014551ded33dc8a79aff891 != 8c17090fc9a1f215d3e86731f1131f73 or 4e08b8911d69f27f8d6197e95d6985c7, /tmp/unmenu_tmp/unraid-swapfile-unmenu-package.conf not installed But this may or may not be a different problem I guess. Still after updating (current version: Version 1.6 Revision: 278) and restarting unmenu, I see no difference in myArray. The id problem has been fixed, I still worry a bit about HPA although I am 99% positive that it really is not an actual problem

Thanks for your response, that's what I thought, too. But in order to change the "hpa_ok" attribute I have to access the settings page which is done by clicking on the disk id. And, as I already mentioned, my id field for the specific drive is empty.

Hi everyone, I am building a new unraid system and started with a WD 6TB Red (WD60EFRX). I just precleared it and added it as parity drive. MyMain has the "HPA?" warning on it. I should note that the Mobo is not a gigabyte and additionally I tried the command I show elsewhere in the forum: dev/sdc: max sectors = 11721045168/11721045168, HPA is disabled So I am guessing it is a bogus warning. I wanted to disable it but i noticed the disk has not an ID. But: hdparm -I /dev/sdc|grep Serial returns a serial number My questions are: 1. Am I right to believe the warning is not correct? 2. If so, how can I remove the warning? 3. Does the lack of id in MyMainsignify a problem? [uPDATE: Ignore question 3. The HDD got an id when I added a second drive. Obviously, for the id to be shown, there an array must have been created]

The PSU is a very good quality 850W one: Corsair CMPSU-850HXEU PSU. I have added recently a new parity drive 3TB in order to use new 3TB data drives in the future. The previous 2TB parity drive replaced a 1TB data drive.

Hi everyone, I have a problem that happens often lately. Unexpectedly, a data drive becomes red-balled and I have to rebuild data (which is no small feat, i have 18 disks on a SATA I Mobo). It happened again yesterday so I proceeded as before. When I came back home today I saw that the data rebuild had been stopped and the drive was still red-balled. Additionally, at a point, I saw 3 more drives being red-balled. I restarted and I saw that only the original drive was still red-balled. The only info I can add is that the first red-balled drive and the consequent 3 were all on the same miniSAS-to-4SATA cable so I think this may be the culprit, but, still, this behavior is strange. How could 3 drives be "de-red-balled"? Any advice as to how I should proceed in general? (Currently I am trying to rebuild data again) Additionally, do you know a good place in Europe where I could find such cables? (I live in Greece) Thanks for any help. PS :I erased some of the syslog because there were the same lines repeating thousands of times syslog-2013-02-28_limited.zip

Thanks, now i remember where I had seen it before... I didnt know that. I have precleared one more 3TB HD but I did not notice that. Thanks for the info.

Hi everyone, I precleared a 3TB HD and by mistake I let it define a starting sector of 1. Is there someway I could change the starting sector to 1 or do I have to preclear again? I am certain I have seen a similar post but I cannot find it... Thanks in advance for your help.

First of all, thanks for your feedback. Now, for some extra info: 1. I am using Windows 7 64 2. I followed the instructions from the provided URL but there was no change (to be honest, that is what I expected; I hadn't changed anything in my PC and previously I used to get reading speeds >30MB/s). 3. I measure the speed by the indication of the copy window on my Windows PC (I use teracopy, which report 9). Additionally, the 'Disk Performance' tab of unMenu is reporting a speed of around 4500KB/s (exactly the half). The numbers I report are not even average speeds for lots of small files but for just a big one. The absolute proof is that an 8087MB file took minutes to copy from unRaid->PC. So the actual speed is 9MB/s. 4. I think (but cannot be absolutely certain) that this problem might have appeared after upgrading from 4.7 -> 5.10. I know for certain I had no such problem with 4.7 but I cannot wuite pinpoint whether the read speed was so low immediately after I upgraded or it became slow later.

Here it is. I didn't post it cause I thought there is nothing wrong with it but, truth be told, some of the messages seem like Sanskrit to me. syslog_2013-02-12.txt

Hi everyone, My array is based on an old mobo (SATA I). My main problem is that, having 18 disks means a bit less than a day for a parity check, but otherwise, eveything is fine. My only problem is that although I have a write speed of 25-40MB/s, my read speed ranges from 8.3-9.3MB/s. This is not terrible, but obviously does not make sense. Any suggestions?

There is a new service called bitcasa that claims to offer unlimited storage and client-side encryption for $70/year. There might be a catch and if they fail, which is probable since I cannot think of a viable unlimited storage business plan (although they use convergent encryption which probably saves lots of space), you lose your backup. but it seems interesting...

Under 'E-mail Notifications' on the 'Settings' page', change, 'Email Frequency' to 1440. That will cause it to only send an E-mail once a day. Ok, I am embarrassed , I never noticed that Thanks a lot

Thanks, that is good to know in case an unexpected situation arises. I am currently rebuilding parity using a new 3TB HD and I though of another instance that could be useful: If during a parity rebuild, a data disk became redballed (not because it were faulty but because a cable moved), I would have to trust my array and rebuild parity.

Hi everyone, SimpleFeatures is excellent but I have a tiny problem. The main page creates too high rows which means that when you have lots of disks (i have 19+parity) you have to unnecessarily (even in full screen) scroll in order to view everything, especially if you want to view the info and options at the low end of the page (status, reboot, etc) which are also unnecessarily distant from each other. I know I am nitpicking, but still, I wonder if there is an easy way for me to fiddle with SimpleFeatures in order to change the html?

You are obviously generally right. But there might be few chances that a drive got red balled while reading from it (that is what happened in my case, the parity drive was spun down and I knew it was a matter of a cable and not a problematic disk, although it was the first time i saw a red ball while reading). Additionally, I can imagine a situation where you feel that a second disk is in danger and you are in hurry to restore the red balled one lest you lose the other (even if that costs you a few missing bytes). That is good. I was just wondering because I saw some posts that said the 'trust my array' procedure does not work. E.g.: http://lime-technology.com/forum/index.php?topic=14830.msg139730#msg139730

So, there is no way to trust my array in unraid 5; Or is it not safe yet?

Thanks for the help with php. I commented the line in the go script because I thought that its existence in \boot\custom\etc\rc.d made it obsolete. obviously i was wrong. As always, thanks a lot Joe.

UPDATE: Joe explains the (very easy) solution to my problem in his reply. Hi everyone, I just moved to 5.0rc10 and everything works fine unmenu is updated and works flawlessly but for one (important) feature: I download and install packages but on reboot they show undownloaded and obviously uninstalled. I should say that in my script I had the line: cd /boot/packages && find . -name '*.auto_install' -type f -print | sort | xargs -n1 sh -c but when i uncommented it after installing and verifying in the 5.0rc10 installation i get a scrambled html page in normal main home page. so i commented it again and the main page is back to normal. I also noticed that i have the \boot\custom\etc\rc.d directory which contains a file 'S10-install_custom_packages' that contains the aforementioned line of code so everything should work fine. But still, packages show undonloaded,uninstalled. Should I wipe the /boot/packages (which is actually full of package files) directory and try from the start? Any other possible solution?

Thanks dgaschk, I already did that and, indeed, it worked fine. But the other question is still valid, how would i go about implementing a 'trust my array' procedure?

Hi everyone, I have recently managed to move to unraid 5.0 rc10. Unfortunately, some time later, i got a red balled data drive which i know is due to a cable problem. I understand that the trust my array procedure does not work anymore. 1. Somewhere in the forum i show that I could use utils->new configuration and then there will be a choice to trust the parity. does that work? 2. If, instead, I want to rebuild my data drive, using the trusted parity, how would I do that in unraid 5?

No, disk 6 shows no errors. Unfortunately, the parity check showed 866 errors, but I am thinking they might be due to the repeated hard restarts (Sorry for taking so long to respond while you try to help, too much work this week)

At my 4th-5th attempt to restart, everything started fine. I really have no clue why that happened, I changed nothing and now I am wondering if I should do the parity check in case the same thing happens again....

I see what I think I am supposed to see. the login prompt. and i can login normally. PS: i attached the syslog. i think i see something irregular (and a bit scary). Those 2 messages repeating a lot: Jan 14 00:14:50 Tower kernel: handle_stripe read error: 1000/6, count: 1 Jan 14 00:14:50 Tower kernel: md: disk6 read error Jan 14 00:15:21 Tower kernel: sas: --- Exit sas_scsi_recover_host Jan 14 00:15:52 Tower kernel: sas: command 0xf2069240, task 0xf29cd640, timed out: BLK_EH_NOT_HANDLED Jan 14 00:15:52 Tower kernel: sas: Enter sas_scsi_recover_host Jan 14 00:15:52 Tower kernel: sas: trying to find task 0xf29cd640 Jan 14 00:15:52 Tower kernel: sas: sas_scsi_find_task: aborting task 0xf29cd640 Jan 14 00:15:52 Tower kernel: /usr/src/sas/trunk/mvsas_tgt/mv_sas.c 1701:mvs_abort_task:rc= 5 Jan 14 00:15:52 Tower kernel: sas: sas_scsi_find_task: querying task 0xf29cd640 Jan 14 00:15:52 Tower kernel: /usr/src/sas/trunk/mvsas_tgt/mv_sas.c 1645:mvs_query_task:rc= 5 Jan 14 00:15:52 Tower kernel: sas: sas_scsi_find_task: task 0xf29cd640 failed to abort Jan 14 00:15:52 Tower kernel: sas: task 0xf29cd640 is not at LU: I_T recover Jan 14 00:15:52 Tower kernel: sas: I_T nexus reset for dev 0400000000000000 Jan 14 00:15:52 Tower kernel: sas: I_T 0400000000000000 recovered Jan 14 00:15:52 Tower kernel: sas: --- Exit sas_scsi_recover_host