LinuxQuestions.org
Go Job Hunting at the LQ Job Marketplace
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Fedora
User Name
Password
Fedora This forum is for the discussion of the Fedora Project.

Notices

Reply
 
Search this Thread
Old 03-28-2005, 04:04 PM   #1
brookepb
LQ Newbie
 
Registered: Mar 2005
Posts: 9

Rep: Reputation: 0
Filesystems always mounted as read-only on boot after recent system freeze


I am not sure that this is a Fedora problem but my googles haven't given me a direction to pursue or where I should be looking to figure out the problem so I'm asking those more knowledgeable for help.

I have a dual Opteron machine with a software raided pair of drives running the Fedora x86_64 builds. This machine occasionally freezes which I've guessed to be a problem from the ATI drivers.

The problem: I try to boot and all kinds of errors are thrown during startup because nothing can write to the drives and I end up at a semi-normal prompt(hostname setting gets screwed up during the boot so I end up with a user@(none) prompt) in a read-only filesystem. Navigation and read-only actions all seem to work fine.

Things I'm guessing could be relevant that were changed before the post-freeze problem started:
1) My machine was a Fedora Core 3 w/updates OS and any of a bunch of kernels up to the most recent available on the 25th for that distrib. I did a:
Quote:
rpm -Uvh /path/fedora-release-3.90-2.noarch.rpm
2) set the exactarch value in /etc/yum.conf to 1 instead of 0 as it was.
3) did a yum update which updated 20 lines worth of files in /var/log/yum.log Everything normal.

Eventually had a system freeze and did a power-off reboot.

4) I allowed fsck to look at filesystem as I always do after a freeze since there are always inconsistencies.
5) Next time I checked in on the machine I had a login prompt and didn't notice anything was wrong until I attempted to invoke X and it threw gobs of errors because it couldn't write lock files and whatnot.
5) I reboot, end up in the same spot. Try mounting a partition, in this case /boot and it works fine and I can write to a test file in it.
6) I looked the last entries in /var/log/messages and don't see anything that appears likely. This and other logs seem to all stop at the point filesystem started being booted as read only. They all look normal to me.
7) I wonder if grub is doing something and I remove the 'ro' portions from a test case kernel version (reg and smp) boot arguments.

No luck so I'm hoping for ideas.

What do I need to do to track down how to fix this?
 
Old 03-28-2005, 04:23 PM   #2
mrGenixus
Member
 
Registered: Dec 2004
Location: Colorado, US
Distribution: gentoo, debian, ubuntu live gnome 2.10
Posts: 440

Rep: Reputation: 30
Check your /etc/fstab to make sure that it is intact, correct. Also If you could post your Boot output using /var/log/messages, dmesg, /var/log/syslog.

This might help explain why it's failing to mount disks, or why it's booting wierd.

ALSO, it might be helpful to see your menu.1st / grub.conf to make usre you're not running the setup with ro
 
Old 03-28-2005, 05:09 PM   #3
brookepb
LQ Newbie
 
Registered: Mar 2005
Posts: 9

Original Poster
Rep: Reputation: 0
log files

I'm not sure as to how I can capture the boot output or anything else that is being output while the system loads as the logs all stopped being updated/written to when this problem started due presumably to their wanting to write to a system that has already been mounted as read only. The last entries in the boot, messages logs date to the 24th, before the problem. I haven't included them until I hear you are still interested in seeing them.

I've copied the dmesg output, my fstab which seems ok on a quick glance, and syslog below.

fstab first: hmm, this was last touched by something on the day of doom, the 25th
Quote:
# This file is edited by fstab-sync - see 'man fstab-sync' for details
/dev/md0 / ext3 defaults 1 1
LABEL=/boot /boot ext3 defaults 1 2
none /dev/pts devpts gid=5,mode=620 0 0
none /dev/shm tmpfs defaults 0 0
none /proc proc defaults 0 0
none /sys sysfs defaults 0 0
/dev/VolGroup00/LogVol00 swap swap defaults 0 0
//bdl1/bdl /home/bburch/bdl1 smbfs noauto,_netdev,user,suid 0 0
/dev/hda /media/cdrecorder auto pamconsole,exec,noauto,managed 0 0
Syslog: I have no /var/log/syslog but I do have /etc/sysconfig/syslog which is ancient (Jan 14) is the following:
Quote:
# Options to syslogd
# -m 0 disables 'MARK' messages.
# -r enables logging from remote machines
# -x disables DNS lookups on messages recieved with -r
# See syslogd(8) for more details
SYSLOGD_OPTIONS="-m 0"
# Options to klogd
# -2 prints all kernel oops messages twice; once for klogd to decode, and
# once for processing with 'ksymoops'
# -x disables all klogd processing of oops messages entirely
# See klogd(8) for more details
KLOGD_OPTIONS="-x"
menu.lst showing the item I tampered with on top:
Quote:
# grub.conf generated by anaconda
#
# Note that you do not have to rerun grub after making changes to this file
# NOTICE: You have a /boot partition. This means that
# all kernel and initrd paths are relative to /boot/, eg.
# root (hd0,0)
# kernel /vmlinuz-version ro root=/dev/md0
# initrd /initrd-version.img
#boot=/dev/sda
default=0
timeout=5
splashimage=(hd0,0)/grub/splash.xpm.gz
hiddenmenu
title Fedora Core (2.6.10-1.770_FC3smp)
root (hd0,0)
kernel /vmlinuz-2.6.10-1.770_FC3smp root=/dev/md0
initrd /initrd-2.6.10-1.770_FC3smp.img
title Fedora Core (2.6.10-1.770_FC3)
root (hd0,0)
kernel /vmlinuz-2.6.10-1.770_FC3 root=/dev/md0
initrd /initrd-2.6.10-1.770_FC3.img
title Fedora Core (2.6.10-1.766_FC3smp)
root (hd0,0)
kernel /vmlinuz-2.6.10-1.766_FC3smp ro root=/dev/md0
initrd /initrd-2.6.10-1.766_FC3smp.img
title Fedora Core (2.6.10-1.766_FC3)
root (hd0,0)
kernel /vmlinuz-2.6.10-1.766_FC3 ro root=/dev/md0
initrd /initrd-2.6.10-1.766_FC3.img
title Fedora Core (2.6.10-1.741_FC3)
root (hd0,0)
kernel /vmlinuz-2.6.10-1.741_FC3 ro root=/dev/md0
initrd /initrd-2.6.10-1.741_FC3.img
title Fedora Core (2.6.10-1.741_FC3smp)
root (hd0,0)
kernel /vmlinuz-2.6.10-1.741_FC3smp ro root=/dev/md0
initrd /initrd-2.6.10-1.741_FC3smp.img
title Fedora Core (2.6.10-1.737_FC3smp)
root (hd0,0)
kernel /vmlinuz-2.6.10-1.737_FC3smp ro root=/dev/md0
initrd /initrd-2.6.10-1.737_FC3smp.img
title Fedora Core (2.6.10-1.737_FC3)
root (hd0,0)
kernel /vmlinuz-2.6.10-1.737_FC3 ro root=/dev/md0
initrd /initrd-2.6.10-1.737_FC3.img
title Fedora Core (2.6.9-1.640smp)
root (hd0,0)
kernel /vmlinuz-2.6.9-1.640smp ro root=/dev/md0
initrd /initrd-2.6.9-1.640smp.img
title Fedora Core (2.6.9-1.640)
root (hd0,0)
kernel /vmlinuz-2.6.9-1.640 ro root=/dev/md0
initrd /initrd-2.6.9-1.640.img
title Fedora Core (2.6.8-1.541smp)
root (hd0,0)
kernel /vmlinuz-2.6.8-1.541smp ro root=/dev/md0
initrd /initrd-2.6.8-1.541smp.img
title Fedora Core-up (2.6.8-1.541)
root (hd0,0)
kernel /vmlinuz-2.6.8-1.541 ro root=/dev/md0
initrd /initrd-2.6.8-1.541.img
dmesg output, I think this may be from the last 'good' config before the problem started. I don't know if this gets around the write problem or not.
Quote:
Bootdata ok (command line is root=/dev/md0)
Linux version 2.6.10-1.770_FC3 (bhcompile@dolly.build.redhat.com) (gcc version 3.4.2 20041017 (Red Hat 3.4.2-6.fc3)) #1 Thu Feb 24 18:09:38 EST 2005
BIOS-provided physical RAM map:
BIOS-e820: 0000000000000000 - 000000000009fc00 (usable)
BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved)
BIOS-e820: 00000000000e0000 - 0000000000100000 (reserved)
BIOS-e820: 0000000000100000 - 00000000adff0000 (usable)
BIOS-e820: 00000000adff0000 - 00000000adfff000 (ACPI data)
BIOS-e820: 00000000adfff000 - 00000000ae000000 (ACPI NVS)
BIOS-e820: 00000000ff780000 - 0000000100000000 (reserved)
No mptable found.
On node 0 totalpages: 712688
DMA zone: 4096 pages, LIFO batch:1
Normal zone: 708592 pages, LIFO batch:16
HighMem zone: 0 pages, LIFO batch:1
ACPI: RSDP (v000 ACPIAM ) @ 0x00000000000f68a0
ACPI: RSDT (v001 A M I OEMRSDT 0x06000428 MSFT 0x00000097) @ 0x00000000adff0000
ACPI: FADT (v001 A M I OEMFACP 0x06000428 MSFT 0x00000097) @ 0x00000000adff0200
ACPI: MADT (v001 A M I OEMAPIC 0x06000428 MSFT 0x00000097) @ 0x00000000adff0380
ACPI: OEMB (v001 A M I OEMBIOS 0x06000428 MSFT 0x00000097) @ 0x00000000adfff040
ACPI: ASF! (v001 AMIASF AMDSTRET 0x00000001 INTL 0x02002026) @ 0x00000000adff3330
ACPI: DSDT (v001 0AAAA 0AAAA000 0x00000000 INTL 0x02002026) @ 0x0000000000000000
ACPI: Local APIC address 0xfee00000
ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
Processor #0 15:5 APIC version 16
ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01] enabled)
Processor #1 15:5 APIC version 16
WARNING: NR_CPUS limit of 1 reached. Processor ignored.
ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0])
IOAPIC[0]: apic_id 2, version 17, address 0xfec00000, GSI 0-23
ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
ACPI: IRQ0 used by override.
ACPI: IRQ2 used by override.
ACPI: IRQ9 used by override.
Setting APIC routing to flat
Using ACPI (MADT) for SMP configuration information
Checking aperture...
CPU 0: aperture @ f0000000 size 128 MB
CPU 1: aperture @ f0000000 size 128 MB
Built 1 zonelists
Kernel command line: root=/dev/md0 console=tty0
Initializing CPU#0
PID hash table entries: 4096 (order: 12, 131072 bytes)
time.c: Using 1.193182 MHz PIT timer.
time.c: Detected 1992.975 MHz processor.
Console: colour VGA+ 80x25
Dentry cache hash table entries: 524288 (order: 10, 4194304 bytes)
Inode-cache hash table entries: 262144 (order: 9, 2097152 bytes)
Memory: 2799072k/2850752k available (2362k kernel code, 50932k reserved, 1268k data, 176k init)
Calibrating delay loop... 3915.77 BogoMIPS (lpj=1957888)
Security Framework v1.0.0 initialized
SELinux: Initializing.
SELinux: Starting in permissive mode
selinux_register_security: Registering secondary module capability
Capability LSM initialized as secondary
Mount-cache hash table entries: 256 (order: 0, 4096 bytes)
CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
CPU: L2 Cache: 1024K (64 bytes/line)
CPU: AMD Opteron(tm) Processor 246 stepping 0a
Using local APIC NMI watchdog using perfctr0
Using local APIC timer interrupts.
Detected 12.456 MHz APIC timer.
checking if image is initramfs... it is
NET: Registered protocol family 16
PCI: Using configuration type 1
mtrr: v2.0 (20020519)
ACPI: Subsystem revision 20041105
ACPI: Interpreter enabled
ACPI: Using IOAPIC for interrupt routing
ACPI: PCI Root Bridge [PCI0] (00:00)
PCI: Probing PCI hardware (bus 00)
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PCI1._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.P0P2._PRT]
ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 9 10 *11 12 14 15)
ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 *9 10 11 12 14 15)
ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 *5 6 7 9 10 11 12 14 15)
ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 7 9 *10 11 12 14 15)
usbcore: registered new driver usbfs
usbcore: registered new driver hub
PCI: Using ACPI for IRQ routing
** PCI interrupts are no longer routed automatically. If this
** causes a device to stop working, it is probably because the
** driver failed to call pci_enable_device(). As a temporary
** workaround, the "pci=routeirq" argument restores the old
** behavior. If this argument makes the device work again,
** please email the output of "lspci" to bjorn.helgaas@hp.com
** so I can fix the driver.
agpgart: Detected AMD 8151 AGP Bridge rev B3
agpgart: Maximum main memory to use for agp memory: 2642M
agpgart: AGP aperture is 128M @ 0xf0000000
PCI-DMA: Disabling IOMMU.
IA32 emulation $Id: sys_ia32.c,v 1.32 2002/03/24 13:02:28 ak Exp $
audit: initializing netlink socket (disabled)
audit(1112018722.273:0): initialized
Total HugeTLB memory allocated, 0
VFS: Disk quotas dquot_6.5.1
Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
SELinux: Registering netfilter hooks
Initializing Cryptographic API
ksign: Installing public key data
Loading keyring
- Added public key B36A0C3CDBFF4E02
- User ID: Red Hat, Inc. (Kernel Module GPG key)
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
ACPI: Processor [CPU1] (supports 8 throttling states)
Real Time Clock Driver v1.12
hpet_acpi_add: no address or irqs in _CRS
Linux agpgart interface v0.100 (c) Dave Jones
serio: i8042 AUX port at 0x60,0x64 irq 12
serio: i8042 KBD port at 0x60,0x64 irq 1
Serial: 8250/16550 driver $Revision: 1.90 $ 76 ports, IRQ sharing enabled
ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered
RAMDISK driver initialized: 16 RAM disks of 16384K size 1024 blocksize
divert: not allocating divert_blk for non-ethernet device lo
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
AMD8111: IDE controller at PCI slot 0000:00:07.1
AMD8111: chipset revision 3
AMD8111: not 100% native mode: will probe irqs later
AMD8111: 0000:00:07.1 (rev 03) UDMA133 controller
ide0: BM-DMA at 0xffa0-0xffa7, BIOS settings: hdaMA, hdbio
ide1: BM-DMA at 0xffa8-0xffaf, BIOS settings: hdcio, hddio
Probing IDE interface ide0...
hda: TEAC DV-W58G-A, ATAPI CD/DVD-ROM drive
elevator: using anticipatory as default io scheduler
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
Probing IDE interface ide1...
Probing IDE interface ide1...
hda: ATAPI 40X DVD-ROM DVD-R CD-R/RW drive, 2048kB Cache, UDMA(33)
Uniform CD-ROM driver Revision: 3.20
ide-floppy driver 0.99.newide
usbcore: registered new driver hiddev
usbcore: registered new driver usbhid
drivers/usb/input/hid-core.c: v2.0:USB HID core driver
mice: PS/2 mouse device common for all mice
md: md driver 0.90.1 MAX_MD_DEVS=256, MD_SB_DISKS=27
NET: Registered protocol family 2
IP: routing cache hash table of 4096 buckets, 224Kbytes
TCP: Hash tables configured (established 524288 bind 37449)
Initializing IPsec netlink socket
NET: Registered protocol family 1
NET: Registered protocol family 17
powernow-k8: Found 1 AMD Athlon 64 / Opteron processors (version 1.00.09e)
powernow-k8: BIOS error - no PSB
ACPI wakeup devices:
PCI1 USB0 USB1 UAR1 SMBC AC97 MODM PWRB
ACPI: (supports S0 S1 S4 S5)
Freeing unused kernel memory: 176k freed
SCSI subsystem initialized
libata version 1.10 loaded.
sata_sil version 0.8
ACPI: PCI interrupt 0000:01:05.0[A] -> GSI 19 (level, low) -> IRQ 169
ata1: SATA max UDMA/100 cmd 0xFFFFFF0000004C80 ctl 0xFFFFFF0000004C8A bmdma 0xFFFFFF0000004C00 irq 169
ata2: SATA max UDMA/100 cmd 0xFFFFFF0000004CC0 ctl 0xFFFFFF0000004CCA bmdma 0xFFFFFF0000004C08 irq 169
ata3: SATA max UDMA/100 cmd 0xFFFFFF0000004E80 ctl 0xFFFFFF0000004E8A bmdma 0xFFFFFF0000004E00 irq 169
ata4: SATA max UDMA/100 cmd 0xFFFFFF0000004EC0 ctl 0xFFFFFF0000004ECA bmdma 0xFFFFFF0000004E08 irq 169
ata1: dev 0 cfg 49:2f00 82:346b 83:7f21 84:4003 85:3469 86:3c01 87:4003 88:203f
ata1: dev 0 ATA, max UDMA/100, 312581808 sectors: lba48
ata1: dev 0 configured for UDMA/100
scsi0 : sata_sil
ata2: dev 0 cfg 49:2f00 82:346b 83:7f21 84:4003 85:3469 86:3c01 87:4003 88:203f
ata2: dev 0 ATA, max UDMA/100, 312581808 sectors: lba48
ata2: dev 0 configured for UDMA/100
scsi1 : sata_sil
ata3: no device found (phy stat 00000000)
scsi2 : sata_sil
ata4: no device found (phy stat 00000000)
scsi3 : sata_sil
Vendor: ATA Model: WDC WD1600JD-00G Rev: 02.0
Type: Direct-Access ANSI SCSI revision: 05
SCSI device sda: 312581808 512-byte hdwr sectors (160042 MB)
SCSI device sda: drive cache: write back
SCSI device sda: 312581808 512-byte hdwr sectors (160042 MB)
SCSI device sda: drive cache: write back
sda: sda1 sda2 sda3
Attached scsi disk sda at scsi0, channel 0, id 0, lun 0
Vendor: ATA Model: WDC WD1600JD-00G Rev: 02.0
Type: Direct-Access ANSI SCSI revision: 05
SCSI device sdb: 312581808 512-byte hdwr sectors (160042 MB)
SCSI device sdb: drive cache: write back
SCSI device sdb: 312581808 512-byte hdwr sectors (160042 MB)
SCSI device sdb: drive cache: write back
sdb: sdb1 sdb2
Attached scsi disk sdb at scsi1, channel 0, id 0, lun 0
device-mapper: 4.3.0-ioctl (2004-09-30) initialised: dm-devel@redhat.com
md: raid0 personality registered as nr 2
md: Autodetecting RAID arrays.
md: autorun ...
md: considering sdb2 ...
md: adding sdb2 ...
md: adding sda2 ...
md: created md0
md: bind<sda2>
md: bind<sdb2>
md: running: <sdb2><sda2>
md0: setting max_sectors to 512, segment boundary to 131071
raid0: looking at sdb2
raid0: comparing sdb2(155163648) with sdb2(155163648)
raid0: END
raid0: ==> UNIQUE
raid0: 1 zones
raid0: looking at sda2
raid0: comparing sda2(155163648) with sdb2(155163648)
raid0: EQUAL
raid0: FINAL 1 zones
raid0: done.
raid0 : md_size is 310327296 blocks.
raid0 : conf->hash_spacing is 310327296 blocks.
raid0 : nb_zone is 1.
raid0 : Allocating 8 bytes for hash.
md: ... autorun DONE.
kjournald starting. Commit interval 5 seconds
EXT3-fs: mounted filesystem with ordered data mode.
FDC 0 is a post-1991 82077
Intel(R) PRO/1000 Network Driver - version 5.5.4-k2-NAPI
Copyright (c) 1999-2004 Intel Corporation.
ACPI: PCI interrupt 0000:01:03.0[A] -> GSI 18 (level, low) -> IRQ 177
divert: allocating divert_blk for eth0
e1000: eth0: e1000_probe: Intel(R) PRO/1000 Network Connection
ip_tables: (C) 2000-2002 Netfilter core team
ACPI: PCI interrupt 0000:00:07.5[B] -> GSI 17 (level, low) -> IRQ 185
intel8x0_measure_ac97_clock: measured 49956 usecs
intel8x0: clocking to 48000
ACPI: PCI interrupt 0000:01:0b.2[C] -> GSI 19 (level, low) -> IRQ 169
ehci_hcd 0000:01:0b.2: EHCI Host Controller
ehci_hcd 0000:01:0b.2: irq 169, pci mem 0xff4ff800
ehci_hcd 0000:01:0b.2: new USB bus registered, assigned bus number 1
ehci_hcd 0000:01:0b.2: USB 2.0 initialized, EHCI 1.00, driver 26 Oct 2004
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 4 ports detected
USB Universal Host Controller Interface driver v2.2
ACPI: PCI interrupt 0000:01:0b.0[A] -> GSI 17 (level, low) -> IRQ 185
uhci_hcd 0000:01:0b.0: UHCI Host Controller
uhci_hcd 0000:01:0b.0: irq 185, io base 0x9400
uhci_hcd 0000:01:0b.0: new USB bus registered, assigned bus number 2
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 2 ports detected
ACPI: PCI interrupt 0000:01:0b.1[B] -> GSI 18 (level, low) -> IRQ 177
uhci_hcd 0000:01:0b.1: UHCI Host Controller
e1000: eth0: e1000_watchdog: NIC Link is Up 100 Mbps Full Duplex
uhci_hcd 0000:01:0b.1: irq 177, io base 0x9800
uhci_hcd 0000:01:0b.1: new USB bus registered, assigned bus number 3
hub 3-0:1.0: USB hub found
hub 3-0:1.0: 2 ports detected
ohci_hcd: 2004 Nov 08 USB 1.1 'Open' Host Controller (OHCI) Driver (PCI)
ACPI: PCI interrupt 0000:01:00.0[D] -> GSI 19 (level, low) -> IRQ 169
ohci_hcd 0000:01:00.0: OHCI Host Controller
ohci_hcd 0000:01:00.0: irq 169, pci mem 0xff4fd000
ohci_hcd 0000:01:00.0: new USB bus registered, assigned bus number 4
hub 4-0:1.0: USB hub found
hub 4-0:1.0: 3 ports detected
ACPI: PCI interrupt 0000:01:00.1[D] -> GSI 19 (level, low) -> IRQ 169
ohci_hcd 0000:01:00.1: OHCI Host Controller
ohci_hcd 0000:01:00.1: irq 169, pci mem 0xff4fe000
ohci_hcd 0000:01:00.1: new USB bus registered, assigned bus number 5
hub 5-0:1.0: USB hub found
hub 5-0:1.0: 3 ports detected
ieee1394: Initialized config rom entry `ip1394'
ohci1394: $Rev: 1223 $ Ben Collins <bcollins@debian.org>
ACPI: PCI interrupt 0000:01:0a.0[A] -> GSI 17 (level, low) -> IRQ 185
ohci1394: fw-host0: OHCI-1394 1.0 (PCI): IRQ=[185] MMIO=[ff4ff000-ff4ff7ff] Max Packet=[2048]
md: Autodetecting RAID arrays.
md: autorun ...
md: ... autorun DONE.
usb 5-1: new low speed USB device using ohci_hcd and address 2
input: USB HID v1.10 Keyboard [Logitech USB Receiver] on usb-0000:01:00.1-1
ACPI: Power Button (FF) [PWRF]
input: USB HID v1.10 Mouse [Logitech USB Receiver] on usb-0000:01:00.1-1
ibm_acpi: ec object not found
usb 5-2: new low speed USB device using ohci_hcd and address 3
input: USB HID v1.00 Mouse [Kensington Kensington USB/PS2 Trackball] on usb-0000:01:00.1-2
ieee1394: Host added: ID:BUS[0-00:1023] GUID[00e081000030393d]
kjournald starting. Commit interval 5 seconds
EXT3 FS on sda1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
 
Old 03-28-2005, 05:18 PM   #4
mrGenixus
Member
 
Registered: Dec 2004
Location: Colorado, US
Distribution: gentoo, debian, ubuntu live gnome 2.10
Posts: 440

Rep: Reputation: 30
Can you mount the disks after you boot up?

If not, what errors do you get?
Can you give me an idea of what the errors are? also, pressing the 'pause' button on the keyboard sometimes will stop kernel output, <enter> should restart it.
 
Old 03-28-2005, 05:38 PM   #5
brookepb
LQ Newbie
 
Registered: Mar 2005
Posts: 9

Original Poster
Rep: Reputation: 0
I know essentially nothing about mounting and unmounting. I've done it manually a few times but its just rote repetition of something I've seen shown somewhere without any deep understanding of what I am doing.

After a boot, I've been able to:
mount /boot
and get into the boot partition in a r/w manner. That is how I was able to generate the dmesg results.

If I try to:
umount -v /
I get '/dev/md0 unmounted' but I actually have no problems navigating to it and using it still.

If I then immediately try to remount it:
mount -v /
I get
'mount: /dev/md0 already mounted or / busy'
'mount: according to mtab, /dev/md0 is already mounted on /'

Which makes sense since umount isn't able to write to mtab.

I haven't managed to get the boot to pause yet through hitting the pause/break button.

Last edited by brookepb; 03-28-2005 at 05:44 PM.
 
Old 03-28-2005, 07:28 PM   #6
brookepb
LQ Newbie
 
Registered: Mar 2005
Posts: 9

Original Poster
Rep: Reputation: 0
I can view part of the boot buffer upt to just prior to the "Welcome to Fedora Core" message using shift+pg up b

----------------
md: ... autorun DONE
Creating root device
Mounting root filesystem
kjournald starting. Commit interval 5 seconds
EXT3-fs: mounted filesystem with ordered data mode.
Switching to new root
INIT: version 2.85 booting
-----------------

Now the 1st error I can see in the portion of the buffer I can reach...

-----------------
/etc/rc.d/rc.sysinit: line 30: /etc/init.d/functions: No such file or directory
Welcome to Fedora Core
Press 'I' to enter interactive startup.
------------------

Pressing 'I' is ignored as are pause, scroll lock though pause does work prior to grub getting going. There are further errors...

------------------
/sbin/start_udev: line 35: /etc/init.d/funcitons: No such file or directory
/etc/rc.d/rc.sysinit: line 135: strstr: command not found ## GOBS OF SYSINIT COMMAND NOT FOUND ERRORS ##
-------------------

This is followed by lots of hardware being found and initialized properly. and then a desire to see if I want to foce a file sysstem integrity check
[/sbin/fsck.ext3 (1) -- /] fsck.ext3 -a /dev/md0 ## AND OTHER PARTITIONS ##

and a bunch of clean-up stuff in /var/lock throwing errors such as this example:
rm: cannot remove '/var/lock/subsys/acpid' : Read-only file system

And then I get a login prompt which will get me logged on and able to view the filesystem though not modify it.
 
Old 03-28-2005, 07:33 PM   #7
mrGenixus
Member
 
Registered: Dec 2004
Location: Colorado, US
Distribution: gentoo, debian, ubuntu live gnome 2.10
Posts: 440

Rep: Reputation: 30
after logging in, mount /boot

them mount /dev/hda1 (or your root partition) /boot/grub
or create a directory in /boot and mount it there

see if you can mount it readonly, and if not, why
 
Old 03-29-2005, 03:29 PM   #8
brookepb
LQ Newbie
 
Registered: Mar 2005
Posts: 9

Original Poster
Rep: Reputation: 0
More info about the symptoms of this problem in response to mrGenixus' last post.

I did the following:
# mount /boot
# cd /boot
# mkdir test_mnt
# mount /dev/md0 test_mnt

This then mounts my root filesystem in read-only mode under test_mnt
I can also do this to set my root filesystem to read-write once logged on
# mount -o remount /

This will get me write access to the root filesystem. However this is lost upon reboot. Where could this be getting set improperly?
 
Old 03-29-2005, 04:48 PM   #9
mrGenixus
Member
 
Registered: Dec 2004
Location: Colorado, US
Distribution: gentoo, debian, ubuntu live gnome 2.10
Posts: 440

Rep: Reputation: 30
Please try to get a complete list of errors from boot
 
Old 03-29-2005, 06:03 PM   #10
brookepb
LQ Newbie
 
Registered: Mar 2005
Posts: 9

Original Poster
Rep: Reputation: 0
With regard to getting more messages from the boot process someone will have to come up with a way for me to log these messages. This system boots very rapidly, it scrolls info far too quickly for human eyes to track. Normally that is a plus! Logging is not happening at all as far as I can tell. I can not pause the boot process via any technique to be able to look at std out. I think I've posted the methods I used in attempting to pause the boot in an earlier email and have hammered every key I could in just hopes. The last point where the boot process will respond to keyboard input is grub.

Is this a new safety feature of some sort reminiscent of safe-mode resulting from the inconsistent journal with fsck.ext3 just not making the changes it should or releasing the drive as clean? I vaguely recollect some mention that fsck might have the power to get drives with problems (though it doesn't actually find any) to boot in read-only mode. Does this ring any bells? This system always thinks its crashing even though reboots are normal and working fine because the system isn't writing its shutdown info. I would think it would be able to write once I've remounted the root filesystem in writable mode but perhaps there are services that aren't getting started that should during the messed up boot with the errors mentioned in my previous message listing those errors which were visible to me.
 
Old 03-29-2005, 06:23 PM   #11
mrGenixus
Member
 
Registered: Dec 2004
Location: Colorado, US
Distribution: gentoo, debian, ubuntu live gnome 2.10
Posts: 440

Rep: Reputation: 30
wothout a complete list of erros, we cannot correc them. PLease reinstall Fedorea Core 3 to correct the problems you are having
 
Old 03-30-2005, 10:58 AM   #12
brookepb
LQ Newbie
 
Registered: Mar 2005
Posts: 9

Original Poster
Rep: Reputation: 0
I appreciate the help I've received. People have to be brave to try to tackle the fairly tough probs. However, I'm not quite ready to throw in the towel and reinstall after hunting down all the important data on the machine and scp'g it to somewhere else temporarily though the time cost is getting close to about break even now.

I have made some progress this morning. I found this page: http://openskills.info/infobox.php?ID=228 I then began walking through the boot steps and quickly focused on the first boot error I HAD been able to recover: (copied from an earlier post) /etc/rc.d/rc.sysinit: line 30: /etc/init.d/functions: No such file or directory

I hunted down 'functions' which appears to be residing at /etc/rc.d/init.d/functions and created a symlink to it in /etc (ln -s /etc/rc.d/init.d /etc/init.d)

I certainly didn't make changes to rc.sysinit nor functions

I am now wondering if my system freeze occurred actually during the last yum upgrade after switching yum to think it was the Fedora 4 test 1 release. Perhaps these files have been changed in FC4?

Doing this has gotten me a lot further into the boot process including getting the root filesystem to mount in a write mode. I now make it to a normal and working login prompt. However attempting a startx is deadly leading to completely blank screens and an unresponsive keyboard.

While there are still problems to solve, now that I am getting most services started properly and have logging working, I should be able to attack them.

Thanks again for the help.
 
Old 03-31-2005, 12:12 PM   #13
brookepb
LQ Newbie
 
Registered: Mar 2005
Posts: 9

Original Poster
Rep: Reputation: 0
In case anyone ends up on this thread due to the title, the read-only filesystem problem was almost certainly due to the rc.sysinit script which appears to intentionally do so for the sake of fsck program. This supposedly makes your system more stable following a crash. My version was having problems running the script because of some wrong location pointers in the script. Fixing these paths DID NOT give me a healthy machine but it did get me a bit further into the normal boot sequence and gave me a writeable root filesystem. If I had been able to get rpm to be able to set locks properly, I might have managed to get YUM to upgrade it into a healthy state. But I couldn't figure out why it claimed locks couldn't be set since it WAS actually writing them in the /var/lib/rpm directory.

I ended up deciding that it wasn't worth any more time and have gone back to doing a fresh install of Fedora 3 stable after dumping the important data off of the machine.
 
Old 03-31-2005, 12:39 PM   #14
mrGenixus
Member
 
Registered: Dec 2004
Location: Colorado, US
Distribution: gentoo, debian, ubuntu live gnome 2.10
Posts: 440

Rep: Reputation: 30
Thanks for letting us know..
 
Old 04-07-2005, 05:32 PM   #15
bfarago
LQ Newbie
 
Registered: Apr 2005
Location: Hungary, Budapest
Posts: 5

Rep: Reputation: 0
read-only root fs

Hi ,

I have the similar problem.
It is a FC3. I have /etc/init.d/functions file.
The 'hdparam /dev/hda' tells this is not a read-only disk.
The related /etc/fstab line has "default" option. So it means rw.
/etc/mtab file has only two line and it isn't the truth, but /proc/mounts looks like ok. So this two file isn't the same.
/var/log/dmesg is old one, but of course I can "mount /dev/hda1 -o remount,rw" than "dmesg >dmesg.log". Unfortunately, there is nothing.
No info in /var/log/message file about the error.
But, when the sytem boots up, It writes error to the screen only.
It is something like recovery needed on root partition. After check (no error found) tries to remount it automatically, but there is error :
I can stop it by [scroll lock]:

Remounting root filesystem in read-write mode: mount: LABEL=/ duplicate - not mounted

Setting up Logical Volume Management: 3 logical volumes in volume group...

mount: LABEL=/ duplicate - not mounted
...
Mounting local file systems: mount: none already mounted or /dev/pts busy
mount: none already mounted or /sys busy
...
rm: cannot remove '/tmp/.X11-unix': Read-only file system



has anyone some idea ?
Thanx a lot,
Barna.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Cannot read table of mounted filesystems: Input/output error k0ljat Linux - Software 1 09-18-2004 02:51 PM
cannot read table of mounted filesystems storto Linux From Scratch 4 08-16-2004 11:41 AM
mounted devices/ filesystems ergo_sum Linux - Newbie 4 11-01-2003 06:43 AM
HELP! mounted hard drive's read only system? Devboy Linux - Newbie 8 10-12-2003 08:39 AM
automounted filesystems should be mounted using nosuid ForumKid Linux - Security 2 01-09-2002 02:45 AM


All times are GMT -5. The time now is 12:50 AM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration