problem with 9.2
in [Suse]
|
From: JM Remacle on 25 Aug 2005 16:09 Hello, I cannot use 9.2 any more, it stops during boot. i do not really know what happened. I get the messages : ------------------------- fsck failed for at least one file system (not /) Please repair manually and reboot (easy to say, not easy to do !!!) The root file system is already mounted read-write. Attention : only CONTROL-D will reboot the system in this maintenance mode, shutdown or reboot will not work. Give root password for login : ohci1394:fw-host0:selfID received outside of bus reset sequence BIOS EDD facility.... --------------------------- When i have given my rooy passwd i get the prompt but do not what to do. 9.2 is on hda4 (it is my basic distro); i have also 9.3 on hda9 and from there i could work on hda4. i tried to repair via the iso install cd; i was told that the filesystem on hda4 was correct, i got not results. I also try e2fsck but i do not what to to with this program... So i am completely in the dark; if someone could help me i would be pleased. Thank you. JM
From: houghi on 24 Aug 2005 18:34 JM Remacle wrote: > Hello, > I cannot use 9.2 any more, it stops during boot. > i do not really know what happened. > I get the messages : > ------------------------- > fsck failed for at least one file system (not /) > Please repair manually and reboot (easy to say, not easy to do !!!) > The root file system is already mounted read-write. > Attention : only CONTROL-D will reboot the system in this maintenance > mode, shutdown or reboot will not work. > Give root password for login : ohci1394:fw-host0:selfID received outside > of bus reset sequence BIOS EDD facility.... > --------------------------- > When i have given my rooy passwd i get the prompt but do not what to do. > 9.2 is on hda4 (it is my basic distro); i have also 9.3 on hda9 and from > there i could work on hda4. fsck /dev/hda4. You can do that from 9.3 or from the boot prompt. I think that if there are a lot of errors, you can run `fsck -y /dev/hda4` > i tried to repair via the iso install cd; i was told that the filesystem > on hda4 was correct, i got not results. That could point to the fact that you have something in /etc/fstab that should not be there. Not sure what you have in /etc/fstab with /dev/hda4, but if it not important, uncomment it from 9.3 and see if that works. Then when booted, go into the 9.2 /etc/fstab and correct what is there. Take /etc/fstab from 9.3 as an example. -- houghi http://houghi.org > Knock-knock. > Who's there? > Under the Patriot Act, we don't have to tell you that.
From: JM Remacle on 26 Aug 2005 10:11 houghi a ýcrit : > JM Remacle wrote: > >>Hello, >>I cannot use 9.2 any more, it stops during boot. >>i do not really know what happened. >>I get the messages : >>------------------------- >>fsck failed for at least one file system (not /) >>Please repair manually and reboot (easy to say, not easy to do !!!) >>The root file system is already mounted read-write. >>Attention : only CONTROL-D will reboot the system in this maintenance >>mode, shutdown or reboot will not work. >>Give root password for login : ohci1394:fw-host0:selfID received outside >>of bus reset sequence BIOS EDD facility.... >>--------------------------- >>When i have given my rooy passwd i get the prompt but do not what to do. >>9.2 is on hda4 (it is my basic distro); i have also 9.3 on hda9 and from >>there i could work on hda4. > > > fsck /dev/hda4. You can do that from 9.3 or from the boot prompt. I > think that if there are a lot of errors, you can run `fsck -y /dev/hda4` > > >>i tried to repair via the iso install cd; i was told that the filesystem >> on hda4 was correct, i got not results. > > > That could point to the fact that you have something in /etc/fstab that > should not be there. Not sure what you have in /etc/fstab with > /dev/hda4, but if it not important, uncomment it from 9.3 and see if > that works. Then when booted, go into the 9.2 /etc/fstab and correct > what is there. Take /etc/fstab from 9.3 as an example. > this is what i did : linux:/home/jmr # fsck -y /dev/hda4 fsck 1.36 (05-Feb-2005) reiserfsck 3.6.18 (2003 www.namesys.com) ************************************************************* ** If you are using the latest reiserfsprogs and it fails ** ** please email bug reports to reiserfs-list(a)namesys.com, ** ** providing as much information as possible -- your ** ** hardware, kernel, patches, settings, all reiserfsck ** ** messages (including version), the reiserfsck logfile, ** ** check the syslog file for any related information. ** ** If you would like advice on using this program, support ** ** is available for $25 at www.namesys.com/support.html. ** ************************************************************* Will read-only check consistency of the filesystem on /dev/hda4 Will put log info to 'stdout' ########### reiserfsck --check started at Fri Aug 26 13:51:53 2005 ########### Replaying journal.. Reiserfs journal '/dev/hda4' in blocks [18..8211]: 0 transactions replayed Checking internal tree..finished Comparing bitmaps..finished Checking Semantic tree: finished No corruptions found There are on the filesystem: Leaves 31247 Internal nodes 215 Directories 12658 Other files 140484 Data block pointers 1093121 (995 of them are zero) Safe links 0 ########### reiserfsck finished at Fri Aug 26 13:53:03 2005 ########## Content of the stdout file /etc/X11/xim: Checking wether an input method should be started. INPUT_METHOD is not set or empty (no user selected input method). Trying to start a default input method for the locale fr_FR.UTF-8 ... There is no default input method for the current locale. xset: bad font path element (#96), possible causes are: Directory does not exist or has wrong permissions Directory missing fonts.dir Incorrect font server address or syntax startkde: Starting up... kbuildsycoca running... kdecore (KLibLoader): WARNING: KLibrary: /opt/kde3/lib/kde3/kcm_keyboard.so: undefined symbol: init_keyboard_layout libhal.c 911 : Error sending msg: No property info.category on device with id /org/freedesktop/Hal/devices/computer libhal.c 1205 : Error sending msg: No property volume.disc.has_audio on device with id /org/freedesktop/Hal/devices/block_8_1 libhal.c 911 : Error sending msg: No property info.category on device with id /org/freedesktop/Hal/devices/usb_usb_device_4b4_6830_1_-1_DEF109219994_0 libhal.c 911 : Error sending msg: No property info.category on device with id /org/freedesktop/Hal/devices/ide_0_0 libhal.c 1205 : Error sending msg: No property volume.disc.has_audio on device with id /org/freedesktop/Hal/devices/block_3_2 libhal.c 1205 : Error sending msg: No property volume.disc.has_audio on device with id /org/freedesktop/Hal/devices/block_3_3 libhal.c 911 : Error sending msg: No property info.category on device with id /org/freedesktop/Hal/devices/ide_0_0 libhal.c 911 : Error sending msg: No property info.category on device with id /org/freedesktop/Hal/devices/ide_0_0 libhal.c 911 : Error sending msg: No property info.category on device with id /org/freedesktop/Hal/devices/ide_0_0 libhal.c 911 : Error sending msg: No property info.category on device with id /org/freedesktop/Hal/devices/ide_0_0 libhal.c 911 : Error sending msg: No property info.category on device with id /org/freedesktop/Hal/devices/ide_0_0 libhal.c 911 : Error sending msg: No property info.category on device with id /org/freedesktop/Hal/devices/ide_0_0 libhal.c 911 : Error sending msg: No property info.category on device with id /org/freedesktop/Hal/devices/ide_1_0 libhal.c 1205 : Error sending msg: No property volume.disc.has_audio on device with id /org/freedesktop/Hal/devices/block_22_2 libhal.c 911 : Error sending msg: No property info.category on device with id /org/freedesktop/Hal/devices/ide_1_0 libhal.c 911 : Error sending msg: No property info.category on device with id /org/freedesktop/Hal/devices/ide_1_0 libhal.c 911 : Error sending msg: No property info.category on device with id /org/freedesktop/Hal/devices/ide_1_0 kdecore (KLibLoader): WARNING: KLibrary: /opt/kde3/lib/kde3/kcm_kdnssd.so: undefined symbol: init_kdnssd kio (KIOConnection): ERROR: Could not write data kio (KIOConnection): ERROR: Could not write data kio (KIOConnection): ERROR: Could not write data kio (KIOConnection): ERROR: Could not write data kio (KIOConnection): ERROR: Could not write data kio (KDirWatch): WARNING: KDirWatch::removeDir can't handle '/dev/stdout' kio (KDirWatch): WARNING: KDirWatch::removeDir can't handle '/dev/stdout' X Error: BadWindow (invalid Window parameter) 3 Major opcode: 20 Minor opcode: 0 Resource id: 0x3000007 X Error: BadWindow (invalid Window parameter) 3 Major opcode: 20 Minor opcode: 0 Resource id: 0x3000007 kio (KDirWatch): WARNING: KDirWatch::removeDir can't handle '/dev' Can we get something from that ? I see some strange messages but do not know what to do with... Thank you JM
From: houghi on 25 Aug 2005 09:00 JM Remacle wrote: >> That could point to the fact that you have something in /etc/fstab that >> should not be there. Not sure what you have in /etc/fstab with >> /dev/hda4, but if it not important, uncomment it from 9.3 and see if >> that works. Then when booted, go into the 9.2 /etc/fstab and correct >> what is there. Take /etc/fstab from 9.3 as an example. >> > this is what i did : > > linux:/home/jmr # fsck -y /dev/hda4 > fsck 1.36 (05-Feb-2005) > reiserfsck 3.6.18 (2003 www.namesys.com) What about putting a # in fromt of /dev/hda4 in .etc/fstab of the version that does not work? -- houghi http://houghi.org > Knock-knock. > Who's there? > Under the Patriot Act, we don't have to tell you that.
From: JM Remacle on 25 Aug 2005 14:14 houghi a ýcrit : > JM Remacle wrote: > >>>That could point to the fact that you have something in /etc/fstab that >>>should not be there. Not sure what you have in /etc/fstab with >>>/dev/hda4, but if it not important, uncomment it from 9.3 and see if >>>that works. Then when booted, go into the 9.2 /etc/fstab and correct >>>what is there. Take /etc/fstab from 9.3 as an example. >>> >> >>this is what i did : >> >>linux:/home/jmr # fsck -y /dev/hda4 >>fsck 1.36 (05-Feb-2005) >>reiserfsck 3.6.18 (2003 www.namesys.com) > > > What about putting a # in fromt of /dev/hda4 in .etc/fstab of the > version that does not work? From 9.3 i commented the 9.2 fstab line concerning hda4 as you suggested Start 9.2 and, youpie, it worked! To be sure i restarted 9.2 and i had a lot of error messages and the startup took nearly half an hour to finally get the prompt... I retried in failsafe mode and the pc stopped at the message : reiserFS:hda4 checking transaction log (hda4) I waited at least 20 minutes and pushed the reset button. The good point is that i could at least start it once. If i cannot get out of that i think i will move all my personal stuff from 9.2 to 9.3 as this distro seems to work correctly. But i always like to know what has happened. Thanks for your help. JM
|
Next
|
Last
Pages: 1 2 Prev: GRUB Error 22 SySE 9.3 with SATA Hard Drive Next: Vivicam 35 on Suse 9.3: Does not detect |