Hozzászólások
Ezek szerint egy particio veget szabad piszkalni, anelkul, hogy a rajta levo file rendszer megerezze?
Vagy mdadmin olyan ugyesen teszi be a superblockot, hogy kozben nem lep ra a file rendszer tyukszemere?
Es kesobb, amikor mar majdnem tele lesz a particio, nem fogja a file rendszer felulirni ezt a md superblockot, azt gondolva hogy ez meg egy ures terulet?
- A hozzászóláshoz be kell jelentkezni
Sziasztok,
Érdekes problémával kapcsolatban szeretnék tanácsokat kérni. A dolog a következő:
Adaptec 1210SA vezerlő + software raid+ 2.6.8 -as kernel, 2 samsung 160-as sata disk
Mivel tudomásom szerint a serial ata diskek hotplug-osak, próbáltam szimulálni egy disk hibát, fogtam és a tükör alól lehúztam az egyik disket.
Erre az adaptec kártyát használva: system hang volt... csak a reset segitett...
Nem fagyott meg a gép, csak nem volt disk művelet. A raid1 nem ment át degraded módba, és nem tudtam tovább használni a gépet.
Az érdekes az, hogy mindezt előtte megcsináltam egy SI3112-es kártyával is, és ott tökéletesen ment a dolog, a rendszer túlélte, a mirror degraded modba váltott, amint észlelte, hogy eltűnt az egyik disk.
Kérdésem, hogy mi lehet ez?
Mindkettő vezérlő a kernelben levő scsi emulalt sata driverrel megy, igaz, hogy a SI3112 kártyának van ott saját modul, adaptecnek nincs. de megy. Lehet ez lenne a baj? vagy pedig a kártya lehet szar hw-esen?
Amúgy mennyi igaz abból, hogy a SATA diszkek hotplugosak?
Köszi
- A hozzászóláshoz be kell jelentkezni
Sziasztok!
Mar eleg sokat olvastam a temaban, de nem tudok rajonni egy problema megoldasara.
Gentoot telepitettem. Raid 1 software raidet hasznalok ket darab sata winyoval. Telepites soran vegig bent volt a 2 kotet a raidben, de a reboot utan nem. mi leget a gond?
ha ujrainditas utan magam hozom letre a kotetet az
mdadm --build dal, akkor a /proc/mdstat alatt szepen latom, hogy bent van mindket kotet a raidben. De bootnal valamiert nem kerul bele.
Itt van par log, a dmesg-rol, grubrol, /proc/mdstat-rol, /etc/raidtab-rol, es par mdadm -D /dev/mdX.
Amit akarok:
md0 {sda2+sdb2}=boot
md1 {sda3+sdb3}=swap
md2 {sda5+sdb5}=/
md3 {sda6+sdb6}=home
Ha van otletetek , akkor lecci irjatok, mert igy mirror nelkul nem tudom/akarom folytatni a telepitest.
/
sda1 technikai okokbol lett windowsos particio
sdb1 ures lemezterulet, ext3-ra formazva
/
[code:1:05831de4cf]
dmesg:
Linux version 2.6.11.11 (root@livecd) (gcc version 3.3.5-20050130 (Gentoo 3.3.5.20050130-r1, ssp-3.3.5.20050130-1, pie-8.7.7.1)) #1 Fri Jun 10 23:18:55 CEST 2005
BIOS-provided physical RAM map:
BIOS-e820: 0000000000000000 - 000000000009f800 (usable)
BIOS-e820: 000000000009f800 - 00000000000a0000 (reserved)
BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
BIOS-e820: 0000000000100000 - 000000000fff0000 (usable)
BIOS-e820: 000000000fff0000 - 000000000fff3000 (ACPI NVS)
BIOS-e820: 000000000fff3000 - 0000000010000000 (ACPI data)
BIOS-e820: 00000000fec00000 - 00000000fec01000 (reserved)
BIOS-e820: 00000000fee00000 - 00000000fee01000 (reserved)
BIOS-e820: 00000000ffff0000 - 0000000100000000 (reserved)
255MB LOWMEM available.
On node 0 totalpages: 65520
DMA zone: 4096 pages, LIFO batch:1
Normal zone: 61424 pages, LIFO batch:14
HighMem zone: 0 pages, LIFO batch:1
DMI 2.2 present.
ACPI: RSDP (v000 Nvidia ) @ 0x000f7550
ACPI: RSDT (v001 Nvidia AWRDACPI 0x42302e31 AWRD 0x00000000) @ 0x0fff3000
ACPI: FADT (v001 Nvidia AWRDACPI 0x42302e31 AWRD 0x00000000) @ 0x0fff3040
ACPI: MADT (v001 Nvidia AWRDACPI 0x42302e31 AWRD 0x00000000) @ 0x0fff79c0
ACPI: DSDT (v001 NVIDIA AWRDACPI 0x00001000 MSFT 0x0100000e) @ 0x00000000
Allocating PCI resources starting at 10000000 (gap: 10000000:eec00000)
Built 1 zonelists
Kernel command line: root=/dev/md2 udev
Initializing CPU#0
PID hash table entries: 1024 (order: 10, 16384 bytes)
Detected 1603.874 MHz processor.
Using tsc for high-res timesource
Console: colour VGA+ 80x25
Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
Memory: 255988k/262080k available (1929k kernel code, 5516k reserved, 771k data, 168k init, 0k highmem)
Checking if this processor honours the WP bit even in supervisor mode... Ok.
Calibrating delay loop... 3162.11 BogoMIPS (lpj=1581056)
Mount-cache hash table entries: 512 (order: 0, 4096 bytes)
CPU: After generic identify, caps: 0383fbff c1cbfbff 00000000 00000000 00000000 00000000 00000000
CPU: After vendor identify, caps: 0383fbff c1cbfbff 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: 0383fbff c1cbfbff 00000000 00000020 00000000 00000000 00000000
Intel machine check architecture supported.
Intel machine check reporting enabled on CPU#0.
CPU: AMD Athlon(tm) XP 1900+ stepping 02
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Checking 'hlt' instruction... OK.
ACPI: setting ELCR to 0200 (from 1c28)
NET: Registered protocol family 16
PCI: PCI BIOS revision 2.10 entry at 0xfbc60, last bus=2
PCI: Using configuration type 1
mtrr: v2.0 (20020519)
ACPI: Subsystem revision 20050211
ACPI: Interpreter enabled
ACPI: Using PIC for interrupt routing
ACPI: PCI Root Bridge [PCI0] (00:00)
PCI: Probing PCI hardware (bus 00)
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.HUB0._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.AGPB._PRT]
ACPI: PCI Interrupt Link [LNK1] (IRQs 3 4 5 6 7 10 11 *12 14 15)
ACPI: PCI Interrupt Link [LNK2] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
ACPI: PCI Interrupt Link [LNK3] (IRQs 3 4 5 6 7 10 *11 12 14 15)
ACPI: PCI Interrupt Link [LNK4] (IRQs 3 4 5 6 7 *10 11 12 14 15)
ACPI: PCI Interrupt Link [LNK5] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
ACPI: PCI Interrupt Link [LUBA] (IRQs 3 4 5 6 7 10 11 *12 14 15)
ACPI: PCI Interrupt Link [LUBB] (IRQs 3 4 5 6 7 *10 11 12 14 15)
ACPI: PCI Interrupt Link [LMAC] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
ACPI: PCI Interrupt Link [LAPU] (IRQs *3 4 5 6 7 10 11 12 14 15)
ACPI: PCI Interrupt Link [LACI] (IRQs 3 4 *5 6 7 10 11 12 14 15)
ACPI: PCI Interrupt Link [LMCI] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
ACPI: PCI Interrupt Link [LSMB] (IRQs 3 4 *5 6 7 10 11 12 14 15)
ACPI: PCI Interrupt Link [LUB2] (IRQs 3 4 5 6 7 10 *11 12 14 15)
ACPI: PCI Interrupt Link [LFIR] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
ACPI: PCI Interrupt Link [L3CM] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
ACPI: PCI Interrupt Link [LIDE] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
ACPI: PCI Interrupt Link [APC1] (IRQs *16), disabled.
ACPI: PCI Interrupt Link [APC2] (IRQs *17), disabled.
ACPI: PCI Interrupt Link [APC3] (IRQs *18), disabled.
ACPI: PCI Interrupt Link [APC4] (IRQs *19), disabled.
ACPI: PCI Interrupt Link [APC5] (IRQs *16), disabled.
ACPI: PCI Interrupt Link [APCF] (IRQs 20 21 22) *0, disabled.
ACPI: PCI Interrupt Link [APCG] (IRQs 20 21 22) *0, disabled.
ACPI: PCI Interrupt Link [APCH] (IRQs 20 21 22) *0, disabled.
ACPI: PCI Interrupt Link [APCI] (IRQs 20 21 22) *0, disabled.
ACPI: PCI Interrupt Link [APCJ] (IRQs 20 21 22) *0, disabled.
ACPI: PCI Interrupt Link [APCK] (IRQs 20 21 22) *0, disabled.
ACPI: PCI Interrupt Link [APCS] (IRQs *23), disabled.
ACPI: PCI Interrupt Link [APCL] (IRQs 20 21 22) *0, disabled.
ACPI: PCI Interrupt Link [APCM] (IRQs 20 21 22) *0, disabled.
ACPI: PCI Interrupt Link [AP3C] (IRQs 20 21 22) *0, disabled.
ACPI: PCI Interrupt Link [APCZ] (IRQs 20 21 22) *0, disabled.
Linux Plug and Play Support v0.97 (c) Adam Belay
pnp: PnP ACPI init
pnp: PnP ACPI: found 12 devices
PnPBIOS: Disabled by ACPI PNP
SCSI subsystem initialized
PCI: Using ACPI for IRQ routing
** PCI interrupts are no longer routed automatically. If this
** causes a device to stop working, it is probably because the
** driver failed to call pci_enable_device(). As a temporary
** workaround, the "pci=routeirq" argument restores the old
** behavior. If this argument makes the device work again,
** please email the output of "lspci" to bjorn.helgaas@hp.com
** so I can fix the driver.
pnp: 00:00: ioport range 0x4000-0x407f could not be reserved
pnp: 00:00: ioport range 0x4080-0x40ff has been reserved
pnp: 00:00: ioport range 0x4400-0x447f has been reserved
pnp: 00:00: ioport range 0x4480-0x44ff could not be reserved
pnp: 00:00: ioport range 0x4200-0x427f has been reserved
pnp: 00:00: ioport range 0x4280-0x42ff has been reserved
pnp: 00:01: ioport range 0x5000-0x503f has been reserved
pnp: 00:01: ioport range 0x5100-0x513f has been reserved
Machine check exception polling timer started.
VFS: Disk quotas dquot_6.5.1
Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
Initializing Cryptographic API
ACPI: Power Button (FF) [PWRF]
ACPI: Thermal Zone [THRM] (20 C)
Linux agpgart interface v0.100 (c) Dave Jones
agpgart: Detected NVIDIA nForce2 chipset
agpgart: Maximum main memory to use for agp memory: 203M
agpgart: AGP aperture is 64M @ 0xd8000000
serio: i8042 AUX port at 0x60,0x64 irq 12
serio: i8042 KBD port at 0x60,0x64 irq 1
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered
RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize
loop: loaded (max 8 devices)
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
NFORCE2: IDE controller at PCI slot 0000:00:09.0
NFORCE2: chipset revision 162
NFORCE2: not 100% native mode: will probe irqs later
NFORCE2: 0000:00:09.0 (rev a2) UDMA133 controller
ide0: BM-DMA at 0xf000-0xf007, BIOS settings: hda:DMA, hdb:DMA
ide1: BM-DMA at 0xf008-0xf00f, BIOS settings: hdc:DMA, hdd:DMA
Probing IDE interface ide0...
Probing IDE interface ide1...
hdc: _NEC DVD_RW ND-3500AG, ATAPI CD/DVD-ROM drive
ide1 at 0x170-0x177,0x376 on irq 15
Probing IDE interface ide0...
Probing IDE interface ide2...
Probing IDE interface ide3...
Probing IDE interface ide4...
Probing IDE interface ide5...
libata version 1.10 loaded.
sata_sil version 0.8
ACPI: PCI Interrupt Link [LNK3] enabled at IRQ 11
PCI: setting IRQ 11 as level-triggered
ACPI: PCI interrupt 0000:01:0b.0[A] -> GSI 11 (level, low) -> IRQ 11
ata1: SATA max UDMA/100 cmd 0xD080E080 ctl 0xD080E08A bmdma 0xD080E000 irq 11
ata2: SATA max UDMA/100 cmd 0xD080E0C0 ctl 0xD080E0CA bmdma 0xD080E008 irq 11
ata1: dev 0 cfg 49:2f00 82:74eb 83:7fea 84:4023 85:74e9 86:3c02 87:4023 88:203f
ata1: dev 0 ATA, max UDMA/100, 321672960 sectors: lba48
ata1: dev 0 configured for UDMA/100
scsi0 : sata_sil
ata2: dev 0 cfg 49:2f00 82:74eb 83:7fea 84:4023 85:74e9 86:3c02 87:4023 88:203f
ata2: dev 0 ATA, max UDMA/100, 321672960 sectors: lba48
ata2: dev 0 configured for UDMA/100
scsi1 : sata_sil
Vendor: ATA Model: HDS722516VLSA80 Rev: V34O
Type: Direct-Access ANSI SCSI revision: 05
Vendor: ATA Model: HDS722516VLSA80 Rev: V34O
Type: Direct-Access ANSI SCSI revision: 05
SCSI device sda: 321672960 512-byte hdwr sectors (164697 MB)
SCSI device sda: drive cache: write back
SCSI device sda: 321672960 512-byte hdwr sectors (164697 MB)
SCSI device sda: drive cache: write back
sda: sda1 sda2 sda3 sda4 < sda5 sda6 sda7 sda8 sda9 >
Attached scsi disk sda at scsi0, channel 0, id 0, lun 0
SCSI device sdb: 321672960 512-byte hdwr sectors (164697 MB)
SCSI device sdb: drive cache: write back
SCSI device sdb: 321672960 512-byte hdwr sectors (164697 MB)
SCSI device sdb: drive cache: write back
sdb: sdb1 sdb2 sdb3 sdb4 < sdb5 sdb6 sdb7 >
Attached scsi disk sdb at scsi1, channel 0, id 0, lun 0
Attached scsi generic sg0 at scsi0, channel 0, id 0, lun 0, type 0
Attached scsi generic sg1 at scsi1, channel 0, id 0, lun 0, type 0
mice: PS/2 mouse device common for all mice
input: AT Translated Set 2 keyboard on isa0060/serio0
md: raid0 personality registered as nr 2
md: raid1 personality registered as nr 3
md: faulty personality registered as nr 10
md: md driver 0.90.1 MAX_MD_DEVS=256, MD_SB_DISKS=27
NET: Registered protocol family 2
IP: routing cache hash table of 2048 buckets, 16Kbytes
TCP established hash table entries: 16384 (order: 5, 131072 bytes)
TCP bind hash table entries: 16384 (order: 4, 65536 bytes)
TCP: Hash tables configured (established 16384 bind 16384)
NET: Registered protocol family 1
NET: Registered protocol family 17
NET: Registered protocol family 15
ACPI wakeup devices:
HUB0 HUB1 USB0 USB1 USB2 F139 MMAC MMCI UAR1
ACPI: (supports S0 S1 S4 S5)
md: Autodetecting RAID arrays.
md: autorun ...
md: considering sdb6 ...
md: adding sdb6 ...
md: sdb5 has different UUID to sdb6
md: sdb3 has different UUID to sdb6
md: sdb2 has different UUID to sdb6
md: adding sda6 ...
md: sda5 has different UUID to sdb6
md: sda3 has different UUID to sdb6
md: sda2 has different UUID to sdb6
md: created md3
md: bind<sda6>
md: export_rdev(sdb6)
md: running: <sda6>
raid1: raid set md3 active with 1 out of 2 mirrors
md: considering sdb5 ...
md: adding sdb5 ...
md: sdb3 has different UUID to sdb5
md: sdb2 has different UUID to sdb5
md: adding sda5 ...
md: sda3 has different UUID to sdb5
md: sda2 has different UUID to sdb5
md: created md2
md: bind<sda5>
md: export_rdev(sdb5)
md: running: <sda5>
raid1: raid set md2 active with 1 out of 2 mirrors
md: considering sdb3 ...
md: adding sdb3 ...
md: sdb2 has different UUID to sdb3
md: adding sda3 ...
md: sda2 has different UUID to sdb3
md: created md1
md: bind<sda3>
md: export_rdev(sdb3)
md: running: <sda3>
raid1: raid set md1 active with 1 out of 2 mirrors
md: considering sdb2 ...
md: adding sdb2 ...
md: adding sda2 ...
md: created md0
md: bind<sda2>
md: export_rdev(sdb2)
md: running: <sda2>
raid1: raid set md0 active with 1 out of 2 mirrors
md: ... autorun DONE.
EXT3-fs: mounted filesystem with ordered data mode.
VFS: Mounted root (ext3 filesystem) readonly.
Freeing unused kernel memory: 168k freed
kjournald starting. Commit interval 5 seconds
Adding 1108408k swap on /dev/md1. Priority:-1 extents:1
EXT3 FS on md2, internal journal
ACPI: PCI interrupt 0000:01:0a.0[A] -> GSI 11 (level, low) -> IRQ 11
3c59x: Donald Becker and others. www.scyld.com/network/vortex.html
0000:01:0a.0: 3Com PCI 3c905 Boomerang 100baseTx at 0x9000. Vers LK1.1.19
eth0: Dropping NETIF_F_SG since no checksum feature.
kjournald starting. Commit interval 5 seconds
EXT3 FS on md3, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
usbcore: registered new driver usbfs
usbcore: registered new driver hub
ACPI: PCI interrupt 0000:01:0a.0[A] -> GSI 11 (level, low) -> IRQ 11
/etc/raidtab
raiddev /dev/md0
raid-level 1
nr-raid-disks 2
nr-spare-disks 0
persistent-superblock 1
device /dev/sda2
raid-disk 0
device /dev/sdb2
raid-disk 1
raiddev /dev/md1
raid-level 1
nr-raid-disks 2
nr-spare-disks 0
persistent-superblock 1
device /dev/sda3
raid-disk 0
device /dev/sdb3
raid-disk 1
raiddev /dev/md2
raid-level 1
nr-raid-disks 2
nr-spare-disks 0
persistent-superblock 1
device /dev/sda5
raid-disk 0
device /dev/sdb5
raid-disk 1
raiddev /dev/md3
raid-level 1
nr-raid-disks 2
nr-spare-disks 0
persistent-superblock 1
device /dev/sda6
raid-disk 0
device /dev/sdb6
raid-disk 1
/proc/mdstat
Personalities : [raid0] [raid1] [faulty]
md1 : active raid1 sda3[0]
1108416 blocks [2/1] [U_]
md2 : active raid1 sda5[0]
40049920 blocks [2/1] [U_]
md3 : active raid1 sda6[0]
40049920 blocks [2/1] [U_]
md0 : active raid1 sda2[0]
176640 blocks [2/1] [U_]
unused devices: <none>
/boot/grub/menu.lst
default 0
timeout 30
title = BorzLinux
root (hd0,1)
kernel /boot/vmlinuz root=/dev/md2 udev
/proc/partitions
major minor #blocks name
8 0 160836480 sda
8 1 8032468 sda1
8 2 176715 sda2
8 3 1108485 sda3
8 4 1 sda4
8 5 40050013 sda5
8 6 40050013 sda6
8 7 24418768 sda7
8 8 9775521 sda8
8 9 37214541 sda9
8 16 160836480 sdb
8 17 8032468 sdb1
8 18 176715 sdb2
8 19 1108485 sdb3
8 20 1 sdb4
8 21 40050013 sdb5
8 22 40050013 sdb6
8 23 71416926 sdb7
9 0 176640 md0
9 3 40049920 md3
9 2 40049920 md2
9 1 1108416 md1
mdstat -D /dev/mdX
/dev/md0:
Version : 00.90.01
Creation Time : Fri Jun 10 13:19:23 2005
Raid Level : raid1
Array Size : 176640 (172.50 MiB 180.88 MB)
Device Size : 176640 (172.50 MiB 180.88 MB)
Raid Devices : 2
Total Devices : 1
Preferred Minor : 0
Persistence : Superblock is persistent
Update Time : Sat Jun 11 16:21:51 2005
State : clean, degraded
Active Devices : 1
Working Devices : 1
Failed Devices : 0
Spare Devices : 0
UUID : a8d77b98:56a952ae:f6c8e10b:311ccdb3
Events : 0.100
Number Major Minor RaidDevice State
0 8 2 0 active sync /dev/sda2
1 0 0 - removed
/dev/md1:
Version : 00.90.01
Creation Time : Fri Jun 10 13:22:22 2005
Raid Level : raid1
Array Size : 1108416 (1082.44 MiB 1135.02 MB)
Device Size : 1108416 (1082.44 MiB 1135.02 MB)
Raid Devices : 2
Total Devices : 1
Preferred Minor : 1
Persistence : Superblock is persistent
Update Time : Sat Jun 11 00:31:40 2005
State : clean, degraded
Active Devices : 1
Working Devices : 1
Failed Devices : 0
Spare Devices : 0
UUID : 744333ec:32be630a:94b7078d:3117ca84
Events : 0.92
Number Major Minor RaidDevice State
0 8 3 0 active sync /dev/sda3
1 0 0 - removed
/dev/md2:
Version : 00.90.01
Creation Time : Fri Jun 10 13:23:25 2005
Raid Level : raid1
Array Size : 40049920 (38.19 GiB 41.01 GB)
Device Size : 40049920 (38.19 GiB 41.01 GB)
Raid Devices : 2
Total Devices : 1
Preferred Minor : 2
Persistence : Superblock is persistent
Update Time : Sat Jun 11 16:23:27 2005
State : clean, degraded
Active Devices : 1
Working Devices : 1
Failed Devices : 0
Spare Devices : 0
UUID : 090c8051:8e4df2c1:0abb5fed:47d33747
Events : 0.10162
Number Major Minor RaidDevice State
0 8 5 0 active sync /dev/sda5
1 0 0 - removed
/dev/md3:
Version : 00.90.01
Creation Time : Fri Jun 10 13:23:54 2005
Raid Level : raid1
Array Size : 40049920 (38.19 GiB 41.01 GB)
Device Size : 40049920 (38.19 GiB 41.01 GB)
Raid Devices : 2
Total Devices : 1
Preferred Minor : 3
Persistence : Superblock is persistent
Update Time : Sat Jun 11 16:18:21 2005
State : clean, degraded
Active Devices : 1
Working Devices : 1
Failed Devices : 0
Spare Devices : 0
UUID : f68a9801:8b63904b:147ad424:57e852e8
Events : 0.28
Number Major Minor RaidDevice State
0 8 6 0 active sync /dev/sda6
1 0 0 - removed
[/code:1:05831de4cf]
- A hozzászóláshoz be kell jelentkezni
Azt elárulod, hogy minek van /etc/raidtab? A még raidtools2-ből származik, mdadm-nek nem kell. Lehe, hogy ez kavar be. Nekem megfelelő kernellel raidtab, initrd stb nélül simán megy...
- A hozzászóláshoz be kell jelentkezni
[quote:6f99cfa43d="bitumen"]Azt elárulod, hogy minek van /etc/raidtab? A még raidtools2-ből származik, mdadm-nek nem kell. Lehe, hogy ez kavar be. Nekem megfelelő kernellel raidtab, initrd stb nélül simán megy...
Ezt nem tudtam. Le is torlom mindjart.
Amugy raktam fel raidutils es raidtoos progikat is. Azok gondolom maradhatnak.
- A hozzászóláshoz be kell jelentkezni
Bar kozvetve a dmesg md resze utal ra, de a particio tipusa fd?
- A hozzászóláshoz be kell jelentkezni
[quote:90210395c1="soky"]Bar kozvetve a dmesg md resze utal ra, de a particio tipusa fd?
Igen, a particio tipusokat mindegyik satas particion, ami a raid tomben szerepelne fd re allitottam, de csak miutan mar a stage1,2,3 felment a gepre. addig siman ext3-om vol.
De a logok amiket ,mar bemasoltam, azok mar az atirt tipusok utan keletkeztek.
Viszont most eszre vettem egy erdekesseget!
Amikor ujra letrehoztam a raid tombot , akkor azt irja, hogy
superblock is not persistent
Nem lehet hogy ez a gond. A tomb jol mukodnek, mindegyikben mindket winyo particioja is benne van.
Hogy tudom perzisztense tenni?adatvesztes es reinstall nelkul
- A hozzászóláshoz be kell jelentkezni
Szerintem nem nagyon lehet utolag ratenni a superblockot.
En ArchLinuxot telepitettem a napokban sata disk-ekre, de a telepites elott hoztam letre a raid tomboket mdadm-al. Akkor kiirta, hogy letrehozta a persistent superblock-ot, ami miatt kisebb is a particio, mert ez a vegen van. Ez utan hoztam letre a file-rendszereket. Az egeszet Arch Wiki alapjan csinaltam, csak az LVM-et kihagytam belole, elsore ez is eleg volt nekem...
Boot utan, dmesgben hasonloan epitgeti fel a tomboket, idezni csak munkaidoben tudnek belole, mivel a munkahelyen csinaltam.
- A hozzászóláshoz be kell jelentkezni
[quote:5d57f0718b="borz"][quote:5d57f0718b="soky"]Bar kozvetve a dmesg md resze utal ra, de a particio tipusa fd?
Igen, a particio tipusokat mindegyik satas particion, ami a raid tomben szerepelne fd re allitottam, de csak miutan mar a stage1,2,3 felment a gepre. addig siman ext3-om vol.
De a logok amiket ,mar bemasoltam, azok mar az atirt tipusok utan keletkeztek.
Viszont most eszre vettem egy erdekesseget!
Amikor ujra letrehoztam a raid tombot , akkor azt irja, hogy
superblock is not persistent
Nem lehet hogy ez a gond. A tomb jol mukodnek, mindegyikben mindket winyo particioja is benne van.
Hogy tudom perzisztense tenni?adatvesztes es reinstall nelkul
Na ugy nez ki, sikerult megoldanom.
Utoljara nem az admd --build dal hoztam letre a tombot, hanem a --create-val.
Igy letrehozott uj superblokkot. Es megy minden.
- A hozzászóláshoz be kell jelentkezni