Reply
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
FDISK errors on RN102/OS6
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2013-09-22
02:21 AM
2013-09-22
02:21 AM
FDISK errors on RN102/OS6
Is the
I have a WD Red 3TB in the NAS and just connected a 1TB drive via usb3.0, I want to use this one for backup.
Errors on filesystems makes it feel unreliable.
Here's my fdisk list
bad?
WARNING: GPT (GUID Partition Table) detected on '/dev/sdb'!
I have a WD Red 3TB in the NAS and just connected a 1TB drive via usb3.0, I want to use this one for backup.
Errors on filesystems makes it feel unreliable.
Here's my fdisk list
root@nasischijf:/# fdisk -l
Disk /dev/mtdblock0: 1 MB, 1572864 bytes
255 heads, 63 sectors/track, 0 cylinders, total 3072 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0xf7ff1c18
Disk /dev/mtdblock0 doesn't contain a valid partition table
Disk /dev/mtdblock1: 0 MB, 131072 bytes
255 heads, 63 sectors/track, 0 cylinders, total 256 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x322e3535
Disk /dev/mtdblock1 doesn't contain a valid partition table
Disk /dev/mtdblock2: 6 MB, 6291456 bytes
255 heads, 63 sectors/track, 0 cylinders, total 12288 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0xe1a0f004
Disk /dev/mtdblock2 doesn't contain a valid partition table
Disk /dev/mtdblock3: 4 MB, 4194304 bytes
255 heads, 63 sectors/track, 0 cylinders, total 8192 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0xfca4bafb
Disk /dev/mtdblock3 doesn't contain a valid partition table
Disk /dev/mtdblock4: 121 MB, 121634816 bytes
255 heads, 63 sectors/track, 14 cylinders, total 237568 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000
Disk /dev/mtdblock4 doesn't contain a valid partition table
WARNING: GPT (GUID Partition Table) detected on '/dev/sda'! The util fdisk doesn't support GPT. Use GNU Parted.
Disk /dev/sda: 3000.6 GB, 3000592982016 bytes
256 heads, 63 sectors/track, 363376 cylinders, total 5860533168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0x00000000
Device Boot Start End Blocks Id System
/dev/sda1 1 4294967295 2147483647+ ee GPT
Partition 1 does not start on physical sector boundary.
Disk /dev/md0: 4290 MB, 4290772992 bytes
2 heads, 4 sectors/track, 1047552 cylinders, total 8380416 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0x00000000
Disk /dev/md0 doesn't contain a valid partition table
Disk /dev/md1: 536 MB, 536281088 bytes
2 heads, 4 sectors/track, 130928 cylinders, total 1047424 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0x00000000
Disk /dev/md1 doesn't contain a valid partition table
Disk /dev/md127: 2995.6 GB, 2995624738816 bytes
2 heads, 4 sectors/track, 731353696 cylinders, total 5850829568 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0x00000000
Disk /dev/md127 doesn't contain a valid partition table
WARNING: GPT (GUID Partition Table) detected on '/dev/sdb'! The util fdisk doesn't support GPT. Use GNU Parted.
Disk /dev/sdb: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders, total 1953525168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000
Device Boot Start End Blocks Id System
/dev/sdb1 1 1953525167 976762583+ ee GPT
Message 1 of 4
Labels:
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2013-09-22
04:18 AM
2013-09-22
04:18 AM
Re: FDISK errors on RN102/OS6
NOTE- I split this from the original topic, since it was totally unrelated
I see the same sort of errors, but everything appears normal.
None of these are file system errors, fdisk isn't recognizing the partitions below the file system.
I see the same sort of errors, but everything appears normal.
None of these are file system errors, fdisk isn't recognizing the partitions below the file system.
Message 2 of 4
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2013-09-22
04:36 AM
2013-09-22
04:36 AM
Re: FDISK errors on RN102/OS6
With disks that use the GPT partitioning scheme you need to use sgdisk not fdisk to print the partition table. fdisk only supports the MBR partitioning scheme. For disks larger than 2TB in capacity the GPT partitioning scheme is needed. For your internal and external disks run these commands:
# sgdisk -p /dev/sda
# sgdisk -p /dev/sdb
Message 3 of 4
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2013-09-22
01:42 PM
2013-09-22
01:42 PM
Re: FDISK errors on RN102/OS6
mdgm wrote: With disks that use the GPT partitioning scheme you need to use sgdisk not fdisk to print the partition table. fdisk only supports the MBR partitioning scheme. For disks larger than 2TB in capacity the GPT partitioning scheme is needed. For your internal and external disks run these commands:
# sgdisk -p /dev/sda
# sgdisk -p /dev/sdb
Aaah okay, so there's nothing to worry about, the only point is that fdisk is not equipped to correctly show the information. Thanks!
Message 4 of 4