TL;DR:
# mkntfs --label media1 --fast /dev/sdb
/dev/sdb is entire device, not just one partition.
Refusing to make a filesystem here!
Why does the script "refuse to make a filesystem on the entire device"?
In detail:
What are the possible downsides if the whole disk is formatted as NTFS? I.e. not one single big partition taking up all the space, but the disk itself.
I imagine that as a system disk (i.e. for running Windows) it would not work, because there would be no space for a boot loader. (Or would be? Does formatting the whole disk also overwrite the MBR area?)
But what if the disk is used only as a data storage? (This is the part that is more relevant to me at the moment.) Would all the OS-es that support NTFS (Windows/Linux/...) still be able to correctly read and write files? Would all other devices handle it correctly? (E.g. HDD connected to a TV via USB.)
Or is there any chance that this could cause irreversible damage to the disk? (This is what is preventing me from simply trying it out.)
Remarks:
I know that I could force formatting the whole drive with the
mkntfs -F
flag, so the question is not how to do it, but whether I should or not?Why would I want to do that in the first place, you may ask? The answer is, why waste space on the partition metadata, if I'm going to use the whole disk as data storage anyway? (But I'm interested in the system-disk POW too, just for broadening my perspective.)