On 09/11/2025 17.54, Sharoy Veduchi wrote: I will try to answer some of these questions. Hi, Sorry to be a bother. There's no need to answer the questions. The developers, if they're still active, seem not to care. I certainly don't care as I can't imagine why I would switch from Win7 to ReactOS. Regards, Mark.
On 23/03/2025 08.26, EmuandCo wrote: DirectX rootkit? Please elaborate what you are talking about Hello, EmuandCo, I'm happy to write about this sad affair. The word "rootkit", first applied to the technique in UNIX, refers to dynamic modification of the kernel during loading based on conditions found at boot time, so named because the administrator account of a UNIX installation is called "root". "Rootkit" in Windows NT4 and its descendants refers to the extension of the UNIX idea to the NT kernel....
Hello, I'm a bit mystified by this. Perhaps others are, too. I need to ask some technical questions. My background is as a processor architect with Intel, High Integration Microprocessor Operation (HIMO), in 1985. You are duplicating the NT API, right? ReactOS is not Linux, right? Does the kernel run Virtual-86 mode and does it implement all 4 rings? How-where are you obtaining the kernel? Have you duplicated or plan to duplicate the Direct-X rootkit? Would you welcome help? money? That will do for...
h264bitstream is a library, right? Can you recommend an application that uses it to display to me the headers and values of AVC (H.264) videos? How do I install h264bitstream? My attempt follows: mark@mark-VirtualBox:~$ sudo apt-get install build-essential libtool autoconf ffmpeg [sudo] password for mark: Reading package lists... Done Building dependency tree Reading state information... Done autoconf is already the newest version (2.69-11.1). libtool is already the newest version (2.4.6-14). The...
Thank you, Leifi.
Quote 'snapraid.txt': " snapraid sync " "This process may take some hours the first time, depending on the size "of the data already present in the disks." Can the first sync be divided into small runs so that the data disks aren't stressed too much? I see that it can be interrupted (Ctrl-C), but is there a built-in way to schedule periodic pausing (for example, when running 'snapraid sync' overnight)? Is there a way to compute parity on one data disk, then spin it down, then compute parity on the...
It's neither a troll technique nor bad manners. It's asking a question. "Sometimes a cigar is just a cigar." -- Freud. Aside: You see, Magistar. This is the damage that a CybrSage troll causes. It's damage, not to me, but to you. When you see my post, you look for things to complain about. CybrSage has successfully turned you into a troll cop (which can also be a troll in its own right). Of course, it is possible that you and CybrSage are the same person with two accounts.
It's neither a troll technique nor bad manners. It's asking a question. "Sometimes a cigar is just a cigar." -- Freud.
It's neither a troll technique or bad manners. It's asking a question. "Sometimes a cigar is just a cigar." -- Freud.
It's neither. It's asking a question.
The syncing would be invisible to the host. And, it would only occur when the portal SSDs were full and needed to be written to the array. The writing would be solely the files that were write posted. The read cache can simply be flushed. That seems to me to be the best of worlds and may be worth buying as an actual hardware product. ...Just an idea.
The syncing would be invisible to the host. And, it would only occur when the portal SSDs were full and needed to be written to the array. The writting would be solely the files that were write posted. The read cache can simply be flushed. That seems to me to be the best of worlds and may be worth buying as an actual hardware product. ...Just an idea.
Indeed. Thanks, Leifi. Has Mr. Mazzoleni given any thought to a SnapRAID hardware server product: - A main disk pool with as-needed, on-demand spin-up for long life - Portal hardware that includes a USB-3 hub (or better) interface with read-caching from and journaled write-posting to mirrored, portal SSDs - Syncing is continuous within the server, transparent to the host ...Just an idea. So, SnapRAID with single 'parity' -- I'll have to expand my concept of what that word means -- uses simple XOR,...
Indeed. Thanks, Leifi. Has Mr. Mazzoleni given any thought to a SnapRAID hardware server product: - A main disk pool with as-needed, on-demand spin-up for long life - Portal hardware that includes a USB-3 hub (or better) interface with read-caching from and journaled write-posting to mirrored, portal SSDs - Syncing is continuous within the server, transparent to the host Just an idea... So, SnapRAID with single 'parity' -- I'll have to expand my concept of what that word means -- uses simple XOR,...
Indeed. Thanks, Leifi. Has Mr. Mazzoleni given any thought to a SnapRAID hardware server product: - A main disk pool with as-needed, on-demand spin-up for long life - Portal hardware that includes a USB-3 hub (or better) interface with read-caching from and journaled write-posting to mirrored, portal SSDs - Syncing is continuous within the server, transparent to the host Just an idea... So, SnapRAID with single 'parity' -- I'll have to expand my concept of what that word means -- uses XOR, eh?
Indeed. Thanks, Leifi. Has Mr. Mazzoleni given any thought to a SnapRAID hardware server product: - A main disk pool with as-needed, on-demand spin-up for long life - Portal hardware that includes a USB-3 hub (or better) interface with read-caching from and journaled write-posting to mirrored, portal SSDs - Syncing is continuous within the server, transparent to the host
Oh, dear. That's not parity. That's ECC. Are people actually calling that parity? Oh, no. And it appears it may be ECC that's based on unproven techniques. My heart is sinking into despair. Since I have your eye, and since my next question is probably simple to you, I ask: Do you have a proof of the PxN matrix solution that has the level of integrity of... say... Elliptical ciphers?
Oh, dear. That's not parity. That's ECC. Are people actually calling that parity? Oh, no. And it appears it may be ECC that's based on unproven techniques. My heart is sinking into despair.
Well here's my opportunity to help you. Odd parity is an x-or operator (simple, one line operations, not a function al all). Even parity is an x-nor operation. X-or is also called the difference operator, and x-nor is also called the equality operator. XOR: A ^ B = OddParity 0 ^ 0 = 0 0 ^ 1 = 1 . . . A & B are different 1 ^ 0 = 1 . . . A & B are different 1 ^ 1 = 0 In 'C', the bitwise XOR is written 'A ^ B' and the bitwise XNOR is its bitwise complement: ~(A ^ B) (which is '1' if A & B are equal,...
Well here's my opportunity to help you. Odd parity is an x-or operator (simple, one line operations, not a function al all). Even parity is an x-nor operation. X-or is also called the difference operator, and x-nor is also called the equality operator. XOR: A ^ B = OddParity 0 ^ 0 = 0 0 ^ 1 = 1 . . . A & B are different 1 ^ 0 = 1 . . . A & B are different 1 ^ 1 = 0 In 'C', the bitwise XOR is written 'A ^ B' and the bitwise XNOR is its bitwise complement: ~(A ^ B) (which is '1' if A & B are equal,...
Okay, the thing that threw me off was that the picture shows physical disks. I assume you borrowed that illustration from a site that sells/explains physical RAID. And by LBA I meant logical rather than physical. Sorry for misleading you. SnapRAID maintains parity based on logical blocks (configurable size). Now, about your 2nd sentence. Supposing that A3 doesn't actually exist, SnapRAID doesn't maintain parity like this: A1 XOR A2 It maintains parity like this: A1 XOR A2 XOR 0x00 That's different...
Leifi, Thank you so much for being patient with us. I am learning a lot about SnapRAID and I'll pay it back by making some top-notch documentation (with pictures). I promise I will fit the work in with my other projects... because SnapRAID is important to me. You wrote: "Data Lots of 8/10 TB disks with 8 TB partition on all." I assume that means, Data: Lots of 8 & 10 TB disks with 8 TB partitions on each. "Parity: 2x4 TB" Why do you use 2 partitions (4TB each) for parity instead of 1 (8TB)? What...
Architectural question: SnapRAID could have been designed so that, when it encounters 2 (or more) volumes that share a physical drive, it concatenates the volumes, could it not? I ask because I'm creating my pictures, and this changes the 'picture' a bit. Leifi, while I have your attention, can I ask a related question? Must the parity drive(s) be dedicated? Or can it/they have other files/filesystems/partitions on them? PS: I just reread Nadine's question. She would like to parity protect 2, 4TB...
Architectural question: SnapRAID could have been designed so that, when it encounters 2 (or more) volumes that share a physical drive, it concatenates the volumes, could it not? I ask because I'm creating my pictures, and this changes the 'picture' a bit. Leifi, while I have your attention, can I ask a related question? Must the parity drive(s) be dedicated? Or can it/they have other files/filesystems/partitions on them? PS: I just reread Nadine's question. She would like to parity protect 2, 4TB...
Architectural question: SnapRAID could have been designed so that, when it encounters 2 (or more) volumes that share a physical drive, it concatenates the volumes, could it not? I ask because I'm creating my pictures, and this changes the 'picture' a bit. Leifi, while I have your attention, can I ask a related question? Must the parity drive(s) be dedicated? Or can it/they have other files/filesystems/partitions on them?
Architectural question: SnapRAID could have been designed so that, when it encounters 2 (or more) volumes that share a physical drive, it concatenates the volumes, could it not? I ask because I'm creating my pictures, and this changes the 'picture' a bit. Leifi, while I have your attention, can I ask a related question? Must the parity drive(s) be dedicated? Or can they have other files/filesystems/partitions on them?
Architectural question: SnapRAID could have been designed so that, when it encounters 2 (or more) volumes that share a physical drive, it concatenates the volumes, could it not? I ask because I'm creating my pictures, and this changes the 'picture' a bit.
Architectural question: SnapRAID could have been designed so that, when it encounters 2 (or more) volumes that share a physical drive, it concatenates the volumes, could it not?
Leifi, In your picture, are A1, A2, A3,... physical sectors (or blocked groups of physical sectors)? Or are they LBAs?
Magistar wrote Another explanation is that hard drives slow down the more data is on it simply because a spinning disk spins faster on the outer edges. So the first 20% of a Seagate drive (faster than wd) will ususally show 200-220 MB/s, whereas the middle shows about 180-200 MB/s and the last 30% will go down to about 150 MB/s. Simply because of physics. You folks probably have forgotten more than I know, but... Aren't HDDs CAV (constant angular velocity) devices? Don't they 'slow down' only in...
Magistar wrote Another explanation is that hard drives slow down the more data is on it simply because a spinning disk spins faster on the outer edges. So the first 20% of a Seagate drive (faster than wd) will ususally show 200-220 MB/s, whereas the middle shows about 180-200 MB/s and the last 30% will go down to about 150 MB/s. Simply because of physics. You folks probably have forgotten more than I know, but... Aren't HDDs CAV (constant angular velocity) devices? Don't they 'slow down' only in...
Magistar wrote Another explanation is that hard drives slow down the more data is on it simply because a spinning disk spins faster on the outer edges. So the first 20% of a Seagate drive (faster than wd) will ususally show 200-220 MB/s, whereas the middle shows about 180-200 MB/s and the last 30% will go down to about 150 MB/s. Simply because of physics. You folks probably have forgotten more than I know, but... Aren't HDDs CAV (constant angular velocity) devices? Don't they 'slow down' only in...
Magistar wrote Another explanation is that hard drives slow down the more data is on it simply because a spinning disk spins faster on the outer edges. So the first 20% of a Seagate drive (faster than wd) will ususally show 200-220 MB/s, whereas the middle shows about 180-200 MB/s and the last 30% will go down to about 150 MB/s. Simply because of physics. You folks probably have forgotten more than I know, but... Aren't HDDs CAV (constant angular velocity) devices? Don't they 'slow down' only in...
Magistar wrote Another explanation is that hard drives slow down the more data is on it simply because a spinning disk spins faster on the outer edges. So the first 20% of a Seagate drive (faster than wd) will ususally show 200-220 MB/s, whereas the middle shows about 180-200 MB/s and the last 30% will go down to about 150 MB/s. Simply because of physics. You folks probably have forgotten more than I know, but... Aren't HDDs CAV (constant angular velocity) devices? Don't they 'slow down' only in...
I'll cook up some preliminary pictures over the next few days. I'll post them via 'Insert Image". PS: Leifi, does SN include all non-excluded files? Including $MFT, for example?
I'll cook up some preliminary pictures over the next few days. I'll post them via 'Insert Image".
There's no abuse button on this forum, so I can do nothing active. Can anyone get this troll off the forum?
I think there's nothing wrong with either person. But this is off-topic. ...I wonder why you continue to snipe at me. Are you a troll?
Words. Words can be misinterpreted. Words can be vague. Words are subject to language differences. Words seem to change depending on the experience of the person writing them and the person reading them. A written 'glass of clear water' to one person reads like a 'glass of mud' to another... Or even, "I don't 'see' a glass." That's words. No matter what a person's preconceptions, a picture of a glass of water is a picture of a glass of water. That's why architects and engineers work in pictures.
Words. Words can be misinterpreted. Words can be vague. Words are subject to language differences. Words seem to change depending on the experience of the person writing them and the person reading them. A written glass of 'clear water' to one person 'reads' like a glass of mud to another... Or even, "I don't 'see' a glass." That's words. No matter what a person's preconceptions, a picture of a glass of water is a picture of a glass of water. That's why architects and engineers work in pictures.
Words. Words can be misinterpreted. Words can be vague. Words are subject to language differences. Words seem to change depending on the experience of the person writing them and the person reading them. A written glass of clear water to one person 'reads' like a glass of mud to another... Or even, "I don't 'see' a glass." That's words. No matter what a person's preconceptions, a picture of a glass of water is a picture of a glass of water. That's why architects and engineers work in pictures.
Words. Words can misinterpreted. Words can be vague. Words are subject to language differences. Words seem to change depending on the experience of the person writing them and the person reading them. A written glass of clear water to one person 'reads' like a glass of mud to another... Or even, "I don't 'see' a glass." That's words. No matter what a person's preconceptions, a picture of a glass of water is a picture of a glass of water. That's why architects and engineers work in pictures.
Thank you! I know some people (who won't be mentioned) think I'm just being stupid, but kindly remember that my experience is designing hardware RAID controllers in which all drives are spinning all the time, and striping is by physical disk sector, and OS files are read and written in parallel across all the disks. Also, a hardware RAID does real-time error correction whereas SnapRAID doesn't. Now that I have a better view of the architecture, I can continue evaluating SnapRAID -- note that I haven't...
Let's take a different approach, shall we? For the sake of explanation, suppose I have 3 data drives. To make the 'picture' simple, suppose each drive is formatted as a single volume and that all files are contiguous & unfragmented. Suppose the 3 volumes contain files A B C ... N. A 'picture' of the drives, left to right (lowest LBA to highest LBA), is, VOLUME1 contains: A0 A1 A2 A3 B0 B1 B2 C0 C1 C2 C3 C4 C5 C6 C7 D0 D1 E0 E1 E2 VOLUME2 contains: F0 F1 F2 F3 G0 G1 G2 G3 G4 G5 H0 H1 H2 H3 I0 I1 I2...
Let's take a different approach, shall we? For the sake of explanation, suppose I have 3 data drives. To make the 'picture' simple, suppose each drive is formatted as a single volume and that all files are contiguous & unfragmented. Suppose the 3 volumes contain files A B C ... N. A 'picture' of the drives, left to right (lowest LBA to highest LBA), is, VOLUME1 contains: A0 A1 A2 A3 B0 B1 B2 C0 C1 C2 C3 C4 C5 C6 C7 D0 D1 E0 E1 E2 VOLUME2 contains: F0 F1 F2 F3 G0 G1 G2 G3 G4 G5 H0 H1 H2 H3 I0 I1 I2...
I suggest you take up a hobby, volunteer for civic work, go hiking, anything but snipe at me here. Regarding whether I have anything else to do, Yes, my plate is full.
Let's take a different approach, shall we? For the sake of explanation, suppose I have 3 data drives. To make the 'picture' simple, suppose each drive is formatted as a single volume and that all files are contiguous & unfragmented. Suppose the 3 volumes contain files A B C ... N. A 'picture' of the drives, left to right (lowest LBA to highest LBA), is, VOLUME1 contains: A0 A1 A2 A3 B0 B1 B2 C0 C1 C2 C3 C4 C5 C6 C7 D0 D1 E0 E1 E2 VOLUME2 contains: F0 F1 F2 F3 G0 G1 G2 G3 G4 G5 H0 H1 H2 H3 I0 I1 I2...
Let's take a different approach, shall we? For the sake of explanation, suppose I have 3 data drives. To make the 'picture' simple, suppose each drive is formatted as a single volume and that all files are contiguous & unfragmented. Suppose the 3 volumes contain files A B C ... N. A 'picture' of the drives, left to right (lowest LBA to highest LBA), is, VOLUME1 contains: A0 A1 A2 A3 B0 B1 B2 C0 C1 C2 C3 C4 C5 C6 C7 D0 D1 E0 E1 E2 VOLUME2 contains: F0 F1 F2 F3 G0 G1 G2 G3 G4 G5 H0 H1 H2 H3 I0 I1 I2...
Let's take a different approach, shall we? For the sake of explanation, suppose I have 3 data drives. To make the 'picture' simple, suppose each drive is formatted as a single volume and that all files are contiguous & unfragmented. Suppose the 3 volumes contain files A B C ... N. A 'picture' of the drives, left to right (lowest LBA to highest LBA), is, VOLUME1 contains: A0 A1 A2 A3 B0 B1 B2 C0 C1 C2 C3 C4 C5 C6 C7 D0 D1 E0 E1 E2 VOLUME2 contains: F0 F1 F2 F3 G0 G1 G2 G3 G4 G5 H0 H1 H2 H3 I0 I1 I2...
CybrSage, don't you have better things to do?
A point of failure can be a design flaw in SnapRAID, or it can be a misunderstanding of the recovery procedure. If a misunderstanding of the recovery procedure, the flaw can manifest as a lack of preparation for recovery (just at the point in time when it's needed most and a lack of preparation or knowledge hurts the most) or it can manifest as a misstep due to misunderstanding of the recovery procedure. A recovery is not something that can be hearsed. It must be fully known and must work when it's...
@CybrSage, I will sleep well tonight knowing that you watch over me... The computer is a laptop. No surge protector needed. Of course, there's always the odd Earth-crossing astroid to fear... Regarding the config file, Yes, I can back that up. The question is this: What other things are there that need to be backed up because they are single points of failure? Without a clear software architecture description of SnapRAID (which is not actually a RAID, hense my questions & concerns) ...without a clear...
Ah, SpookyHash, I forgot that. I'm looking for single points of failure in the architecture. If the content files are stored in only one place, that can be a single point of failure. I'll review the config file info before going further down that road. Oh, wait. A single config file is also a single point of failure. Update: I see "The "content" file is stored in multiple copies, and each one must be in a different disk, to ensure that in even in case of multiple disk failures at least one copy is...
Ah, SpookyHash, I forgot that. I'm looking for single points of failure in the architecture. If the content files are stored in only one place, that can be a single point of failure. I'll review the config file info before going further down that road. Oh, wait. A single config file is also a single point of failure.
Regarding the hashes -- I assume MD5 -- used when scanning for changed files, are they stored somewhere secure? Are they part of the content files? Are the content files stored redundantly in the JBOF (pool) or do they (and possibly the hashes) need to be backed up manually by the user to a non-parity/non-JBOF (non-pool) drive? If so, does SR check the integrity of that backup? There's a lot to admire with SR. I like your term: "virtual striping". I called it "parity spanning", but I like your term...
Regarding the hashes -- I assume MD5 -- used when scanning for changed files, are they stored somewhere secure? Are they part of the content files? Are the content files stored redundantly in the JBOF or do they (and possibly the hashes) need to be backed up manually by the user to a non-parity/non-JBOF (non-pool) drive? If so, does SR check the integrity of that backup? There's a lot to admire with SR. I like your term: "virtual striping". I called it "parity spanning", but I like your term bet...
You should read the rest of what I wrote.
Hi David, You care that I know how to use SR. That's good of you. For that reason, I sincerely want to avoid wasting your time. To that end, I ask very specific questions. I'm a very serious guy with deep technical knowledge & experience. I assure you that the culmination of my questions will benefit both you & me. I'm expert in computer architecture, circuit design, chip design, assembly language drivers, compiled applications, scripts, operating systems, and technical documentation. I designed...
SnapRAID is a parity backup & restore scheme for JBOF. Am I right? It's not a RAID. It doesn't handle JBOD. It handles JBOF. Am I right?
Re: 1, My goal is backup, not access. I don't think a NAS would help unless it was a mirror. Mirrors are wasteful. Re: 2, No cloud. And I don't think it would help unless it was a mirror. Re: 3, No mirrors, please.
Hi Leifi, I like your explanation. I do realize that D: & E: are not striped (nor are the underlying physical drives striped). I do realize that stripes are not really needed (as they would be for hardware RAID). I assume F: stores the parity bits by spanning D: & E: like this: F;\ParityFile(bit n) = XOR( Vol_D(bit n), Vol_E(bit n) ) F;\ParityFile(bit n+1) = XOR( Vol_D(bit n+1), Vol_E(bit n+1) ) F;\ParityFile(bit n+2) = XOR( Vol_D(bit n+2), Vol_E(bit n+2) ) et cetera so that the data in Vol_D & Vol_E...
My question was "Can SnapRAID create a RAID?" If what has been written here is correct, the answer is "No". Thanks for your time, Leifi & David. You guys are caring people, and that counts for a lot. But it appears I must go elsewhere. Before I go, and because you are knowlegeable, do you have any pointers to where I need to go? Microsoft is a bust, and other sources are too vague about what it is they would have me do. I'm willing to load almost any OS into the media center laptop provided I can...
My question was "Can SnapRAID create a RAID?" If what has been written here is correct, the answer is "No". Thanks for your time, Leifi & David. You guys are carring people, and that counts for a lot. But it appears I must go elsewhere. Before I go, and because you are knowlegeable, do you have any pointers to where I need to go? Microsoft is a bust, and other sources are too vague about what it is they would have me do. I'm willing to load almost any OS into the media center laptop provided I can...
Hi Leifi, You wrote: "Snapraid works on top of the existing file system". Oh! That's a show-stopper.
Hi David, You wrote: "...you seem wedded to using RAID0" I'd actually prefer RAID-4. You wrote: "I'm not sure why you insist on that." So that if one of the drives in the RAID goes bad, I can replace it and rebuild the RAID. Of course, you can't do that with RAID-0. That's why I actually want RAID-4, but providers think RAID-4 is not viable anymore and insist on RAID-5. But RAID-5 would require me to carry around 3 drives, and I don't want to do that. It's really unnecessary because there's a smart...
David, I'm mystified by your response. But no matter. I assume you will not help me. That's okay, but I wish I could find a soft-RAID-0. Perhaps (misleadingly-named) SnapRAID is the way to go for parity, but first I need the array. How I will create the array remains my first priority. I apologize for wasting your time. I was mislead (https://sourceforge.net/p/snapraid/discussion/1677233/thread/37fe949fe4/#4827) into thinking SnapRAID provided the RAID. Oh, well.
David, I'm mystified by your response. But no matter. I assume you will not help me. That's okay, but I wish I could find a soft-RAID-0. Perhaps (misleadingly-named) SnapRAID is the way to go for parity, but first I need the array. How I will create the array remains my first priority. I appologize for wasting your time. I was mislead (https://sourceforge.net/p/snapraid/discussion/1677233/thread/37fe949fe4/#4827) into thinking SnapRAID provided the RAID. Oh, well.
Thank you so much for your comments, David. I feel your frustration that I don't seem to 'get it'. Based on my background, perhaps I'm misleading myself -- I once designed a 17-drive RAID-5 for NetApp... I think it was 17 drives. You wrote: If you have a 8TB RAID0 set, then you have 2 4TB drives striped, correct? I have nothing right now. I have one 4TB, USB, media drive and it's full (and, it's unprotected). I want to create a 2-drive RAID-0 for media, then add a 3rd (parity) drive for protection...
Thank you so much for your comments, David. I feel your frustration that I don't seem to 'get it'. Based on my background, perhaps I'm misleading myself -- I once designed a 17-drive RAID-5 for NetApp... I think it was 17 drives. You wrote: If you have a 8TB RAID0 set, then you have 2 4TB drives striped, correct? I have nothing right now. I have one 4TB, USB, media drive and it's full (and, it's unprotected). I want to create a 2-drive RAID-0 for media, then add a 3rd (parity) drive for protection...
Thank you so much for your comments, David. I feel your frustration that I don't seem to 'get it'. Based on my background, perhaps I'm misleading myself -- I once designed a 24-drive RAID-5 for NetApp... I think it was 24 drives. You wrote: If you have a 8TB RAID0 set, then you have 2 4TB drives striped, correct? I have nothing right now. I have one 4TB, USB, media drive and it's full (and, it's unprotected). I want to create a 2-drive RAID-0 for media, then add a 3rd (parity) drive for protection...
Thank you so much for your comments, David. I feel your frustration that I don't seem to 'get it'. Based on my background, perhaps I'm misleading myself -- I once designed a 24-drive RAID-5 for NetApp... I think it was 24 drives. You wrote: If you have a 8TB RAID0 set, then you have 2 4TB drives striped, correct? I have nothing right now. I have one 4TB media drive and it's full (and, it's unprotected). I want to create a 2-drive RAID-0 for media., then add a 3rd (parity) drive for protection of...
Thank you so much for your comments, David. I feel your frustration that I don't seem to 'get it'. Based on my background, perhaps I'm misleading myself -- I once designed a 24-drive RAID-5 for NetApp... I think it was 24 drives. You wrote: If you have a 8TB RAID0 set, then you have 2 4TB drives striped, correct? I have nothing right now. I have one 4TB media drive and it's full (and, it's unprotected). I want to create a 2-drive RAID-0 for media., then add a 3rd (parity) drive for protection of...
Hi David, I read all the documents many times before I joined this forum. The documents provide hints regarding how to use SR, but nothing I read said what SR is. How about I start with my requirements. I'm making a media server/home theater combo from an old Win7 laptop. I want to add a 2-drive, 8TB RAID-0, then 'back it up' via a 3rd, 4TB drive (for parity, thus making a RAID-4). With a set-up like that, I could take the 8TB on the road and leave the 4TB parity drive at home. From what I've read,...
Hi David, I read all the documents many times before I joined this forum. The documents provide hints regarding how to use SR, but nothing I read said what SR is. How about I start with my requirements. I'm making a media server/home theater combo from an old Win7 laptop. I want to add a 2-drive, 8TB RAID-0, then 'back' it up via a 3rd, 4TB drive (for parity, thus making a RAID-4). With a set up like that, I could take the 8TB on the road and leave the 4TB parity drive at home. From what I've read,...
So SnapRAID is not a device driver. It cannot create a stripe set. It cannot create a RAID-0 or RAID-4. Am I correct?
I've been studying the various commands. I see no command that actually creates a soft RAID. Does SnapRAID create the RAID, or do I need to look elsewhere? Here: http://forum.flexraid.com/index.php?topic=49615.0#msg78676, in a post titled "Why I am leaving FlexRaid behind", KarlF writes: "It [DrivePool by StableBit] provides drive-pooling only, while Snapraid (free) provides software RAID". Does SnapRAID provide a software RAID?
From here: https://www.snapraid.it/manual 4 Getting Started To use SnapRAID you need to first select one disk of your disk array... What disk array? I hoped SnapRAID could be used to create a RAID-4, but it apparently cannot. Or am I missing something? Warm Regards, Mark Filipak, retired Electronic R&D Engineer & Computer System Architect.
From here: https://www.snapraid.it/manual 4 Getting Started To use SnapRAID you need to first select one disk of your disk array... What disk array? I hoped SnapRAID could be used to create a RAID-4, but it apparently cannot. Or am I missing something? Warm Regards, Mark Filipak, retired Electronic R&D Engineer & Computer System Architect.
github, eh? What is the URL? Every time I go to github (for Linux Mint), I can't...
...you edited your comment... Aha! I see that the 'eye' to the upper-right is a preview...
...documentation is stalled. I would be delighted to write high-quality documentation...
...documentation is stalled. I would be delighted to write high-quality documentation...
I don't know that they are different issues. I can't figure out how the CLI program...
I don't know that they are different issues. I can't figure out how the CLI program...
I don't know that they are different issues. I can't figure out how the CLI program...
I don't know that they are different issues. I can't figure out how the CLI program...
I don't know that they are different issues. I can't figure out how the CLI program...
I don't know that they are different issues.
I downloaded the latest version (0.7.91) and tried this: C:\Program Files>MediaInfo...
I downloaded the latest version (0.7.91) and tried this: C:\Program Files>MediaInfo...
Oh my. It now works -- I took the quotes (") out of MediaInfo.args.utf8... But, I've...
Oh my. It now works -- I took the quotes (") out of MediaInfo.args.utf8... But, I've...
Win7 64-bit, using command line. This next command line works C:\Program Files (x86)>MediaInfo...
Thank you, Rob. That seemed to do the trick. Now all I have to do is figure out how...
Thank you, Rob. That seemed to do the trick. Now all I have to do is figure out how...