[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#312279: Error Message on 2.4.27 boot



On Mon, Jul 04, 2005 at 04:20:56PM -0700, Jefferson Cowart wrote:
> (Sorry this took so long for me to get. The person I was hoping was 
> going to be able to get it for me was on vacation for a while and then I 
> forgot about it. In any case below is what I get when trying to boot 
> 2.4.27.)
> 
> hda3: bad access: block=4, count=4
> end_request: I/O error, dev 03:03 (hda), sector 4
> hda3: bad access: block=6, count=2
> end_request: I/O error, dev 03:03 (hda), sector 6
> hda3: bad access: block=8, count=8
> end_request: I/O error, dev 03:03 (hda), sector 8
> hda3: bad access: block=10, count=6
> end_request: I/O error, dev 03:03 (hda), sector 10
> hda3: bad access: block=12, count=4
> end_request: I/O error, dev 03:03 (hda), sector 12
> hda3: bad access: block=14, count=2
> end_request: I/O error, dev 03:03 (hda), sector 14
> hda3: bad access: block=16, count=8
> end_request: I/O error, dev 03:03 (hda), sector 16
> hda3: bad access: block=18, count=6
> end_request: I/O error, dev 03:03 (hda), sector 18
> hda3: bad access: block=20, count=4
> end_request: I/O error, dev 03:03 (hda), sector 20
> hda3: bad access: block=22, count=2
> end_request: I/O error, dev 03:03 (hda), sector 22
> pivot_root: No such file or directory
> /sbin/init: 432: cannot open dev/console: No such file
> Kernel panic: Attempted to kill init!
> 
> When I scroll back up I see more of the same messages as far as I can 
> scroll.
> 
> (As I've said before I will probably be using 2.6.8 most of the time, 
> but I would like a second kernel around in case something gets screwed 
> up with 2.6.8.)

That smells a lot like a failing disk to me.


-- 
Horms



Reply to: