But Since I Am Here.. Need To Set Up 8TB Drive

  • How exactly would I adjust the offset for my particular setup.

    Let parted decide: mkpart mylabel ext4 0% 100%

    Please note that the first mkpart parameter for gpt is the gpt partition label.

    Use unit s or unit B (check help unit) to see the exact alignment with print.

    .. I am guessing the 512B/4096B has something to do with it

    The hard disk is internally using 4096 byte sectors but the command interface counts 512 byte sectors.

    Windows became my addiction

    diskpart is not that different :)

  • OK It looks like I need to scan the HD as per Joe Average's initial suggestion.. It will likely take a while, so I will check back in when it's done..


    Thanx to all for the help and suggestions... It's very much apprecaited..

  • I always thought it meant Keep It Simple, Stupid... :cool:

    Klojum you're talking scrap ! :@


    Then the fsck.ext4 gave me this..

    fsck.ext4 or e2fsck shouldn't run on an mounted partition

    fsck.ext4(8): check ext2/ext3/ext4 file system - Linux man page

    Chap. "Description",

    2cd Paragraph:

    cit.: "Note that in general it is not safe to run e2fsck on mounted filesystems. ..."

    Edited 2 times, last by GDPR-7: Merged a post created by JoeAverage into this post. (December 19, 2021 at 8:45 PM).

  • I am thinking that this means what Joe Average was talking about above?? That the HD has some bad areas??

    Bad areas or Bad Blocks are damaged area's on a disk.

    Superblock are ~sorta~ additional copies of partition table/filesystem info's

    a partition table is created when you create a partition on the disk

    Superblocks are created when you create the ext4 filesystem

    e2fsck or fsck.ext4 checks Superblocks too

    if e2fsck cries regarding Superblocks something is up with your filesystem

    in general:

    a disk should always be unmounted when you

    - create a partition [1]

    - create a filesystem

    - fsck the filesystem (though, a readonly switch for mounted FS is available)

    [1]

    afterwards the linux kernel isn't aware of the new created partition

    either a reboot or partprobe (thanks @frakkin64) should do the re-reading

    you could always feed google with the commands you aren't clear about e.g.

    man parted

    Edited 2 times, last by GDPR-7 (December 19, 2021 at 8:57 PM).

  • after creation of the 8TB partition, did you create a file systen, e.g. with mkfs.ext4?

    in your commands I see only fsck.ext4 (probably on an uninitialied partition).