| View previous topic :: View next topic |
| Author |
Message |
Powdered_Cesium
n00b
Joined: 26 Apr 2004
Posts: 8
|
 Posted: Tue Apr 27, 2004 12:49 am Post subject: Problem with laptop HD |
 |
|
Hi,
When I booted my laptop up after finishing the install, I was greeted with a series of errors including a collection claiming that I did not have awk (though I could and can run it, after chrooting, on the LiveCD) and "Error reading from block 8978434 (Attempt to read block from filesystem resulted in short read) while doing inode scan.".
Here is my /etc/fstab:
| Quote: |
# /etc/fstab: static file system information.
# $Header: /home/cvsroot/gentoo-src/rc-scripts/etc/fstab,v 1.14 2003/10/13 20:03:38 azarah Exp $
#
# noatime turns off atimes for increased performance (atimes normally aren't
# needed; notail increases performance of ReiserFS (at the expense of storage
# efficiency). It's safe to drop the noatime options if you want and to
# switch between notail and tail freely.
# <fs> <mountpoint> <type> <opts> <dump/pass>
# NOTE: If your BOOT partition is ReiserFS, add the notail option to opts.
#/dev/ide/host0/bus0/target0/lun0/part3
/dev/hda1 /boot ext3 noauto,noatime 1 1
/dev/hda3 / ext3 noatime 0 1
/dev/hda2 none swap sw 0 0
/dev/cdroms/cdrom0 /mnt/cdrom iso9660 noauto,ro 0 0
#/dev/fd0 /mnt/floppy auto noauto 0 0
# NOTE: The next line is critical for boot!
none /proc proc defaults 0 0
# glibc 2.2 and above expects tmpfs to be mounted at /dev/shm for
# POSIX shared memory (shm_open, shm_unlink).
# (tmpfs is a dynamically expandable/shrinkable ramdisk, and will
# use almost no memory if not populated with files)
# Adding the following line to /etc/fstab should take care of this:
none /dev/shm tmpfs defaults 0 0
|
My partition tables, as read by fdisk:
| Quote: |
Disk /dev/hda: 40.0 GB, 40007761920 bytes
255 heads, 63 sectors/track, 4864 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/hda1 * 1 5 40131 83 Linux
/dev/hda2 6 18 104422+ 82 Linux swap
/dev/hda3 19 4864 38925495 83 Linux
|
Cheers. |
|
| Back to top |
|
 |
Passe-Poil
Tux's lil' helper
Joined: 18 Feb 2004
Posts: 139
Location: Québec, QC, Canada
|
| Posted: Tue Apr 27, 2004 8:26 pm Post subject: |
|
|
might be a hardware problem with your harddrive..
_________________
Violence is the last refuge of the incompetent. |
|
| Back to top |
|
|
Powdered_Cesium
n00b
Joined: 26 Apr 2004
Posts: 8
|
| Posted: Wed Apr 28, 2004 2:54 am Post subject: |
|
|
| I'm really hoping it's not, as I just bought this laptop. And a fsck.ext3 -cc from the livecd assures me that the HD is fine. |
|
| Back to top |
|
|
Powdered_Cesium
n00b
Joined: 26 Apr 2004
Posts: 8
|
| Posted: Wed Apr 28, 2004 4:19 am Post subject: |
|
|
Now, if I choose to go into maintenance mode I get something really insane.
| Quote: |
bash-2.05b# fsck.ext3 /dev/hda3
e2fsck 1.34 (25-Jul-2003)
Error reading block 8978433 (Attempt to read block from filesystem resulted in
short read) while reading inode and block bitmaps. Ignore error<y>? n
e2fsck: Can't read an block bitmap while retrying to read bitmaps for
/dev/hda3
|
Now, I'm not exactly sure what that sentence is supposed to mean, but googling it returns only two hits: both posts like this on message boards, neither of the posters ever got a reply. [/i] |
|
| Back to top |
|
|
Sequentious
Apprentice
Joined: 07 Jun 2002
Posts: 290
Location: Canada
|
| Posted: Wed Apr 28, 2004 6:29 am Post subject: |
|
|
does it work fine from the live cd?
Do you have support for your chipset in the kernel? there may be special workarounds that are needed to make it work nice.
What chipset is it?
_________________
--
Seq |
|
| Back to top |
|
|
Powdered_Cesium
n00b
Joined: 26 Apr 2004
Posts: 8
|
| Posted: Wed Apr 28, 2004 6:42 am Post subject: |
|
|
| The processor? It's a 1.4ghz Centrino. |
|
| Back to top |
|
|
Sequentious
Apprentice
Joined: 07 Jun 2002
Posts: 290
Location: Canada
|
| Posted: Wed Apr 28, 2004 6:53 am Post subject: |
|
|
That's not the chipset, that's the processor.
But, theres only one or two intel chipsets used for pentium-m cpus in centrino packages, and luckily enough i'm posting this from one. I've no clue why it's giving you that trouble.
Again, does it happen from the live cd, or give you any errors in windows?
_________________
--
Seq |
|
| Back to top |
|
|
Powdered_Cesium
n00b
Joined: 26 Apr 2004
Posts: 8
|
| Posted: Wed Apr 28, 2004 7:00 am Post subject: |
|
|
| Quote: |
That's not the chipset, that's the processor.
|
Sorry, I don't know that much about hardware. x_x
| Quote: |
Again, does it happen from the live cd, or give you any errors in windows?
|
It happens on the liveCD /now/, but it didn't before. Even so, on the liveCD the errors are correctable. |
|
| Back to top |
|
|
Powdered_Cesium
n00b
Joined: 26 Apr 2004
Posts: 8
|
| Posted: Thu Apr 29, 2004 11:58 am Post subject: |
|
|
| Well, I just reinstalled from scratch, and it still happens. |
|
| Back to top |
|
|
Powdered_Cesium
n00b
Joined: 26 Apr 2004
Posts: 8
|
| Posted: Sat May 01, 2004 6:12 am Post subject: |
|
|
| In fact, it seems that my install is somehow DAMAGING my filesystem. If I try to boot from my HD, it says there is an unfixable error. Then if I boot from the LiveCD and do a fsck.ext3 it will detect an error and fix it, whereas if I just boot from the LiveCD twice, there will be no error. |
|
| Back to top |
|
|
Powdered_Cesium
n00b
Joined: 26 Apr 2004
Posts: 8
|
| Posted: Sun May 02, 2004 1:14 am Post subject: |
|
|
| It works with slackware... |
|
| Back to top |
|
|
DkReaver
n00b
Joined: 25 May 2004
Posts: 2
|
| Posted: Tue May 25, 2004 10:53 pm Post subject: Inode Short Read |
|
|
I am experiencing the same problem with an IBM Thinkpad T41 configured for multiboot with Windows XP. It is a Machine-Type and Model 2373-9FU.
This computer shipped with an NTFS partition and a FAT partition. Originally, I shrank the NTFS partition and placed the Gentoo partitions between the NTFS and FAT partition on the hard disk. I had successful builds that did not experience the short inode read.
Now I have relocated the FAT partition to be /dev/hda2.
The final partition on my drive, /dev/hda9, is having the short inode read issue. This appears _irrecoverable_ within Gentoo, yet booting from System Recovery CD (built on Gentoo) yields a successful (and sometimes clean?!?!) e2fsck of the ext3 filesystem on this device.
I currently have no solution for this issue, and am planning to attempt repartitioning.
The possible causes I see at this time are:
- kernel issue: I have recompiled the kernel many times during builds on this system and have not been consistent in my selection of kernel modules and compiled in options
- ext3/partitioning bug: Perhaps there is an issue with the last device on the drive being ext3?
I am interested in any information others may bring to this problem. |
|
| Back to top |
|
|
dave_euser
n00b
Joined: 07 Jul 2002
Posts: 42
|
| Posted: Tue May 25, 2004 10:59 pm Post subject: from a google search.... |
|
|
dug this up....
https://listman.redhat.com/archives/ext3-users/2002-August/msg00125.html
says to run e2fsck -c to mark out any bad blocks......
if there are a lot of them, you might have an imminent hardware failure on your hands....drives can exhibit infant mortality failures (the number of dead drives that get out of mfg. is actually pretty high) |
|
| Back to top |
|
|
|
Kernel & Hardware
