Partitionen springen in Read-Only

Dieses Thema im Forum "Web- & File-Services" wurde erstellt von LukeGee, 23.08.2008.

  1. #1 LukeGee, 23.08.2008
    LukeGee

    LukeGee Mitglied

    Dabei seit:
    02.03.2007
    Beiträge:
    28
    Zustimmungen:
    0
    Hallo,

    ich habe ein Problem: Ich hab einen Homeserver mit Samba laufen, über den einige Partitionen im Netzwerk verteilt werden.
    Grade eben wollte ich einige größeren Datenmengen rüberkopieren, als ein Fehler auftrit und die Partition auf read-only gesetzt wird. Hab schon neu gestartet und wieder probiert -> selbes problem.

    dmesg sagt folgendes:
    Code:
      PREFETCH window: disabled.
    PCI: Setting latency timer of device 0000:00:08.0 to 64
    PCI: Setting latency timer of device 0000:00:0b.0 to 64
    PCI: Setting latency timer of device 0000:00:0c.0 to 64
    PCI: Setting latency timer of device 0000:00:0d.0 to 64
    PCI: Setting latency timer of device 0000:00:0e.0 to 64
    PCI: Setting latency timer of device 0000:00:0f.0 to 64
    PCI: Setting latency timer of device 0000:00:10.0 to 64
    PCI: Setting latency timer of device 0000:00:11.0 to 64
    NET: Registered protocol family 2
    IP route cache hash table entries: 32768 (order: 5, 131072 bytes)
    TCP established hash table entries: 131072 (order: 8, 1048576 bytes)
    TCP bind hash table entries: 65536 (order: 7, 524288 bytes)
    TCP: Hash tables configured (established 131072 bind 65536)
    TCP reno registered
    NET: Registered protocol family 1
    Unpacking initramfs... done
    Freeing initrd memory: 671k freed
    apm: BIOS version 1.2 Flags 0x02 (Driver version 1.16ac)
    apm: overridden by ACPI.
    highmem bounce pool size: 64 pages
    VFS: Disk quotas dquot_6.5.1
    Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
    msgmni has been set to 1749
    Block layer SCSI generic (bsg) driver version 0.4 loaded (major 254)
    io scheduler noop registered
    io scheduler anticipatory registered
    io scheduler deadline registered
    io scheduler cfq registered (default)
    pci 0000:00:12.0: Boot video device
    PCI: Setting latency timer of device 0000:00:0b.0 to 64
    assign_interrupt_mode Found MSI capability
    Allocate Port Service[0000:00:0b.0:pcie00]
    Allocate Port Service[0000:00:0b.0:pcie03]
    PCI: Setting latency timer of device 0000:00:0c.0 to 64
    assign_interrupt_mode Found MSI capability
    Allocate Port Service[0000:00:0c.0:pcie00]
    Allocate Port Service[0000:00:0c.0:pcie03]
    PCI: Setting latency timer of device 0000:00:0d.0 to 64
    assign_interrupt_mode Found MSI capability
    Allocate Port Service[0000:00:0d.0:pcie00]
    Allocate Port Service[0000:00:0d.0:pcie03]
    PCI: Setting latency timer of device 0000:00:0e.0 to 64
    assign_interrupt_mode Found MSI capability
    Allocate Port Service[0000:00:0e.0:pcie00]
    Allocate Port Service[0000:00:0e.0:pcie03]
    PCI: Setting latency timer of device 0000:00:0f.0 to 64
    assign_interrupt_mode Found MSI capability
    Allocate Port Service[0000:00:0f.0:pcie00]
    Allocate Port Service[0000:00:0f.0:pcie03]
    PCI: Setting latency timer of device 0000:00:10.0 to 64
    assign_interrupt_mode Found MSI capability
    Allocate Port Service[0000:00:10.0:pcie00]
    Allocate Port Service[0000:00:10.0:pcie03]
    PCI: Setting latency timer of device 0000:00:11.0 to 64
    assign_interrupt_mode Found MSI capability
    Allocate Port Service[0000:00:11.0:pcie00]
    Allocate Port Service[0000:00:11.0:pcie03]
    isapnp: Scanning for PnP cards...
    isapnp: No Plug & Play device found
    Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing disabled
    serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
    00:09: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
    input: Macintosh mouse button emulation as /class/input/input0
    PNP: No PS/2 controller found. Probing ports directly.
    serio: i8042 KBD port at 0x60,0x64 irq 1
    serio: i8042 AUX port at 0x60,0x64 irq 12
    mice: PS/2 mouse device common for all mice
    cpuidle: using governor ladder
    cpuidle: using governor menu
    TCP cubic registered
    NET: Registered protocol family 17
    Using IPI No-Shortcut mode
    registered taskstats version 1
    Freeing unused kernel memory: 264k freed
    No dock devices found.
    SCSI subsystem initialized
    libata version 3.00 loaded.
    PCI: Setting latency timer of device 0000:00:06.0 to 64
    ACPI: PCI Interrupt Link [LSA0] enabled at IRQ 23
    ACPI: PCI Interrupt 0000:00:09.0[A] -> Link [LSA0] -> GSI 23 (level, low) -> IRQ 23
    PCI: Setting latency timer of device 0000:00:09.0 to 64
    ACPI: PCI interrupt for device 0000:00:09.0 disabled
    pata_amd 0000:00:06.0: version 0.3.10
    PCI: Setting latency timer of device 0000:00:06.0 to 64
    scsi0 : pata_amd
    scsi1 : pata_amd
    ata1: PATA max UDMA/133 cmd 0x1f0 ctl 0x3f6 bmdma 0xffa0 irq 14
    ata2: PATA max UDMA/133 cmd 0x170 ctl 0x376 bmdma 0xffa8 irq 15
    ata2: port disabled. ignoring.
    ahci 0000:00:09.0: version 3.0
    ACPI: PCI Interrupt 0000:00:09.0[A] -> Link [LSA0] -> GSI 23 (level, low) -> IRQ 23
    ahci 0000:00:09.0: AHCI 0001.0100 32 slots 4 ports 3 Gbps 0xf impl IDE mode
    ahci 0000:00:09.0: flags: 64bit ncq sntf led clo pmp pio
    PCI: Setting latency timer of device 0000:00:09.0 to 64
    scsi2 : ahci
    scsi3 : ahci
    scsi4 : ahci
    scsi5 : ahci
    ata3: SATA max UDMA/133 abar m8192@0xfd77a000 port 0xfd77a100 irq 23
    ata4: SATA max UDMA/133 abar m8192@0xfd77a000 port 0xfd77a180 irq 23
    ata5: SATA max UDMA/133 abar m8192@0xfd77a000 port 0xfd77a200 irq 23
    ata6: SATA max UDMA/133 abar m8192@0xfd77a000 port 0xfd77a280 irq 23
    ata3: SATA link down (SStatus 0 SControl 300)
    ata4: SATA link down (SStatus 0 SControl 300)
    ata5: SATA link down (SStatus 0 SControl 300)
    ata6: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
    ata6.00: ATA-8: WDC WD5000AACS-00D0B0, 01.01B01, max UDMA/133
    ata6.00: 976773168 sectors, multi 16: LBA48 NCQ (depth 31/32)
    ata6.00: configured for UDMA/133
    scsi 5:0:0:0: Direct-Access     ATA      WDC WD5000AACS-0 01.0 PQ: 0 ANSI: 5
    usbcore: registered new interface driver usbfs
    usbcore: registered new interface driver hub
    usbcore: registered new device driver usb
    ohci_hcd: 2006 August 04 USB 1.1 'Open' Host Controller (OHCI) Driver
    ACPI: PCI Interrupt Link [LUB0] enabled at IRQ 22
    ACPI: PCI Interrupt 0000:00:02.0[A] -> Link [LUB0] -> GSI 22 (level, low) -> IRQ 22
    PCI: Setting latency timer of device 0000:00:02.0 to 64
    ohci_hcd 0000:00:02.0: OHCI Host Controller
    ohci_hcd 0000:00:02.0: new USB bus registered, assigned bus number 1
    ohci_hcd 0000:00:02.0: irq 22, io mem 0xfd77f000
    usb usb1: configuration #1 chosen from 1 choice
    hub 1-0:1.0: USB hub found
    hub 1-0:1.0: 6 ports detected
    ACPI: PCI Interrupt Link [UB11] enabled at IRQ 21
    ACPI: PCI Interrupt 0000:00:04.0[A] -> Link [UB11] -> GSI 21 (level, low) -> IRQ 21
    PCI: Setting latency timer of device 0000:00:04.0 to 64
    ohci_hcd 0000:00:04.0: OHCI Host Controller
    ohci_hcd 0000:00:04.0: new USB bus registered, assigned bus number 2
    ohci_hcd 0000:00:04.0: irq 21, io mem 0xfd77d000
    usb usb2: configuration #1 chosen from 1 choice
    hub 2-0:1.0: USB hub found
    hub 2-0:1.0: 5 ports detected
    ACPI: PCI Interrupt Link [LUB2] enabled at IRQ 20
    ACPI: PCI Interrupt 0000:00:02.1[B] -> Link [LUB2] -> GSI 20 (level, low) -> IRQ 20
    PCI: Setting latency timer of device 0000:00:02.1 to 64
    ehci_hcd 0000:00:02.1: EHCI Host Controller
    ehci_hcd 0000:00:02.1: new USB bus registered, assigned bus number 3
    ehci_hcd 0000:00:02.1: debug port 1
    PCI: cache line size of 64 is not supported by device 0000:00:02.1
    ehci_hcd 0000:00:02.1: irq 20, io mem 0xfd77ec00
    ehci_hcd 0000:00:02.1: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004
    usb usb3: configuration #1 chosen from 1 choice
    hub 3-0:1.0: USB hub found
    hub 3-0:1.0: 6 ports detected
    ACPI: PCI Interrupt Link [UB12] enabled at IRQ 23
    ACPI: PCI Interrupt 0000:00:04.1[B] -> Link [UB12] -> GSI 23 (level, low) -> IRQ 23
    PCI: Setting latency timer of device 0000:00:04.1 to 64
    ehci_hcd 0000:00:04.1: EHCI Host Controller
    ehci_hcd 0000:00:04.1: new USB bus registered, assigned bus number 4
    ehci_hcd 0000:00:04.1: debug port 1
    PCI: cache line size of 64 is not supported by device 0000:00:04.1
    ehci_hcd 0000:00:04.1: irq 23, io mem 0xfd77e800
    ehci_hcd 0000:00:04.1: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004
    usb usb4: configuration #1 chosen from 1 choice
    hub 4-0:1.0: USB hub found
    hub 4-0:1.0: 5 ports detected
    Driver 'sd' needs updating - please use bus_type methods
    sd 5:0:0:0: [sda] 976773168 512-byte hardware sectors (500108 MB)
    sd 5:0:0:0: [sda] Write Protect is off
    sd 5:0:0:0: [sda] Mode Sense: 00 3a 00 00
    sd 5:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
    sd 5:0:0:0: [sda] 976773168 512-byte hardware sectors (500108 MB)
    sd 5:0:0:0: [sda] Write Protect is off
    sd 5:0:0:0: [sda] Mode Sense: 00 3a 00 00
    sd 5:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
     sda: sda1 sda2 sda3 < sda5 sda6 sda7 sda8 >
    sd 5:0:0:0: [sda] Attached SCSI disk
    kjournald starting.  Commit interval 5 seconds
    EXT3-fs: mounted filesystem with ordered data mode.
    rtc_cmos 00:07: rtc core: registered rtc_cmos as rtc0
    rtc0: alarms up to one year, y3k
    forcedeth: Reverse Engineered nForce ethernet driver. Version 0.61.
    ACPI: PCI Interrupt Link [LMAC] enabled at IRQ 22
    ACPI: PCI Interrupt 0000:00:0a.0[A] -> Link [LMAC] -> GSI 22 (level, low) -> IRQ 22
    PCI: Setting latency timer of device 0000:00:0a.0 to 64
    forcedeth 0000:00:0a.0: ifname eth0, PHY OUI 0x732 @ 1, addr 00:19:66:71:d7:e9
    forcedeth 0000:00:0a.0: highdma pwrctl mgmt timirq gbit lnktim msi desc-v3
    input: Power Button (FF) as /class/input/input1
    ACPI: Power Button (FF) [PWRF]
    input: Power Button (CM) as /class/input/input2
    ACPI: Power Button (CM) [PWRB]
    ACPI: ACPI0007:00 is registered as cooling_device0
    sd 5:0:0:0: Attached scsi generic sg0 type 0
    ACPI: WMI: Mapper loaded
    input: PC Speaker as /class/input/input3
    PPP generic driver version 2.4.2
    lp: driver loaded but no devices found
    ppdev: user-space parallel port driver
    parport_pc 00:05: reported by Plug and Play ACPI
    parport0: PC-style at 0x378 (0x778), irq 7, dma 3 [PCSPP,TRISTATE,COMPAT,ECP,DMA]
    lp0: using parport0 (interrupt-driven).
    EXT3 FS on sda1, internal journal
    kjournald starting.  Commit interval 5 seconds
    EXT3-fs warning (device sda5): ext3_clear_journal_err: Filesystem error recorded from previous mount: IO failure
    EXT3-fs warning (device sda5): ext3_clear_journal_err: Marking fs in need of filesystem check.
    EXT3-fs warning: mounting unchecked fs, running e2fsck is recommended
    EXT3 FS on sda5, internal journal
    EXT3-fs: recovery complete.
    EXT3-fs: mounted filesystem with ordered data mode.
    kjournald starting.  Commit interval 5 seconds
    EXT3-fs warning (device sda6): ext3_clear_journal_err: Filesystem error recorded from previous mount: IO failure
    EXT3-fs warning (device sda6): ext3_clear_journal_err: Marking fs in need of filesystem check.
    EXT3-fs warning: mounting unchecked fs, running e2fsck is recommended
    EXT3 FS on sda6, internal journal
    EXT3-fs: recovery complete.
    EXT3-fs: mounted filesystem with ordered data mode.
    kjournald starting.  Commit interval 5 seconds
    EXT3-fs warning: mounting unchecked fs, running e2fsck is recommended
    EXT3 FS on sda7, internal journal
    EXT3-fs: mounted filesystem with ordered data mode.
    kjournald starting.  Commit interval 5 seconds
    EXT3-fs warning: mounting unchecked fs, running e2fsck is recommended
    EXT3 FS on sda8, internal journal
    EXT3-fs: mounted filesystem with ordered data mode.
    Adding 3116600k swap on /dev/sda2.  Priority:-1 extents:1 across:3116600k
    w83627ehf: Found W83627EHG chip at 0x290
    warning: `smbd' uses 32-bit capabilities (legacy support in use)
    journal_bmap: journal block not found at offset 4108 on sda6
    Aborting journal on device sda6.
    EXT3-fs error (device sda6) in ext3_new_blocks: Journal has aborted
    __journal_remove_journal_head: freeing b_committed_data
    __journal_remove_journal_head: freeing b_committed_data
    ext3_abort called.
    EXT3-fs error (device sda6): ext3_journal_start_sb: Detected aborted journal
    Remounting filesystem read-only
    __journal_remove_journal_head: freeing b_frozen_data
    __journal_remove_journal_head: freeing b_frozen_data
    __journal_remove_journal_head: freeing b_committed_data
    __journal_remove_journal_head: freeing b_frozen_data
    
    
    Was soll ich machen? Ich bin grad am verzweifeln. Regt mich alleinschon wegen der Uptime auf, die nun futsch ist.
     
  2. Anzeige

    Schau dir mal diese Kategorie an. Dort findest du bestimmt etwas.
    Registrieren bzw. einloggen, um diese und auch andere Anzeigen zu deaktivieren
  3. Gast1

    Gast1 Guest

    Code:
    EXT3-fs warning: mounting unchecked fs, [B]running e2fsck is recommended[/B]
     
  4. #3 LukeGee, 24.08.2008
    Zuletzt bearbeitet: 24.08.2008
    LukeGee

    LukeGee Mitglied

    Dabei seit:
    02.03.2007
    Beiträge:
    28
    Zustimmungen:
    0
    Bin grade dabei...überall defektes Dateisystem. Anscheinend kann ers reparieren. Aber wie kanns dazu kommen?

    WTF, irgendwie scheinen alle partionen ein defektes dateisystem zu haben. Wie kann das passieren? Und btw: wie kann ich die root-partition reparieren? muss sie ja unmounten. Geht das einfach so?

    EDIT: HAT SICH ERLEDIGT: WAR EIN DUMMER LEICHTSSINNSFEHER MEINERSEITS.....(atm keine Zeit Details zu äußern)
    TRotzdem Danke für die Hilfe.
     
Thema:

Partitionen springen in Read-Only

Die Seite wird geladen...

Partitionen springen in Read-Only - Ähnliche Themen

  1. Upgrade Sles11 auf Sles12 findet Partitionen nicht

    Upgrade Sles11 auf Sles12 findet Partitionen nicht: Hallo zusammen, ich versuche gerade ein upgrade von Sles11 auf Sles12. Das ist auch durchgelaufen. Nach einem boot Versuch meldet das System es...
  2. Redhat 7 Installer zeigt keine vorhanenden Partitionen (SSD)

    Redhat 7 Installer zeigt keine vorhanenden Partitionen (SSD): Hallo zusammen, vielleicht kann mir hier einer helfen. Ich versuche Redhat Enterprise 7 auf einen Esprimo 720 zu installieren. Der Installer...
  3. Datei als image mit mehreren Partitionen: wie kann man diese formatieren?

    Datei als image mit mehreren Partitionen: wie kann man diese formatieren?: Hallo zusammen, wie ich (aus einem Script) eine Datei (img) erstelle und mehrere Partitionen darauf einrichte, ist mir bekannt - es funktioniert...
  4. Partitionen auf SD-Karte lassen sich nicht löschen

    Partitionen auf SD-Karte lassen sich nicht löschen: Hallo, aus meinem Handy stammt eine microSDHC-Karte (4GB), die jetzt einige Zeit nicht verwendet wurde. Ich wollte diese "platt" machen um sie...
  5. logische Partitionen erstellen LVM

    logische Partitionen erstellen LVM: Hallo, ich möchte logische Partionen erstellen. Ich hatte bisher nur primäre Partitionen eingerichtet. Leider kam ich durch Google auch nicht...