Cannot Transfer File to USB (Too Large?) - windows

I bought a 64gb USB to install Windows on since my version of Windows corrupted. When I download the ISO and try to drag it to my USB it says that the file size is too large (even though it's less than 5gb). I was wondering if I was doing anything wrong here and if anyone could help me. Screenshots: https://prnt.sc/lq8dy2 https://prnt.sc/lq8dpx
Thank you!
Edit: Wrong section, was going to delete this post but someone already posted an answer.

Is your drive formatted to NTFS? If it is Formatted as Fat32 and the file size is larger than 4GB it won't work, because Fat32 only supports files up to 4GB.
Try formatting the USB Drive to NTFS and see if that works.

Related

Centos 7 installer shows incorrect free space

I booted from a USB to install centos7 onto another USB.
However, when I tried to select the installation destination, the installer showed incorrect (very little) free space on all my devices, shown as in the figure below.
Indeed both sdb and sdc are empty, formatted in FAT32 and NTFS, respectively.
sda is the HDD on my PC, which is also only about 50% full.
Anyone knows how this can happen?
installation destination
OK, the answer seems that I have to delete the partition first on the "installation destination" page, although the devices are originally empty. After deletion the devices become completely free and I can allocate the mount points.

Any tool that can confirm if a drive with raw partition is part of a ZFS pool?

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.

copying an Apple Mac Hard Drive from a dead mac?

I have little experience with macs so I thought I would ask a quick question before I go ahead with this.
My friend's 6 year old mac desktop died the other day, she took it into the tech guys at the apple store to find out if she can get her documents back and they said no because the hard drive is in a different code you can't take it out.
That sounds like a load of crap to me so I want to rip out the hard drive and plug it into my PC then copy everything over. I also have access to linux if I need to.
So is there anything I need to know before doing this?
Thanks!
Assuming the hard drive itself isn't dead, you can get your hands on something like Ubuntu and copy all the files onto a different hard drive. You usually can't do this from windows because windows uses NTFS file system and will not recognize the mac file system (HFS or HFSPlus). Most flavors of linux can recognize mac hard drives and copy the contents. There can be some tricks with ownership of the files so here's a good post on how to do this in ubuntu:
http://ubuntuforums.org/archive/index.php/t-852144.html
Hope that helps!
If your friend plans on buying a new Mac, you should keep the disk itself; with an external HDD enclosure, a new machine (or a new OSX installation) will be able to migrate basically everything from the old drive.
Late answer, I know, but I just rescued a broken mac disk using dd_rescue, booting Trinity 3.4 on a HP and cloning the broken disk to a working disk. Then I popped the working disk into a working mac and hey presto, the user got the files back.

All partitions missing when copying

I bought a new 320GB SATA hard drive few months ago no recently when i try to copy something to the drive after about 20 seconds the all the partitions in the hard drive suddenly disappears.
The hard drive is not shown in either Disk manager or device manager. To get the HD work i have to restart the PC again.The same thing happens when i try to copy. Even when i play any audio or video after abt 5 minutes i get the same problem.
The drives are NTFS and im running Windows XP.. Xan some one please help me solve the problem??
did you check all the wires ? sounds like a disconnect of the wire somehow ... otherwise the hdd is broken...
The problem was the ide hard drive that i had connected, there seems to be a speed issue. Changing the ide to a different sata drive solved it

Best file system to transfer 5+GB files between OS X and Windows on removable media

I need to transfer DVD image files between a Windows XP computer and a Mac running Leopard.
The machines are not connected via a fast network, and I have a few USB drives floating around that I want to use, e.g. 8GB flash, 60GB and 250GB USB hard drives.
Sometimes the files creep above 4GB (the maximum size of a single file on FAT32), and I've had no luck with NTFS on Leopard. I'm not aware of any drivers for XP/Vista that support Mac file systems like HFS.
Anyone got any suggestions as to what file system would best suit here?
Thanks
Tom
What did you try for NTFS on Leopard?
It's pretty simple:
install MacFUSE and NTFS-3G driver.
???
Profit.
You could use split on the Mac to divide the files up into 2GB fragments and then recombine the fragments on Windows using copy.
split -b 2048m file
copy xxa + xxb file
You could try a linux filesystem, e.g. with e2fs on mac (I've only ever tried reading these however). There are drivers for windows.
Alternatively you could use the split utility on the mac to cut the file up into smaller chunks, and recombine them on windows.
Formatting to exFAT worked for me, it suppose to have some limitations with old-windows but is not my case.

Resources