[Linuxtrent] Re: md autodetect e moduli dischi
- From: "Giuliano Natali (el Diaolin)" <diaolin@xxxxxxxxxxx>
- To: linuxtrent@xxxxxxxxxxxxx
- Date: Tue, 5 Oct 2004 21:10:09 +0200 (CEST)
Daniele P. ha scritto:
> Alle 12:07, lunedì 4 ottobre 2004, hai scritto:
>> Alle 00:50, lunedì 4 ottobre 2004, hai scritto:
>> > | con mdadm?
>> >
>> > /etc/mdadm/mdadm.conf
>> >
>> > Ci vengono specificate all'interno le associazione md device, uuid e
>> > partizioni.
>>
>> Ok,
>> ma il passo successivo sarà spostare la partizione di root su raid e
>> quindi
>> il sistema dovrà funzionare per forza con l'autodetect, visto che /etc
>> sarà
>> visto solo dopo il mount della root. Anzi, a dire il vero l'intenzione è
>> lvm sopra raid software per root e altro, raid software per /boot.
>>
>> Daniele P.
>
> La saga continua...
> Con due strade sono giunto agli stessi risultati (prima ho staccato il
> cdrom,
> per evitare il freeze):
> 1) Facendo mkinitrd e forzando il caricamento del modulo raid1 come
> suggerito
> da Diaolin.
> 2)Installando nuovamente debian in un altra partizione dell'lvm.
> Addesso ho capito meglio, ma non del tutto, quello che è successo.
> L'installer vede le partizioni che costituiscono il raid ma non i device
> mdX.
> Se si prendono due partizioni che costituiscono un raid1 e si mettono
> assieme manualmente (nell'interfaccia dell'installer) l'installer non
> tocca il contenuto delle partizioni ma poi lo vede correttamente.
> Nel mio caso sia la partizione /boot che tutta la stuttura lvm dopo aver
> creato il device mdX e mdY hanno mantenuto i loro dati.
> Il fatto che l'installer di default prenda come buona una partizione
> contenente lvm sopra raid invece del raid intero secondo me è un baco.
Ah interessante conclusione...
e ????
spiegaci il motivo di questa certezza :-)
a me senbra una feature....
> Ora però all'avvio e allo spegnimento da un po' di messaggi strani
> che ben pochi sembrano avere...
>
> Anche dopo apt-get upgrade e dist-upgrade (che aggiornava lvm2)
> Meno male che si può catturare tutto (o meglio quasi!) via seriale...
>
> Linux version 2.6.8-1-386 (dilinger@xxxxxxxxxxxxxxxxxxxx) (gcc version
> 3.3.4
> (Debian 1:3.3.4-11)) #1 Mon Sep 13 23:29:55 EDT 2004
> BIOS-provided physical RAM map:
> BIOS-e820: 0000000000000000 - 000000000009fc00 (usable)
> BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved)
> BIOS-e820: 00000000000e8000 - 0000000000100000 (reserved)
> BIOS-e820: 0000000000100000 - 000000003ff30000 (usable)
> BIOS-e820: 000000003ff30000 - 000000003ff40000 (ACPI data)
> BIOS-e820: 000000003ff40000 - 000000003fff0000 (ACPI NVS)
> BIOS-e820: 000000003fff0000 - 0000000040000000 (reserved)
> BIOS-e820: 00000000ffb80000 - 0000000100000000 (reserved)
> Warning only 896MB will be used.
> Use a HIGHMEM enabled kernel.
> 896MB LOWMEM available.
> # Ok, ma intato vediamo di funzionare con 896
> found SMP MP-table at 000ff780
> DMI 2.3 present.
> ACPI: RSDP (v002 ACPIAM ) @ 0x000f9e30
> ACPI: XSDT (v001 A M I OEMXSDT 0x11000321 MSFT 0x00000097) @ 0x3ff30100
> ACPI: FADT (v003 A M I OEMFACP 0x11000321 MSFT 0x00000097) @ 0x3ff30290
> ACPI: MADT (v001 A M I OEMAPIC 0x11000321 MSFT 0x00000097) @ 0x3ff30390
> ACPI: OEMB (v001 A M I OEMBIOS 0x11000321 MSFT 0x00000097) @ 0x3ff40040
> ACPI: DSDT (v001 P4CED P4CED096 0x00000096 INTL 0x02002026) @ 0x00000000
> ACPI: PM-Timer IO Port: 0x808
> ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
> Processor #0 15:3 APIC version 20
> ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01] enabled)
> Processor #1 15:3 APIC version 20
> WARNING: NR_CPUS limit of 1 reached. Processor ignored.
> ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0])
> IOAPIC[0]: Assigned apic_id 2
> IOAPIC[0]: apic_id 2, version 32, 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 9 global_irq 9 high level)
> Enabling APIC mode: Flat. Using 1 I/O APICs
> Using ACPI (MADT) for SMP configuration information
> Built 1 zonelists
> Kernel command line: root=/dev/mapper/mdk-home ro console=ttyS0
> console=tty0
> Initializing CPU#0
> PID hash table entries: 4096 (order 12: 32768 bytes)
> Detected 2798.936 MHz processor.
> Using pmtmr for high-res timesource
> Console: colour VGA+ 80x25
> Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
> Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
> Memory: 901572k/917504k available (1329k kernel code, 15184k reserved,
> 727k
> data, 204k init, 0k highmem)
> Checking if this processor honours the WP bit even in supervisor mode...
> Ok.
> Calibrating delay loop... 5554.17 BogoMIPS
> Security Scaffold v1.0.0 initialized
> Mount-cache hash table entries: 512 (order: 0, 4096 bytes)
> monitor/mwait feature present.
> using mwait in idle threads.
> CPU: Trace cache: 12K uops, L1 D cache: 16K
> CPU: L2 cache: 1024K
> CPU: Intel(R) Pentium(R) 4 CPU 2.80GHz stepping 03
> Enabling fast FPU save and restore... done.
> Enabling unmasked SIMD FPU exception support... done.
> Checking 'hlt' instruction... OK.
> Checking for popad bug... OK.
> enabled ExtINT on CPU#0
> ESR value before enabling vector: 00000000
> ESR value after enabling vector: 00000000
> ENABLING IO-APIC IRQs
> ..TIMER: vector=0x31 pin1=2 pin2=-1
> Using local APIC timer interrupts.
> calibrating APIC timer ...
> ..... CPU clock speed is 2798.0237 MHz.
> ..... host bus clock speed is 199.0873 MHz.
> checking if image is initramfs...it isn't (ungzip failed); looks like an
> initrd
> Freeing initrd memory: 4608k freed
> NET: Registered protocol family 16
> EISA bus registered
> PCI: PCI BIOS revision 2.10 entry at 0xf0031, last bus=3
> PCI: Using configuration type 1
> mtrr: v2.0 (20020519)
> ACPI: Subsystem revision 20040326
> ACPI: Interpreter enabled
> ACPI: Using IOAPIC for interrupt routing
> ACPI: PCI Root Bridge [PCI0] (00:00)
> PCI: Probing PCI hardware (bus 00)
> PCI: Ignoring BAR0-3 of IDE controller 0000:00:1f.1
> PCI: Transparent bridge - 0000:00:1e.0
> ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 10 *11 12 14 15)
> ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 10 *11 12 14 15)
> ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 6 7 10 *11 12 14 15)
> ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 7 10 *11 12 14 15)
> ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 10 *11 12 14 15)
> ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 10 11 12 14 15) *0,
> disabled.
> ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 10 *11 12 14 15)
> ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 *5 6 7 10 11 12 14 15)
> Linux Plug and Play Support v0.97 (c) Adam Belay
> PnPBIOS: Scanning system for PnP BIOS support...
> PnPBIOS: Found PnP BIOS installation structure at 0xc00f5270
> PnPBIOS: PnP BIOS version 1.0, entry 0xf0000:0x5e5a, dseg 0xf0000
> PNPBIOS fault.. attempting recovery.
> PnPBIOS: Warning! Your PnP BIOS caused a fatal error. Attempting to
> continue
> PnPBIOS: You may need to reboot with the "nobiospnp" option to operate
> stably
> PnPBIOS: Check with your vendor for an updated BIOS
> PnPBIOS: get_dev_node: unexpected status 0x28
> PnPBIOS: 6 nodes reported by PnP BIOS; 6 recorded by driver
> PCI: Using ACPI for IRQ routing
> ACPI: PCI interrupt 0000:00:1d.0[A] -> GSI 16 (level, low) -> IRQ 169
> ACPI: PCI interrupt 0000:00:1d.1[B] -> GSI 19 (level, low) -> IRQ 177
> ACPI: PCI interrupt 0000:00:1d.2[C] -> GSI 18 (level, low) -> IRQ 185
> ACPI: PCI interrupt 0000:00:1d.3[A] -> GSI 16 (level, low) -> IRQ 169
> ACPI: PCI interrupt 0000:00:1d.7[D] -> GSI 23 (level, low) -> IRQ 193
> ACPI: PCI interrupt 0000:00:1f.1[A] -> GSI 18 (level, low) -> IRQ 185
> ACPI: PCI interrupt 0000:00:1f.2[A] -> GSI 18 (level, low) -> IRQ 185
> ACPI: PCI interrupt 0000:00:1f.3[B] -> GSI 17 (level, low) -> IRQ 201
> ACPI: PCI interrupt 0000:00:1f.5[B] -> GSI 17 (level, low) -> IRQ 201
> ACPI: PCI interrupt 0000:01:00.0[A] -> GSI 16 (level, low) -> IRQ 169
> ACPI: PCI interrupt 0000:02:01.0[A] -> GSI 18 (level, low) -> IRQ 185
> ACPI: PCI interrupt 0000:03:03.0[A] -> GSI 20 (level, low) -> IRQ 209
> ACPI: PCI interrupt 0000:03:0a.0[A] -> GSI 22 (level, low) -> IRQ 217
> testing the IO APIC.......................
> Using vector-based indexing
> .................................... done.
> VFS: Disk quotas dquot_6.5.1
> Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
> devfs: 2004-01-31 Richard Gooch (rgooch@xxxxxxxxxxxxx)
> devfs: boot_options: 0x0
> Initializing Cryptographic API
> isapnp: Scanning for PnP cards...
> isapnp: No Plug & Play device found
> Serial: 8250/16550 driver $Revision: 1.90 $ 54 ports, IRQ sharing enabled
> ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
> ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A
> RAMDISK driver initialized: 16 RAM disks of 8192K size 1024 blocksize
> serio: i8042 AUX port at 0x60,0x64 irq 12
> serio: i8042 KBD port at 0x60,0x64 irq 1
> input: AT Translated Set 2 keyboard on isa0060/serio0
> EISA: Probing bus 0 at eisa0
> EISA: Detected 0 cards.
> NET: Registered protocol family 2
> IP: routing cache hash table of 8192 buckets, 64Kbytes
> TCP: Hash tables configured (established 262144 bind 65536)
> NET: Registered protocol family 8
> NET: Registered protocol family 20
> ACPI: (supports S0 S1 S3 S4 S5)
> RAMDISK: cramfs filesystem found at block 0
> RAMDISK: Loading 4608 blocks [1 disk] into ram disk... | / - \ | / - \ | /
> - \
> | / - \ | / - \ | / - \ | / - \ | / - \ | / - \ | / - \ | / - \ | / - \ |
> / -
> \ | / - \ | / - \ | / - \ | / - \ | / - \ | / - \ | / - \ | / - \ | / - \
> | /
> - \ | / - \ | / - \ | / - \ | / - \ | / - \ | / - \ | / - \ | / - \ | / -
> \ |
> / - \ | / - \ | / - \ | / - \ | / - \ | / - \ | / - \ | / - \ | / - \ | /
> - \
> | / - \ | / - \ | / - \ | / - \ | / - \ | / - \ | / - \ | / - \ | / - \ |
> / -
> \ | / - \ | / - \ | / - \ | / - \ | / - \ | / - \ | / - \ | / - \ | / - \
> | /
> - \ | / - \ | / - \ | / - \ | / - \ | / - \ | / - \ | / - \ | / - \ | / -
> \ |
> / - \ done.
> VFS: Mounted root (cramfs filesystem) readonly.
> Freeing unused kernel memory: 204k freed
> vesafb: probe of vesafb0 failed with error -6
> NET: Registered protocol family 1
> md: md driver 0.90.0 MAX_MD_DEVS=256, MD_SB_DISKS=27
> md: raid1 personality registered as nr 3
> SCSI subsystem initialized
> ACPI: PCI interrupt 0000:00:1f.2[A] -> GSI 18 (level, low) -> IRQ 185
> ata1: SATA max UDMA/133 cmd 0xEFE0 ctl 0xEFAE bmdma 0xEF90 irq 185
> ata2: SATA max UDMA/133 cmd 0xEFA0 ctl 0xEFAA bmdma 0xEF98 irq 185
> ata1: dev 0 ATA, max UDMA/133, 320173056 sectors: lba48
> ata1: dev 0 configured for UDMA/133
> scsi0 : ata_piix
> ata2: dev 0 ATA, max UDMA/133, 320173056 sectors: lba48
> ata2: dev 0 configured for UDMA/133
> scsi1 : ata_piix
> Using anticipatory io scheduler
> Vendor: ATA Model: Maxtor 6Y160M0 Rev: YAR5
> Type: Direct-Access ANSI SCSI revision: 05
> Vendor: ATA Model: Maxtor 6Y160M0 Rev: YAR5
> Type: Direct-Access ANSI SCSI revision: 05
> SCSI device sda: 320173056 512-byte hdwr sectors (163929 MB)
> SCSI device sda: drive cache: write back
> /dev/scsi/host0/bus0/target0/lun0: p1 p2 p3
> Attached scsi disk sda at scsi0, channel 0, id 0, lun 0
> SCSI device sdb: 320173056 512-byte hdwr sectors (163929 MB)
> SCSI device sdb: drive cache: write back
> /dev/scsi/host1/bus0/target0/lun0: p1 p2 p3
> Attached scsi disk sdb at scsi1, channel 0, id 0, lun 0
> device-mapper: 4.1.0-ioctl (2003-12-10) initialised: dm@xxxxxxxxxxxxxx
> md: md0 stopped.
> md: bind<sdb2>
> md: bind<sda2>
> raid1: raid set md0 active with 2 out of 2 mirrors
> devfs_mk_dir: invalid argument.<4>devfs_mk_dir: invalid
> argument.<4>devfs_mk_dev: could not append to parent for /disc
> devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to parent
> for
> /disc
> devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to parent
> for
> /disc
>
> # E così via per circa 144 volte
Ovvio, non ti crea il disc....
ma il modulo devfs è incluso nell'initrd e lo hai inizializzato come
parametro al boot?
> # Qui mi sono accorto si blocca se nella riga di boot di grub si passa
> anche
> # console=ttyS0 console=tty0 (Sarà un altro baco???)
Di chi???? :-)
>
> # E qui il sistema stacca la spina
>
E vorrei vedere...
non è che la stacca, non è riuscito neanche a trovarla ... la spina
Diaolin
--
Ghe gent che come 'l bis la sponge e po sparis
e quei che come 'l tas che a volte no capis
che col nervos ados se fà el zoch che piase al bis
http://www.linuxtrent.it/Members/diaolin/index_html/view
--
Per iscriversi (o disiscriversi), basta spedire un messaggio con OGGETTO
"subscribe" (o "unsubscribe") a mailto:linuxtrent-request@xxxxxxxxxxxxx
Other related posts: