Hi,
I am getting the error(s);

HTFS: Inode 11915 on HTFS dev hd (1/43) has bad type 000000000000
HTFS: I/O failure occured accessing logical block 477364230 on HTFS dev
hd (1/43)

and then the system shuts down.

Is there any way to fix these? We have done the command 'unix auto' at
the Boot: prompt and it goes through its file system checks and appears
to correct some problems. We have had some corruption on the database
but were able to fix the problems.

Our next plan of action is to clone the drive, but if anyone has any
other suggestions for a way to fix this issue I would appreciate it.

Lori Calkins

It would help if you'd provided disk information, such as how many
partitions. I'm guessing from what you provided that the problem is on
the root partition. By default 5.0.6 doesn't check the root file
system on an auto boot. What you're seeing is the file system checks
on the rest of the partitions.

When you get the Boot: prompt just press enter. Eventually you'll be
prompted for the root password to enter maintenance mode. Do that.
Then type

fsck /

Ray Robert
Three Star Software

Lori wrote:
> Hi,
> I am getting the error(s);
>
> HTFS: Inode 11915 on HTFS dev hd (1/43) has bad type 000000000000
> HTFS: I/O failure occured accessing logical block 477364230 on HTFS dev
> hd (1/43)
>
> and then the system shuts down.
>
> Is there any way to fix these? We have done the command 'unix auto' at
> the Boot: prompt and it goes through its file system checks and appears
> to correct some problems. We have had some corruption on the database
> but were able to fix the problems.
>
> Our next plan of action is to clone the drive, but if anyone has any
> other suggestions for a way to fix this issue I would appreciate it.
>
> Lori Calkins

ThreeStar wrote (on Wed, Dec 27, 2006 at 03:51:52PM -0800):
> It would help if you'd provided disk information, such as how many
> partitions. I'm guessing from what you provided that the problem is on
> the root partition. By default 5.0.6 doesn't check the root file
> system on an auto boot. What you're seeing is the file system checks
> on the rest of the partitions.
>
> When you get the Boot: prompt just press enter. Eventually you'll be
> prompted for the root password to enter maintenance mode. Do that.
> Then type
>
> fsck /
>
> Ray Robert
> Three Star Software

You may need to type 'fsck -ofull /' to get any useful results.

--
_________________________________________
Nachman Yaakov Ziskind, FSPA, LLM awacs@ziskind.us
Attorney and Counselor-at-Law http://ziskind.us
Economic Group Pension Services http://egps.com
Actuaries and Employee Benefit Consultants

There is only one partition...I will try going into single user mode
and running the fsck -ofull.

Thank you,

Lori
Nachman Yaakov Ziskind wrote:
> ThreeStar wrote (on Wed, Dec 27, 2006 at 03:51:52PM -0800):
> > It would help if you'd provided disk information, such as how many
> > partitions. I'm guessing from what you provided that the problem is on
> > the root partition. By default 5.0.6 doesn't check the root file
> > system on an auto boot. What you're seeing is the file system checks
> > on the rest of the partitions.
> >
> > When you get the Boot: prompt just press enter. Eventually you'll be
> > prompted for the root password to enter maintenance mode. Do that.
> > Then type
> >
> > fsck /
> >
> > Ray Robert
> > Three Star Software
>
> You may need to type 'fsck -ofull /' to get any useful results.
>
> --
> _________________________________________
> Nachman Yaakov Ziskind, FSPA, LLM awacs@ziskind.us
> Attorney and Counselor-at-Law http://ziskind.us
> Economic Group Pension Services http://egps.com
> Actuaries and Employee Benefit Consultants

Lori wrote:
> There is only one partition...I will try going into single user mode
> and running the fsck -ofull.
>
> Thank you,
>
> Lori
> Nachman Yaakov Ziskind wrote:
> > ThreeStar wrote (on Wed, Dec 27, 2006 at 03:51:52PM -0800):
> > > It would help if you'd provided disk information, such as how many
> > > partitions. I'm guessing from what you provided that the problem is on
> > > the root partition. By default 5.0.6 doesn't check the root file
> > > system on an auto boot. What you're seeing is the file system checks
> > > on the rest of the partitions.
> > >
> > > When you get the Boot: prompt just press enter. Eventually you'll be
> > > prompted for the root password to enter maintenance mode. Do that.
> > > Then type
> > >
> > > fsck /
> > >
> > > Ray Robert
> > > Three Star Software
> >
> > You may need to type 'fsck -ofull /' to get any useful results.

This might be a hard drive error rather than a fs confusion. Check
/var/adm/messages for NOTICE messages. Of course it can also be bad
ram or bad disk controller. But yes, start with fsck -o full.

--
Tony Lawrence
Unix/Linux/Mac OS X Resources
http://aplawrence.com

Hi,
I didn't see any 'NOTICE' messages except for the error messages that I
prevously asked about.
I did the 'fsck -ofull' and plan on cloning the drive, although this is
a pc with raid 0 set up.

Since I could not be on site, I had walked the customer through doing
the filesystem check.

Thank you for your help.

Lori

Lori wrote:
> There is only one partition...I will try going into single user mode
> and running the fsck -ofull.
>
> Thank you,
>
> Lori
> Nachman Yaakov Ziskind wrote:
> > ThreeStar wrote (on Wed, Dec 27, 2006 at 03:51:52PM -0800):
> > > It would help if you'd provided disk information, such as how many
> > > partitions. I'm guessing from what you provided that the problem is on
> > > the root partition. By default 5.0.6 doesn't check the root file
> > > system on an auto boot. What you're seeing is the file system checks
> > > on the rest of the partitions.
> > >
> > > When you get the Boot: prompt just press enter. Eventually you'll be
> > > prompted for the root password to enter maintenance mode. Do that.
> > > Then type
> > >
> > > fsck /
> > >
> > > Ray Robert
> > > Three Star Software
> >
> > You may need to type 'fsck -ofull /' to get any useful results.
> >
> > --
> > _________________________________________
> > Nachman Yaakov Ziskind, FSPA, LLM awacs@ziskind.us
> > Attorney and Counselor-at-Law http://ziskind.us
> > Economic Group Pension Services http://egps.com
> > Actuaries and Employee Benefit Consultants

Lori äæÔÊå ÇÓÊ:
> Hi,
> I am getting the error(s);
>
> HTFS: Inode 11915 on HTFS dev hd (1/43) has bad type 000000000000
> HTFS: I/O failure occured accessing logical block 477364230 on HTFS dev
> hd (1/43)
>
> and then the system shuts down.
>
> Is there any way to fix these? We have done the command 'unix auto' at
> the Boot: prompt and it goes through its file system checks and appears
> to correct some problems. We have had some corruption on the database
> but were able to fix the problems.
>
> Our next plan of action is to clone the drive, but if anyone has any
> other suggestions for a way to fix this issue I would appreciate it.
>
> Lori Calkins

On 29 Dec 2006 08:06:01 -0800, "Lori" <lori_calkins@msn.com> wrote:

-I did the 'fsck -ofull' and plan on cloning the drive, although this is
-a pc with raid 0 set up.

Just as a matter of interest - why are you using RAID 0 at all?

regards

-Rob
robatwork at mail dot com

I am sorry, we are using RAID 1....It wasn't a decision I was included
in on, it was recommended by our Corporate office (I think).

-Lori
Rob S wrote:
> On 29 Dec 2006 08:06:01 -0800, "Lori" <lori_calkins@msn.com> wrote:
>
> -I did the 'fsck -ofull' and plan on cloning the drive, although this is
> -a pc with raid 0 set up.
>
> Just as a matter of interest - why are you using RAID 0 at all?
>
> regards
>
> -Rob
> robatwork at mail dot com

On 3 Jan 2007 05:34:30 -0800, "Lori" <lori_calkins@msn.com> wrote:

-I am sorry, we are using RAID 1....It wasn't a decision I was included
-in on, it was recommended by our Corporate office (I think).
-
Raid 1 is entirely different to Raid 0 - and to be recommended.....

I can't imagine any scenario in business where you would use Raid 0.


-Rob
robatwork at mail dot com