rohitsz Posted January 26, 2006 Report Share Posted January 26, 2006 Greetings there, i was working on a java program, that included heavy compilation and has a big memory foot-print... at times, the screen did not respond to mouse/keyboard input... then i did a ALT+CTRL+SysRq+B and the system rebooted... then after that when the boot prompt came(i have mandriva/win98/winXP) when i choose mandriva.. it showed the splash screen(penguin with stars on its eyes).. then it went away for a text login. when i put in the user name, it did not ask me for a password and went back to the same prompt. i tried running in failsafe mode but the same experience.. i am unable to go past that login.. though previously i had a full-GUI login... PS: my win partitions are working fine... kindly help me get out of this problem.. regards, rohit. [moved from Installing Mandriva by spinynorman] Quote Link to comment Share on other sites More sharing options...
devries Posted January 26, 2006 Report Share Posted January 26, 2006 Is it really a login prompt or just a prompt? If it´s just a prompt type: init 3 and hit enter. After that log in. Quote Link to comment Share on other sites More sharing options...
rohitsz Posted January 26, 2006 Author Report Share Posted January 26, 2006 (edited) Hello there, Is it really a login prompt or just a prompt? If it´s just a prompt type: init 3 and hit enter. After that log in. <{POST_SNAPBACK}> its a GUI verbose background.. the prompt is like a description of the distro(line 1) and kernel(line 2) and the next line is: (none)login: [edit 1] i tried this but does not work... i guess its a login prompt but do not know why its not asking for a password?! [edit 2] i was re-reading the ALT+SysRq tip link, so i realize.. i did not follow the sequence in order... i just did the reboot... also this happened yesterday night also, so i had an fsck where it deleted some inodes... so i hope as a non-user (yesterday & today), there is no way i could have corrupted some system files!? or could i?? thanks, rohit. Edited January 26, 2006 by rohitsz Quote Link to comment Share on other sites More sharing options...
rohitsz Posted January 26, 2006 Author Report Share Posted January 26, 2006 Greetings there, more on the problem.. i tried knoppix 3.6 it worked fine until i shut it down.. i got the following error at shut-down.. X-Window session terminated without error shutting down scsi0:Error on channel 0,id 0,lun 0,cdb:0x03, 00 00 00 40 00 info fld=0x2500a, current sd0b:00: sns=f03 ASC=11 ASCQ=0 raw sense data:0xf0 0x00 0x03 0x00 0x02 0x50 0x0a 0x00 0x00 0x00 0x00 0x11 0x00 0x00 0x00 0x00 0x00 I/O error: dev0b:00, sector 606248 #the following two lines were repeated 4 times cloop:read error at pos 305962099 in field /cdrom/KNOPPIX/KNOPPIX, 23997 bytes lost cloop:error -3 compressing block 13646 65536/0/23997/0 305962099-305986096 #the last line: /etc/init.d/xsession:line/80:/sbin/init:Input/output error the comments are for explanation/brevity, they were not there on my console. after the above state, i had to again hard-reboot the machine.. i doubt i have a hdd related error? please help.. regards, rohit. Quote Link to comment Share on other sites More sharing options...
ianw1974 Posted January 26, 2006 Report Share Posted January 26, 2006 I would check your cables to make sure they are connected correctly. If you have a spare, try another one instead to see if it makes any difference. Could be a loose connection from the drive to the motherboard, if using IDE, or SCSI card if using SCSI based disks, or connectors for SATA drives, if using SATA. I'd be tempted to remove the cable, and reconnect, to see if it helps. Quote Link to comment Share on other sites More sharing options...
rohitsz Posted January 26, 2006 Author Report Share Posted January 26, 2006 Hello ian, I would check your cables to make sure they are connected correctly. If you have a spare, try another one instead to see if it makes any difference. Could be a loose connection from the drive to the motherboard, if using IDE, or SCSI card if using SCSI based disks, or connectors for SATA drives, if using SATA. I'd be tempted to remove the cable, and reconnect, to see if it helps. <{POST_SNAPBACK}> i had already done that half-heartedly.. that because, couple of my fat32 partitions sit on the same hdd as mandriva does.. i did not have any problems accessing them in win... as i am able to run a live cd.. is it possible that i atleast get some thing work for mandriva..? i can access /boot partition.. is there something i can try? thanks, rohit. Quote Link to comment Share on other sites More sharing options...
ianw1974 Posted January 26, 2006 Report Share Posted January 26, 2006 Do you know your partitions within LE2005, and what mount point they are? For example, if I do a default install with swap, root and home partition, they are as follows: / = /dev/hda5 (or /dev/sda5 if using sata/scsi) home = /dev/hda6 (or /dev/sda6) Also, do you know what filesystems are installed? ext2 ext3 reiserfs xfs jfs if so, we can boot from a Mandriva LE2005 CD1/DVD and do some checking. So: 1. Boot from LE2005 CD/DVD and choose F1 or type "linux rescue" without the quotes. 2. One of the options displayed in a menu is to go to a command prompt. At this prompt we can then check the file systems for errors, this will depend on what filesystem you chose. If ext2/ext3: e2fsck /dev/hda5 (or /dev/sda5) if reiserfs, then: reiserfsck /dev/hda5 or replace the partition with whatever yours are. Once the disks have been checked, you can then mount them. What I tend to do are: mkdir /mnt/mandriva mount /dev/hda5 /mnt/mandriva substitute your partition info with mine, as it's just an example. Quote Link to comment Share on other sites More sharing options...
rohitsz Posted January 28, 2006 Author Report Share Posted January 28, 2006 Hello ian, Do you know your partitions within LE2005, and what mount point they are? For example, if I do a default install with swap, root and home partition, they are as follows: / = /dev/hda5 (or /dev/sda5 if using sata/scsi) home = /dev/hda6 (or /dev/sda6) Also, do you know what filesystems are installed? ext2 ext3 reiserfs xfs jfs if so, we can boot from a Mandriva LE2005 CD1/DVD and do some checking. So: 1. Boot from LE2005 CD/DVD and choose F1 or type "linux rescue" without the quotes. 2. One of the options displayed in a menu is to go to a command prompt. At this prompt we can then check the file systems for errors, this will depend on what filesystem you chose. If ext2/ext3: e2fsck /dev/hda5 (or /dev/sda5) i did what you suggested but from a knoppix live cd and got the folllowing results.. for my /boot partition: root@ttyp0[knoppix]# e2fsck -cvfn /dev/hdb2 e2fsck 1.35 (28-Feb-2004) Checking for bad blocks (read-only test): done Pass 1: Checking inodes, blocks, and sizes Pass 2: Checking directory structure Pass 3: Checking directory connectivity Pass 4: Checking reference counts Pass 5: Checking group summary information /dev/hdb2: ***** FILE SYSTEM WAS MODIFIED ***** 55 inodes used (0%) 7 non-contiguous inodes (12.7%) # of inodes with ind/dind/tind blocks: 14/4/0 12261 blocks used (12%) 0 bad blocks 0 large files 37 regular files 3 directories 0 character device files 0 block device files 0 fifos 0 links 6 symbolic links (6 fast symbolic links) 0 sockets -------- 46 files root@ttyp0[knoppix]# for my root partition(/) root@ttyp0[knoppix]# e2fsck -vfn /dev/hdb8 e2fsck 1.35 (28-Feb-2004) Pass 1: Checking inodes, blocks, and sizes Deleted inode 132833 has zero dtime. Fix? no Deleted inode 132834 has zero dtime. Fix? no Deleted inode 132835 has zero dtime. Fix? no Deleted inode 132837 has zero dtime. Fix? no Deleted inode 132838 has zero dtime. Fix? no Deleted inode 132839 has zero dtime. Fix? no Deleted inode 132840 has zero dtime. Fix? no Deleted inode 132841 has zero dtime. Fix? no Deleted inode 132842 has zero dtime. Fix? no Deleted inode 132843 has zero dtime. Fix? no Deleted inode 132844 has zero dtime. Fix? no Deleted inode 132845 has zero dtime. Fix? no Deleted inode 132846 has zero dtime. Fix? no Deleted inode 132847 has zero dtime. Fix? no Deleted inode 132849 has zero dtime. Fix? no Deleted inode 132850 has zero dtime. Fix? no Deleted inode 132851 has zero dtime. Fix? no Deleted inode 132852 has zero dtime. Fix? no Deleted inode 132854 has zero dtime. Fix? no Deleted inode 132855 has zero dtime. Fix? no Deleted inode 132856 has zero dtime. Fix? no Deleted inode 132857 has zero dtime. Fix? no Deleted inode 132858 has zero dtime. Fix? no Deleted inode 132859 has zero dtime. Fix? no Deleted inode 132860 has zero dtime. Fix? no Deleted inode 132861 has zero dtime. Fix? no Deleted inode 132862 has zero dtime. Fix? no Deleted inode 132863 has zero dtime. Fix? no Deleted inode 132864 has zero dtime. Fix? no Deleted inode 218785 has zero dtime. Fix? no Deleted inode 218786 has zero dtime. Fix? no Deleted inode 218787 has zero dtime. Fix? no Deleted inode 218789 has zero dtime. Fix? no Deleted inode 218790 has zero dtime. Fix? no Deleted inode 218791 has zero dtime. Fix? no Deleted inode 218792 has zero dtime. Fix? no Deleted inode 218793 has zero dtime. Fix? no Deleted inode 218794 has zero dtime. Fix? no Deleted inode 218796 has zero dtime. Fix? no Deleted inode 218797 has zero dtime. Fix? no Deleted inode 218798 has zero dtime. Fix? no Deleted inode 218799 has zero dtime. Fix? no Deleted inode 218800 has zero dtime. Fix? no Deleted inode 218801 has zero dtime. Fix? no Deleted inode 218802 has zero dtime. Fix? no Deleted inode 218803 has zero dtime. Fix? no Deleted inode 218804 has zero dtime. Fix? no Deleted inode 218805 has zero dtime. Fix? no Deleted inode 218806 has zero dtime. Fix? no Deleted inode 218807 has zero dtime. Fix? no Deleted inode 218808 has zero dtime. Fix? no Deleted inode 218809 has zero dtime. Fix? no Deleted inode 218810 has zero dtime. Fix? no Deleted inode 218811 has zero dtime. Fix? no Deleted inode 218812 has zero dtime. Fix? no Deleted inode 218813 has zero dtime. Fix? no Deleted inode 218814 has zero dtime. Fix? no Deleted inode 218815 has zero dtime. Fix? no Deleted inode 218816 has zero dtime. Fix? no Inodes that were part of a corrupted orphan linked list found. Fix? no Inode 577282 was part of the orphaned inode list. IGNORED. Inode 577282 is in use, but has dtime set. Fix? no Inode 577282 has illegal block(s). Clear? no Illegal block #0 (8440192) in inode 577282. IGNORED. Inode 577283 was part of the orphaned inode list. IGNORED. Inode 577283 is in use, but has dtime set. Fix? no Inode 577283 has illegal block(s). Clear? no Illegal block #0 (8489088) in inode 577283. IGNORED. Illegal block #4 (8388608) in inode 577283. IGNORED. Inode 577284 was part of the orphaned inode list. IGNORED. Inode 577284 is in use, but has dtime set. Fix? no Inode 577286 was part of the orphaned inode list. IGNORED. Inode 577286 is in use, but has dtime set. Fix? no Inode 577286, i_blocks is 0, should be 8. Fix? no Inode 577287 was part of the orphaned inode list. IGNORED. Inode 577287 is in use, but has dtime set. Fix? no Inode 577288 was part of the orphaned inode list. IGNORED. Inode 577288 is in use, but has dtime set. Fix? no Inode 577289 is in use, but has dtime set. Fix? no Inode 577290 was part of the orphaned inode list. IGNORED. Inode 577290 is in use, but has dtime set. Fix? no Inode 577290 has illegal block(s). Clear? no Illegal block #0 (8435840) in inode 577290. IGNORED. Inode 577291 is in use, but has dtime set. Fix? no Inode 577291 has illegal block(s). Clear? no Illegal block #10 (8388608) in inode 577291. IGNORED. Inode 577292 is in use, but has dtime set. Fix? no Inode 577293 was part of the orphaned inode list. IGNORED. Inode 577293 is in use, but has dtime set. Fix? no Inode 577293 has illegal block(s). Clear? no Illegal block #0 (9488768) in inode 577293. IGNORED. Illegal block #1 (8388608) in inode 577293. IGNORED. Inode 577294 was part of the orphaned inode list. IGNORED. Inode 577294 is in use, but has dtime set. Fix? no Inode 577294, i_blocks is 8388608, should be 8. Fix? no Inode 577284 has illegal block(s). Clear? no Illegal block #0 (9619968) in inode 577284. IGNORED. Inode 577284, i_blocks is 0, should be 24. Fix? no Inode 577287 has illegal block(s). Clear? no Illegal block #0 (8498560) in inode 577287. IGNORED. Inode 577288 has illegal block(s). Clear? no Illegal block #0 (9619840) in inode 577288. IGNORED. Illegal block #-1 (8388608) in inode 577288. IGNORED. Error while iterating over blocks in inode 577288: Illegal indirect block found e2fsck: aborted root@ttyp0[knoppix]# so this is what i got ..is my system recoverable? should i allow e2fsck to fix error's... as far as i can recall, i remember seeing similar messages when i first time did a ALT+SysRq+R .. so what next..? thanks, rohit. Quote Link to comment Share on other sites More sharing options...
ianw1974 Posted January 28, 2006 Report Share Posted January 28, 2006 I would suggest saying yes to the errors to fix the problems encountered, and see if anything is better after that. Keep us posted. Quote Link to comment Share on other sites More sharing options...
rohitsz Posted January 29, 2006 Author Report Share Posted January 29, 2006 Hello there, well i did say 'yes' to all what e2fsck wanted to fix.. but still no luck.. i am still unable to boot LE2005, so have decided to do a fresh install... on searching over the web... i got a hint about an old version of ldconfig responsible for what happened with me.... but it said replacing it when one can log into the system.. that's not happening in my case. so am re-installing .. another off-topic question.. i have 20G for all my linux work.. currently i am actively using 10G and the other half is unused.. now as i plan to reinstall..i have decided to do a more *mature* partitioning of space..so that when a fs error happens i just can reinstall the / partition.. is this possible? i'll keep mandriva as my main place to work on and play with other distro's too.. so i plan to do as follows: /boot(100M) /swap(512M) /(2G) /home(5G) /usr(4G) also as i plan to install other linux distros(atmost 2) would the above partitions work or i can still get more space for mandriva?? need your suggestions... thanks , rohit. Quote Link to comment Share on other sites More sharing options...
ianw1974 Posted January 30, 2006 Report Share Posted January 30, 2006 The partitioning sounds fine to me. The good thing about splitting it up is that if one area has problems, you only need to restore the area that has problems. For example, if the only partition mounted was "/" then you'd have to restore everything when there are disk problems, etc. With the example you listed above, you can of course see, that you'd have a max to restore of 5GB should anything go wrong, instead of a full 10GB or less, depending on how much is in use. Of course, if you have very little hard disk space, then it's best not to split it, because you'd be restricting yourself. Example is, say a 6GB drive or less, then of course you would just mount one partition of "/" and not split it anymore, because you'd restrict space for installing apps, or for the home account, etc, etc. Something I'm learning as I train for my Red Hat Certified Engineer Course. Maybe go for reiserfs as your file system this time. I have one system I will be spending time on tomorrow which is running on XFS and I'm having a few problems with it, so I'm currently going to be going through a conversion process, and then splitting the drive partitions. Presently, I have 20GB allocated to "/" and 160GB allocated to "home". This time, I will be splitting similar to yourself, but I will use the first 20GB of my 160GB drive, to use software raid should I have a problem with disk failure. Home will then utilise the remaining space of about 90GB on the 160GB drive. The 20GB will be partitioned pretty much like you have listed above. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.