Jump to content

alpenwasser

Retired Staff
  • Posts

    4,129
  • Joined

  • Last visited

Everything posted by alpenwasser

  1. That is my current interpretation of the CS, and I'll enact it that way until I'm told that I was wrong.
  2. Problem is, at some point the benefits of the new forum will outweigh its downsides compared to the old forum. We waited quite a long time to upgrade, but we can't just keep postponing forever until the IPS devs have fixed everything we'd like them to fix. Then we'd probably never upgrade at all. We actually also looked at getting a better editor than the stock one and hacking that into IPS4, but it turned out to not really be feasible. I do miss BBCode, most definitely. But apparently it's "old, and horrible, and terrible, and archaic, and blablablabla" (or so mortis and I were told when we objected to BBCode being removed). I feel your pain, I really do, but unfortunately other factors were also important in deciding when and how to ugprade, and in the end they just outweighed the editor issues.
  3. Ah yes, life... she can be a bit spontaneous and uncooperative with plans on occasion, have made experiences with that too.
  4. Not according to the IPB devs! Their tirades against BBCode were actually quite funny. :D Honestly though, I don't so much need or want BBCode, I would just like more fine-grained control over my posts than a rich text editor usually offers (plus, I prefer never having to use my mouse, so I'd rather type out [url=something]linky[/url] on my keyboard than move my hand to the mouse and then click stuff, although at least for some things there are keyboard shortcuts). But it could also be something other than BBCode, like a Markdown-style kinda thing or even something else.
  5. I used BBCode for pretty much everything to be honest, and do rather miss it. But ah well, such is life. I suppose I'll get used to the new editor.
  6. You're not the only one. mortis and I made ourselves quite unpopular with the developers on their forum when we protested the removal of BBCode. They did not react too kindly to our feedback, to say the least :D. But everything gets converted to HTML5 with the new forum software, so as the colonel said, hacking BBCode back into it so that it would actually work properly would be a monumental task.
  7. They're coming back, but it's still a work in progress.
  8. Are you actually having issues connecting, or do you just not like the IP address? Because 10.<stuff> isn't inherently wrong for a private network. There are three address spaces set aside on the IPv4 space for private usage: 10.0.0.0 - 10.255.255.255, 172.16.0.0 - 172.31.255.255 and 192.168.0.0 - 192.168.255.255. The most commonly used one for small home networks is the 192 range (because it's the smallest one and you don't usually need more addresses), but the other two can be used just as well. Seems your router is 10.0.1.1, which would fit with your machine's IP address and the one of the other computer you mentioned. See also here: https://en.wikipedia.org/wiki/Private_network
  9. 1) This is not a place to promote Youtube Channels. 2) We've had this kind of thread before. A lot of 'em. Locked.
  10. Hehe, that was my thinking too, thanks! Yeah, SR-2 is really hard to find these days, I've been trying to get one for ages (for a reasonable price). I am very happy with how the black paint turned out, definitely a much better fit than the weird salmon red color it was before.
  11. Alrighty people, cleaned out the thread, let's try again. Keep in mind, there is no obligation for anyone to answer any topic. Ignoring threads is indeed a possibility. In fact, it's what we recommend if a thread doesn't cater to your personal preferences. Anyway, be nice. Thanks.
  12. Guys, when a member who's new around here asks a question, I think it's proper form to stay at least somewhat on topic. Cleaned out thread.
  13. The Build Logs section has additional guidelines from the Community Standards that members must follow when posting. These guidelines are subject to change without notice. General: Sponsored build logs are allowed, with one banner for your sponsors per build log update. We reserve the right to remove sponsor banners if we deem their usage excessive. You are not allowed to link to their corporate or product sites. The primary goal of your build log is a written/photographic documentation of your build. If you want to include a video, please see the additional items below. The build log should be yours with original content. You can have links to PCPartPicker in your build link for your specific items Videos: Videos are allowed, as long as the focus is on the build. No advertising spots for your channel or your sponsors. The video is only to complement your written build log on the site. You cannot simply post a video. Subscribes or likes are mentioned a maximum of once throughout the video. Build logs are not a chance for you to advertise your own channel. Video does not contain advertisement (similar to the style of LTT ads). Failure to comply with guidelines may result in your thread being locked or removed, along with the possibility of warning points being assigned. These guidelines are subject to updating and/or change without notice.
  14. I'd say "the one you can get running" I found a great tutorial for Arch for the Macbook Pro, and since I'd been using Arch for a few years anyway, I ended up going with that. But your mileage may vary.
  15. Not sure to be honest. I have experience with ZFS, but not with FreeNAS. I'd expect you'll need to export your pool, then do a fresh install, then re-import it. But maybe have a googly around to make sure that's right.
  16. Same thing happened to me about three and a half years ago. I didn't feel like forcing it, so I've just been doing other things which tickle my fancy (I think the last game I played was Mass Effect 3). It's not like gaming is the be-all-end-all thing to do in life, there are tons of other things you can do, we live in a world of countless possibilities. Plus, you can always come back to gaming once you start to feel that itch again. I haven't yet, but maybe one day. And if not, ah well, I'll just be doing other things.
  17. Indeed, FreeNAS is not the only thing out there. There are alternatives which are more frugal when it comes to hardware requirements/recommendations. As for ZFS's memory needs: Last I checked, FreeNAS recommended 8 GB of minimum RAM, regardless of how much storage you have. ZFS itself can run with less, I've fun it on 4 GB (Linux, not FreeNAS, though). But if other stuff starts using your RAM, performance can degrade almost to standstill (happened to me a few times). The "1 GB of RAM per 1 TB of storage" is no longer really true as best as I can tell, especially not for home setups. I have 30 TB raw storage in my pool and 24 GB of RAM in my machine, and it usually sits between 10 GB and 15 GB of RAM usage. Anyway, as said, instead of dealing with all the possible headaches which can occur when you're running FreeNAS with stuff below its specs, I'd recommend looking at alternatives (Amahi and Openmediavault come to mind, though there are more). It might be fine. Hell, it probably will be fine, but it might also not be. In the end though, decision is yours, of course.
  18. You'll probably get by with 128, but I went for 256 in my 15" MBP and am quite happy to have done so. Unless you have a strong reason to go for 128, I'd go with 256.
  19. @whud99 1) It was initially an enterprise drive: http://www.anandtech.com/show/4902/intel-ssd-710-200gb-review 2) It is old, as you can see from that review.
  20. Note: I've renamed the topic to better reflect the actual question. General "AMD vs. Intel" threads don't tend to go that well. Be nice to each other.
  21. I see you're up and running again. 19"... yeah, I'm in.
  22. Locked due to serious necro.
  23. Dammit, I really should be in bed. Last post for today. Funny thing is actually happening to me on that one: Some of my Reds are getting park counts in the hundreds of thousands as well for some reason, and I have absolutely not a clue as to why. Others are fine. And they even run the same firmware version. But not that much I can do about it I suppose. And the extremely weird thing? My Greens are only at about 1,000 and about 2,000 park operations (while having about 20% of the power-on hours of the youngest WD Red which is suffering from the head parking issue). Unless you've disabled checksumming, ZFS will still checksum and validate every block it reads. So if you read a block, calculate its checksum, then read the checksum from the drive and compare the two, and you get an error somewhere in there, might still lead to trouble. Hard to say what precisely will happen though. Yeah, I know that most of the time it will be fine. I ran ZFS without ECC for more than a year as well, and I'm still running some secondary ZFS standalone disks without ECC (although the data's primary copy is stored on an ECC server). Look at it this way: risk = (probability of occurrence) × (amount of damage upon occurrence)Most of the time it will be perfectly fine. And even when do you have an error, it might be in a non-important part of your pool. BUT: The potential damage is that you lose everything. The chances of that occurring are low, but they're non-zero, and the potential damage is huge (unless you have a backup of your stuff somewhere else, which you should have anyway I'd say, at least of the important stuff).In the end, what you need to do is make a risk assessment, and then a decision. You have the relevant info, the rest is up to you. Most desktop drives would probably have that problem (on top of the TLER issue I mentioned above), although the extent of it may vary a lot. If the drive's power saving methods aren't too aggressive, it might not be that big of a deal. I have some Samsung desktop drives which have 42,000 power-on hours on them (though they don't give me a head park count unfortunately) and have been running fine since 2008 or so (*knock on wood*), a big proportion of which in 24/7 mode. As for why this is an issue: The read/write head gets mechanically worn down a tiny bit each time they get parked, as far as I know. @Captain_WD might be able to give more reliable info on that one than my educated guess though.
  24. The reliability is one thing (I'm not really sure how much better the Reds are than regular drives in that area to be honest). The more important thing (IMHO, at least) is TLER. Long story short: Desktop drive firmware is programmed in such a fashion that it can cause a RAID controller to think a drive is broken, and the controller can drop it from the array even though it is perfectly fine. If this happens to lots of your drive at once, that might nuke your entire pool. Now, I'm honestly not 100% sure how ZFS handles this, but I do know of at least one person who's had this issue with software RAID (mdadm, to be precise) and WD Greens, so it's not just an issue for hardware RAID controllers. Depending on the software RAID implementation, that can be affected as well. Still up to you, it might work fine with Greens or other desktop drives. Hell, most of the time it probably will work fine. But I think this info is good to know when making a decision. You could also look into amahi and Openmediavault (there are lots of others, but those are the ones about which I've read quite a few positive things, and I'm currently playing around with OMV in a virtual machine to get to know it a bit), as an alternative to FreeNAS. They don't really require ECC. Openmediavault is based on Debian Linux, so it has a very solid base to build on (not that there's anything wrong with FreeBSD, the base for FreeNAS, as far as I know). As for ZFS and ECC: It's not absolutely strictly needed. It can run fine. And depending on your data, the odd minute corruption might not be a big deal (say, a pixel in one frame of one of your movies has a different color, probably not that big of a deal). BUT: It could also corrupt your metadata, in which case your entire pool could be nuked. It probably won't, but from what I've been able to find out, it is a possibility (haven't personally suffered that fate, though I have recently done some experimenting with ZFS and corruption out of curiosity). That's personally what made me go with ECC RAM in my ZFS machine. I'll be back and have a closer look at the hardware once I've had some sleep (rather late here atm).
×