Conversation started Oct 10, 2015 at 4:49.
Oct 10, 2015 04:49
user image
2
@oldmud0 This is precisely why my planned storage server will use double parity.
and why I always use RAID10 or RAID1
that's what just happened to my home server... one drive failed, didn't have a spare so I ordered a lot of 6 drives twice the size and left the server on degraded state. 2 days later, I wanted to make a current backup of the server... but guess what, the server was down because another drive stopped responding. Can't confirm that it was a fail, but the drive won't even show its basic information.
I'm not touching that second drive until all the new drives arrive in a week
That really sucks.
Two drives failing at essentially the same time is a very real risk. That's why I don't consider single-parity RAID to be a robust storage solution.
@oldmud0: Raid is not backup
I'd consider most raid levels a little like the black knight
"Tis only a flesh wound!"
Oct 10, 2015 04:59
Yeah I know
There isn't anything critical on the server, otherwise I would be crying my heart out
RAID is not in itself a backup. When properly configured, RAID can provide a high degree of resistance against data loss in the event of disk failure, but it's not a substitute for another copy of the data stored separately from the array.
Only thing I'd be concerned about is wasting time recreating config files and such. Also I had whipped up a minimal CMS in PHP for my tiny website.
However, if my desktop's HDD dies...
@oldmud0: I'm a big fan of distributed backups
(since the array is a backup layer for your desktop)
I'd need one NAS, an internal hard drive and an external hard drive dying to lose data
Oct 10, 2015 05:06
(besides my server weighs like 60lbs and runs win2003, it deserves to die)
Ouch. Windows Server 2003 is EOL.
Another thing I do? I can survive any one of my systems dying
I can grab the files off the latest backup.
(no raid in sight)
and the best part, it's x86 so win2003 is the end of the line for the server, unless I really wanted to put some effort into setting up LVM
No 64-bit support, wow. That is outright ancient.
Oct 10, 2015 05:10
oh no that's not the best part sorry: the motherboard only supports ~1.1 TB of internal storage
it also has 2 serial ports, is missing a bezel, and uses SCSI
I suspect the machine doesn't even support PCI Express.
and has 512mb of ram?
An old rackmount server, eh?
nah, it has 1gb ram and supports up to 12 gb (don't ask me how it addresses it). and it's actually a tower, not a rackmounted
DDR1
Oct 10, 2015 05:13
the good part about the drives is that you can find them very easily, although they're increasing in price
ooh scott manley
@oldmud0 third level page tables.
In computing, Physical Address Extension (PAE), sometimes referred to as Page Address Extension, is a memory management feature for the IA-32 architecture. PAE was first introduced in the Pentium Pro. It defines a page table hierarchy of three levels, with table entries of 64 bits each instead of 32, allowing these CPUs to access a physical address space larger than 4 gigabytes (232 bytes). The page table structure used by x86-64 CPUs when operating in 64-bit mode further extends the page table hierarchy to four levels, extending the virtual address space, and uses additional physical address bits...
Beat me to it.
right, PAE..
"DDR1"
I think my nuc brix might be marginally more useful and maybe even more powerful...
Oct 10, 2015 05:16
surprisingly, the server runs with a 3ghz xeon
Should I consider using Windows 10 Storage Spaces? Software-defined storage is all the rage these days.
A double-parity storage space needs as many as seven disks, though.
No, if it doesn't have any benefit over software RAID, it'd probably become a burden in the future
Well, bye
Hope my 2004 server rots and all my data burns
Good riddance
 
Conversation ended Oct 10, 2015 at 5:20.