Persistent Virtual Machine Mount

Question

Level 1

4 points

Persistent Virtual Machine Mount

Ive been trying my best configure a RAID system which includes having Windows Partitions. As someone who is in the media industry we use applications and files that can be demanding od a lot of performance and storage capacity. Also need to be Mobile/Remote at times.

My biggest issue is that, I am currently using a MacBook Pro M2 2023, and Previously I was on the IMac 2012, and I also have the G10250 Cheese grater. My Object was to utilize the Cheese as the Main Storage for the media files and to have the IMac as the Main Communication Administrator between the MacBook and the Files/data. Now what seemed to have happened is that, the MacBook Pro has now integrated the Cheese-grater's system information whilst I was still trying to configure the set-up. So my original MacBook Pro FileSystem has gone vanished, as I was trying to unmount and restore the Disk Image.

Now I am sitting on a Device tree path : IODeviceTree:/arm-io@10F00000/ans@77400000/iop-ans-nub/AppleANS3NVMeController

which was not intended. I think when I was configuring the networking ports and all on the HUAWEI-B535, since the default site is unencrypted, and I was still using default addresses it may have occurred that the communication between devices got juggled up. I tried to go a simpler route by using Xammp but I think that just made everything even more messy.

Please send Help!

Yours Truly

T

MacBook Pro 13″, macOS 15.5

Posted on May 5, 2025 3:40 AM

Reply

Answer 1

May 5, 2025 6:50 AM in response to TshephegoM

<< the G10250 Cheese grater. >>

That number is not familiar.

What model-year MacPro?

<< Now I am sitting on a Device tree path : IODeviceTree:/arm-io@10F00000/ans@77400000/iop-ans-nub/AppleANS3NVMeController. >>

Most users have never even SEEN such designations, and you say you are "sitsing on one" ?

what are you trying to say?

You don't need a Virtual Machine OR a Windows partition to host Windows files on a Mac File server.

Reply

Answer 2

May 5, 2025 6:51 AM in response to TshephegoM

R in RAID is for redundant, but RAID is NOT backup!

• Mirrored RAID is used to reduce the time-to-repair after a failure, and to keep drive failures from becoming a data disaster. It does not protect from human error, crazy software, or 'just-because' failures.

• Striped RAID can be somewhat faster in some cases (especially in an array built from Rotating Magnetic drives), but it is brittle, and you MUST have another copy nearby in case of failure. A striped RAID failure destroys EVERYTHING on it, with No hope of recovery. Most users would be better served by a faster SSD than a striped rotating magnetic RAID.

• Concatenated RAID is not really RAID at all, it is "just a bunch of drives" aka JBOD, pasted together and acting as if it were one HUGE drive. So you can take two larger drives, concatenate them into one Volume, and have a really big Backup drive, for example.

• RAID 5 computes checksums of the data blocks (in real-time, coming and going), and stores two copies of the data AND the checksum blocks in such a way that a failure in any one of the three drives still allows the data can to be recovered from the other two drives. It requires checksum-computing hardware to be seen as anywhere near fast enough for most uses.

Criticisms of RAID-5 include the cost and delays induced by the extra hardware, and the HUGE amount of time it takes to re-create a large data set using RAID-5. Re-creation time is so large, another drive is non-trivially likely to fail in the time it takes to re-create the data, making the entire concept shaky.

Executive summary: Most users would be better served using multiple drives to make multiple backups, rather than dedicating multiple drives to RAID arrays.

Reply

Answer 3

g_wolfman

Level 4

3,142 points

May 5, 2025 3:40 PM in response to TshephegoM

I'm sorry, but nothing in your post makes sense. Can you please explain - step-by-step if possible what you think you did to get into this...well, I hesitate to call it a "state" yet.

IODeviceTree:/arm-io@10F00000/ans@77400000/iop-ans-nub/AppleANS3NVMeController is the standard path for an OEM Apple NVMe SSD - i.e., your internal storage. But you shouldn't ever be seeing the Device Path unless you are looking at the detailed system information, or in the command line running some at least uncommon, if not actually rare and unusual, commands. Saying that you are "sitting on a Device tree path" doesn't make sense in any context I can think of.

Similarly no computer can "integrate" another's information, unless you mean you were using Migration Assistant to set the target up - but that has nothing to do with configuring a Huawei broadband 4G modem...

It sounds like a bunch of device configurations are jumbled together in your description (in ways that they can't possibly be jumbled in the real world). So we're going to need oyu to help disambiguate what happened here.

Reply