I have a 32GB USB drive that I am trying to use as both a boot drive for a ChromeOS version available from here, and to use the remaining space on the drive as I normally would, just for storage to be accessed via Windows or hopefully the ChromeOS.
I've tried partitioning it in various ways using EaseUS, but every time I've written the ChromeOS image to a partition with the Win32DiskImager, I can't access the larger partition I want as storage.
I feel like I'm missing something major here, can anyone shed some light on this for me?
Thanks!
when you make a bootable usb using ChromeOs image
When does resizing occur?
Partition resizing is initiated by the system, not by the user.
refer here for more information
Related
I want to improve my backup system by using RAID technology accompanied by Cloud backup services.
I use several macOS computers, and would prefer the NAS solution over the DAS one.
The first step would be to backup all my existing data.
I currently store it in external HHD/SSD formatted in HFS+ Journaled;
1x HDD 4TB - almost full - Format: HFS+ Journaled.
1x SSD 4TB - almost full - Format: HFS+ Journaled.
1x SSD 1TB - almost full - Format: HFS+ Journaled.
My professional surroundings as well as reviews on the internet often recommend the brand Synology.
I was tempted to make the following investment according to my needs:
Synology DS1821+ (8 bays)
5x 8TB HHD (WD Red Plus WD80EFZX 8TB)
SHR-2 protection type (24TB of free space, 16TB allocated for protection)
IDrive® Cloud backup service (provides DSM extension).
Problem:
I want to find the best way to efficiently and safely transfer all my current data (around 10 TB) from my external HDD/SSD disks (HFS+ Journaled fromats) to the future NAS volume.
I have the feeling that doing so via SMB or FTP will be way to long and uncertain.
So I thought that the most straight forward way would probably be to simply connect each external disks directly to the NAS (USB 3.1), and simply transfer portions of all data manually directly in DSM.
However, after extra investigations, I was surprised to learn the following:
Synology knowledge base says:
https://www.synology.com/enus/knowledgebase/DSM/help/DSM/AdminCenter/system_externaldevice_devicelist
Some models support HFS/HFS Plus with read-only.
Journal is not supported on HFS/HFS Plus.
You will need to install exFAT Access from Package Center to enable Synology NAS to support exFAT.
Make sure you have ejected the external disk before unplugging it.
Clearly states that no model supports journaling.
Product specs says:
https://www.synology.com/en-us/products/DS1821+#specs
Unless I am missing it, it does not inform much about the journaling matter or size limits.
About disabling journaling via the Disk utility app on macOS:
It feels like it is only possible via CLI these days (since BigSur).
I understand what disabling journaling implies, that it is probably not a big deal for temporary transferring all the data to the NAS, but I still would like to avoid such accommodations as much as possible (I've never done it, I don't know).
I looked for NAS alternatives that would support HFS+ Journaled formats but couldn't find any.
Are my concerns justified or am I overthinking this ?
Any pieces of advice from experienced NAS & macOS users would be much appreciated.
I have a client issue that I am working on with a stack of SSD drives and a machine that they were previously installed in. As of now, the stack of drives shows up in a few Operating Systems (Win10, Win7, Mac OSX) as an unpartitioned raw space. I am looking for a simple way to examine the drive and see if it is actually raw, or just formatted for ZFS.
Does anyone know of a Windows or Mac Utility that could help? I've tried a few recovery software programs, that hinted at being compatible with ZFS formatted drives, but have yet to see anything that would indicate if it was actually a ZFS, or simply not formatted.
Regards,
Ed
ZFS is storing at the start and at the end of each device a magic number, 0x00bab10c ("oobabloc", i.e. überblock), reversed for little-endian: 0x0cb1ba00.
So if this number doesn't appear in the device data, you can be sure it isn't used by ZFS. If it does appear, you need to investigate a little further.
For details, have a look to the ZFS on disk specification draft available here, especially page 13.
In genymotion settings->storage there is only the internal storage, no SD card.
Is there a way to have a SD card also?
There's already some emulation of SD card (external) storage in Genymotion that might work for you, depending on what you're trying to do. Although Settings->Storage doesn't show it separately as External Storage like you might expect, Genymotion does emulate external storage. The size of files stored there will be reflected in the totals shown under Internal Storage by Settings-Storage.
Running in Genymotion, an app using Environment.getExternalStorageDirectory().getPath() or .getAbsolutePath() will get back /storage/emulated/<userId>, where userId=0 if the app is running as Owner, and 10, 11, 12, etc. if the app is running as another user or restricted/managed profile. The Android framework actually maps this for you to /mnt/shell/emulated/<userId>, which is why you won't find /storage/emulated/<userId> if you use a shell to poke around.
The paths /sdcard and /mnt/sdcard are symlinks to /storage/emulated/legacy, which is basically the Owner's storage. Don't use these in your apps, since they might not exist everywhere and/or your app might not have access to them if not running as Owner. They are just there to support legacy hardcoded apps.
Not being sure what you're trying to do, it's probably also worth mentioning that Genymotion now supports VirtualBox shared folders which will appear under /mnt/shared inside your VM. Check their Google+ post for instructions.
Dokan currently does not create a virtual hard disk for its filesystem (i.e. in Device manager, you dont see another disk drive). Anyone have any idea on how to start to correct that?
Dokany is the active fork of Dokan and bring the ability to create virtual drive.
Dokany have made big progress by implementing the mount manager of dokan. There is only the PnP part that is not totally implemented. When this will be added, you will see the dokan device in the device manager.
Representation in device manager requires a plug-n-play device driver. so you need to write one. Or use our Callback File System
How does one go about creating a virtual CD driver on Mac OS X programatically?
I can't find any relevant Cocoa APIs or any pure C BSD solutions.
Any help or information is appreciated.
You would need to use the I/O Kit framework to develop your own device driver that would emulate a virtual CD drive. Here are some links to the relevant APIs to get you started.
I/O Kit Fundamentals
I/O Kit Device Driver Guidelines
Kernel Extension Programming Topics
There are several different answers people have proposed here. The issue at hand is what are you trying to accomplish. If you really want to emulate a CD ROM (down to the commandset) you will need to write a device driver. If your goal is merely to emulate a block device with contents similiar to a CD you can create a disk image using disk utility and let the builtin disk image driver handle it for you.
MacFUSE is useful if you want to present some sort of custom filesystem functionality, but if what you are looking for is something that has the same semantics as an optical disc (whether that is and block or command set level) it is the wrong tool.
If you're simply looking to mount an ISO or something then it's done through the Disk Utility, simply drag it into the side-bar and then select it and choose mount.
If you want to do it from code you can issue the hdiutil command, as shown here. I'm not sure if there's an API call to do it, but getting that command to do the work is quite painless.
The simplest way to mount a custom volume is MacFUSE. It handles the IOKit details for you and lets you write the implementation in user space. However, I don’t think you can make a MacFUSE “look like” a CD; you’d have to modify FUSE to achieve that.
I had a nosey around DAEMON Tools for Mac's driver:
/Library/Extensions/DAEMONToolsVirtualSCSIBus.kext/Contents/MacOS/DAEMONToolsVirtualSCSIBus
I disassembled the binary using Hopper and discovered they are using
IOSCSIProtocolServices.