-
FakeRaid error, S/W Raid used..
Hi,
everytime I reboot our NAS-XSR SMB system it will come up with the following error:
Dec 13 15:09:53 nas fakeraid: Fakeraid found on /dev/sdc. Raid type linear. Please use S/W RAID insead of fakeraid. Fakeraid found on /dev/sdd. Raid type linear. Please use S/W RAID insead of fakeraid.
I know from another thread and from other Linux systems this means that the base linux system isn't capable of using the HW RAID provided by the BIOS.
My system runs on an Intel Desktop Board D102GGC2 , which does not have any RAID functionality in its BIOS. The RAID-5 I'm currently using is a SW RAID provided by the NAS-XSR. Why am I seeing this message?
Erwin
-
Are all drives connected to the motherboard? What type of drives SATA? Try to update the BIOS of the motherboard. It could also be a setting in the BIOS that could be causing this.
If this continues please send logs to support@open-e.com
All the best,
Todd Maxwell
-
BIOS is at latest level. All SATA connected to MB.
Which logs should I send?
Here are some parts of the dmesg LOG file:
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
Probing IDE interface ide0...
hda: PQI IDE Secured DiskOnModule, ATA DISK drive
Probing IDE interface ide1...
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
hda: max request size: 128KiB
hda: 512000 sectors (262 MB) w/0KiB Cache, CHS=1000/16/32
hda: cache flushes not supported
hda: hda1 hda2 hda3
PCI: Enabling device 0000:00:13.2 (0000 -> 0002)
ACPI: PCI Interrupt 0000:00:13.2[A] -> GSI 19 (level, low) -> IRQ 16
ehci_hcd 0000:00:13.2: EHCI Host Controller
ehci_hcd 0000:00:13.2: BIOS handoff failed (160, 01010001) <=============
ehci_hcd 0000:00:13.2: continuing after BIOS bug...
ehci_hcd 0000:00:13.2: new USB bus registered, assigned bus number 1
ehci_hcd 0000:00:13.2: irq 16, io mem 0x30202000
ehci_hcd 0000:00:13.2: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004
sata_sil 0000:00:11.0: version 0.9
ACPI: PCI Interrupt 0000:00:11.0[A] -> GSI 23 (level, low) -> IRQ 17
ata1: SATA max UDMA/100 cmd 0xDC836680 ctl 0xDC83668A bmdma 0xDC836600 irq 17
ata2: SATA max UDMA/100 cmd 0xDC8366C0 ctl 0xDC8366CA bmdma 0xDC836608 irq 17
ata1: dev 0 cfg 49:2f00 82:346b 83:7f01 84:4003 85:3469 86:3c01 87:4003 88:203f
ata1: dev 0 ATA-6, max UDMA/100, 625142448 sectors: LBA48
ata1: dev 0 configured for UDMA/100
scsi0 : sata_sil
ata2: dev 0 cfg 49:2f00 82:346b 83:7f01 84:4003 85:3469 86:3c01 87:4003 88:203f
ata2: dev 0 ATA-6, max UDMA/100, 625142448 sectors: LBA48
ata2: dev 0 configured for UDMA/100
scsi1 : sata_sil
Vendor: ATA Model: WDC WD3200JD-00K Rev: 08.0
Type: Direct-Access ANSI SCSI revision: 05
SCSI device sda: 625142448 512-byte hdwr sectors (320073 MB)
SCSI device sda: drive cache: write back
SCSI device sda: 625142448 512-byte hdwr sectors (320073 MB)
SCSI device sda: drive cache: write back
sda: unknown partition table
sd 0:0:0:0: Attached scsi disk sda
Vendor: ATA Model: WDC WD3200JD-00K Rev: 08.0
Type: Direct-Access ANSI SCSI revision: 05
SCSI device sdb: 625142448 512-byte hdwr sectors (320073 MB)
SCSI device sdb: drive cache: write back
SCSI device sdb: 625142448 512-byte hdwr sectors (320073 MB)
SCSI device sdb: drive cache: write back
sdb: unknown partition table
sd 1:0:0:0: Attached scsi disk sdb
ACPI: PCI Interrupt 0000:00:12.0[A] -> GSI 22 (level, low) -> IRQ 18
ata3: SATA max UDMA/100 cmd 0xDC838480 ctl 0xDC83848A bmdma 0xDC838400 irq 18
ata4: SATA max UDMA/100 cmd 0xDC8384C0 ctl 0xDC8384CA bmdma 0xDC838408 irq 18
ata3: dev 0 cfg 49:2f00 82:346b 83:7f01 84:4003 85:3469 86:3c01 87:4003 88:203f
ata3: dev 0 ATA-6, max UDMA/100, 625142448 sectors: LBA48
ata3: dev 0 configured for UDMA/100
scsi2 : sata_sil
ata4: dev 0 cfg 49:2f00 82:346b 83:7f01 84:4003 85:3469 86:3c01 87:4003 88:203f
ata4: dev 0 ATA-6, max UDMA/100, 625142448 sectors: LBA48
ata4: dev 0 configured for UDMA/100
scsi3 : sata_sil
Vendor: ATA Model: WDC WD3200SD-01K Rev: 08.0
Type: Direct-Access ANSI SCSI revision: 05
SCSI device sdc: 625142448 512-byte hdwr sectors (320073 MB)
SCSI device sdc: drive cache: write back
SCSI device sdc: 625142448 512-byte hdwr sectors (320073 MB)
SCSI device sdc: drive cache: write back
sdc: unknown partition table
sd 2:0:0:0: Attached scsi disk sdc
Vendor: ATA Model: WDC WD3200SD-01K Rev: 08.0
Type: Direct-Access ANSI SCSI revision: 05
SCSI device sdd: 625142448 512-byte hdwr sectors (320073 MB)
SCSI device sdd: drive cache: write back
SCSI device sdd: 625142448 512-byte hdwr sectors (320073 MB)
SCSI device sdd: drive cache: write back
sdd: unknown partition table
sd 3:0:0:0: Attached scsi disk sdd
md: md0 stopped.
md: bind<sdb>
md: bind<sdc>
md: bind<sdd>
md: bind<sda>
raid5: device sda operational as raid disk 0
raid5: device sdd operational as raid disk 3
raid5: device sdc operational as raid disk 2
raid5: device sdb operational as raid disk 1
raid5: allocated 4203kB for md0
raid5: raid level 5 set md0 active with 4 out of 4 devices, algorithm 2
RAID5 conf printout:
--- rd:4 wd:4 fd:0
disk 0, o:1, dev:sda
disk 1, o:1, dev:sdb
disk 2, o:1, dev:sdc
disk 3, o:1, dev:sdd
kjournald starting. Commit interval 5 seconds
EXT3 FS on dm-4, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
-
It is saying that it found on /dev/sdc a fake raid. Was this drive added or from another system that had an existing partition? I would have this drive checked out. Also to confirm please download logs and send them to support@open-e.com (All logs).
All the best,
Todd Maxwell
-
It's been a while, but I'm still here
It seems fakeraid is detected on sdc and sdd, ut not on sda and sdb. All 4 drives are part of the same software RAID-5 provided by the NAS-XSR. The only real difference I see is that both the sdc and sdd are RAID Edition verions of Western Digital 250GB SATA drives..... The other two are regular 250GB drives. Could this be the cause?
-
This should not mater. I have set up many non RAID Edition drives mixed with RAID Edition drives and still not have a problem. Now I do recommend using the RAID Edition drives depending on manufacture (I like the Hitachi drives) and keeping continuity of the drive specs.
All the best,
Todd Maxwell
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules