🚀 go-pugleaf

Xiaoqiang Luo <xiao@jhu.edu> writes:

>hi,

>I have been using linux1.2.13(slackware 3.0.0) for a while and it works 
>just fine till yesterday -- after I moved my PC from one room to the 
>other, my linux cannot be booted. I am quite sure this is not due to 
>hardware failure(of moving-related) because (1) I have a partition where 
>I installed Win95 and it worked fine as usual after I moved my PC; (2) 
>today I was able to use slackware rescue-disk to boot my PC and mount 
>the linux partition on /mnt. I then ran e2fsck and the filesystem seemed 
>fine because I can access files on the filesystem. But I simply cannot 
>boot ..

>OK, here is my setup:

>-1.08GB IDE harddrive with 3 partitions;
>	 /dev/hda1: DOS/WIN95
>	 /dev/hda2: linux swap
>	 /dev/hda3: linux 

>And the following is a few lines seen when linux was booted:
>....
>Linux version 1.2.13(root@bigkitty)(gcc version 2.7.0) #1 Tue Aug 22 
>22:35:35 CDT 1995
>Partition check:
>	hda: multiple mode turned off
>	hda: hda1 hda2 hda3
>VFS: Mounted root (ext2 filesystem) readonly
>Adding swap space: 34268 swap-space
>Unable to indentify CD-ROM format
>end_request: I/O error, dev 2100, sector 64
>iso_fs_read_super: bread failed, dev 0x2100, iso_blknum 16
>Unable to indentify CD-ROM format

>----- end of messages ------

>The boot process seemed halted at some point!

>AT first I thought the failure might be caused by CDROM -- linux seems 
>to have trouble with it, but after I boot my system with floppy disks, I 
>checked /var/log/messages on /dev/hda3 and found that I had these kind 
>of messages of "Unable to indentify CD-ROM format" long long ago. My 
>linux was bootable all the time prior to yesterday!

>could linux gurus out there help me out? Particularly, I want to know 
>what linux1.2.13 is doing after prompting "Unable to indentify CD-ROM 
>format"? Please send your reply to xiao@jhu.edu. Many thanks in advance.

I had a similar problem when I moved my computer.
The first time I booted it up, I started X-windows, and issued
'shutdown' from an xterm...big mistake.  After that, the machine booted,
froze at the spot yours did, and eventually propmted for a login.
It let me log in but my mouse didn't work and X-windows would
no longer start.  After about two days of continous work, I found a solution
that works although it seemed kinda radical.  
  I read in some how-to that /dev/console should be a symlink to /dev/tty0.
On my machine, however, /dev/console wasn't a link to anything but /dev/systty
was a link to /dev/console.  So I deleted /dev/console and then
'ln -s /dev/tty0 console' from /dev.

Now everything works fine, xwindows, mouse, virtual consoles and everything.

go figure....use at your own risk.