> On Jul 4, 2015, at 3:51 PM, Denis Heidtmann <[email protected]> wrote: > > As I said, "I booted from a live CD and attempted to run fsck. It spends > zero time to respond that /dev/sda1 is clean.”
Check your partition table with fdisk, cfdisk, or parted. It is possible the partition table is corrupted as well. > > Are there some options I should use when running fsck? I know when Ubuntu > runs automatically every so often on boot that it takes a few minutes to > complete. Yet when I run fsck from the live CD it completes immediately, > with no errors. This is looking like a hardware problem, the drive should be checked in a different machine. It is possible that the motherboard has caused the problems on the drive, and it may need to be zeroed out, repartitioned and formatted. It is also possible that the drive itself has gone bad, this will show up in the zeroing process. To zero the drive if it is sda, run the command: dd if=/dev/zero of=/dev/sda This will destroy all data on the drive! The command will run until it runs out of space, make sure the size of the command is the same as the size of the drive. Good luck, Derek > > -Denis > > On Sat, Jul 4, 2015 at 2:03 PM, Ken Stephens <[email protected]> wrote: > >> Denis Heidtmann wrote: >>> Yesterday and today on starting I get errors such as: >>> Boot from (hd0,0) ext3 d7d8b1c0-f79..... >>> Error 16: Inconsistent file system structure >>> press any key to continue... >>> >>> key press presented list of boot options. I selected memtest. I got >> just >>> a flashing cursor. >>> >>> Power off and restart produced: >>> Busybox v 1.18.5 (ubuntu1: 1.1.18.5-1ubuntu4.1 built-in shell (ash) >>> (initramfs) [this is the prompt] >>> (initramfs) exit >>> about 10 lines of stuff, including kernel panic. >>> >>> Later boot went to what looked like normal completion, but could not shut >>> down in the usual way (gui). ^alt bksp caused: >>> >>> (numbers...) ext3-fs error (da1): >>> ext3_get_inode_loc: unable to read node block -inaode = (numbers...) >>> >>> I booted from a live CD and attempted to run fsck. It spends zero time >> to >>> respond that /dev/sda1 is clean. >>> >>> Suggestions? >>> >>> Thanks.\, >>> -Denis >>> >> Denis, >> >> Investigate the fsk command. Your file system is corrupted and needs >> correcting. The file system check command should fix it. You may need >> to boot up on a live CD, which should mount your system disk da1 if you >> ask it. But don't ask it. The fschk command need the file system to be >> unmounted. >> >> Ken >> CAD 2 CAM >> _______________________________________________ >> PLUG mailing list >> [email protected] >> http://lists.pdxlinux.org/mailman/listinfo/plug >> > _______________________________________________ > PLUG mailing list > [email protected] > http://lists.pdxlinux.org/mailman/listinfo/plug _______________________________________________ PLUG mailing list [email protected] http://lists.pdxlinux.org/mailman/listinfo/plug
