kifysara

@Kaj your guide worked. Thanks a bunch!

Hey all, I just tried flashing my IBM ServeRAID M1015 card, using the tools kindly provided by @Fireball3, but I get the "No LSI SAS adapters found!" error on FreeDOS (during the 1st step). I am attaching a pic from the card's initialization phase during boot, which shows its current status. Any workarounds/ideas?

Do we know if any of the unRAID-compatible HBA cards are shorter than 6'', so that they can fit into the DS380 without sacrificing one drive slot? Most LSI cards and clones I've looked up are 6.6'', so probably too long to fit.

Thank you again for your help! I'm in the process of buying a card off eBay. Is there something to be careful about or preference when choosing manufacturer/type of card, or are all LSI 9200-8i clones created equal and I could just go for the most affordable option?

Thank you, guys. I'll get him the 54W one.

Dear all, I've been asked to build a new DS380 setup for a (jealous!) friend and have a couple of questions, in case you can help out. Considering the Asus P10S-i as a mobo, 16GB DDR4, 300W Silverstone SFX PSU, along with a Pentium G4560 Kaby Lake CPU. Do you happen to know if the stock CPU cooler that comes in the box will fit in the DS380? Moreover, does it make any sense to pay some more for the G4560T (35W version) of the CPU, to sacrifice some performance for lower consumption (and perhaps lower noise)? Not exactly sure how we'll setup unRAID at this point, but considering he's not very tech-savvy I don't believe he'll need any heavy work (e.g. transcoding) on it.

Great info; thank you. Would it make sense to go for an H270/Z270 motherboard instead? Some models, such as the Gigabyte GA-Z270N-WI-FI or the ASROCK H270M-ITX/AC, can be bought for the same price. A server-class alternative would be the Asus P10S-I.

Thank you for your input, guys. Appreciated. So, if I got it right, I'll need an HBA card instead of the Syba I bought and then a SAS to SATA cable (e.g. like this) that goes to the DS380 or, alternatively, a SAS cable between the boxes and then a bracket like this on the DS380 side? Any recommendations for affordable HBAs that work OK with the Gen7/Unraid combo? Perhaps the one mentioned here?

Hello all, As my G7 Microserver is now full of HDDs, I was looking for expansion options. I have already bought a SATA/eSATA card from Syba (this one), and, while I considering the usual options that come in these threads (e.g. ICYBox enclosures like the MB561U3S-4S), I came across a good deal on the Silverstone DS380 that I just couldn't resist. Perhaps I will use this case to build a stronger, more versatile NAS and replace the HP in the future, but for now I would just like to use it as a "dumb" box, like the ICYBox cited above, to expand the Microserver's storage via eSATA. Nevertheless, I am not quite sure about what I will need to purchase to achieve this, other than a PSU for the DS380 to power the drives. In other words, assuming I install 3-4 disks and a PSU on the DS380, how can I "bridge" their SATA cables and route them through a single eSATA port? I assume some sort of controller does this in standalone expansion boxes like the ICYBox, but not sure the exact product(s) I would need to buy, also considering that there will be no mobo/cpu in the DS380 for now. Any ideas are appreciated. Best Regards, Kostas

Nope, I begun my Unraid adventures with 5.0.5. But what you say (errr..write) makes sense, as I often use MC to transfer files between shares. Thanks for the tips; will keep them in mind!

Thanks for the prompt reply, Bob! I was not aware of the "newperms" thingie. It seems to do the trick; everything works as intended now (at least with my shares set as public). Is that something I need to run every time I change the share permissions?

Hey all, I'm trying to edit some files on my SMB shares (Unraid 5.0.5 on HP Microserver) via my desktop PC (Win 7, 64bit). While (I thought) I had all the shares set up properly, I often notice some glitches, in that I can delete *some* folders/files of a certain share but I get errors when trying to do the same for other folders/files on the *same* share! What's more frustrating is that this behavior persists even when setting the share to public. To give an example: I have a "TV Shows" share, where you can find "Show 1" and "Show 2". The share is set to public (for troubleshooting purposes). I can edit & delete files in "Show 1", but I cannot do the same for "Show 2"; I can actually edit the files of in "Show 2" but when I try to delete them I get the attached error message. So, for some of my Shows/Movies/whatever, I have to connect through Putty and delete the folders via terminal, which is not really practical. Tried restarting the server and the desktop, as well as play around with the share settings, but no luck - I still need to get permission from that "nobody" guy. Any ideas on how to solve this?

Great work! Re. memory utlization, if you guys visit the Stats -> System Stats page, you'll see that most of it is cached.

Nope, the only optimization I tried was the tunable settings, but that didn't do much good, as you can see from my earlier posts. Regarding reads, I suspect the bottleneck is in my network, as the drives are read at >100MB/s during other operations. In real use, though, the difference between 75MB/s and 100MB/s is not really noticeable. Writes could be a bit faster, but I don't write to the array that often (transfers are handled via mover transparently), so I'm not that fussed about it either. Things are a bit crazy at work right now, but when I get some free time I may investigate this further for the fun of it. Haven't been to TheBay for a while, but I think mine was the newer version (based on the one HP released in early 2013). You can find it here That's strange. Perhaps something is messed up with the USB stick/unRAID environment? Check the syslog for anything suspicious.

We could have an "Oh f!@#%" icon to represent multiple errors.

I like it! Dynamix keeps getting better and better. It'd be nice to have the parity rebuild status show up in the "Parity Status" section. Only other thing I can think of is to have all the Faulty/Overheated/SMART stuff group together (as they're all related to disk health). The easiest approach would be to just move the "Unassigned" category up the list a bit. Better yet (IMHO) the fault conditions could all be represented in one line and replaced with icons (with a tooltip explaining what each icon means, much like what happens with the disk status circles/icons in the Main view). I've taken the liberty to edit the Dashboard to help visualize my two suggestions (the attached fault icons are from Google images).

Two drives + parity + an SSD cache drive, to be exact! Also got me a new WD Red that I'm pre-clearing as we speak. Read speeds are ~70-80MB/s. Write speeds are ~20MB/s when it comes to non-cached shares and ~50+MB/s on cached ones.

Looking great.

I think I prefer Dynamix to Limetech's enhanced webGui, but it is mentioned elsewhere that the Lime's one will be integrated into a future unRAID release. As the two are incompatible, would that affect the future of Dynamix?

Not true! I hadn't spotted the issue with the flash drive. Plus, it's always nice to know you're not just talking to yourself! I think I'll proceed with installing plugins and stuff for now, and resume troubleshooting when I have nothing better to do!

Yes, I can live with that. Thanks for sticking with me through this.

Installed the latest HP BIOS on the Microserver (a modded version, to be exact). Not sure if it's related to the BIOS update but I re-run the tunables script and, while a cap is still evident, performance is way better now (~ x3 times the initial one - see attached).

Nope, you got it right: the initial post refers to the write performance *without* a parity drive. I tried to ignore the sub-par numbers and, after all the copying was done, went on to add the parity drive. But when I run the tunables script, its results gave me an even clearer indication that something is not right with my setup. Still, I let it build the parity (even with the 35MB/s cap), just for the sake of it.

Done. It previously reported: Self-test execution status: ( 25) The self-test routine was aborted by the host. And now I see: Self-test execution status: ( 0) The previous self-test routine completed without error or no self-test has ever been run. So it completed successfully, I guess. Same results, more or less. SMART overall-health self-assessment test result: PASSED I could try installing the new Seagate firmware, though I'm not sure the performance cap I see can be attributed to this drive. Btw, I just initiated a parity check and it runs at ~105MB/s. As soon as it's done, I'll rerun the tunables script to check if the cap is still there. 1.5TB_SeagateLP_SMARTc.txt

Oh, yes, thanks for spotting that. I thought I had set the spin off delay long enough, but apparently that was not the case! Set it to never and I'm currently re-running the test. The only "suspicious" looking entries on my syslog (reported as "Minor Issues" by unmenu) are the following: Feb 1 00:33:06 HP_Microserver kernel: xor: measuring software checksum speed (Minor Issues) ... Feb 1 00:33:06 HP_Microserver kernel: acpi PNP0A08:00: ignoring host bridge window [mem 0x000d0000-0x000dffff] (conflicts with Adapter ROM [mem 0x000cf000-0x000d19ff]) (Minor Issues) The above show up on startup. When unRAID is up and running, I sometimes get this: Feb 1 00:39:57 HP_Microserver emhttp: shcmd (27): :>/etc/samba/smb-shares.conf (Other emhttp) Feb 1 00:39:57 HP_Microserver avahi-daemon[1113]: Files changed, reloading. Feb 1 00:39:57 HP_Microserver emhttp: Restart SMB... (Other emhttp) Feb 1 00:39:57 HP_Microserver emhttp: shcmd (28): killall -HUP smbd (Minor Issues) Feb 1 00:39:57 HP_Microserver emhttp: shcmd (29): cp /etc/avahi/services/smb.service- /etc/avahi/services/smb.service (Other emhttp) (i.e. it kills the smdb service daemon for some reason) Options I'm considering (once the SMART test is done): - Update BIOS on Microserver - Upgrade firmware on the Seagate drive - Upgrade to unRAID 6.0 x64 beta Edit for a comic relief: Apparently Seagate insist that the clicking noise users sometimes notice on Barracuda LP drives is "normal operational noise".