TeraByte Unlimited

I have used partinfo to analyse my disks and need some help on interpreting the data for disk1. This disk is intended to be used as a data drive - does anyone have any idea what is going on there and how I should best address the error?
and Happy New Year to everyone

PARTINFW 1.14
Copyright (c) 1996-2008,2013 TeraByte, Inc. All rights reserved.

Run date: 12/31/2015 10:34

======================================================================
MBR Partition Information (HD0 - 0xA6A1F4CA)
(CHS: 496/46/36) (WCHS: 345652/47/36)
+====+====+=============+====+=============+============+============+
| 0: | 0 | 0 1 1 | de | 38 4 36 | 36 | 65952 |
| 1: | 80 | 39 44 13 | 7 | 1023 46 36 | 67584 | 6291456 |
| 2: | 0 | 1023 14 1 | 7 | 1023 46 36 | 6359040 | 309168128 |
| 3: | 0 | 1023 36 21 | 7 | 1023 46 36 | 315527168 | 269316096 |
+====+====+=============+====+=============+============+============+
BOOT SECTOR INFORMATION
-------------------------------------------------------------------------------
File System ID: 0x7 LBA: 67584 Total Sectors: 6291456 ID: 0x2
Jump: EB 52 90
OEM Name: NTFS
Bytes Per Sec: 512
Sec Per Clust: 8
Res Sectors: 0
Zero 1: 0x0
Zero 2: 0x0
NA 1: 0x0
Media: 0xF8
Zero 3: 0x0
Sec Per Track: 36
Heads: 47
Hidden Secs: 67584
NA 2: 0x0
NA 3: 0x800080
Total Sectors: 0x05FFFFF
MFT LCN: 0x040000
MFT Mirr LCN: 0x02
Clust Per FRS: 0xF6
Clust Per IBlock: 0x1
Volume SN: 0xB65285365284FBFD
Checksum: 0x0
Boot Flag: 0xAA55
-------------------------------------------------------------------------------
File System ID: 0x7 LBA: 6359040 Total Sectors: 309168128 ID: 0x3
Jump: EB 52 90
OEM Name: NTFS
Bytes Per Sec: 512
Sec Per Clust: 8
Res Sectors: 0
Zero 1: 0x0
Zero 2: 0x0
NA 1: 0x0
Media: 0xF8
Zero 3: 0x0
Sec Per Track: 36
Heads: 47
Hidden Secs: 6359040
NA 2: 0x0
NA 3: 0x800080
Total Sectors: 0x0126D87FF
MFT LCN: 0x0C0000
MFT Mirr LCN: 0x02
Clust Per FRS: 0xF6
Clust Per IBlock: 0x1
Volume SN: 0xEA14879614876483
Checksum: 0x0
Boot Flag: 0xAA55
-------------------------------------------------------------------------------
File System ID: 0x7 LBA: 315527168 Total Sectors: 269316096 ID: 0x4
Jump: E9 57 0
OEM Name: NTFS
Bytes Per Sec: 512
Sec Per Clust: 8
Res Sectors: 0
Zero 1: 0x0
Zero 2: 0x0
NA 1: 0x0
Media: 0xF8
Zero 3: 0x0
Sec Per Track: 36
Heads: 47
Hidden Secs: 315527168
NA 2: 0x0
NA 3: 0x800000
Total Sectors: 0x0100D6FFF
MFT LCN: 0x032
MFT Mirr LCN: 0x019AF199
Clust Per FRS: 0xF6
Clust Per IBlock: 0x1
Volume SN: 0x1D010DA4B8A1580
Checksum: 0x0
Boot Flag: 0xAA55
-------------------------------------------------------------------------------
======================================================================
MBR Partition Information (HD1 - 0x6E697373)
(CHS: 1022/254/63) (WCHS: 36404/255/63)
+====+====+=============+====+=============+============+============+
| 0: | d | 335 10 2 | 7 | 327 84 13 | 1936269394 | 1836016416 |
| 1: | 70 | 371 114 37 | 73 | 256 101 36 | 1917848077 | 544437093 |
| 2: | 43 | 364 116 50 | 2b | 372 65 44 | 1818575915 | 544175136 |
| 3: | 72 | 372 101 51 | 61 | 269 114 52 | 2844524554 | 54974 |
+====+====+=============+====+=============+============+============+
BOOT SECTOR INFORMATION
-------------------------------------------------------------------------------
Error reading LBA 1936269394
-------------------------------------------------------------------------------

it's either just a bunch of garbage or it's not a partitioned drive.

What do you see in the list of partitions for that drive in IFW/IFL or IFD
(or BootIt Partition Work) ?


"beethoven" wrote in message news:[email protected]...

I have used partinfo to analyse my disks and need some help on interpreting
the data for disk1. This disk is intended to be used as a data drive -
does anyone have any idea what is going on there and how I should best
address the error?
and Happy New Year to everyone

PARTINFW 1.14
Copyright (c) 1996-2008,2013 TeraByte, Inc. All rights reserved.

Run date: 12/31/2015 10:34

======================================================================
MBR Partition Information (HD0 - 0xA6A1F4CA)
(CHS: 496/46/36) (WCHS: 345652/47/36)
+====+====+=============+====+=============+============+============+
| 0: | 0 | 0 1 1 | de | 38 4 36 | 36 | 65952 |
| 1: | 80 | 39 44 13 | 7 | 1023 46 36 | 67584 | 6291456 |
| 2: | 0 | 1023 14 1 | 7 | 1023 46 36 | 6359040 | 309168128 |
| 3: | 0 | 1023 36 21 | 7 | 1023 46 36 | 315527168 | 269316096 |
+====+====+=============+====+=============+============+============+
BOOT SECTOR INFORMATION
-------------------------------------------------------------------------------
File System ID: 0x7 LBA: 67584 Total Sectors: 6291456 ID: 0x2
Jump: EB 52 90
OEM Name: NTFS
Bytes Per Sec: 512
Sec Per Clust: 8
Res Sectors: 0
Zero 1: 0x0
Zero 2: 0x0
NA 1: 0x0
Media: 0xF8
Zero 3: 0x0
Sec Per Track: 36
Heads: 47
Hidden Secs: 67584
NA 2: 0x0
NA 3: 0x800080
Total Sectors: 0x05FFFFF
MFT LCN: 0x040000
MFT Mirr LCN: 0x02
Clust Per FRS: 0xF6
Clust Per IBlock: 0x1
Volume SN: 0xB65285365284FBFD
Checksum: 0x0
Boot Flag: 0xAA55
-------------------------------------------------------------------------------
File System ID: 0x7 LBA: 6359040 Total Sectors: 309168128 ID: 0x3
Jump: EB 52 90
OEM Name: NTFS
Bytes Per Sec: 512
Sec Per Clust: 8
Res Sectors: 0
Zero 1: 0x0
Zero 2: 0x0
NA 1: 0x0
Media: 0xF8
Zero 3: 0x0
Sec Per Track: 36
Heads: 47
Hidden Secs: 6359040
NA 2: 0x0
NA 3: 0x800080
Total Sectors: 0x0126D87FF
MFT LCN: 0x0C0000
MFT Mirr LCN: 0x02
Clust Per FRS: 0xF6
Clust Per IBlock: 0x1
Volume SN: 0xEA14879614876483
Checksum: 0x0
Boot Flag: 0xAA55
-------------------------------------------------------------------------------
File System ID: 0x7 LBA: 315527168 Total Sectors: 269316096 ID: 0x4
Jump: E9 57 0
OEM Name: NTFS
Bytes Per Sec: 512
Sec Per Clust: 8
Res Sectors: 0
Zero 1: 0x0
Zero 2: 0x0
NA 1: 0x0
Media: 0xF8
Zero 3: 0x0
Sec Per Track: 36
Heads: 47
Hidden Secs: 315527168
NA 2: 0x0
NA 3: 0x800000
Total Sectors: 0x0100D6FFF
MFT LCN: 0x032
MFT Mirr LCN: 0x019AF199
Clust Per FRS: 0xF6
Clust Per IBlock: 0x1
Volume SN: 0x1D010DA4B8A1580
Checksum: 0x0
Boot Flag: 0xAA55
-------------------------------------------------------------------------------
======================================================================
MBR Partition Information (HD1 - 0x6E697373)
(CHS: 1022/254/63) (WCHS: 36404/255/63)
+====+====+=============+====+=============+============+============+
| 0: | d | 335 10 2 | 7 | 327 84 13 | 1936269394 | 1836016416 |
| 1: | 70 | 371 114 37 | 73 | 256 101 36 | 1917848077 | 544437093 |
| 2: | 43 | 364 116 50 | 2b | 372 65 44 | 1818575915 | 544175136 |
| 3: | 72 | 372 101 51 | 61 | 269 114 52 | 2844524554 | 54974 |
+====+====+=============+====+=============+============+============+
BOOT SECTOR INFORMATION
-------------------------------------------------------------------------------
Error reading LBA 1936269394
-------------------------------------------------------------------------------

It's not garbage - some actual data files. Not sure what you mean it's not partitioned - while it has never set-up into several partitions as there was no need for this, it should not throw up the errors? As suggested I attach a further screenshot from Ifw, hopefully this provides more info?

it's unpartitioned, so the partition information is garbage. That's why
partinfo can't read the sector that doesn't exist.


"beethoven" wrote in message news:[email protected]...

It's not garbage - some actual data files. Not sure what you mean it's not
partitioned - while it has never set-up into several partitions as there
was no need for this, it should not throw up the errors? As suggested I
attach a further screenshot from Ifw, hopefully this provides more info?

I am sorry but I am not very experienced and was under the impression that any kind of drive needs to be partitioned so that you write to it. As this drive contains files and I can retrieve these files, I assume it has been partitioned before though only containing one partition for the whole drive. Perhaps my terminology is all wrong

it's not partitioned, it's treated like removable media, like a floppy would
be. Just the file system instead of a partition table.


"beethoven" wrote in message news:[email protected]...

I am sorry but I am not very experienced and was under the impression that
any kind of drive needs to be partitioned so that you write to it. As this
drive contains files and I can retrieve these files, I assume it has been
partitioned before though only containing one partition for the whole drive.
Perhaps my terminology is all wrong


TeraByte Support wrote:
> it's not partitioned, it's treated like removable media, like a floppy
> would
> be. Just the file system instead of a partition table.


I'm not familiar with non partitioned hard drives either. How can you set up a hard drive so you can write data to it without having a partition? Can the data be backed up with IFW?

On Sun, 3 Jan 2016 18:58:28 PST, just as I was about to take a herb,
beethoven disturbed my reverie and wrote:

>I am sorry but I am not very experienced and was under the impression that any kind of drive needs to be partitioned so that you write to it.
That is, or now was (LOL) my understanding too.
--
Cheers,

DrT

"If you want to find out what is wrong
with democracy, spend five minutes with
the average voter." - Winston Churchill

you can force it using IFD/IFL/IFW or linux, etc.. It's not normal.


yes you can backup fine using IFD/IFL/IFW, that's why you see "vol" next to
the drive type.


"Brian K" wrote in message news:[email protected]...

TeraByte Support wrote:
> it's not partitioned, it's treated like removable media, like a floppy
> would
> be. Just the file system instead of a partition table.


I'm not familiar with non partitioned hard drives either. How can you set up
a hard drive so you can write data to it without having a partition? Can the
data be backed up with IFW?

I would agree on a need to partition in order to write/read to a drive,
even to format, especially if wanting to use only part of its capacity.

On 1/4/2016 4:51 AM, DrTeeth wrote:
> On Sun, 3 Jan 2016 18:58:28 PST, just as I was about to take a herb,
> beethoven disturbed my reverie and wrote:
>
>> I am sorry but I am not very experienced and was under the impression that any kind of drive needs to be partitioned so that you write to it.
> That is, or now was (LOL) my understanding too.
>