En el artículo <
465cmclfeq1ibed45...@4ax.com>, Richard
Treen <
treen...@googlemail.com> escribió:
>"Supported drive mappings: GUID Partition Table (GPT) and Master Boot
>Record (MBR)" I'm not so sure of
A drive has to be partitioned before use. The partition table contains
information on how the drive has been divided into logical volumes.
There's the legacy MBR (master boot record) and the newer GPT (GUID
partition table).
It's like a list of chapters in a book. The list tells you how many
chapters are present and the page number each starts at.
For your purposes, it doesn't matter which is used unless the drive is
larger than 2TB, in which case GPT is required.
Once the drive is partitioned, a filesystem is then laid down within the
partition(s). These can be NTFS, FAT32, Linux ext2/3/4, etc.
The filesystem is blank pages with page numbers. Writing data to the
drive is filling those pages with words, then the filesystem creates an
index (the FAT in FAT, FAT16, FAT32, exFAT, etc) or the MFT (Master file
table) in NTFS.
>Where can I read the current state in this regard on the drive?
As Chris said, gparted will show you how the drive is laid out and
attempt to correct any errors.
>Does this not get cleared and renewed during formatting?
Formatting creates a filesystem, not a partition table. If there are
problems with the partition table, this might be why the router is
complaining.
The error you quote isn't helpful. What would be helpful is the exact
error thrown by the attempt to mount the drive. This might be visible
in your router's system log.
One possibility is that you've created the NTFS fileystem in Win10. I
don't know if the Linux NTFS code (assuming your router runs Linux) has
yet caught up with the substantial changes to NTFS M$ made in Win10.
If the drive is 2TB or smaller, I suggest you try reformatting it with
MBR and use FAT32 or exFAT as the filesystem, and see if that works.
--
(\_/)
(='.'=) "Between two evils, I always pick
(")_(") the one I never tried before." - Mae West