raw disks and error messages

Database
Enthusiast

raw disks and error messages

Does anyone know what either of the following errors from verify_pdisks on TNT mean?:

"BAD CI HEADER LENGTH"
"RAW DISK READ FAILED"

the sector size is correctly entered from the value given from partitioninfo.

Thanks in advance!
4 REPLIES
Enthusiast

Re: raw disks and error messages

Interestingly, 'partitioninfo -o' gave me a few insights:

I receive "RAW DISK READ FAILED" if I create the partition on the disk and don't do anything else.
partitioninfo -o shows the Type is 6 (HUGE Partition - MS-DOS V4)

I receive "BAD CI HEADER LENGTH" if I create the partition, format it NTFS, then unassign a drive letter.
partitioninfo -o shows the Type is 7 (NTFS Partition)

So, can anyone tell me, if not diskmgmt.msc, what tool is used to create partitions on a disk for raw use under Teradata, and what format (if any) should they be in to begin with?

Many thanks in advance!
Senior Apprentice

Re: raw disks and error messages

It must be a unformatted primary partition without assigned drive letter.

Dieter
Enthusiast

Re: raw disks and error messages

That's what I had thought. Though verify_pdisks still shows:
"Bad CI header length (rc=5)"

Does it have to be specially initialized or formatted, or shouldn't vprocmanager's 'initvidsk' command be able to format it once PDE comes up? As it is, it's AMP immediately goes to FATAL** during DBS startup...

Thanks in advance!!
Senior Apprentice

Re: raw disks and error messages

Of course a new AMP must initialize it's filesystem.
It's done through vprocmanager's initvproc (for a single AMP) or a sysinit (for all AMPs).

I don't know what you're actually trying to achieve (hopefully it's not on a production system), you'd better contact support before you kill the system.

Dieter