Anzeige:
Ergebnis 1 bis 12 von 12

Thema: usb-festplatten

  1. #1
    Registrierter Benutzer
    Registriert seit
    Feb 2004
    Beiträge
    12

    usb-festplatten

    hi!
    ich habe 2 usb-festplatten.
    seit ich sie im betrieb unter suse 9 mal abgeschaltet habe, kann ich nicht
    mehr darauf zugreifen.
    die geräte werden erkannt, ich kann sie aber nicht einbinden.
    fehlermeldung:

    "Laufwerk konnte nicht eingebunden werden.
    Die Fehlermeldung war:
    mount: Falscher Dateisystemtyp, ungültige Optionen, der
    »Superblock« von /dev/sda1 ist beschädigt oder es sind
    zu viele Dateisysteme eingehängt "

    bitte helft mir.
    außerdem möchte ich die usb-festplatten ja nicht immer mitlaufen lassen.

    m.f.g.
    w.freudenstein

  2. #2
    Registrierter Benutzer Avatar von ThorstenHirsch
    Registriert seit
    Nov 2002
    Beiträge
    6.431
    Was sagt dmesg wenn du die Platten einstöpselst?
    ¡Nuestro amigo... el Computador!

  3. #3
    Registrierter Benutzer
    Registriert seit
    Feb 2004
    Beiträge
    12
    hi.
    bin gerade von xp auf suse9 umgestiegen.
    ich weiß nicht, wie man dmesg einsehen kann.

  4. #4
    :) Hijacker Avatar von peschmae
    Registriert seit
    Mar 2002
    Ort
    Bern
    Beiträge
    2.681
    mit "dmesg" - das ist ein Konsolen-Programm. Konsole starten. dmesg [ENTER]

    Ich sehe zwei Möglichkeiten:

    1) Du hattest die Platten vorher nicht korrekt geumountet - das Dateisystem ist wohl (ein bisschen) beschädigt oder tut zumindest so.
    2) Die Festplatte hat eine andere Device verpasst gekriegt - hängt jetzt also z. B. statt an /dev/sda1 an /dev/sdb1 oder so. (Deshalb dmesg, das solltest du dort dann sehen - neben jeder Menge anderer Informationen)

    MfG Peschmä
    Debian Sid User

  5. #5
    Registrierter Benutzer
    Registriert seit
    Feb 2004
    Beiträge
    12
    ok.
    wolfgang@linux:~> dmesg
    786368k available (1727k kernel code, 12656k reserved, 605k data, 176k init, 0k highmem)
    Dentry cache hash table entries: 131072 (order: 8, 1048576 bytes)
    Inode cache hash table entries: 65536 (order: 7, 524288 bytes)
    Mount cache hash table entries: 512 (order: 0, 4096 bytes)
    Buffer-cache hash table entries: 65536 (order: 6, 262144 bytes)
    Page-cache hash table entries: 262144 (order: 8, 1048576 bytes)
    CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
    CPU: L2 Cache: 256K (64 bytes/line)
    Intel machine check architecture supported.
    Intel machine check reporting enabled on CPU#0.
    CPU: After generic, caps: 0383fbff c1c3fbff 00000000 00000000
    CPU: Common caps: 0383fbff c1c3fbff 00000000 00000000
    CPU: AMD Athlon(tm) XP 2600+ stepping 01
    Enabling fast FPU save and restore... done.
    Enabling unmasked SIMD FPU exception support... done.
    Checking 'hlt' instruction... OK.
    POSIX conformance testing by UNIFIX
    mtrr: v1.40 (20010327) Richard Gooch (rgooch@atnf.csiro.au)
    mtrr: detected mtrr type: Intel
    ACPI: Subsystem revision 20030619
    PCI: PCI BIOS revision 2.10 entry at 0xf9b00, last bus=1
    PCI: Using configuration type 1
    Looking for DSDT in initrd ... not found!
    ACPI: Interpreter enabled
    ACPI: Using PIC for interrupt routing
    ACPI: System [ACPI] (supports S0 S3 S4 S5)
    ACPI: PCI Root Bridge [PCI0] (00:00)
    PCI: Probing PCI hardware (bus 00)
    ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
    ACPI: PCI Interrupt Link [LNKA] (IRQs 1 3 4 5 6 7 *10 11 12 14 15)
    ACPI: PCI Interrupt Link [LNKB] (IRQs 1 3 4 5 6 7 10 *11 12 14 15)
    ACPI: PCI Interrupt Link [LNKC] (IRQs 1 3 4 5 6 7 10 *11 12 14 15)
    ACPI: PCI Interrupt Link [LNKD] (IRQs 1 3 4 *5 6 7 10 11 12 14 15)
    ACPI: PCI Interrupt Link [ALKA] (IRQs 20)
    ACPI: PCI Interrupt Link [ALKB] (IRQs 21)
    ACPI: PCI Interrupt Link [ALKC] (IRQs 22)
    ACPI: PCI Interrupt Link [ALKD] (IRQs 23)
    PCI: Probing PCI hardware
    ACPI: PCI Interrupt Link [LNKB] enabled at IRQ 11
    00:00:09[A] -> IRQ 11 Mode 1 Trigger 1
    ACPI: PCI Interrupt Link [LNKC] enabled at IRQ 11
    PIC: IRQ (11) already programmed
    ACPI: PCI Interrupt Link [LNKD] enabled at IRQ 5
    00:00:09[C] -> IRQ 5 Mode 1 Trigger 1
    ACPI: PCI Interrupt Link [LNKA] enabled at IRQ 10
    00:00:09[D] -> IRQ 10 Mode 1 Trigger 1


    wenn ich mir mit dem partitionsprogramm von yast die festplatten anschaue,
    verändert sich auch der mountpoint bei jedem aus/einstecken. statt data2 und
    data3 steht dann nur ein stern drin.

  6. #6
    Registrierter Benutzer
    Registriert seit
    Feb 2004
    Beiträge
    12
    wolfgang@linux:~> dmesg
    Common caps: 0383fbff c1c3fbff 00000000 00000000
    CPU: AMD Athlon(tm) XP 2600+ stepping 01
    Enabling fast FPU save and restore... done.
    Enabling unmasked SIMD FPU exception support... done.
    Checking 'hlt' instruction... OK.
    POSIX conformance testing by UNIFIX
    mtrr: v1.40 (20010327) Richard Gooch (rgooch@atnf.csiro.au)
    mtrr: detected mtrr type: Intel
    ACPI: Subsystem revision 20030619
    PCI: PCI BIOS revision 2.10 entry at 0xf9b00, last bus=1
    PCI: Using configuration type 1
    Looking for DSDT in initrd ... not found!
    ACPI: Interpreter enabled
    ACPI: Using PIC for interrupt routing
    ACPI: System [ACPI] (supports S0 S3 S4 S5)
    ACPI: PCI Root Bridge [PCI0] (00:00)
    PCI: Probing PCI hardware (bus 00)
    ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
    ACPI: PCI Interrupt Link [LNKA] (IRQs 1 3 4 5 6 7 *10 11 12 14 15)
    ACPI: PCI Interrupt Link [LNKB] (IRQs 1 3 4 5 6 7 10 *11 12 14 15)
    ACPI: PCI Interrupt Link [LNKC] (IRQs 1 3 4 5 6 7 10 *11 12 14 15)
    ACPI: PCI Interrupt Link [LNKD] (IRQs 1 3 4 *5 6 7 10 11 12 14 15)
    ACPI: PCI Interrupt Link [ALKA] (IRQs 20)
    ACPI: PCI Interrupt Link [ALKB] (IRQs 21)
    ACPI: PCI Interrupt Link [ALKC] (IRQs 22)
    ACPI: PCI Interrupt Link [ALKD] (IRQs 23)
    PCI: Probing PCI hardware
    ACPI: PCI Interrupt Link [LNKB] enabled at IRQ 11
    00:00:09[A] -> IRQ 11 Mode 1 Trigger 1
    ACPI: PCI Interrupt Link [LNKC] enabled at IRQ 11
    PIC: IRQ (11) already programmed
    ACPI: PCI Interrupt Link [LNKD] enabled at IRQ 5
    00:00:09[C] -> IRQ 5 Mode 1 Trigger 1
    ACPI: PCI Interrupt Link [LNKA] enabled at IRQ 10
    00:00:09[D] -> IRQ 10 Mode 1 Trigger 1
    PIC: IRQ (11) already programmed
    PIC: IRQ (5) already programmed
    PIC: IRQ (10) already programmed
    PIC: IRQ (11) already programmed
    PIC: IRQ (5) already programmed
    PIC: IRQ (10) already programmed
    PIC: IRQ (11) already programmed
    PIC: IRQ (11) already programmed
    PIC: IRQ (10) already programmed
    PIC: IRQ (11) already programmed
    PIC: IRQ (11) already programmed
    PIC: IRQ (5) already programmed
    PIC: IRQ (11) already programmed
    PIC: IRQ (11) already programmed
    PIC: IRQ (5) already programmed
    PIC: IRQ (10) already programmed
    PIC: IRQ (11) already programmed
    PIC: IRQ (5) already programmed
    PIC: IRQ (10) already programmed
    PIC: IRQ (11) already programmed
    PIC: IRQ (10) already programmed
    PIC: IRQ (11) already programmed
    PIC: IRQ (11) already programmed
    PIC: IRQ (5) already programmed
    PIC: IRQ (10) already programmed
    PIC: IRQ (11) already programmed
    PIC: IRQ (11) already programmed
    PIC: IRQ (5) already programmed
    PIC: IRQ (10) already programmed
    PIC: IRQ (11) already programmed
    PIC: IRQ (11) already programmed
    PIC: IRQ (5) already programmed
    PIC: IRQ (10) already programmed
    PIC: IRQ (11) already programmed
    PIC: IRQ (11) already programmed
    PIC: IRQ (5) already programmed
    PCI: Using ACPI for IRQ routing
    PCI: if you experience problems, try using option 'pci=noacpi' or even 'acpi=off'
    Linux NET4.0 for Linux 2.4
    Based upon Swansea University Computer Society NET3.039
    Initializing RT netlink socket
    apm: BIOS version 1.2 Flags 0x07 (Driver version 1.16)
    apm: overridden by ACPI.
    Starting kswapd
    bigpage subsystem: allocated 0 bigpages (=0MB).
    kinoded started
    VFS: Disk quotas vdquot_6.5.1
    aio_setup: num_physpages = 49148
    aio_setup: sizeof(struct page) = 48
    vesafb: framebuffer at 0xd8000000, mapped to 0xf0817000, size 65536k
    vesafb: mode is 1280x1024x16, linelength=2560, pages=24
    vesafb: protected mode interface info at c000:569e
    vesafb: scrolling: redraw
    vesafb: directcolor: size=0:5:6:5, shift=0:11:5:0
    bootsplash 3.0.9-2003/09/08: looking for picture.... silenjpeg size 30981 bytes, found (1280x1024, 15663 bytes, v3).
    bootsplash: silent jpeg found.
    bootsplash: silent jpeg found.
    Console: switching to colour frame buffer device 148x51
    fb0: VESA VGA frame buffer device
    pty: 256 Unix98 ptys configured
    Serial driver version 5.05c (2001-07-08) with HUB-6 MANY_PORTS MULTIPORT SHARE_IRQ SERIAL_PCI enabled
    ttyS00 at 0x03f8 (irq = 4) is a 16550A
    ttyS01 at 0x02f8 (irq = 3) is a 16550A
    Real Time Clock Driver v1.10e
    Floppy drive(s): fd0 is 1.44M
    FDC 0 is a post-1991 82077
    RAMDISK driver initialized: 16 RAM disks of 64000K size 1024 blocksize
    loop: loaded (max 16 devices)
    Uniform Multi-Platform E-IDE driver Revision: 7.00beta4-2.4
    ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
    VP_IDE: IDE controller at PCI slot 00:11.1
    VP_IDE: chipset revision 6
    VP_IDE: not 100% native mode: will probe irqs later
    VP_IDE: VIA vt8235 (rev 00) IDE UDMA133 controller on pci00:11.1
    ide0: BM-DMA at 0xe000-0xe007, BIOS settings: hdaMA, hdbMA
    ide1: BM-DMA at 0xe008-0xe00f, BIOS settings: hdcMA, hddMA
    hda: ST380023A, ATA DISK drive
    hdb: SAMSUNG SV1604N, ATA DISK drive
    blk: queue c03e66c0, I/O limit 4095Mb (mask 0xffffffff)
    blk: queue c03e681c, I/O limit 4095Mb (mask 0xffffffff)
    hdc: JLMS DVD-ROM LTD-166S, ATAPI CD/DVD-ROM drive
    hdd: LITE-ON LTR-48246S, ATAPI CD/DVD-ROM drive
    ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
    ide1 at 0x170-0x177,0x376 on irq 15
    hda: attached ide-disk driver.
    hda: host protected area => 1
    hda: 156301488 sectors (80026 MB) w/2048KiB Cache, CHS=9729/255/63, UDMA(100)
    hdb: attached ide-disk driver.
    hdb: host protected area => 1
    hdb: 312581807 sectors (160042 MB) w/2048KiB Cache, CHS=19457/255/63, UDMA(100)
    ide-floppy driver 0.99.newide
    Partition check:
    hda: hda1 hda2
    hdb: hdb1 < hdb5 >
    ide-floppy driver 0.99.newide
    md: md driver 0.90.0 MAX_MD_DEVS=256, MD_SB_DISKS=27
    md: Autodetecting RAID arrays.
    md: autorun ...
    md: ... autorun DONE.
    NET4: Linux TCP/IP 1.0 for NET4.0
    IP Protocols: ICMP, UDP, TCP, IGMP
    IP: routing cache hash table of 8192 buckets, 64Kbytes
    TCP: Hash tables configured (established 262144 bind 65536)
    Linux IP multicast router 0.06 plus PIM-SM
    NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
    cryptoapi: loaded
    RAMDISK: Compressed image found at block 0
    Freeing initrd memory: 292k freed
    VFS: Mounted root (ext2 filesystem).
    reiserfs: found format "3.6" with standard journal
    reiserfs: enabling write barrier flush mode
    reiserfs: using ordered data mode
    reiserfs: checking transaction log (device ide0(3,2)) ...
    for (ide0(3,2))
    Using r5 hash to sort names
    VFS: Mounted root (reiserfs filesystem) readonly.
    Trying to move old root to /initrd ... failed
    Unmounting old root
    Trying to free ramdisk memory ... okay
    Freeing unused kernel memory: 176k freed
    md: Autodetecting RAID arrays.
    md: autorun ...
    md: ... autorun DONE.
    reiserfs: enabling write barrier flush mode
    lvm-mp: allocating 42 lowmem entries at c295e000
    LVM version 1.0.5+(mp-v6c)(22/07/2002) module loaded
    reiserfs: enabling write barrier flush mode
    Adding Swap: 1052216k swap-space (priority 42)
    reiserfs: enabling write barrier flush mode
    reiserfs: enabling write barrier flush mode
    SCSI subsystem driver Revision: 1.00
    hdc: attached ide-cdrom driver.
    hdc: ATAPI 48X DVD-ROM drive, 512kB Cache
    Uniform CD-ROM driver Revision: 3.12
    hdd: attached ide-scsi driver.
    scsi0 : SCSI host adapter emulation for IDE ATAPI devices
    Vendor: LITE-ON Model: LTR-48246S Rev: SID4
    Type: CD-ROM ANSI SCSI revision: 02
    8139too Fast Ethernet driver 0.9.26
    eth0: RealTek RTL8139 Fast Ethernet at 0xf48d8000, 00:50:22:b0:34:eb, IRQ 10
    eth0: Identified 8139 chip type 'RTL-8139C'
    eth1: RealTek RTL8139 Fast Ethernet at 0xf48da000, 00:20:ed:b5:9e:f5, IRQ 11
    eth1: Identified 8139 chip type 'RTL-8139C'
    eth0: Setting half-duplex based on auto-negotiated partner ability 0000.
    raw1394: /dev/raw1394 device initialized
    usb.c: registered new driver usbdevfs
    usb.c: registered new driver hub
    ehci_hcd 00:0a.3: ALi Corporation. [ALi] USB 2.0 Controller
    ehci_hcd 00:0a.3: irq 11, pci mem f48dc000
    usb.c: new USB bus registered, assigned bus number 1
    PCI: 00:0a.3 PCI cache line size set incorrectly (32 bytes) by BIOS/FW.
    PCI: 00:0a.3 PCI cache line size corrected to 64.
    ehci_hcd 00:0a.3: USB 2.0 enabled, EHCI 1.00, driver 2003-Jun-19/2.4
    hub.c: USB hub found
    hub.c: 6 ports detected
    ehci_hcd 00:10.3: VIA Technologies, Inc. USB 2.0
    ehci_hcd 00:10.3: irq 5, pci mem f48de000
    usb.c: new USB bus registered, assigned bus number 2
    PCI: 00:10.3 PCI cache line size set incorrectly (32 bytes) by BIOS/FW.
    PCI: 00:10.3 PCI cache line size corrected to 64.
    ehci_hcd 00:10.3: USB 2.0 enabled, EHCI 1.00, driver 2003-Jun-19/2.4
    hub.c: USB hub found
    hub.c: 6 ports detected
    usb-uhci.c: $Revision: 1.275 $ time 19:01:30 Dec 18 2003
    usb-uhci.c: High bandwidth mode enabled
    usb-uhci.c: USB UHCI at I/O 0xd400, IRQ 10
    usb-uhci.c: Detected 2 ports
    usb.c: new USB bus registered, assigned bus number 3
    hub.c: USB hub found
    hub.c: 2 ports detected
    usb-uhci.c: USB UHCI at I/O 0xd800, IRQ 11
    usb-uhci.c: Detected 2 ports
    usb.c: new USB bus registered, assigned bus number 4
    hub.c: USB hub found
    hub.c: 2 ports detected
    usb-uhci.c: USB UHCI at I/O 0xdc00, IRQ 11
    usb-uhci.c: Detected 2 ports
    usb.c: new USB bus registered, assigned bus number 5
    hub.c: USB hub found
    hub.c: 2 ports detected
    usb-uhci.c: v1.275:USB Universal Host Controller Interface driver
    uhci.c: USB Universal Host Controller Interface driver v1.1
    usb-ohci.c: USB OHCI at membase 0xf48e0000, IRQ 5
    usb-ohci.c: usb-00:0a.0, ALi Corporation. [ALi] USB 1.1 Controller
    usb.c: new USB bus registered, assigned bus number 6
    hub.c: USB hub found
    hub.c: 2 ports detected
    usb-ohci.c: USB OHCI at membase 0xf48e2000, IRQ 10
    usb-ohci.c: usb-00:0a.1, ALi Corporation. [ALi] USB 1.1 Controller (#2)
    usb.c: new USB bus registered, assigned bus number 7
    hub.c: USB hub found
    hub.c: 2 ports detected
    usb-ohci.c: USB OHCI at membase 0xf48e4000, IRQ 11
    usb-ohci.c: usb-00:0a.2, ALi Corporation. [ALi] USB 1.1 Controller (#3)
    usb.c: new USB bus registered, assigned bus number 8
    hub.c: USB hub found
    hub.c: 2 ports detected
    mice: PS/2 mouse device common for all mice
    hub.c: new USB device 00:10.3-3, assigned address 2
    usb.c: USB device 2 (vend/prod 0xd49/0x5000) is not claimed by any active driver.
    hub.c: new USB device 00:10.3-4, assigned address 3
    usb.c: USB device 3 (vend/prod 0xd49/0x5000) is not claimed by any active driver.
    hub.c: new USB device 00:10.0-2, assigned address 2
    hub.c: USB hub found
    hub.c: 7 ports detected
    hub.c: new USB device 00:10.0-2.2, assigned address 3
    usb.c: USB device 3 (vend/prod 0x46d/0xc00e) is not claimed by any active driver.
    Attached scsi CD-ROM sr0 at scsi0, channel 0, id 0, lun 0
    sr0: scsi3-mmc drive: 32x/48x writer cd/rw xa/form2 cdda tray
    ACPI: Power Button (FF) [PWRF]
    ACPI: Sleep Button (CM) [SLPB]
    ACPI: Processor [CPU0] (supports C1 C2, 2 throttling states)
    via82xx: Assuming DXS channels with 48k fixed sample rate.
    Please try dxs_support=1 option and report if it works on your machine.
    PCI: Setting latency timer of device 00:11.5 to 64
    IPsec Security Association Database (SADB): initialized.
    IPsec Security Policy Database (SPD): initialized.
    IPsec PF_KEY V2: initialized
    IPv6 v0.8 (usagi-cvs/IPsec6 based StS) for NET4.0
    IPv6 over IPv4 tunneling driver
    bootsplash: silent jpeg found.
    parport0: PC-style at 0x378 [PCSPP,TRISTATE,EPP]
    lp0: using parport0 (polling).
    isapnp: Scanning for PnP cards...
    isapnp: No Plug & Play device found
    usb.c: registered new driver serial
    usbserial.c: USB Serial support registered for Generic
    usbserial.c: USB Serial Driver core v1.4
    Linux agpgart interface v0.99 (c) Jeff Hartmann
    agpgart: Maximum main memory to use for agp memory: 690M
    agpgart: Detected Via KT400/KT400A/KT600 chipset
    agpgart: AGP aperture is 128M @ 0xd0000000
    [drm] AGP 0.99 aperture @ 0xd0000000 128MB
    [drm] Initialized radeon 1.7.0 20020828 on minor 0
    agpgart: Device is in legacy mode, falling back to 2.x
    agpgart: Putting AGP V2 device at 00:00.0 into 1x mode
    agpgart: Putting AGP V2 device at 01:00.0 into 1x mode
    Linux video capture interface: v1.00
    [drm] Loading R200 Microcode
    eth0: no IPv6 routers present
    Initializing USB Mass Storage driver...
    usb.c: registered new driver usb-storage
    scsi1 : SCSI emulation for USB Mass Storage devices
    Vendor: Maxtor Model: 5000XT v01.00.00 Rev: 0100
    Type: Direct-Access ANSI SCSI revision: 02
    Attached scsi disk sda at scsi1, channel 0, id 0, lun 0
    SCSI device sda: 490232832 512-byte hdwr sectors (250999 MB)
    sda: sda1
    WARNING: USB Mass Storage data integrity not assured
    USB Mass Storage device found at 2
    scsi2 : SCSI emulation for USB Mass Storage devices
    Vendor: Maxtor Model: 5000XT v01.00.00 Rev: 0100
    Type: Direct-Access ANSI SCSI revision: 02
    Attached scsi disk sdb at scsi2, channel 0, id 0, lun 0
    SCSI device sdb: 490232832 512-byte hdwr sectors (250999 MB)
    sdb: sdb1
    WARNING: USB Mass Storage data integrity not assured
    USB Mass Storage device found at 3
    USB Mass Storage support registered.
    spurious 8259A interrupt: IRQ7.
    usb.c: registered new driver hiddev
    usb.c: registered new driver hid
    input: USB HID v1.10 Mouse [Logitech USB-PS/2 Optical Mouse] on usb3:3.0
    hid-core.c: v1.8.1 Andreas Gal, Vojtech Pavlik <vojtech@suse.cz>
    hid-core.c: USB HID support drivers
    reiserfs: found format "3.6" with standard journal
    Filesystem on 08:01 cannot be mounted because it is bigger than the device
    You may need to run fsck or increase size of your LVM partition
    Or may be you forgot to reboot after fdisk when it told you to
    reiserfs: found format "3.6" with standard journal
    Filesystem on 08:01 cannot be mounted because it is bigger than the device
    You may need to run fsck or increase size of your LVM partition
    Or may be you forgot to reboot after fdisk when it told you to
    reiserfs: found format "3.6" with standard journal
    CSLIP: code copyright 1989 Regents of the University of California
    PPP generic driver version 2.4.2
    reiserfs: enabling write barrier flush mode
    reiserfs: using ordered data mode
    reiserfs: checking transaction log (device ide0(3,69)) ...
    for (ide0(3,69))
    Using r5 hash to sort names
    reiserfs: found format "3.6" with standard journal
    reiserfs: enabling write barrier flush mode
    reiserfs: using ordered data mode
    reiserfs: checking transaction log (device sd(8,17)) ...
    for (sd(8,17))
    is_tree_node: node level 4198 does not match to the expected one 4
    vs-5150: search_by_key: invalid format found in block 26966934. Fsck?
    vs-13070: reiserfs_read_inode2: i/o failure occurred trying to find stat data of [1 2 0x0 SD]
    Using r5 hash to sort names
    is_tree_node: node level 4198 does not match to the expected one 4
    vs-5150: search_by_key: invalid format found in block 26966934. Fsck?
    zam-7001: io error in reiserfs_find_entry
    reiserfs: xattrs/ACLS enabled and couldn't find/create .reiserfs_priv. Failing mount.
    agpgart: Device is in legacy mode, falling back to 2.x
    agpgart: Putting AGP V2 device at 00:00.0 into 1x mode
    agpgart: Putting AGP V2 device at 01:00.0 into 1x mode
    [drm] Loading R200 Microcode
    usb.c: USB disconnect on device 00:10.3-3 address 2
    usb.c: USB disconnect on device 00:10.3-4 address 3
    Device 08:00 not ready.
    I/O error: dev 08:00, sector 0
    Device 08:10 not ready.
    I/O error: dev 08:10, sector 0
    hub.c: connect-debounce failed, port 3 disabled
    Device 08:00 not ready.
    I/O error: dev 08:00, sector 0
    Device 08:10 not ready.
    I/O error: dev 08:10, sector 0
    hub.c: new USB device 00:10.3-4, assigned address 4
    WARNING: USB Mass Storage data integrity not assured
    USB Mass Storage device found at 4
    hub.c: new USB device 00:10.3-3, assigned address 5
    WARNING: USB Mass Storage data integrity not assured
    USB Mass Storage device found at 5
    wolfgang@linux:~> wolfgang@linux:~> dmesg
    bash: wolfgang@linux:~: command not found
    wolfgang@linux:~> 786368k available (1727k kernel code, 12656k reserved, 605k data, 176k init, 0k highmem)
    bash: syntax error near unexpected token `('
    wolfgang@linux:~> Dentry cache hash table entries: 131072 (order: 8, 1048576 bytes)
    bash: syntax error near unexpected token `('
    wolfgang@linux:~> Inode cache hash table entries: 65536 (order: 7, 524288 bytes)bash: syntax error near unexpected token `('
    wolfgang@linux:~> Mount cache hash table entries: 512 (order: 0, 4096 bytes)
    bash: syntax error near unexpected token `('
    wolfgang@linux:~> Buffer-cache hash table entries: 65536 (order: 6, 262144 bytes)
    bash: syntax error near unexpected token `('
    wolfgang@linux:~> Page-cache hash table entries: 262144 (order: 8, 1048576 bytes)
    bash: syntax error near unexpected token `('
    wolfgang@linux:~> CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
    bash: syntax error near unexpected token `('
    wolfgang@linux:~> CPU: L2 Cache: 256K (64 bytes/line)
    bash: syntax error near unexpected token `('
    wolfgang@linux:~> Intel machine check architecture supported.
    bash: Intel: command not found
    wolfgang@linux:~> Intel machine check reporting enabled on CPU#0.
    bash: Intel: command not found
    wolfgang@linux:~> CPU: After generic, caps: 0383fbff c1c3fbff 00000000 00000000
    bash: CPU:: command not found
    wolfgang@linux:~> CPU: Common caps: 0383fbff c1c3fbff 00000000 00000000
    bash: CPU:: command not found
    wolfgang@linux:~> CPU: AMD Athlon(tm) XP 2600+ stepping 01
    bash: syntax error near unexpected token `('
    wolfgang@linux:~> Enabling fast FPU save and restore... done.
    bash: Enabling: command not found
    wolfgang@linux:~> Enabling unmasked SIMD FPU exception support... done.
    bash: Enabling: command not found
    wolfgang@linux:~> Checking 'hlt' instruction... OK.
    bash: Checking: command not found
    wolfgang@linux:~> POSIX conformance testing by UNIFIX
    bash: POSIX: command not found
    wolfgang@linux:~> mtrr: v1.40 (20010327) Richard Gooch (rgooch@atnf.csiro.au)
    bash: syntax error near unexpected token `('
    wolfgang@linux:~> mtrr: detected mtrr type: Intel
    bash: mtrr:: command not found
    wolfgang@linux:~> ACPI: Subsystem revision 20030619
    bash: ACPI:: command not found
    wolfgang@linux:~> PCI: PCI BIOS revision 2.10 entry at 0xf9b00, last bus=1
    bash: PCI:: command not found
    wolfgang@linux:~> PCI: Using configuration type 1
    bash: PCI:: command not found
    wolfgang@linux:~> Looking for DSDT in initrd ... not found!
    bash: Looking: command not found
    wolfgang@linux:~> ACPI: Interpreter enabled
    bash: ACPI:: command not found
    wolfgang@linux:~> ACPI: Using PIC for interrupt routing
    bash: ACPI:: command not found
    wolfgang@linux:~> ACPI: System [ACPI] (supports S0 S3 S4 S5)
    bash: syntax error near unexpected token `('
    wolfgang@linux:~> ACPI: PCI Root Bridge [PCI0] (00:00)
    bash: syntax error near unexpected token `('
    wolfgang@linux:~> PCI: Probing PCI hardware (bus 00)
    bash: syntax error near unexpected token `('
    wolfgang@linux:~> ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
    bash: ACPI:: command not found
    wolfgang@linux:~> ACPI: PCI Interrupt Link [LNKA] (IRQs 1 3 4 5 6 7 *10 11 12 14 15)
    bash: syntax error near unexpected token `('
    wolfgang@linux:~> ACPI: PCI Interrupt Link [LNKB] (IRQs 1 3 4 5 6 7 10 *11 12 14 15)
    bash: syntax error near unexpected token `('
    wolfgang@linux:~> ACPI: PCI Interrupt Link [LNKC] (IRQs 1 3 4 5 6 7 10 *11 12 14 15)
    bash: syntax error near unexpected token `('
    wolfgang@linux:~> ACPI: PCI Interrupt Link [LNKD] (IRQs 1 3 4 *5 6 7 10 11 12 14 15)
    bash: syntax error near unexpected token `('
    wolfgang@linux:~> ACPI: PCI Interrupt Link [ALKA] (IRQs 20)
    bash: syntax error near unexpected token `('
    wolfgang@linux:~> ACPI: PCI Interrupt Link [ALKB] (IRQs 21)
    bash: syntax error near unexpected token `('
    wolfgang@linux:~> ACPI: PCI Interrupt Link [ALKC] (IRQs 22)
    bash: syntax error near unexpected token `('
    wolfgang@linux:~> ACPI: PCI Interrupt Link [ALKD] (IRQs 23)
    bash: syntax error near unexpected token `('
    wolfgang@linux:~> PCI: Probing PCI hardware
    bash: PCI:: command not found
    wolfgang@linux:~> ACPI: PCI Interrupt Link [LNKB] enabled at IRQ 11
    bash: ACPI:: command not found
    wolfgang@linux:~> 00:00:09[A] -> IRQ 11 Mode 1 Trigger 1
    bash: 00:00:09[A]: command not found
    wolfgang@linux:~> ACPI: PCI Interrupt Link [LNKC] enabled at IRQ 11
    bash: ACPI:: command not found
    wolfgang@linux:~> PIC: IRQ (11) already programmed
    bash: syntax error near unexpected token `('
    wolfgang@linux:~> ACPI: PCI Interrupt Link [LNKD] enabled at IRQ 5
    bash: ACPI:: command not found
    wolfgang@linux:~> 00:00:09[C] -> IRQ 5 Mode 1 Trigger 1
    bash: 00:00:09[C]: command not found
    wolfgang@linux:~> ACPI: PCI Interrupt Link [LNKA] enabled at IRQ 10
    bash: ACPI:: command not found
    wolfgang@linux:~> 00:00:09[D] -> IRQ 10 Mode 1 Trigger 1
    bash: 00:00:09[D]: command not found
    wolfgang@linux:~> PIC: IRQ (11) already programmed
    bash: syntax error near unexpected token `('
    wolfgang@linux:~> PIC: IRQ (5) already programmed
    bash: syntax error near unexpected token `('
    wolfgang@linux:~> PIC: IRQ (10) already programmed
    bash: syntax error near unexpected token `('
    wolfgang@linux:~> PIC: IRQ (11) already programmed
    bash: syntax error near unexpected token `('
    wolfgang@linux:~> PIC: IRQ (5) already programmed
    bash: syntax error near unexpected token `('
    wolfgang@linux:~> PIC: IRQ (10) already programmed
    bash: syntax error near unexpected token `('
    wolfgang@linux:~> PIC: IRQ (11) already programmed
    bash: syntax error near unexpected token `('
    wolfgang@linux:~> PIC: IRQ (11) already programmed
    bash: syntax error near unexpected token `('
    wolfgang@linux:~> PIC: IRQ (10) already programmed
    bash: syntax error near unexpected token `('
    wolfgang@linux:~> PIC: IRQ (11) already programmed
    bash: syntax error near unexpected token `('
    wolfgang@linux:~> PIC: IRQ (11) already programmed
    bash: syntax error near unexpected token `('
    wolfgang@linux:~> PIC: IRQ (5) already programmed
    bash: syntax error near unexpected token `('
    wolfgang@linux:~> PIC: IRQ (11) already programmed
    bash: syntax error near unexpected token `('
    wolfgang@linux:~> PIC: IRQ (11) already programmed
    bash: syntax error near unexpected token `('
    wolfgang@linux:~> PIC: IRQ (5) already programmed
    bash: syntax error near unexpected token `('
    wolfgang@linux:~> PIC: IRQ (10) already programmed
    bash: syntax error near unexpected token `('
    wolfgang@linux:~> PIC: IRQ (11) already programmed
    bash: syntax error near unexpected token `('
    wolfgang@linux:~> PIC: IRQ (5) already programmed
    bash: syntax error near unexpected token `('
    wolfgang@linux:~> PIC: IRQ (10) already programmed
    bash: syntax error near unexpected token `('
    wolfgang@linux:~> PIC: IRQ (11) already programmed
    bash: syntax error near unexpected token `('
    wolfgang@linux:~> PIC: IRQ (10) already programmed
    bash: syntax error near unexpected token `('
    wolfgang@linux:~> PIC: IRQ (11) already programmed
    bash: syntax error near unexpected token `('
    wolfgang@linux:~> PIC: IRQ (11) already programmed
    bash: syntax error near unexpected token `('
    wolfgang@linux:~> PIC: IRQ (5) already programmed
    bash: syntax error near unexpected token `('
    wolfgang@linux:~> PIC: IRQ (10) already programmed
    bash: syntax error near unexpected token `('
    wolfgang@linux:~> PIC: IRQ (11) already programmed
    bash: syntax error near unexpected token `('
    wolfgang@linux:~> PIC: IRQ (11) already programmed
    bash: syntax error near unexpected token `('
    wolfgang@linux:~> PIC: IRQ (5) already programmed
    bash: syntax error near unexpected token `('
    wolfgang@linux:~> PIC: IRQ (10) already programmed
    bash: syntax error near unexpected token `('
    wolfgang@linux:~> PIC: IRQ (11) already programmed
    bash: syntax error near unexpected token `('
    wolfgang@linux:~> PIC: IRQ (11) already programmed
    bash: syntax error near unexpected token `('
    wolfgang@linux:~> PIC: IRQ (5) already programmed
    bash: syntax error near unexpected token `('
    wolfgang@linux:~> PIC: IRQ (10) already programmed
    bash: syntax error near unexpected token `('
    wolfgang@linux:~> PIC: IRQ (11) already programmed
    bash: syntax error near unexpected token `('
    wolfgang@linux:~> PIC: IRQ (11) already programmed
    bash: syntax error near unexpected token `('
    wolfgang@linux:~> PIC: IRQ (5) already programmed
    bash: syntax error near unexpected token `('
    wolfgang@linux:~> PCI: Using ACPI for IRQ routing
    bash: PCI:: command not found
    wolfgang@linux:~> PCI: if you experience problems, try using option 'pci=noacpi' or even 'acpi=off'
    bash: PCI:: command not found
    wolfgang@linux:~> Linux NET4.0 for Linux 2.4
    bash: Linux: command not found
    wolfgang@linux:~> Based upon Swansea University Computer Society NET3.039
    bash: Based: command not found
    wolfgang@linux:~> Initializing RT netlink socket
    bash: Initializing: command not found
    wolfgang@linux:~> apm: BIOS version 1.2 Flags 0x07 (Driver version 1.16)
    bash: syntax error near unexpected token `('
    wolfgang@linux:~> apm: overridden by ACPI.
    bash: apm:: command not found
    wolfgang@linux:~> Starting kswapd
    bash: Starting: command not found
    wolfgang@linux:~> bigpage subsystem: allocated 0 bigpages (=0MB).
    bash: syntax error near unexpected token `('
    wolfgang@linux:~> kinoded started
    bash: kinoded: command not found
    wolfgang@linux:~> VFS: Disk quotas vdquot_6.5.1
    bash: VFS:: command not found
    wolfgang@linux:~> aio_setup: num_physpages = 49148
    bash: aio_setup:: command not found
    wolfgang@linux:~> aio_setup: sizeof(struct page) = 48
    bash: syntax error near unexpected token `('
    wolfgang@linux:~> vesafb: framebuffer at 0xd8000000, mapped to 0xf0817000, size 65536k
    bash: vesafb:: command not found
    wolfgang@linux:~> vesafb: mode is 1280x1024x16, linelength=2560, pages=24
    bash: vesafb:: command not found
    wolfgang@linux:~> vesafb: protected mode interface info at c000:569e
    bash: vesafb:: command not found
    wolfgang@linux:~> vesafb: scrolli

  7. #7
    Registrierter Benutzer Avatar von ThorstenHirsch
    Registriert seit
    Nov 2002
    Beiträge
    6.431
    Initializing USB Mass Storage driver...
    usb.c: registered new driver usb-storage
    scsi1 : SCSI emulation for USB Mass Storage devices
    Vendor: Maxtor Model: 5000XT v01.00.00 Rev: 0100
    Type: Direct-Access ANSI SCSI revision: 02
    Attached scsi disk sda at scsi1, channel 0, id 0, lun 0
    SCSI device sda: 490232832 512-byte hdwr sectors (250999 MB)
    sda: sda1
    WARNING: USB Mass Storage data integrity not assured
    USB Mass Storage device found at 2
    scsi2 : SCSI emulation for USB Mass Storage devices
    Vendor: Maxtor Model: 5000XT v01.00.00 Rev: 0100
    Type: Direct-Access ANSI SCSI revision: 02
    Attached scsi disk sdb at scsi2, channel 0, id 0, lun 0
    SCSI device sdb: 490232832 512-byte hdwr sectors (250999 MB)
    sdb: sdb1
    WARNING: USB Mass Storage data integrity not assured
    Das sind die beiden. Also Linux findet sie, die entsprechenden devices sollten existieren. Du hast dann die beiden Platten mal ausgestöpselt und wieder eingestöpselt - das wurde auch erkannt. Dein Problem ist jetzt das mounten.
    Unabhängig von yast solltest du sie als root folgendermaßen mounten können:
    Code:
    mount -t vfat /dev/sda1 /mnt/platte1
    ...wobei du vorher das Verzeichnis /mnt/platte1 erstellt haben musst.
    Wichtig ist dann, dass du bevor du die Platte rausziehst das da eingibst:
    Code:
    umount /mnt/platte1
    Tjo, bleibt noch folgendes zu sagen: mit yast und KDE kann man das auch durch anklicken von irgendwelchen Symbolen so einrichten, schau halt mal in die Hilfe oder SuSE Handbücher.
    ¡Nuestro amigo... el Computador!

  8. #8
    Registrierter Benutzer
    Registriert seit
    Feb 2004
    Beiträge
    12
    hab ich gemacht.
    es kommt aber die selbe fehlermeldung. er kann sie nicht mounten.

  9. #9
    ... Avatar von drunkenPenguin
    Registriert seit
    Jan 2003
    Ort
    Hamsterdam
    Beiträge
    2.264
    Kannst Du mal einen Filesystemcheck drüberlaufen lassen? Dafür müssen sie ja nicht gemountet sein.

  10. #10
    Registrierter Benutzer
    Registriert seit
    Feb 2004
    Beiträge
    12
    wie macht man den filesystemcheck?

  11. #11
    Registrierter Benutzer Avatar von ThorstenHirsch
    Registriert seit
    Nov 2002
    Beiträge
    6.431
    Code:
    fsck.vfat /dev/sda1
    (als root)
    ¡Nuestro amigo... el Computador!

  12. #12
    Registrierter Benutzer
    Registriert seit
    Feb 2004
    Beiträge
    12
    Danke!
    ich habe hilfe gefunden im programm reiserfsck.
    habe alles reparieren können.

Lesezeichen

Berechtigungen

  • Neue Themen erstellen: Nein
  • Themen beantworten: Nein
  • Anhänge hochladen: Nein
  • Beiträge bearbeiten: Nein
  •