June 14, 20179 yr For those that don't know him. He's a Youtube Tech Reviewer with 4.6 Million subscribers. I think this is awesome and great visibility for unRaid!
June 14, 20179 yr With that many subscribers, you have enough money to not bother with individual UPSes and instead have an entire home backup generator system.
June 14, 20179 yr Ouch.. 1 parity for 14 drives all bought at the same time? Double ouch! And they called it backed up? Any raid is never a backup, additional redundancy yes but never a backup. I have seen some other stuff various boards posted about the Linus guy that will make you shudder dealing with hard drive arrays.
June 14, 20179 yr Yes I was confused when we said that was safe having all those drives with only 1 parity drive! Maybe they thought mentioning 2 parity drives would confused people? Anyway, the ad, I mean video was clearly paid for by Seagate and the company that made the chassis so I'm sure they don't really care.
June 14, 20179 yr Linus is famous for knowing very little making stupid decisions (like running his main server in a crazy undafe RAID config with no backups which he then lost), he is entertaining which is why he's popular. These guys get all kinds of hardware for free so companies can get some free advertising, meanwhile a lot of people with real content and knowledge are unknown. Its the culture we live in.
June 14, 20179 yr 8 hours ago, digiblur said: Ouch.. 1 parity for 14 drives They did explain that due to how unRaid works without striping that they can always take advantage of Seagates included data recovery service at no charge during the warranty period. That, and unlike a traditional RAID system, a URE does not constitute a failure of a drive within unRaid. Pure RAID systems value data integrity above all else. Its better to lose ALL of the data than have any part of it compromised. This is what you want you bank to run unRaid values resiliency. The odds of having any data compromsed is small but does exist, and in the event of a situation where data may get compromised, then you're better off having most of it (maybe only a single file got trashed) than none of it. This is what I want to run. Edited June 14, 20179 yr by Squid
June 15, 20179 yr Fully aware of how unRaid works but no way would you catch me running 14:1 on any type of array with the same drives bought at the same time.
June 15, 20179 yr 5 hours ago, digiblur said: Fully aware of how unRaid works but no way would you catch me running 14:1 on any type of array with the same drives bought at the same time. These are probably the most reliable drives you can buy, and they have data recovery service on these. And of course they didn't pay for any of this. I wish they'd covered more details.
June 15, 20179 yr These are probably the most reliable drives you can buy, and they have data recovery service on these. And of course they didn't pay for any of this. I wish they'd covered more details. Dumb decision no matter what drives were used. Linus is known to do some dumb things with arrays so this is the norm for him.
June 15, 20179 yr Lets not forget its great exposure and promotion for unRAID, Linus has been a big champion of unRAID for quite awhile which I see as a big win for Lime-Tech.
June 15, 20179 yr Fully aware of how unRaid works but no way would you catch me running 14:1 on any type of array with the same drives bought at the same time.I, and I assume many others, have never seen any evidence that drives from the same batch are more likely to die together than drives from separate batches. As to your example of nobody would every catch you running 14:1, I ran (4) chassis all running 28:0, no parity drives at all. Parity isn't a backup method, never has been, and never will be. My chassis ran along just fine for years. Two were main servers and two were backup servers containing an identical set of data disconnected from power and network. Since unRAID doesn't stripe data, 14:0, 14:1, or 14:2 is honestly just personal preference. Unless you have at least one full backup of your data, and preferable a third set off site, your playing with fire. Sent from my iPhone using Tapatalk
June 15, 20179 yr 4 minutes ago, CyberSkulls said: drives from the same batch are more likely to die together than drives from separate batches Handling issues. If that particular box of drives got dropped somewhere in transit, chances are good they all suffered the same trauma. I see many more failures from careless handling than from manufacturing defects.
June 15, 20179 yr Handling issues. If that particular box of drives got dropped somewhere in transit, chances are good they all suffered the same trauma. I see many more failures from careless handling than from manufacturing defects.Now that I would defiantly agree with. Amazon/Newegg craptastic packaging FTW!!Sent from my iPhone using Tapatalk
June 15, 20179 yr With that much data does it really matter if its 1 or 2 parity drives? You need to have backups in any case. There are plenty of users with >15 drives an donly 1 parity drive, 2 is a very new feature. And the drives were not the same batch, they got it in 2 shipments. Even if they were I very much doubt it makes any difference. In fact if all of them got damaged thats a good thing as you'd be able to replace them immediately.
June 15, 20179 yr 18 minutes ago, MrCrispy said: In fact if all of them got damaged thats a good thing as you'd be able to replace them immediately. Damage doesn't always show up until later, and doesn't always effect all drives in a shipment. That's one of the biggest reasons to run several preclear cycles, to increase confidence.
June 15, 20179 yr I, and I assume many others, have never seen any evidence that drives from the same batch are more likely to die together than drives from separate batches. As to your example of nobody would every catch you running 14:1, I ran (4) chassis all running 28:0, no parity drives at all. Parity isn't a backup method, never has been, and never will be. My chassis ran along just fine for years. Two were main servers and two were backup servers containing an identical set of data disconnected from power and network. Since unRAID doesn't stripe data, 14:0, 14:1, or 14:2 is honestly just personal preference. Unless you have at least one full backup of your data, and preferable a third set off site, your playing with fire. Sent from my iPhone using TapatalkWhy are we all here?
June 15, 20179 yr Why are we all here? Only you can answer that for yourself.Sent from my iPhone using Tapatalk
June 15, 20179 yr Only you can answer that for yourself.Sent from my iPhone using TapatalkWasn't asking for myself.
June 16, 20179 yr ?? Why did you ask then??Why would I post a question to myself on a forum to others... That would be weird.
June 16, 20179 yr Well you could be an AI construct trying to learn through social interactions with yourself...
June 16, 20179 yr Well you could be an AI construct trying to learn through social interactions with yourself...New unRaid plugin in testing!
June 16, 20179 yr Author 57 minutes ago, digiblur said: Why would I post a question to myself on a forum to others... That would be weird. Why are you being so aggressive? You use unRaid how you like, let others use it how they like? What's so difficult about that concept?
June 16, 20179 yr 11 hours ago, CyberSkulls said: I, and I assume many others, have never seen any evidence that drives from the same batch are more likely to die together than drives from separate batches. As to your example of nobody would every catch you running 14:1, I ran (4) chassis all running 28:0, no parity drives at all. Parity isn't a backup method, never has been, and never will be. My chassis ran along just fine for years. Two were main servers and two were backup servers containing an identical set of data disconnected from power and network. Since unRAID doesn't stripe data, 14:0, 14:1, or 14:2 is honestly just personal preference. Unless you have at least one full backup of your data, and preferable a third set off site, your playing with fire. Sent from my iPhone using Tapatalk Agree with everything. If I have a backup server with frequent rsyncs, parity is not that essential and may in fact be not preferred. Its the same tradeoff you make when choosing to have a non-mirrored cache, which many people also have. I know everyone says you need 3 backups with 1 offsite, but in practice very few can afford that with large datasets.
Archived
This topic is now archived and is closed to further replies.