DD externe qui ne répond pas

Qui est en ligne ?

Il y a : 29 utilisateurs en ligne, consultez le détail

Auteur	Message
papatou	#0 Message posté le : 05-07-2007 à 22:10:12
Hobbit Forum : Inscrit Association : Arrivé(e) le : 19-02-2003 Nombre de messages : 1716	j'ai un disque dur externe qui n'est pas détecté ?? comment je peux vérifier qu'il n'est pas hs ? ------------------------------------- J'AIME TRUSTONME !!!! utilisateur linux n° 318818

jblecanard	#1 Message posté le : 05-07-2007 à 23:33:38
Jedi Forum : Modérateur Association : Arrivé(e) le : 08-01-2005 Nombre de messages : 4030	Bah, la première chose à faire est de le brancher à chaud (allumé !) et de regarder si dmesg réagi au branchement. Si ce n'est pas le cas, c'est sûrement que l'alim du disque est en panne. Sinon, il faudra se pencher plus précisément sur le problème. ------------------------------------- C'est une situation bien inconfortable que d'être assez sensible à la bêtise pour en souffrir et trop intelligent pour s'en indigner. - Gustave Thibon -

papatou	#2 Message posté le : 08-07-2007 à 23:12:08
Hobbit Forum : Inscrit Association : Arrivé(e) le : 19-02-2003 Nombre de messages : 1716	je l'ai branché en direct dans un pc rien à faire, y à t'il moyen réparer ?? ou du moins de récupérer les données ?? ------------------------------------- J'AIME TRUSTONME !!!! utilisateur linux n° 318818

jblecanard	#3 Message posté le : 09-07-2007 à 03:01:45
Jedi Forum : Modérateur Association : Arrivé(e) le : 08-01-2005 Nombre de messages : 4030	Je te prie de m'excuser mais ça t'ennuierai de répondre à ma question ? Que donne dmesg après un branchement à chaud ? ------------------------------------- C'est une situation bien inconfortable que d'être assez sensible à la bêtise pour en souffrir et trop intelligent pour s'en indigner. - Gustave Thibon -

papatou	#4 Message posté le : 11-07-2007 à 21:22:35
Hobbit Forum : Inscrit Association : Arrivé(e) le : 19-02-2003 Nombre de messages : 1716	désolé de ne pas avoir donné signe de vie, pour de DD rien à faire la commande dmesg ne donne rien rien n'est reconnu. je pense qu'il à rendu l'ame ------------------------------------- J'AIME TRUSTONME !!!! utilisateur linux n° 318818

jblecanard	#5 Message posté le : 11-07-2007 à 22:19:43
Jedi Forum : Modérateur Association : Arrivé(e) le : 08-01-2005 Nombre de messages : 4030	si dmesg ne réagit pas après branchement à chaud, il se peut fort que ce ne soit que l'alim qui aie cramé. En ce cas, il y a une chance de récupérer les données en ouvrant le boîtier et en récupérant le disque dur pour le brancher sur une nappe ide ou sata selon son modèle. Si tu le penses foutu, tu n'as pas grand chose à y perdre, à part peut être la garantie... --Message édité par jblecanard le 11-07-2007 à 22:20:27-- ------------------------------------- C'est une situation bien inconfortable que d'être assez sensible à la bêtise pour en souffrir et trop intelligent pour s'en indigner. - Gustave Thibon -

Sly007	#6 Message posté le : 12-07-2007 à 15:05:30
Naboo Forum : Inscrit Association : Arrivé(e) le : 19-11-2003 Nombre de messages : 2400	jblecanard a écrit : si dmesg ne réagit pas après branchement à chaud, il se peut fort que ce ne soit que l'alim qui aie cramé. En ce cas, il y a une chance de récupérer les données en ouvrant le boîtier et en récupérant le disque dur pour le brancher sur une nappe ide ou sata selon son modèle. Si tu le penses foutu, tu n'as pas grand chose à y perdre, à part peut être la garantie... je pense que c'est ce qu'il a fait quand il parle de branchement "direct". Non? --Message édité par Sly007 le 12-07-2007 à 15:05:53-- ------------------------------------- RHAAAAAA! (lovely) G.W.B.

jblecanard	#7 Message posté le : 12-07-2007 à 18:03:24
Jedi Forum : Modérateur Association : Arrivé(e) le : 08-01-2005 Nombre de messages : 4030	"Je l'ai branché en direct dans un pc, rien à faire", je ne trouve pas ça très clair. Que veux dire "rien" ? Sous linux, pas grand chose hélas... d'où ma question. ------------------------------------- C'est une situation bien inconfortable que d'être assez sensible à la bêtise pour en souffrir et trop intelligent pour s'en indigner. - Gustave Thibon -

nali	#8 Message posté le : 13-07-2007 à 05:20:14
Elfe Forum : Modérateur Association : Arrivé(e) le : 05-04-2003 Nombre de messages : 3670	je presume que c est un usb. Dont on commence par un tail -f /varlog/messages /var/log/syslog voir si quqnd on branche ca se voit . modprobe usbstorage ca peut aider si c est pas fait . Tiens , le 2 eme arrive , ca va etre un autre garcon :P ------------------------------------- un Cathare a l Ouest

papatou	#9 Message posté le : 13-07-2007 à 20:16:17
Hobbit Forum : Inscrit Association : Arrivé(e) le : 19-02-2003 Nombre de messages : 1716	j'ai sorti le DD du boitier et l'ai branché sur une nappe IDE, j'ai testé dans 2 pc differents et sous des OS different à chaque fois le bios ne detecte rien résultat de dmesg : [root@papatou_land papatou]# dmesg Linux version 2.6.17-14mdv (qateam@mercury.mandriva.com) (gcc version 4.1.2 20070302 (prerelease) (4.1.2-1mdv2007.1)) #1 SMP Wed May 9 21:11:43 MDT 2007 BIOS-provided physical RAM map: BIOS-e820: 0000000000000000 - 000000000009fc00 (usable) BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved) BIOS-e820: 00000000000e4000 - 0000000000100000 (reserved) BIOS-e820: 0000000000100000 - 000000003ffc0000 (usable) BIOS-e820: 000000003ffc0000 - 000000003ffd0000 (ACPI data) BIOS-e820: 000000003ffd0000 - 0000000040000000 (ACPI NVS) BIOS-e820: 00000000fec00000 - 00000000fec01000 (reserved) BIOS-e820: 00000000fee00000 - 00000000fee01000 (reserved) BIOS-e820: 00000000ff780000 - 0000000100000000 (reserved) 127MB HIGHMEM available. 895MB LOWMEM available. found SMP MP-table at 000ff780 On node 0 totalpages: 262080 DMA zone: 4096 pages, LIFO batch:0 Normal zone: 225279 pages, LIFO batch:31 HighMem zone: 32705 pages, LIFO batch:7 DMI 2.3 present. ACPI: RSDP (v000 ACPIAM ) @ 0x000f9ed0 ACPI: RSDT (v001 A M I OEMRSDT 0x09000506 MSFT 0x00000097) @ 0x3ffc0000 ACPI: FADT (v002 A M I OEMFACP 0x09000506 MSFT 0x00000097) @ 0x3ffc0200 ACPI: MADT (v001 A M I OEMAPIC 0x09000506 MSFT 0x00000097) @ 0x3ffc0390 ACPI: OEMB (v001 A M I OEMBIOS 0x09000506 MSFT 0x00000097) @ 0x3ffd0040 ACPI: DSDT (v001 A0128 A0128003 0x00000003 INTL 0x02002026) @ 0x00000000 ACPI: PM-Timer IO Port: 0x4008 ACPI: Local APIC address 0xfee00000 ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled) Processor #0 15:12 APIC version 16 ACPI: IOAPIC (id[0x01] address[0xfec00000] gsi_base[0]) IOAPIC[0]: apic_id 1, version 17, address 0xfec00000, GSI 0-23 ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl) ACPI: BIOS IRQ0 pin2 override ignored. ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level) ACPI: INT_SRC_OVR (bus 0 bus_irq 14 global_irq 14 high edge) ACPI: INT_SRC_OVR (bus 0 bus_irq 15 global_irq 15 high edge) ACPI: IRQ9 used by override. ACPI: IRQ14 used by override. ACPI: IRQ15 used by override. Enabling APIC mode: Flat. Using 1 I/O APICs Using ACPI (MADT) for SMP configuration information Allocating PCI resources starting at 50000000 (gap: 40000000:bec00000) Built 1 zonelists Kernel command line: BOOT_IMAGE=linux root=/dev/hdb1 resume=/dev/hdb5 splash=silent vga=788 bootsplash: silent mode. mapped APIC to ffffe000 (fee00000) mapped IOAPIC to ffffd000 (fec00000) Enabling fast FPU save and restore... done. Enabling unmasked SIMD FPU exception support... done. Initializing CPU#0 PID hash table entries: 4096 (order: 12, 16384 bytes) Detected 1808.954 MHz processor. Using pmtmr for high-res timesource Console: colour dummy device 80x25 Dentry cache hash table entries: 131072 (order: 7, 524288 bytes) Inode-cache hash table entries: 65536 (order: 6, 262144 bytes) Memory: 1033476k/1048320k available (2430k kernel code, 13660k reserved, 760k data, 244k init, 130820k highmem, 0k BadRAM) Checking if this processor honours the WP bit even in supervisor mode... Ok. Calibrating delay using timer specific routine.. 3621.79 BogoMIPS (lpj=7243583) Mount-cache hash table entries: 512 CPU: After generic identify, caps: 078bfbff c1d3fbff 00000000 00000000 00000000 00000000 00000000 CPU: After vendor identify, caps: 078bfbff c1d3fbff 00000000 00000000 00000000 00000000 00000000 CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line) CPU: L2 Cache: 256K (64 bytes/line) CPU: After all inits, caps: 078bfbff c1d3fbff 00000000 00000410 00000000 00000000 00000000 Intel machine check architecture supported. Intel machine check reporting enabled on CPU#0. Checking 'hlt' instruction... OK. SMP alternatives: switching to UP code Freeing SMP alternatives: 16k freed checking if image is initramfs... it is Freeing initrd memory: 733k freed ACPI: Looking for DSDT in initramfs... error, file /DSDT.aml not found. CPU0: AMD Sempron(tm) Processor 3100+ stepping 00 Total of 1 processors activated (3621.79 BogoMIPS). ENABLING IO-APIC IRQs ..TIMER: vector=0x31 apic1=0 pin1=0 apic2=-1 pin2=-1 Brought up 1 CPUs migration_cost=0 NET: Registered protocol family 16 ACPI: bus type pci registered PCI: PCI BIOS revision 2.10 entry at 0xf0031, last bus=2 Setting up standard PCI resources ACPI: Subsystem revision 20060127 ACPI: Interpreter enabled ACPI: Using IOAPIC for interrupt routing ACPI: PCI Root Bridge [PCI0] (0000:00) PCI: Probing PCI hardware (bus 00) Boot video device is 0000:01:00.0 ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.P0P1._PRT] ACPI: Power Resource [ISAV] (on) ACPI: PCI Interrupt Link [LNKA] (IRQs 16 17 18 19) 0, disabled. ACPI: PCI Interrupt Link [LNKB] (IRQs 16 17 18 19) 11 ACPI: PCI Interrupt Link [LNKC] (IRQs 16 17 18 19) 11 ACPI: PCI Interrupt Link [LNKD] (IRQs 16 17 18 19) 9 ACPI: PCI Interrupt Link [LNKE] (IRQs 16 17 18 19) 11 ACPI: PCI Interrupt Link [LUS0] (IRQs 20 21 22) 3 ACPI: PCI Interrupt Link [LUS1] (IRQs 20 21 22) 9 ACPI: PCI Interrupt Link [LUS2] (IRQs 20 21 22) 10 ACPI: PCI Interrupt Link [LKLN] (IRQs 20 21 22) 11 ACPI: PCI Interrupt Link [LAUI] (IRQs 20 21 22) 9 ACPI: PCI Interrupt Link [LKMO] (IRQs 20 21 22) 0, disabled. ACPI: PCI Interrupt Link [LKSM] (IRQs 20 21 22) 0, disabled. ACPI: PCI Interrupt Link [LTID] (IRQs 20 21 22) 0 ACPI: PCI Interrupt Link [LTIE] (IRQs 20 21 22) 0, disabled. ACPI: PCI Interrupt Link [LATA] (IRQs 20 21 22) *14 Linux Plug and Play Support v0.97 (c) Adam Belay pnp: PnP ACPI init pnp: PnP ACPI: found 16 devices PnPBIOS: Disabled PCI: Using ACPI for IRQ routing PCI: If a device doesn't work, try "pci=routeirq". If it helps, post a report pnp: 00:0c: ioport range 0x480-0x487 has been reserved pnp: 00:0c: ioport range 0xd00-0xd07 has been reserved PCI: Bridge: 0000:00:0b.0 IO window: disabled. MEM window: fc900000-fe9fffff PREFETCH window: cc800000-ec7fffff PCI: Bridge: 0000:00:0e.0 IO window: b000-bfff MEM window: fea00000-feafffff PREFETCH window: disabled. PCI: Setting latency timer of device 0000:00:0e.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 apm: BIOS version 1.2 Flags 0x03 (Driver version 1.16ac) apm: overridden by ACPI. audit: initializing netlink socket (disabled) audit(1184354681.544:1): initialized highmem bounce pool size: 64 pages Total HugeTLB memory allocated, 0 VFS: Disk quotas dquot_6.5.1 Dquot-cache hash table entries: 1024 (order 0, 4096 bytes) Initializing Cryptographic API io scheduler noop registered io scheduler anticipatory registered (default) io scheduler deadline registered io scheduler cfq registered vesafb: framebuffer at 0xd0000000, mapped to 0xf8880000, using 3750k, total 131072k vesafb: mode is 800x600x16, linelength=1600, pages=2 vesafb: protected mode interface info at c000:e780 vesafb: scrolling: redraw vesafb: Truecolor: size=0:5:6:5, shift=0:11:5:0 bootsplash 3.1.6-2004/03/31: looking for picture...<6> silentjpeg size 197324 bytes,<6>...found (800x600, 197276 bytes, v3). Console: switching to colour frame buffer device 93x31 fb0: VESA VGA frame buffer device isapnp: Scanning for PnP cards... isapnp: No Plug & Play device found Real Time Clock Driver v1.12ac Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing enabled serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A 00:0e: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A RAMDISK driver initialized: 16 RAM disks of 32000K size 1024 blocksize Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2 ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx NFORCE3-250: IDE controller at PCI slot 0000:00:08.0 NFORCE3-250: chipset revision 162 NFORCE3-250: not 100% native mode: will probe irqs later NFORCE3-250: BIOS didn't set cable bits correctly. Enabling workaround. NFORCE3-250: 0000:00:08.0 (rev a2) UDMA133 controller ide0: BM-DMA at 0xffa0-0xffa7, BIOS settings: hdaMA, hdbMA ide1: BM-DMA at 0xffa8-0xffaf, BIOS settings: hdcMA, hddMA Probing IDE interface ide0... hda: Maxtor 6Y080P0, ATA DISK drive hdb: WDC WD600BB-00CAA1, ATA DISK drive ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 Probing IDE interface ide1... hdc: BENQ DVD DD DW1620, ATAPI CD/DVD-ROM drive hdd: SAMSUNG DVD-ROM SD-616Q, ATAPI CD/DVD-ROM drive ide1 at 0x170-0x177,0x376 on irq 15 hda: max request size: 128KiB hda: 160086528 sectors (81964 MB) w/7936KiB Cache, CHS=65535/16/63, UDMA(133) hda: cache flushes supported hda: hda1 hda2 < hda5 hda6 hda7 > hdb: max request size: 128KiB hdb: 117231408 sectors (60022 MB) w/2048KiB Cache, CHS=65535/16/63, UDMA(100) hdb: cache flushes not supported hdb: hdb1 hdb2 < hdb5 hdb6 hdb7 hdb8 hdb9 > hdb3 PNP: PS/2 Controller [PNP0303:PS2K,PNP0f03:PS2M] at 0x60,0x64 irq 1,12 serio: i8042 AUX port at 0x60,0x64 irq 12 serio: i8042 KBD port at 0x60,0x64 irq 1 mice: PS/2 mouse device common for all mice md: md driver 0.90.3 MAX_MD_DEVS=256, MD_SB_DISKS=27 md: bitmap version 4.39 TCP bic registered NET: Registered protocol family 1 Using IPI No-Shortcut mode ACPI wakeup devices: PS2K PS2M UAR1 USB0 MAC USB1 USB2 P0P1 ACPI: (supports S0 S1 S3 S4 S5) BIOS EDD facility v0.16 2004-Jun-25, 2 devices found Freeing unused kernel memory: 244k freed input: AT Translated Set 2 keyboard as /class/input/input0 kjournald starting. Commit interval 5 seconds EXT3-fs: mounted filesystem with ordered data mode. input: PS2++ Logitech MX Mouse as /class/input/input1 ts: Compaq touchscreen protocol output usbcore: registered new driver usbfs usbcore: registered new driver hub ohci_hcd: 2005 April 22 USB 1.1 'Open' Host Controller (OHCI) Driver (PCI) ACPI: PCI Interrupt Link [LUS0] enabled at IRQ 22 ACPI: PCI Interrupt 0000:00:02.0[A] -> Link [LUS0] -> GSI 22 (level, low) -> IRQ 16 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 16, io mem 0xfebfd000 usb usb1: configuration #1 chosen from 1 choice hub 1-0:1.0: USB hub found hub 1-0:1.0: 4 ports detected ACPI: PCI Interrupt Link [LUS1] enabled at IRQ 21 ACPI: PCI Interrupt 0000:00:02.1[B] -> Link [LUS1] -> GSI 21 (level, low) -> IRQ 17 PCI: Setting latency timer of device 0000:00:02.1 to 64 ohci_hcd 0000:00:02.1: OHCI Host Controller ohci_hcd 0000:00:02.1: new USB bus registered, assigned bus number 2 ohci_hcd 0000:00:02.1: irq 17, io mem 0xfebfe000 usb usb2: configuration #1 chosen from 1 choice hub 2-0:1.0: USB hub found hub 2-0:1.0: 4 ports detected ACPI: PCI Interrupt Link [LUS2] enabled at IRQ 20 ACPI: PCI Interrupt 0000:00:02.2[C] -> Link [LUS2] -> GSI 20 (level, low) -> IRQ 18 PCI: Setting latency timer of device 0000:00:02.2 to 64 ehci_hcd 0000:00:02.2: EHCI Host Controller ehci_hcd 0000:00:02.2: new USB bus registered, assigned bus number 3 ehci_hcd 0000:00:02.2: debug port 1 PCI: cache line size of 64 is not supported by device 0000:00:02.2 ehci_hcd 0000:00:02.2: irq 18, io mem 0xfebffc00 ehci_hcd 0000:00:02.2: 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: 8 ports detected Linux agpgart interface v0.101 (c) Dave Jones agpgart: Detected AGP bridge 0 agpgart: Setting up Nforce3 AGP. agpgart: aperture base > 4G powernow-k8: Found 1 AMD Athlon 64 / Opteron processors (version 1.60.2) powernow-k8: BIOS error - no PSB or ACPI _PSS objects Floppy drive(s): fd0 is 1.44M FDC 0 is a post-1991 82077 SCSI subsystem initialized libata version 1.20 loaded. sata_nv 0000:00:0a.0: version 0.8 ACPI: PCI Interrupt Link [LTID] BIOS reported IRQ 0, using IRQ 22 ACPI: PCI Interrupt Link [LTID] enabled at IRQ 22 ACPI: PCI Interrupt 0000:00:0a.0[A] -> Link [LTID] -> GSI 22 (level, low) -> IRQ 16 PCI: Setting latency timer of device 0000:00:0a.0 to 64 ata1: SATA max UDMA/133 cmd 0x9F0 ctl 0xBF2 bmdma 0xC800 irq 16 ata2: SATA max UDMA/133 cmd 0x970 ctl 0xB72 bmdma 0xC808 irq 16 ata1: SATA link down (SStatus 0) scsi0 : sata_nv ata2: SATA link down (SStatus 0) scsi1 : sata_nv device-mapper: 4.6.0-ioctl (2006-02-17) initialised: dm-devel@redhat.com EXT3 FS on hdb1, internal journal Adding 2040212k swap on /dev/hdb5. Priority:-1 extents:1 across:2040212k Adding 746980k swap on /dev/hdb8. Priority:-2 extents:1 across:746980k Supermount version 2.0.4 for kernel 2.6 NTFS driver 2.1.27 [Flags: R/O DEBUG MODULE]. NTFS volume version 3.1. NTFS volume version 3.1. kjournald starting. Commit interval 5 seconds EXT3 FS on hdb7, internal journal EXT3-fs: mounted filesystem with ordered data mode. kjournald starting. Commit interval 5 seconds EXT3 FS on hdb9, internal journal EXT3-fs: mounted filesystem with ordered data mode. kjournald starting. Commit interval 5 seconds EXT3 FS on hdb6, internal journal EXT3-fs: mounted filesystem with ordered data mode. loop: loaded (max 8 devices, max 1 partitions per device) hdc: ATAPI 40X DVD-ROM DVD-R CD-R/RW drive, 2048kB Cache, UDMA(33) Uniform CD-ROM driver Revision: 3.20 ide-cd: cmd 0x5a timed out hdd: irq timeout: status=0xd0 { Busy } ide: failed opcode was: unknown hdd: DMA disabled hdd: ATAPI reset complete hdd: ATAPI 48X DVD-ROM drive, 512kB Cache Netfilter messages via NETLINK v0.30. ip_conntrack version 2.4 (8190 buckets, 65520 max) - 224 bytes per conntrack Removing netfilter NETLINK layer. ACPI: Power Button (FF) [PWRF] ACPI: Power Button (CM) [PWRB] i2c_adapter i2c-0: nForce2 SMBus adapter at 0x5000 i2c_adapter i2c-1: nForce2 SMBus adapter at 0x5040 Using specific hotkey driver it87: Found IT8712F chip at 0xd00, revision 7 NET: Registered protocol family 10 lo: Disabled Privacy Extensions IPv6 over IPv4 tunneling driver NET: Registered protocol family 17 ACPI: PCI Interrupt Link [LNKC] enabled at IRQ 19 ACPI: PCI Interrupt 0000:02:08.0[A] -> Link [LNKC] -> GSI 19 (level, low) -> IRQ 19 forcedeth.c: Reverse Engineered nForce ethernet driver. Version 0.54. ACPI: PCI Interrupt Link [LKLN] enabled at IRQ 21 ACPI: PCI Interrupt 0000:00:05.0[A] -> Link [LKLN] -> GSI 21 (level, low) -> IRQ 17 PCI: Setting latency timer of device 0000:00:05.0 to 64 eth0: forcedeth.c: subsystem: 01043:80a7 bound to 0000:00:05.0 eth0: no link during initialization. ADDRCONF(NETDEV_UP): eth0: link is not ready 8139too Fast Ethernet driver 0.9.27 ACPI: PCI Interrupt Link [LNKB] enabled at IRQ 18 ACPI: PCI Interrupt 0000:02:07.0[A] -> Link [LNKB] -> GSI 18 (level, low) -> IRQ 20 eth1: RealTek RTL8139 at 0xf904ac00, 00:08:54:3e:a0:eb, IRQ 20 eth1: Identified 8139 chip type 'RTL-8100B/8139D' eth1: link down ADDRCONF(NETDEV_UP): eth1: link is not ready eth0: link up. ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready vmmon: module license 'unspecified' taints kernel. /dev/vmmon[3719]: Module vmmon: registered with major=10 minor=165 /dev/vmmon[3719]: Module vmmon: initialized parport: PnPBIOS parport detected. parport0: PC-style at 0x378 (0x778), irq 7, dma 3 [PCSPP,TRISTATE,COMPAT,ECP,DMA] /dev/vmnet: open called by PID 4106 (vmnet-bridge) /dev/vmnet: hub 0 does not exist, allocating memory. /dev/vmnet: port on hub 0 successfully opened bridge-eth0: enabling the bridge bridge-eth0: up bridge-eth0: already up bridge-eth0: attached /dev/vmnet: open called by PID 4170 (vmnet-natd) /dev/vmnet: hub 8 does not exist, allocating memory. /dev/vmnet: port on hub 8 successfully opened /dev/vmnet: open called by PID 4220 (vmnet-netifup) /dev/vmnet: port on hub 8 successfully opened /dev/vmnet: open called by PID 4221 (vmnet-netifup) /dev/vmnet: hub 1 does not exist, allocating memory. /dev/vmnet: port on hub 1 successfully opened Installing knfsd (copyright (C) 1996 okir@monad.swb.de). NFSD: Using /var/lib/nfs/v4recovery as the NFSv4 state recovery directory NFSD: starting 90-second grace period eth0: no IPv6 routers present /dev/vmnet: open called by PID 4258 (vmnet-dhcpd) /dev/vmnet: port on hub 8 successfully opened /dev/vmnet: open called by PID 4248 (vmnet-dhcpd) /dev/vmnet: port on hub 1 successfully opened ppdev: user-space parallel port driver ACPI: PCI Interrupt Link [LNKE] enabled at IRQ 17 ACPI: PCI Interrupt 0000:01:00.0[A] -> Link [LNKE] -> GSI 17 (level, low) -> IRQ 21 NVRM: loading NVIDIA Linux x86 Kernel Module 1.0-9629 Wed Nov 1 19:30:07 PST 2006 vmnet8: no IPv6 routers present vmnet1: no IPv6 routers present bootsplash 3.1.6-2004/03/31: looking for picture...<6>...found (800x600, 14222 bytes, v3). bootsplash: status on console 0 changed to on bootsplash 3.1.6-2004/03/31: looking for picture...<6>...found (800x600, 14222 bytes, v3). bootsplash: status on console 1 changed to on bootsplash 3.1.6-2004/03/31: looking for picture...<6>...found (800x600, 14222 bytes, v3). bootsplash: status on console 2 changed to on bootsplash 3.1.6-2004/03/31: looking for picture...<6>...found (800x600, 14222 bytes, v3). bootsplash: status on console 3 changed to on bootsplash 3.1.6-2004/03/31: looking for picture...<6>...found (800x600, 14222 bytes, v3). bootsplash: status on console 4 changed to on bootsplash 3.1.6-2004/03/31: looking for picture...<6>...found (800x600, 14222 bytes, v3). bootsplash: status on console 5 changed to on ohci_hcd 0000:00:02.1: wakeup usb 2-2: new full speed USB device using ohci_hcd and address 2 usb 2-2: configuration #1 chosen from 1 choice Initializing USB Mass Storage driver... scsi2 : SCSI emulation for USB Mass Storage devices usbcore: registered new driver usb-storage USB Mass Storage support registered. usb-storage: device found at 2 usb-storage: waiting for device to settle before scanning Vendor: Sony Model: Sony DSC Rev: 3.28 Type: Direct-Access ANSI SCSI revision: 00 2:0:0:0: Attached scsi generic sg0 type 0 usb-storage: device scan complete SCSI device sda: 15840 512-byte hdwr sectors (8 MB) sda: assuming Write Enabled sda: assuming drive cache: write through SCSI device sda: 15840 512-byte hdwr sectors (8 MB) sda: assuming Write Enabled sda: assuming drive cache: write through sda: sda1 sd 2:0:0:0: Attached scsi removable disk sda end_request: I/O error, dev fd0, sector 0 end_request: I/O error, dev fd0, sector 0 end_request: I/O error, dev fd0, sector 0 end_request: I/O error, dev fd0, sector 0 end_request: I/O error, dev fd0, sector 0 end_request: I/O error, dev fd0, sector 0 usb 2-2: USB disconnect, address 2 2:0:0:0: rejecting I/O to dead device FAT: Directory bread(block 7) failed 2:0:0:0: rejecting I/O to dead device FAT: Directory bread(block 8) failed 2:0:0:0: rejecting I/O to dead device FAT: Directory bread(block 9) failed 2:0:0:0: rejecting I/O to dead device FAT: Directory bread(block 10) failed 2:0:0:0: rejecting I/O to dead device FAT: Directory bread(block 11) failed 2:0:0:0: rejecting I/O to dead device FAT: Directory bread(block 12) failed 2:0:0:0: rejecting I/O to dead device FAT: Directory bread(block 13) failed 2:0:0:0: rejecting I/O to dead device FAT: Directory bread(block 14) failed 2:0:0:0: rejecting I/O to dead device FAT: Directory bread(block 15) failed 2:0:0:0: rejecting I/O to dead device FAT: Directory bread(block 16) failed 2:0:0:0: rejecting I/O to dead device FAT: Directory bread(block 17) failed 2:0:0:0: rejecting I/O to dead device FAT: Directory bread(block 18) failed 2:0:0:0: rejecting I/O to dead device FAT: Directory bread(block 19) failed 2:0:0:0: rejecting I/O to dead device FAT: Directory bread(block 20) failed 2:0:0:0: rejecting I/O to dead device FAT: Directory bread(block 21) failed 2:0:0:0: rejecting I/O to dead device FAT: Directory bread(block 22) failed 2:0:0:0: rejecting I/O to dead device FAT: Directory bread(block 23) failed 2:0:0:0: rejecting I/O to dead device FAT: Directory bread(block 24) failed 2:0:0:0: rejecting I/O to dead device FAT: Directory bread(block 25) failed 2:0:0:0: rejecting I/O to dead device FAT: Directory bread(block 26) failed 2:0:0:0: rejecting I/O to dead device FAT: Directory bread(block 27) failed 2:0:0:0: rejecting I/O to dead device FAT: Directory bread(block 28) failed 2:0:0:0: rejecting I/O to dead device FAT: Directory bread(block 29) failed 2:0:0:0: rejecting I/O to dead device FAT: Directory bread(block 30) failed 2:0:0:0: rejecting I/O to dead device FAT: Directory bread(block 31) failed 2:0:0:0: rejecting I/O to dead device FAT: Directory bread(block 32) failed 2:0:0:0: rejecting I/O to dead device FAT: Directory bread(block 33) failed 2:0:0:0: rejecting I/O to dead device FAT: Directory bread(block 34) failed 2:0:0:0: rejecting I/O to dead device FAT: Directory bread(block 35) failed 2:0:0:0: rejecting I/O to dead device FAT: Directory bread(block 36) failed 2:0:0:0: rejecting I/O to dead device FAT: Directory bread(block 37) failed 2:0:0:0: rejecting I/O to dead device FAT: Directory bread(block 38) failed end_request: I/O error, dev fd0, sector 0 end_request: I/O error, dev fd0, sector 0 end_request: I/O error, dev fd0, sector 0 end_request: I/O error, dev fd0, sector 0 end_request: I/O error, dev fd0, sector 0 end_request: I/O error, dev fd0, sector 0 [root@papatou_land papatou]# ------------------------------------- J'AIME TRUSTONME !!!! utilisateur linux n° 318818

Azollyx	#10 Message posté le : 13-07-2007 à 20:27:18
Naboo Forum : Modérateur Association : Président Arrivé(e) le : 09-04-2006 Nombre de messages : 2095	Si tu veux qu'on puisse faire quelque chose de ce que tu nous donnes, ça serait pas mal que tu metes un dmesg avant tentative et un autre après branchement ou encore mieux, que tu compares toi-même les deux pour nous donner les différences... Si c'est le bon, il a l'air d'être détecté : usb-storage: device scan complete SCSI device sda: 15840 512-byte hdwr sectors (8 MB) sda: assuming Write Enabled sda: assuming drive cache: write through SCSI device sda: 15840 512-byte hdwr sectors (8 MB) sda: assuming Write Enabled sda: assuming drive cache: write through sda: sda1 En root, essaye ça : cd mkdir sda1 mount -o ro /dev/sda1 sda1 ls -l sda1 (disque branché)

jblecanard	#11 Message posté le : 13-07-2007 à 20:46:10
Jedi Forum : Modérateur Association : Arrivé(e) le : 08-01-2005 Nombre de messages : 4030	+1 avec Azollyx. Il semble bien être détecté... il faut voir si on peut en tirer quelque chose. D'expérience, le système peut détecter un matériel invisible du BIOS. Malheureusement, quand ça m'est arrivé, le disque était complètement corrompu . Espérons que ça ne soit pas le cas... ------------------------------------- C'est une situation bien inconfortable que d'être assez sensible à la bêtise pour en souffrir et trop intelligent pour s'en indigner. - Gustave Thibon -

papatou	#12 Message posté le : 13-07-2007 à 23:10:23
Hobbit Forum : Inscrit Association : Arrivé(e) le : 19-02-2003 Nombre de messages : 1716	[root@papatou_land papatou]# cd [root@papatou_land ~]# mkdir sda1 [root@papatou_land ~]# mount -o ro /dev/sda1 sda1 mount: périphérique spécial /dev/sda1 n'existe pas ------------------------------------- J'AIME TRUSTONME !!!! utilisateur linux n° 318818

trucker38	#13 Message posté le : 14-07-2007 à 00:00:37
Maître Jedi Forum : Modérateur Association : Arrivé(e) le : 26-11-2003 Nombre de messages : 6233	usb 2-2: USB disconnect, address 2 2:0:0:0: rejecting I/O to dead device FAT: Directory bread(block 7) failed 2:0:0:0: rejecting I/O to dead device FAT: Directory bread(block 8) failed 2:0:0:0: rejecting I/O to dead device FAT: Directory bread(block 9) failed 2:0:0:0: rejecting I/O to dead device FAT: Directory bread(block 10) failed 2:0:0:0: rejecting I/O to dead device FAT: Directory bread(block 11) failed 2:0:0:0: rejecting I/O to dead device FAT: Directory bread(block 12) failed 2:0:0:0: rejecting I/O to dead device FAT: Directory bread(block 13) failed 2:0:0:0: rejecting I/O to dead device FAT: Directory bread(block 14) failed 2:0:0:0: rejecting I/O to dead device FAT: Directory bread(block 15) failed 2:0:0:0: rejecting I/O to dead device FAT: Directory bread(block 16) failed 2:0:0:0: rejecting I/O to dead device FAT: Directory bread(block 17) failed 2:0:0:0: rejecting I/O to dead device FAT: Directory bread(block 18) failed 2:0:0:0: rejecting I/O to dead device FAT: Directory bread(block 19) failed 2:0:0:0: rejecting I/O to dead device FAT: Directory bread(block 20) failed 2:0:0:0: rejecting I/O to dead device FAT: Directory bread(block 21) failed 2:0:0:0: rejecting I/O to dead device FAT: Directory bread(block 22) failed 2:0:0:0: rejecting I/O to dead device FAT: Directory bread(block 23) failed 2:0:0:0: rejecting I/O to dead device FAT: Directory bread(block 24) failed 2:0:0:0: rejecting I/O to dead device FAT: Directory bread(block 25) failed 2:0:0:0: rejecting I/O to dead device FAT: Directory bread(block 26) failed 2:0:0:0: rejecting I/O to dead device FAT: Directory bread(block 27) failed 2:0:0:0: rejecting I/O to dead device FAT: Directory bread(block 28) failed 2:0:0:0: rejecting I/O to dead device FAT: Directory bread(block 29) failed 2:0:0:0: rejecting I/O to dead device FAT: Directory bread(block 30) failed 2:0:0:0: rejecting I/O to dead device FAT: Directory bread(block 31) failed 2:0:0:0: rejecting I/O to dead device FAT: Directory bread(block 32) failed 2:0:0:0: rejecting I/O to dead device FAT: Directory bread(block 33) failed 2:0:0:0: rejecting I/O to dead device FAT: Directory bread(block 34) failed 2:0:0:0: rejecting I/O to dead device FAT: Directory bread(block 35) failed 2:0:0:0: rejecting I/O to dead device FAT: Directory bread(block 36) failed 2:0:0:0: rejecting I/O to dead device FAT: Directory bread(block 37) failed 2:0:0:0: rejecting I/O to dead device FAT: Directory bread(block 38) failed C'est pas tres bon ça ! ton dd externe est en FAT ? si oui, reformates-le ! :/ ------------------------------------- "[ ] Quand il pleut des roubles, le malchanceux n'a pas de sac.[ ] _Coluche_

Azollyx	#14 Message posté le : 14-07-2007 à 01:01:09
Naboo Forum : Modérateur Association : Président Arrivé(e) le : 09-04-2006 Nombre de messages : 2095	Le but c'est quand même de récupérer les données... bon bah il y a effectivement me bug et le noyau ne te laisse pas accéde au disque (pas de sda1). Quand tu as essayé, il était connecté comment ?

papatou	#15 Message posté le : 14-07-2007 à 10:09:05
Hobbit Forum : Inscrit Association : Arrivé(e) le : 19-02-2003 Nombre de messages : 1716	trucker38: Le dd est partitionné une partition ntfs et une ext3 le but c'est d'y acceder pour récupérer les données, ensuite retour à l'envoyeur il est encore sous garantie Azollyx: oui il etait connecté comparaison de dmesg avant branchement ICI Après branchement LA --Message édité par papatou le 14-07-2007 à 13:04:58-- ------------------------------------- J'AIME TRUSTONME !!!! utilisateur linux n° 318818