strange errors during boot

[beerstein]

Hi:
TC works fine on all of my computers, exept a SOTEC notebook with only one
NTFS partition. When I boot it seems that TC can not recognize the /dev/hda1
It recognizes the CD/DVD and the USB stick = sda1

The errors appear shortly after the F2/F3 options input and they era like this:

hda task no_data_....
Drive Ready Seek Complete Error
Drive status error
hda possible failed opcode 0xea

I assume that the problem has something to do with the hda recognition of TC, but I have no clou how to fix it.

Later after boot everything works fine with TC 3.0 )and(TC 2.9) exept I can not use the mount tool do
mount hda1. The mount tool sees hda1 but can not mount. Itried the comman line mount - was not able to mount.

Has someone experienced similar problems - please help
All the best
 

[tinypoodle]

Do you load any extension containing file system drivers at boot or not?

[curaga]

Your HD, ide cable, or ide chip is beginning to fail.

On the other issue, as tinypoodle says, NTFS is not supported in the base, load one of the extensions: ntfsprogs, ntfs-3g, filesystems-xxx.

[tinypoodle]

Sorry if my preceding post gives reason for ambiguity, I had rather in mind to exclude any relation of these errors to file system (by checking output without file system support).

Agreed on suspicion of hardware failure.

[beerstein]

Thank you all for the help. I think it has something to do that TC, during boot, only finds a hda1 which is
100% NTSF. I do not input any  boot codes (exept the one below). On all other machines I am using with TC I have either a
FAT 32 or a ext3 partition on my hard drive.
Here is only NTFS and I think TC tries to read or write to that NTFS partition and can not do it.
The USB stick is FAT 32 and will be recognized because of my "tinycore waitusb=7" bootcode.

Did somebody boot TC on a machine without any hd and stick?

all the best to you.

[Juanito]

Did somebody boot TC on a machine without any hd and stick?

I take it you don't mean from cd 

It should be possible to perform a netboot  - if you search the forum I seem to remember there were posts on this subject.

[beerstein]

I ment is it possible to have a computer without a hd and a stick. Just a CD-ROM.
Then boot from the CD and work in RAM. With such a machine TC should also not
look for something to write to or to read from.

[Juanito]

Yes, this will work as long as the bios supports booting from cd

[curaga]

You can prevent the autoscan by using the codes "base norestore". You will still see the HD errors, because your HW is failing, and the kernel sees that from merely checking the HD's info.

[thane]

FWIW, on my old TC box (Compaq Deskpro EN) I was booting off CD and had the TCE directory etc. on a USB stick. But when the hard drive started to fail I had trouble booting TC even though nothing TC-related was installed on it. To resolve this I disconnected all the hard drive cables.

[beerstein]

Do you load any extension containing file system drivers at boot or not?

HI:
I think I need to load the NTFS file system drivers at boot. TinyCore is trying to look at all my devices such as hda1, sda1 and the CD/DVD devices and so on. Since my hda1 is 100% NTFS and TC can not handle NTFS and generates these "strange errors". Somewhere in this forum I learned that TC needs a ntfs-3g driver to read NTFS partitions. The TC repository lists a "ntfs-3g-adv-dev.tgz"
I installed this one already.

But now - I think I still have to  aktivate this drivers during boot - but I do not know how to do that?

During boot I also can see that TC is generating an fstab file.   In this fstab file I can see after boot that an entry line was generated which tries to mount an NTFS partition on hda1. After boot I am not able to mount hda1. sda1 is mounted, because I fed the bootcode "tinycore waitsub=7"

The solution might be to load the NTFS-3g drivers during boot and set up fstab that it mounts NTFS-3g instead of NTFS?

Can somebody help me on this?

Thank you so much in advance

beerstein

[tinypoodle]

For better troubleshooting you can boot with param

Code: [Select]

syslogwhich creates a system log in /var/log/messages

[tinypoodle]

Please read all replies again, you seem to overlook several details of what has been answered already.

IMHO, in such case best not to attempt to mount the file system without any clear diagnosis and strategy, and if
then read-only.

Be aware that any further procedure involving the disk could potentially reduce chances of successful data rescue.

Should you not care at all about loss of current data, the disk has still to be considered as unreliable to write further data to it, until more evidence from diagnostic tests
is available.