RAID5 unknown partition table

BX787 · 26. August 2013

Hello,

I upgraded to 0.5 and reboot the system. This takes a very long time and I found the following in the logs

Code

[    7.554145] raid5: device sdb operational as raid disk 0
[    7.554148] raid5: device sdc operational as raid disk 2
[    7.554151] raid5: device sdd operational as raid disk 1
[    7.554554] raid5: allocated 3230kB for md0
[    7.554599] 0: w=1 pa=0 pr=3 m=1 a=2 r=3 op1=0 op2=0
[    7.554602] 2: w=2 pa=0 pr=3 m=1 a=2 r=3 op1=0 op2=0
[    7.554605] 1: w=3 pa=0 pr=3 m=1 a=2 r=3 op1=0 op2=0
[    7.554608] raid5: raid level 5 set md0 active with 3 out of 3 devices, algorithm 2
[    7.554611] RAID5 conf printout:
[    7.554613]  --- rd:3 wd:3
[    7.554615]  disk 0, o:1, dev:sdb
[    7.554617]  disk 1, o:1, dev:sdd
[    7.554619]  disk 2, o:1, dev:sdc
[    7.554652] md0: detected capacity change from 0 to 6001183588352
[    7.556361]  md0: unknown partition table
[ 1040.770604] EXT4-fs (md0): mounted filesystem with ordered data mode

Alles anzeigen

Is this a problem? Or can the RAID become broken in the future?

And sorry for my english. I'm from Germany and a german replay is also okay

Greetings

Alex

jensk · 29. August 2013

I have the same error in syslog. I guess It is because you have done the same as me. Make a raid covering the whole device eg. /dev/sdb and not a partition like /dev/sdb1. Then formattet the raid with ext4 or another filesystem.
Then there will be no partition table on niether the disk /dev/sdb nor on the raid /dev/md127.

This should be no cause for alarm except the that there will be this error on boot in /var/log/syslog.

I'm not a raid specialist though - maybe Ryeco have a comment on this?

ryecoaaron · 29. August 2013

That is a strange error. Upgrading OMV doesn't change anything but the web interface. So, that shouldn't cause the problem. What does cat /proc/mdstat show?

BX787 · 30. August 2013

Code

Personalities : [raid6] [raid5] [raid4]
md0 : active raid5 sdb[0] sdc[2] sdd[1]
      5860530848 blocks super 1.2 level 5, 16k chunk, algorithm 2 [3/3] [UUU]


unused devices: <none>

ryecoaaron · 30. August 2013

That looks ok. How about:

fdisk -l

jensk · 30. August 2013

Code

Personalities : [raid6] [raid5] [raid4] 
md127 : active raid6 sdf[10] sde[7] sdc[8] sdd[6] sda[9] sdb[11]
      11721061888 blocks super 1.2 level 6, 128k chunk, algorithm 2 [6/6] [UUUUUU]

Code

Disk /dev/sda: 3000.6 Gb, 3000592982016 byte
255 heads, 63 sectors/track, 364801 cylinders
Units = cylindre of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0x00000000


Disk /dev/sda indeholder ikke en gyldig partitionstabel


.... repeat for al physical disks in my raid


Disk /dev/md127: 12002.4 Gb, 12002367373312 byte
2 heads, 4 sectors/track, -1364701824 cylinders
Units = cylindre of 8 * 512 = 4096 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 131072 bytes / 524288 bytes
Disk identifier: 0x00000000


Disk /dev/md127 indeholder ikke en gyldig partitionstabel

Alles anzeigen

Disk /dev/xxx indeholder ikke en gyldig partitionstabel = the disk /dev/xxx doesn't contain any valid partition table

ryecoaaron · 30. August 2013

All of that is fine. How about:

cat /etc/mdadm/mdadm.conf
mdadm --examine --scan

BX787 · 30. August 2013

cat /proc/mdstat

Code

Personalities : [raid6] [raid5] [raid4]
md0 : active raid5 sdb[0] sdc[2] sdd[1]
      5860530848 blocks super 1.2 level 5, 16k chunk, algorithm 2 [3/3] [UUU]


unused devices: <none>

fdisk -l

Code

Disk /dev/sda: 4059 MB, 4059611136 bytes
255 heads, 63 sectors/track, 493 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x0004f1f8


   Device Boot      Start         End      Blocks   Id  System
/dev/sda1   *           1         467     3747840   83  Linux
Partition 1 does not end on cylinder boundary.
/dev/sda2             467         494      214017    5  Extended
Partition 2 does not end on cylinder boundary.
/dev/sda5             467         494      214016   82  Linux swap / Solaris


Disk /dev/sdb: 3000.6 GB, 3000592982016 bytes
256 heads, 63 sectors/track, 363376 cylinders
Units = cylinders of 16128 * 512 = 8257536 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0x3cee9658


   Device Boot      Start         End      Blocks   Id  System
/dev/sdb1               1      266306  2147483647+  ee  GPT
Partition 1 does not start on physical sector boundary.


Disk /dev/sdd: 3000.6 GB, 3000592982016 bytes
255 heads, 63 sectors/track, 364801 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0x7becca85


   Device Boot      Start         End      Blocks   Id  System


Disk /dev/sdc: 3000.6 GB, 3000592982016 bytes
24 heads, 55 sectors/track, 4439797 cylinders
Units = cylinders of 1320 * 512 = 675840 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0x40c3ca4a


   Device Boot      Start         End      Blocks   Id  System
/dev/sdc1               2      554974   366281728    7  HPFS/NTFS


Disk /dev/md0: 6001.2 GB, 6001183588352 bytes
2 heads, 4 sectors/track, 1465132712 cylinders
Units = cylinders of 8 * 512 = 4096 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 16384 bytes / 32768 bytes
Disk identifier: 0x00000000


Disk /dev/md0 doesn't contain a valid partition table

Alles anzeigen

cat /etc/mdadm/mdadm.conf (Mailaddr changed by me)

Code

# mdadm.conf
#
# Please refer to mdadm.conf(5) for information about this file.
#


# by default, scan all partitions (/proc/partitions) for MD superblocks.
# alternatively, specify devices to scan, using wildcards if desired.
# Note, if no DEVICE line is present, then "DEVICE partitions" is assumed.
# To avoid the auto-assembly of RAID devices a pattern that CAN'T match is
# used if no RAID devices are configured.
DEVICE partitions


# auto-create devices with Debian standard permissions
CREATE owner=root group=disk mode=0660 auto=yes


# automatically tag new arrays as belonging to the local system
HOMEHOST <system>


# definitions of existing MD arrays
ARRAY /dev/md0 metadata=1.2 name=openmediavault:SG01 UUID=8de9f199:c6e4b147:9b8e008d:dde34fc3


# instruct the monitoring daemon where to send mail alerts
MAILADDR xyz
MAILFROM root

Alles anzeigen

mdadm --examine --scan (Command takes about 5 seconds)

Code

ARRAY /dev/md/SG01 metadata=1.2 UUID=8de9f199:c6e4b147:9b8e008d:dde34fc3 name=openmediavault:SG01

ryecoaaron · 30. August 2013

BX787, in your case, you might be getting the error because of leftover partitions on the drives. sdb has a gpt partition, sdc has an NTFS partition, and sdd is clean like it should be. While mdadm should ignore them, I think that is what is causing your problem. I try a few things in a VM to see if you can fix it.

ryecoaaron · 30. August 2013

I tried duplicating your setup and it didn't have the long pause at startup. I was able to remove the unnecessary partitions from the drive without losing data. If you want to try this, please have a backup. While I didn't lose any data, I can not guarantee you won't.

Code

parted /dev/sdb mklabel msdos
parted /dev/sdc mklabel msdos

jensk · 31. August 2013

cat /etc/mdadm/mdadm.onf

Code

# mdadm.conf
#
# Please refer to mdadm.conf(5) for information about this file.
#


# by default, scan all partitions (/proc/partitions) for MD superblocks.
# alternatively, specify devices to scan, using wildcards if desired.
# Note, if no DEVICE line is present, then "DEVICE partitions" is assumed.
# To avoid the auto-assembly of RAID devices a pattern that CAN'T match is
# used if no RAID devices are configured.
DEVICE partitions


# auto-create devices with Debian standard permissions
CREATE owner=root group=disk mode=0660 auto=yes


# automatically tag new arrays as belonging to the local system
HOMEHOST <system>


# definitions of existing MD arrays
ARRAY /dev/md/Storage metadata=1.2 name=LHJ-OMV:Storage UUID=35931a35:3cc54307:0651f2c9:0e317bc2


# instruct the monitoring daemon where to send mail alerts
MAILADDR mymail@mydomain.tld
MAILFROM root

Alles anzeigen

mdadm --examine --scan

Code

ARRAY /dev/md/Storage metadata=1.2 UUID=35931a35:3cc54307:0651f2c9:0e317bc2 name=LHJ-OMV:Storage

ryecoaaron · 31. August 2013

Jensk, your mdadm scan output line should be in your mdadm.conf.

jensk · 31. August 2013

Zitat von "jensk"

Code

# mdadm.conf
#
# Please refer to mdadm.conf(5) for information about this file.
#
...........
.......
# definitions of existing MD arrays
ARRAY /dev/md/Storage metadata=1.2 name=LHJ-OMV:Storage UUID=35931a35:3cc54307:0651f2c9:0e317bc2


# instruct the monitoring daemon where to send mail alerts
MAILADDR mymail@mydomain.tld
MAILFROM root

Alles anzeigen

I believe it is there but I still get:

Code

Aug 31 07:59:58 LHJ-OMV kernel: [    2.704100]  sdb: unknown partition table
Aug 31 07:59:58 LHJ-OMV kernel: [    2.705638]  sdc: unknown partition table
Aug 31 07:59:58 LHJ-OMV kernel: [    2.706284]  sda: unknown partition table
Aug 31 07:59:58 LHJ-OMV kernel: [    2.708119]  sdd: unknown partition table
Aug 31 07:59:58 LHJ-OMV kernel: [    2.708576]  sdf: unknown partition table
Aug 31 07:59:58 LHJ-OMV kernel: [    2.714945]  sde: unknown partition table
Aug 31 07:59:58 LHJ-OMV kernel: [    3.682747]  md127: unknown partition table

in my /var/log/syslog

BX787 · 2. September 2013

ryecoaaron, first of all thank you very much for your help. because i have not enough space i will try it later if i have enough (first i must buy 2 big external hdds). At the moment this error should not be a problem should it?

ryecoaaron · 2. September 2013

It doesn't seem to be since it still mounts (slowly).

jensk · 2. September 2013

Ryeco does it have any implications that i have the same error? I believe i have no old partitions on my drive since they was installed from brand new. I installed them, build the array and formatted the array with ext4 but i didn't make any partiton table on neither the disks nor on the array. I thought this was ok or...?

ryecoaaron · 3. September 2013

Well if you have the same error, maybe it is a specific driver?? I've never had that error and can't find about it. bx787, what mothrtboard? You might have posted but I am on my phone.

BX787 · 10. September 2013

ASRock G31M-GS

dmidecode

Code

# dmidecode 2.9
SMBIOS 2.4 present.
22 structures occupying 1124 bytes.
Table at 0x000FC420.


Handle 0x0000, DMI type 0, 24 bytes
BIOS Information
        Vendor: American Megatrends Inc.
        Version: P1.40
        Release Date: 02/05/2009
        Address: 0xF0000
        Runtime Size: 64 kB
        ROM Size: 512 kB
        Characteristics:
                PCI is supported
                BIOS is upgradeable
                BIOS shadowing is allowed
                Boot from CD is supported
                Selectable boot is supported
                BIOS ROM is socketed
                EDD is supported
                5.25"/1.2 MB floppy services are supported (int 13h)
                3.5"/720 KB floppy services are supported (int 13h)
                3.5"/2.88 MB floppy services are supported (int 13h)
                Print screen service is supported (int 5h)
                8042 keyboard services are supported (int 9h)
                Serial services are supported (int 14h)
                Printer services are supported (int 17h)
                CGA/mono video services are supported (int 10h)
                ACPI is supported
                USB legacy is supported
                LS-120 boot is supported
                ATAPI Zip drive boot is supported
                BIOS boot specification is supported
                Function key-initiated network boot is supported
                Targeted content distribution is supported
        BIOS Revision: 8.14


Handle 0x0001, DMI type 1, 27 bytes
System Information
        Manufacturer: To Be Filled By O.E.M.
        Product Name: To Be Filled By O.E.M.
        Version: To Be Filled By O.E.M.
        Serial Number: To Be Filled By O.E.M.
        UUID: 00020003-0004-0005-0006-000700080009
        Wake-up Type: Power Switch
        SKU Number: To Be Filled By O.E.M.
        Family: To Be Filled By O.E.M.


Handle 0x0002, DMI type 2, 15 bytes
Base Board Information
        Manufacturer: ASRock
        Product Name: G31M-GS
        Version:
        Serial Number:
        Asset Tag:
        Features:
                Board is a hosting board
                Board is replaceable
        Location In Chassis:
        Chassis Handle: 0x0003
        Type: Motherboard
        Contained Object Handles: 0


Handle 0x0003, DMI type 3, 21 bytes
Chassis Information
        Manufacturer: To Be Filled By O.E.M.
        Type: Desktop
        Lock: Not Present
        Version: To Be Filled By O.E.M.
        Serial Number: To Be Filled By O.E.M.
        Asset Tag: To Be Filled By O.E.M.
        Boot-up State: Safe
        Power Supply State: Safe
        Thermal State: Safe
        Security Status: None
        OEM Information: 0x00000000
        Height: Unspecified
        Number Of Power Cords: 1
        Contained Elements: 0


Handle 0x0004, DMI type 4, 35 bytes
Processor Information
        Socket Designation: CPUSocket
        Type: Central Processor
        Family: Pentium 4
        Manufacturer: Intel
        ID: FD 06 00 00 FF FB EB BF
        Signature: Type 0, Family 6, Model 15, Stepping 13
        Flags:
                FPU (Floating-point unit on-chip)
                VME (Virtual mode extension)
                DE (Debugging extension)
                PSE (Page size extension)
                TSC (Time stamp counter)
                MSR (Model specific registers)
                PAE (Physical address extension)
                MCE (Machine check exception)
                CX8 (CMPXCHG8 instruction supported)
                APIC (On-chip APIC hardware supported)
                SEP (Fast system call)
                MTRR (Memory type range registers)
                PGE (Page global enable)
                MCA (Machine check architecture)
                CMOV (Conditional move instruction supported)
                PAT (Page attribute table)
                PSE-36 (36-bit page size extension)
                CLFSH (CLFLUSH instruction supported)
                DS (Debug store)
                ACPI (ACPI supported)
                MMX (MMX technology supported)
                FXSR (Fast floating-point save and restore)
                SSE (Streaming SIMD extensions)
                SSE2 (Streaming SIMD extensions 2)
                SS (Self-snoop)
                HTT (Hyper-threading technology)
                TM (Thermal monitor supported)
                PBE (Pending break enabled)
        Version: Intel(R) Pentium(R) Dual  CPU  E2160  @ 1.80GHz
        Voltage: 1.3 V
        External Clock: 200 MHz
        Max Speed: 1800 MHz
        Current Speed: 1800 MHz
        Status: Populated, Enabled
        Upgrade: Other
        L1 Cache Handle: 0x0005
        L2 Cache Handle: 0x0006
        L3 Cache Handle: Not Provided
        Serial Number: To Be Filled By O.E.M.
        Asset Tag: To Be Filled By O.E.M.
        Part Number: To Be Filled By O.E.M.


Handle 0x0005, DMI type 7, 19 bytes
Cache Information
        Socket Designation: L1-Cache
        Configuration: Enabled, Not Socketed, Level 1
        Operational Mode: Write Back
        Location: Internal
        Installed Size: 64 KB
        Maximum Size: 64 KB
        Supported SRAM Types:
                Other
        Installed SRAM Type: Other
        Speed: Unknown
        Error Correction Type: Parity
        System Type: Data
        Associativity: 8-way Set-associative


Handle 0x0006, DMI type 7, 19 bytes
Cache Information
        Socket Designation: L2-Cache
        Configuration: Enabled, Not Socketed, Level 2
        Operational Mode: Write Back
        Location: Internal
        Installed Size: 1024 KB
        Maximum Size: 1024 KB
        Supported SRAM Types:
                Other
        Installed SRAM Type: Other
        Speed: Unknown
        Error Correction Type: Single-bit ECC
        System Type: Unified
        Associativity: 4-way Set-associative


Handle 0x0007, DMI type 5, 20 bytes
Memory Controller Information
        Error Detecting Method: 64-bit ECC
        Error Correcting Capabilities:
                None
        Supported Interleave: One-way Interleave
        Current Interleave: One-way Interleave
        Maximum Memory Module Size: 4096 MB
        Maximum Total Memory Size: 8192 MB
        Supported Speeds:
                Other
        Supported Memory Types:
                DIMM
                SDRAM
        Memory Module Voltage: 3.3 V
        Associated Memory Slots: 2
                0x0008
                0x0009
        Enabled Error Correcting Capabilities:
                None


Handle 0x0008, DMI type 6, 12 bytes
Memory Module Information
        Socket Designation: DIMM0
        Bank Connections: 0 1
        Current Speed: Unknown
        Type: DIMM SDRAM
        Installed Size: 2048 MB (Double-bank Connection)
        Enabled Size: 2048 MB (Double-bank Connection)
        Error Status: OK


Handle 0x0009, DMI type 6, 12 bytes
Memory Module Information
        Socket Designation: DIMM1
        Bank Connections: 4 5
        Current Speed: Unknown
        Type: DIMM SDRAM
        Installed Size: 2048 MB (Double-bank Connection)
        Enabled Size: 2048 MB (Double-bank Connection)
        Error Status: OK


Handle 0x000A, DMI type 9, 13 bytes
System Slot Information
        Designation: PCI1
        Type: 32-bit PCI
        Current Usage: In Use
        Length: Short
        ID: 1
        Characteristics:
                3.3 V is provided
                Opening is shared
                PME signal is supported


Handle 0x000B, DMI type 9, 13 bytes
System Slot Information
        Designation: PCI2
        Type: 32-bit PCI
        Current Usage: Available
        Length: Short
        ID: 2
        Characteristics:
                3.3 V is provided
                Opening is shared
                PME signal is supported


Handle 0x000C, DMI type 126, 13 bytes
Inactive


Handle 0x000D, DMI type 9, 13 bytes
System Slot Information
        Designation: PCIE2
        Type: x1 PCI Express
        Current Usage: Available
        Length: Short
        ID: 18
        Characteristics:
                3.3 V is provided
                Opening is shared
                PME signal is supported


Handle 0x000E, DMI type 16, 15 bytes
Physical Memory Array
        Location: System Board Or Motherboard
        Use: System Memory
        Error Correction Type: None
        Maximum Capacity: 4 GB
        Error Information Handle: Not Provided
        Number Of Devices: 2


Handle 0x000F, DMI type 19, 15 bytes
Memory Array Mapped Address
        Starting Address: 0x00000000000
        Ending Address: 0x000FFFFFFFF
        Range Size: 4 GB
        Physical Array Handle: 0x000E
        Partition Width: 0


Handle 0x0010, DMI type 17, 27 bytes
Memory Device
        Array Handle: 0x000E
        Error Information Handle: Not Provided
        Total Width: 64 bits
        Data Width: 64 bits
        Size: 2048 MB
        Form Factor: DIMM
        Set: None
        Locator: DIMM0
        Bank Locator: BANK0
        Type: SDRAM
        Type Detail: Synchronous
        Speed: Unknown
        Manufacturer: Manufacturer0
        Serial Number: SerNum0
        Asset Tag: AssetTagNum0
        Part Number: PartNum0


Handle 0x0011, DMI type 20, 19 bytes
Memory Device Mapped Address
        Starting Address: 0x00000000000
        Ending Address: 0x0007FFFFFFF
        Range Size: 2 GB
        Physical Device Handle: 0x0010
        Memory Array Mapped Address Handle: 0x000F
        Partition Row Position: 1
        Interleaved Data Depth: 1


Handle 0x0012, DMI type 17, 27 bytes
Memory Device
        Array Handle: 0x000E
        Error Information Handle: Not Provided
        Total Width: 64 bits
        Data Width: 64 bits
        Size: 2048 MB
        Form Factor: DIMM
        Set: None
        Locator: DIMM1
        Bank Locator: BANK1
        Type: SDRAM
        Type Detail: Synchronous
        Speed: Unknown
        Manufacturer: Manufacturer1
        Serial Number: SerNum1
        Asset Tag: AssetTagNum1
        Part Number: PartNum1


Handle 0x0013, DMI type 20, 19 bytes
Memory Device Mapped Address
        Starting Address: 0x00080000000
        Ending Address: 0x000FFFFFFFF
        Range Size: 2 GB
        Physical Device Handle: 0x0012
        Memory Array Mapped Address Handle: 0x000F
        Partition Row Position: 1
        Interleaved Data Depth: 1


Handle 0x0014, DMI type 32, 20 bytes
System Boot Information
        Status: No errors detected


Handle 0x0015, DMI type 127, 4 bytes
End Of Table

Alles anzeigen

ryecoaaron · 10. September 2013

That board should be fully supported by Debian Squeeze. Maybe a bios issue...

Jetzt mitmachen!