[S.u.S.E. Linux] error file system
To:
hi ppl,
When i start my linux-box, i got the following msg: ------------------------------------------- Uncompressing Linux...done. Now booting the Kernel ide_setup: hdb=cdrom console:16 point font, 400 scans console: colour VGA+ 80x25, 1 virtual console (max 63) pcibios_init : BIOS32 Service Directory structure at 0x000f0280 pcibios_init : BIOS32 Service Directory entry at 0xf0210 pcibios_init : PCI BIOS revision 2.10 entry at 0xf0200 Probing PCI hardware. Calibration delay loop...ok -39.94 BogoMIPS Memory: 30688k/32768k available (772k kernel code, 384k reserved, 924k data SwANSEA University Computer Society NET3.035 for Linux 2.0 NET3: Unix domain sockets 0.13 for Linux NET3.034 IP Protocols: ICMP, UDP, TCP checking 386/387 coupling ...ok, fpu using exception 16 error reporting. checking 'hlt' instruction...ok. Linux version 2.0.29 (root@Mandelbrot.suse.de) gcc version 2.7.2.1 ..... serial driver cersion 4.13 with no serial options enabled tty00 at 0x03f8 (irq =4) is a 16550A tty00 at 0x03f8 (irq =3) is a 16550A PS/2 auiliary pointing device detected -- driver installed. tpqic02: Runtime config, $Revision: 0.4.1.5 $, $Date:1994..... tpqic02: DMA buffers:20 blocks, at address 0x1fde00 (0x1fdc50) ftape-2.08 960314 for Linux 1.3.70 Ramdisk driver initialized: 16 ramdisks of 4096K size ide: i82371 PIIX (Triton) on PCI bus 0 function 57 ide: BM-DMA feature is not enabled (BIOS) hda: ST51080A,1033MB w/256kB Cache, LBA,CHS=525/64/63 hdb: ATAPI cdrom ide at 0x1f0-0x1f7,0x3f6 on irq 14 Floppy driver(s): fd0 is 1.44 started kswapd v .4.2.2 FDC 0 is apost-1991 82077 Partition check: hda: hda1 hda2 hda3 hda4 < hda5 hda6> VFS: Mounted root (ext2 filesystem) readonly. INIT: Version 2.65f booting Running /sbin/init.d/boot. Activating swap-devices in /etc/fstab.. Adding Swap: 50364k swap-space Running update (bdflush) daemon. checking file systems Parallelizing fsck version 1.06 (7-Oct-96) /dev/hda2 contains a file system errors, check forced. hda: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error } hda: read_intr: status=0x40 { UncorrectableError }. LBAsect=385922, sector=18029 end_request: I/O error, dev 03:02, sector 180290 hda: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error } hda: read_intr: status=0x40 { UncorrectableError }. LBAsect=385922, sector=18029 end_request: I/O error, dev 03:02, sector 180290 Error reading block 90145 (Attempt to read block from filesystem resulted in short read) while doing inode scan.
/dev/hda2: UNEXPECTED INCONSISTENC; RUN fsck MANUALLY (i.e., without -a or -p options) Loading /etc/default.keytab
fsck failed. Please repair maually and report. The root file system is currently mounted read-only. To remount it read-write do: bash# mount -n -o remount, rw / Attention: Only Control-D will reboot the system in this maintanance mode. shutdown or reboot will not work.
Give root password to login: -------------------------------------------------------------------
What shall i do?
Thx in advance fadi
-- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
I got the same error once when I was new to linux. If /dev/hda on your box is home to both linux and windows and you defragment in windows it screws up the partition table for linux, or something. Say you have a 2 gig drive, and you repartition, giving windows 1 gig and linux 1 gig. Windows still sees A: as being two gigs. No big deal, you know it's only a gig. But if you defrag in windows it creates problems. I don't think you can recover from that. I reinstalled when it happened to me. Sorry to be vague, I don't fully understand what gets screwed up, but it did happen to me, and I ended up having to reinstall. Perhaps Bodo or someone more qualified can provide a better explanation of what happened. Fadi Sodah wrote:
To:
hi ppl,
When i start my linux-box, i got the following msg: ------------------------------------------- Uncompressing Linux...done. Now booting the Kernel ide_setup: hdb=cdrom console:16 point font, 400 scans console: colour VGA+ 80x25, 1 virtual console (max 63) pcibios_init : BIOS32 Service Directory structure at 0x000f0280 pcibios_init : BIOS32 Service Directory entry at 0xf0210 pcibios_init : PCI BIOS revision 2.10 entry at 0xf0200 Probing PCI hardware. Calibration delay loop...ok -39.94 BogoMIPS Memory: 30688k/32768k available (772k kernel code, 384k reserved, 924k data SwANSEA University Computer Society NET3.035 for Linux 2.0 NET3: Unix domain sockets 0.13 for Linux NET3.034 IP Protocols: ICMP, UDP, TCP checking 386/387 coupling ...ok, fpu using exception 16 error reporting. checking 'hlt' instruction...ok. Linux version 2.0.29 (root@Mandelbrot.suse.de) gcc version 2.7.2.1 ..... serial driver cersion 4.13 with no serial options enabled tty00 at 0x03f8 (irq =4) is a 16550A tty00 at 0x03f8 (irq =3) is a 16550A PS/2 auiliary pointing device detected -- driver installed. tpqic02: Runtime config, $Revision: 0.4.1.5 $, $Date:1994..... tpqic02: DMA buffers:20 blocks, at address 0x1fde00 (0x1fdc50) ftape-2.08 960314 for Linux 1.3.70 Ramdisk driver initialized: 16 ramdisks of 4096K size ide: i82371 PIIX (Triton) on PCI bus 0 function 57 ide: BM-DMA feature is not enabled (BIOS) hda: ST51080A,1033MB w/256kB Cache, LBA,CHS=525/64/63 hdb: ATAPI cdrom ide at 0x1f0-0x1f7,0x3f6 on irq 14 Floppy driver(s): fd0 is 1.44 started kswapd v .4.2.2 FDC 0 is apost-1991 82077 Partition check: hda: hda1 hda2 hda3 hda4 < hda5 hda6> VFS: Mounted root (ext2 filesystem) readonly. INIT: Version 2.65f booting Running /sbin/init.d/boot. Activating swap-devices in /etc/fstab.. Adding Swap: 50364k swap-space Running update (bdflush) daemon. checking file systems Parallelizing fsck version 1.06 (7-Oct-96) /dev/hda2 contains a file system errors, check forced. hda: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error } hda: read_intr: status=0x40 { UncorrectableError }. LBAsect=385922, sector=18029 end_request: I/O error, dev 03:02, sector 180290 hda: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error } hda: read_intr: status=0x40 { UncorrectableError }. LBAsect=385922, sector=18029 end_request: I/O error, dev 03:02, sector 180290 Error reading block 90145 (Attempt to read block from filesystem resulted in short read) while doing inode scan.
/dev/hda2: UNEXPECTED INCONSISTENC; RUN fsck MANUALLY (i.e., without -a or -p options) Loading /etc/default.keytab
fsck failed. Please repair maually and report. The root file system is currently mounted read-only. To remount it read-write do: bash# mount -n -o remount, rw / Attention: Only Control-D will reboot the system in this maintanance mode. shutdown or reboot will not work.
Give root password to login: -------------------------------------------------------------------
What shall i do?
Thx in advance fadi -- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
-- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
Hi! Trying to kill the keyboard, satan@nfinity.com produced:
I got the same error once when I was new to linux. If /dev/hda on your box is home to both linux and windows and you defragment in windows it screws up the partition table for linux, or something. Say you have a 2 gig drive, and you repartition, giving windows 1 gig and linux 1 gig. Windows still sees A: as being two gigs. No big deal, you know it's only a gig. But if you defrag in windows it creates problems. I don't think you can recover from that. I reinstalled when it happened to me. Sorry to be vague, I don't fully understand what gets screwed up, but it did happen to me, and I ended up having to reinstall. Perhaps Bodo or someone more qualified can provide a better explanation of what happened.
Well, I know that M$ Soft is evil at times, knows not that it should not touch the MBR and more of these stuff, but I certainly doubt your explanation. You see, even Windows knows there might be other partitions on the same HD (like d: e: and f:), especially on such a large one. And so defrag is not ging to touch other partitions. And if Windows saw c: (you mean c:, not a:) as 2 Gigs in size, would it know that there was no more space left? (Operating Computers by popular myth is ... well, like living by superstition. You'll never get any good in it, you just learn not to get too close to imagined or read danger. And different to life, computers do always do things logically, even if they are very complex ...) But whatever happened to his partition must have been very bad, cause fsck is usually able to repair a lot of damage. Better hope that you have a working backup somewhere. -Wolfgang -- PGP 2 welcome: Mail me, subject "send PGP-key". If you've nothing at all to hide, you must be boring. Unsolicited Bulk E-Mails: *You* pay for ads you never wanted. Is our economy _so_ weak we have to tolerate SPAMMERS? I guess not. -- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
Let me be specific: On my box, I have a 4 gig drive which is /dev/hda and a 2 gig drive which is /dev/hdb. Before installing linux, /dev/hda consisted of a 2 gig primary partition which windows recognized as C: and a 2 gig extended partition containing a 2 gig logical partition which windows saw as E:. /dev/hdb was seen by windows as D:. I had been using E: as my linux drive when I decided to give linux an extra gig from A:. I repartitioned /dev/hda thusly: /dev/hda1 primary 1 gig windows /dev/hda2 extended 3 gigs -- /dev/hda5 logical 64 megs swap /dev/hda6 logical 100 megs / /dev/hda7 logical 300 megs /opt /dev/hda8 logical 2.3 gigs /usr /dev/hda9 logical 200 megs /home Having installed linux, the two operating systems began a peaceful coexistence. However, windows still reported C: as being the previous 2 gigs (E:, of course was no longer visible to windows, being a 3 gig ext2 set of partitions). If I went into dos fdisk it reported the correct partition information, 1 gig fat16 and 3 gigs of type unknown. I decided that perhaps to have windows properly report the correct partition size it would be necessary to repartition using dos fdisk then reinstall windows. There was no need to go to those lengths just to have windows tell me that C: was the correct size so I dismissed the notion and reconciled myself to living with the mild annoyance. Several weeks later I defragged C: in windows. Later that day when I booted linux I went into kernel panic, got the same error messages that were displayed on this list earlier. I manually ran fsck, and an hour later after repairing error after error and no end in sight I decided reinstalling would be faster than fixing and reformatted the disk and reinstalled. If you don't think that windows defrag is to blame what would you suggest? Wolfgang Weisselberg wrote:
Hi!
Trying to kill the keyboard, satan@nfinity.com produced:
I got the same error once when I was new to linux. If /dev/hda on your box is home to both linux and windows and you defragment in windows it screws up the partition table for linux, or something. Say you have a 2 gig drive, and you repartition, giving windows 1 gig and linux 1 gig. Windows still sees A: as being two gigs. No big deal, you know it's only a gig. But if you defrag in windows it creates problems. I don't think you can recover from that. I reinstalled when it happened to me. Sorry to be vague, I don't fully understand what gets screwed up, but it did happen to me, and I ended up having to reinstall. Perhaps Bodo or someone more qualified can provide a better explanation of what happened.
Well, I know that M$ Soft is evil at times, knows not that it should not touch the MBR and more of these stuff, but I certainly doubt your explanation. You see, even Windows knows there might be other partitions on the same HD (like d: e: and f:), especially on such a large one. And so defrag is not ging to touch other partitions. And if Windows saw c: (you mean c:, not a:) as 2 Gigs in size, would it know that there was no more space left?
(Operating Computers by popular myth is ... well, like living by superstition. You'll never get any good in it, you just learn not to get too close to imagined or read danger. And different to life, computers do always do things logically, even if they are very complex ...)
But whatever happened to his partition must have been very bad, cause fsck is usually able to repair a lot of damage. Better hope that you have a working backup somewhere.
-Wolfgang
-- PGP 2 welcome: Mail me, subject "send PGP-key". If you've nothing at all to hide, you must be boring. Unsolicited Bulk E-Mails: *You* pay for ads you never wanted. Is our economy _so_ weak we have to tolerate SPAMMERS? I guess not. -- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
-- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
While we'ew talking about the future, what's the news about the next release. Will it be 6.0 or 5.3? Will it include Gnome, glibc, whatever.rpm? -- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
Wow, I could've sworn I heard mp3's, au's and wav's playing from my Soundblaster AWE32 on my SuSE box :) It DOES have sound support, you just have to compile it in. RTFM. -- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
On 28-Apr-98 John Weekley wrote:
Wow, I could've sworn I heard mp3's, au's and wav's playing from my Soundblaster AWE32 on my SuSE box :)
It DOES have sound support, you just have to compile it in. RTFM.
For me it's impossible to play a sound with my SB 16 PnP and my PnP BIOS. I though that the kernel must have modular sound support for Sound Blaster to use Isapnp ... but for my surprise it doesn't and I'm pretty sure that for example Red Hat 5.0 does :-? Could someone tell me what I must do to have my sound card running in S.u.S.E. 5.2? I'm absolutely lost about this question :-( Thanks in advance, -- Sergio Rael Gutierrez E-mail: sergio@spainmail.com Albatera, Alicante, SPAIN -- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
Setting up sound on a linux box is somewhat daunting the first time you attempt it. You need to compile sound as a module in your kernel. The best advice I can give is to drop by <A HREF="ftp://sunsite.unc.edu"><A HREF="ftp://sunsite.unc.edu</A">ftp://sunsite.unc.edu, and download the various how to's on sound and isapnp. Sunsite is down at the moment, but I believe they are in /pub/Linux/doc/HOWTO. I realize this probably doesn't seem very helpful to you now, but read the available documentation, post _specific_ questions to the mailing list (or on irc), and you'll get it sooner or later. Good luck to you. Sergio Rael Gutierrez wrote:
On 28-Apr-98 John Weekley wrote:
Wow, I could've sworn I heard mp3's, au's and wav's playing from my Soundblaster AWE32 on my SuSE box :)
It DOES have sound support, you just have to compile it in. RTFM.
For me it's impossible to play a sound with my SB 16 PnP and my PnP BIOS. I though that the kernel must have modular sound support for Sound Blaster to use Isapnp ... but for my surprise it doesn't and I'm pretty sure that for example Red Hat 5.0 does :-?
Could someone tell me what I must do to have my sound card running in S.u.S.E. 5.2? I'm absolutely lost about this question :-(
Thanks in advance,
-- Sergio Rael Gutierrez E-mail: sergio@spainmail.com Albatera, Alicante, SPAIN -- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
-- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
Sergio Rael Gutierrez wrote:
On 28-Apr-98 John Weekley wrote:
Wow, I could've sworn I heard mp3's, au's and wav's playing from my Soundblaster AWE32 on my SuSE box :)
It DOES have sound support, you just have to compile it in. RTFM.
For me it's impossible to play a sound with my SB 16 PnP and my PnP BIOS. I though that the kernel must have modular sound support for Sound Blaster to use Isapnp ... but for my surprise it doesn't and I'm pretty sure that for example Red Hat 5.0 does :-?
there is a file /etc/conf.modules. this file has to be edited too. I got beserk with an ethernet card that whould not work on my running system. (it worked for diskboot and nfs-install). possibly, changes have to be done there too. If you use PnP, there is the isapnp tool. (I never understood it's output ;-( ) I use an old 8 bit soundblaster with _JUMPERS_, hate all this "fuck and pay" stuff. Tried one of these cards too. ran nice under windows. But these were the days before I heared of conf.modules and isapnp.
Could someone tell me what I must do to have my sound card running in S.u.S.E. 5.2? I'm absolutely lost about this question :-(
Jürgen -- ========================================== __ _ Jürgen Braukmann e-mail: brauki@cww.de | / / (_)__ __ ____ __ Tel: 0201-743648 dk4jb@db0qs.#nrw.deu.eu | / /__/ / _ \/ // /\ \/ / ========================================== /____/_/_//_/\_,_/ /_/\_\ -- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
Sergio, I have the same card, and I just want to let you know, it works great under 5.2 SuSE. The default config is IO=220, DMA 1 & 5 and IRQ 7. My card had set it's self up to IRQ 5 so I had to change the settings in the kernel config. Also be sure to turn on /dev/dsp and /dev/audio line in the same area of kernel config. Then go through the steps of build and installing a kernel and modules. Here is a section of my .config # # Sound # CONFIG_SOUND=m # CONFIG_PAS is not set CONFIG_SB=y # CONFIG_ADLIB is not set # CONFIG_GUS is not set # CONFIG_MPU401 is not set # CONFIG_UART6850 is not set # CONFIG_PSS is not set # CONFIG_GUS16 is not set # CONFIG_GUSMAX is not set # CONFIG_MSS is not set # CONFIG_SSCAPE is not set # CONFIG_TRIX is not set # CONFIG_MAD16 is not set # CONFIG_CS4232 is not set # CONFIG_MAUI is not set CONFIG_AUDIO=y # CONFIG_MIDI is not set # CONFIG_YM3812 is not set SBC_BASE=220 SBC_IRQ=5 SBC_DMA=1 SB_DMA2=5 SB_MPU_BASE=0 SB_MPU_IRQ=-1 DSP_BUFFSIZE=65536 # CONFIG_LOWLEVEL_SOUND is not set Good Luck Lach -- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
Can you determine what address and IRQ you sound card is configured at? Have you tried to use the PnP package that is included in SuSE? I have never used a PnP card with Linux so you'll have to try and use it to setup your sound card. When that is done you will have to buils a kernel that has support for you card. Check the Linux Documentation Project for sound HOWTO's www.sunsite.unc.edu Hope that helps Frank *********** REPLY SEPARATOR *********** On 4/29/98, at 1:09 PM, Sergio Rael Gutierrez wrote:
On 28-Apr-98 John Weekley wrote:
Wow, I could've sworn I heard mp3's, au's and wav's playing from my Soundblaster AWE32 on my SuSE box :)
It DOES have sound support, you just have to compile it in. RTFM.
For me it's impossible to play a sound with my SB 16 PnP and my PnP BIOS. I though that the kernel must have modular sound support for Sound Blaster to use Isapnp ... but for my surprise it doesn't and I'm pretty sure that for example Red Hat 5.0 does :-?
Could someone tell me what I must do to have my sound card running in S.u.S.E. 5.2? I'm absolutely lost about this question :-(
Thanks in advance,
-- Sergio Rael Gutierrez E-mail: sergio@spainmail.com Albatera, Alicante, SPAIN -- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
-- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
On Wed, 29 Apr 1998, Sergio Rael Gutierrez wrote:
Could someone tell me what I must do to have my sound card running in S.u.S.E. 5.2? I'm absolutely lost about this question :-(
You mat try the latest OSS sound driver. It will detect your sound card automatically and install the software for it. Please note that the software is not free, nut not expensive either ;) It works like a charm. Regards, Ruud. -- Forget everything, as one day everything will forget you. -- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
John Weekley wrote:
Wow, I could've sworn I heard mp3's, au's and wav's playing from my Soundblaster AWE32 on my SuSE box :)
It DOES have sound support, you just have to compile it in. RTFM.
Wow... it didn't work for me... any of the 3 ways I tried it. Wow... is it POSSIBLE that not everything is equal? Wow... perhaps people that are having problems getting something to work, and are tired of it, are just supposed to shut up. -- Bruce -- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
Hi! Trying to kill the keyboard, sodah@qatar.net.qa produced:
/dev/hda2: UNEXPECTED INCONSISTENC; RUN fsck MANUALLY (i.e., without -a or -p options) Loading /etc/default.keytab
fsck failed. Please repair maually and report. The root file system is ^^^^^^^ reboot. currently mounted read-only. To remount it read-write do: bash# mount -n -o remount, rw / Attention: Only Control-D will reboot the system in this maintanance mode. shutdown or reboot will not work.
Give root password to login: -------------------------------------------------------------------
What shall i do?
Exactly what it says: ===================== "RUN fsck MANUALLY" "Please repair manually and reboot" (the man page for e2fsck is printed out in the SuSE handbook, in the appendices) after typing in the root password as requested. Shesh, don't people read what they copy&paste any more? -Wolfgang PS: If you, for any reason, cannot read the manpage, mail me personally (i.e. not via the list) and I'll mail it to you. PPS: the text he quoted (mangled?) comes straight out of /sbin/init.d/boot. -- PGP 2 welcome: Mail me, subject "send PGP-key". If you've nothing at all to hide, you must be boring. Unsolicited Bulk E-Mails: *You* pay for ads you never wanted. Is our economy _so_ weak we have to tolerate SPAMMERS? I guess not. -- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
participants (11)
-
barothwe＠cca.rockwell.com -
brauki＠cww.de -
fpawlak＠execpc.com -
kar＠webline.dk -
lach＠lach.net -
rdebruin＠cistron.nl -
satan＠nfinity.com -
sergio＠spainmail.com -
sodah＠qatar.net.qa -
weekleyj＠fastrans.net -
weissel＠jupiter.ph-cip.uni-koeln.de