LinuxQuestions.org
Welcome to the most active Linux Forum on the web.
Home Forums Tutorials Articles Register
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Hardware
Reload this Page [SOLVED] Software Raid
User Name
Password
Linux - Hardware This forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?

Notices


Reply
  Search this Thread
Old 10-25-2011, 09:51 PM   #1
spwnt
Member
 
Registered: Jun 2006
Distribution: Linux Mint/Debian/Arch
Posts: 78

Rep: Reputation: 12
Software Raid

so I'm running a software raid5 with 6 3 tb harddrives with 8 gigs of ram and a 1.6 ghz amd fusion cpu dual core, and my processor is getting a serious workout. constantly at 50-80 percent of the full load. i know that it has to do parity while writing, but this just seems a little much to me. i can deal with it if this is how it's gunna be but it seems a little off.

ubuntu 11.10 server edition running unity.

dmesg says this "[ 3.689932] md/raid:md0: not clean -- starting background reconstruction"

but it also says this "[ 3.691314] md/raid:md0: raid level 5 active with 6 out of 6 devices, algorithm 2"

what's going on? I just built the raid.. and it says all the devices are working.. why would it need to reconstruct anything?

top output
Code:
  284 root      20   0     0    0    0 R   48  0.0   1181:59 md0_resync         
  283 root      20   0     0    0    0 S   30  0.0 803:40.60 md0_raid5          
 2454 anonymou  20   0  527m  37m  18m R   20  0.5 512:34.30 gnome-system-mo    
 1712 anonymou  20   0  664m  89m  24m R   18  1.2   1:00.61 firefox            
 2608 root      20   0 59848  31m  888 D   15  0.4 505:16.35 rsync              
 1978 anonymou  20   0  746m  93m  24m R   13  1.2 263:25.42 compiz             
 2544 root      20   0 18516 3908  708 D    9  0.1 240:56.20 mount.ntfs         
 1467 root      20   0  196m  48m 9412 S    8  0.6 398:14.52
part of dmesg output

Code:
[    0.000000] Linux version 3.0.0-12-generic (buildd@crested) (gcc version 4.6.1 (Ubuntu/Linaro 4.6.1-9ubuntu3) ) #20-Ubuntu SMP Fri Oct 7 14:56:25 UTC 2011 (Ubuntu 3.0.0-12.20-generic 3.0.4)
[    0.000000] Command line: BOOT_IMAGE=/vmlinuz-3.0.0-12-generic root=/dev/mapper/sdg5_crypt ro splash quiet vt.handoff=7
[    0.000000] KERNEL supported cpus:
[    0.000000]   Intel GenuineIntel
[    0.000000]   AMD AuthenticAMD
[    0.000000]   Centaur CentaurHauls
[    0.000000] NX (Execute Disable) protection: active
[    0.000000] DMI 2.6 present.
[    0.000000] DMI: System manufacturer System Product Name/E35M1-I, 
[    2.548634] ata1.00: ATA-8: Hitachi HDS5C3030ALA630, MEAOA5C0, max UDMA/133
[    2.548641] ata1.00: 5860533168 sectors, multi 16: LBA48 NCQ (depth 0/32)
[    2.548897] ata1.01: ATA-8: Hitachi HDS5C3030ALA630, MEAOA5C0, max UDMA/133
[    2.548905] ata1.01: 5860533168 sectors, multi 16: LBA48 NCQ (depth 0/32)
[    2.548916] ata1.00: limited to UDMA/33 due to 40-wire cable
[    2.548920] ata1.01: limited to UDMA/33 due to 40-wire cable
[    2.556658] ata1.00: configured for UDMA/33
[    2.564664] ata1.01: configured for UDMA/33
[    2.564898] scsi 0:0:0:0: Direct-Access     ATA      Hitachi HDS5C303 MEAO PQ: 0 ANSI: 5
[    2.565197] sd 0:0:0:0: Attached scsi generic sg0 type 0
[    2.565384] scsi 0:0:1:0: Direct-Access     ATA      Hitachi HDS5C303 MEAO PQ: 0 ANSI: 5
[    2.565577] sd 0:0:1:0: Attached scsi generic sg1 type 0
[    2.565729] sd 0:0:1:0: [sdb] 5860533168 512-byte logical blocks: (3.00 TB/2.72 TiB)
[    2.565837] sd 0:0:1:0: [sdb] Write Protect is off
[    2.565842] sd 0:0:1:0: [sdb] Mode Sense: 00 3a 00 00
[    2.565888] sd 0:0:1:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[    2.589736] [drm] fb mappable at 0xC0141000
[    2.589739] [drm] vram apper at 0xC0000000
[    2.589742] [drm] size 5242880
[    2.589744] [drm] fb depth is 24
[    2.589746] [drm]    pitch is 5120
[    2.589859] fbcon: radeondrmfb (fb0) is primary device
[    2.590509] Console: switching to colour frame buffer device 160x64
[    2.590562] fb0: radeondrmfb frame buffer device
[    2.590565] drm: registered panic notifier
[    2.590576] [drm] Initialized radeon 2.10.0 20080528 for 0000:00:01.0 on minor 0
[    2.596315] usb 4-1: new low speed USB device number 2 using ohci_hcd
[    2.604353] sd 0:0:0:0: [sda] 5860533168 512-byte logical blocks: (3.00 TB/2.72 TiB)
[    2.605544] sd 0:0:0:0: [sda] Write Protect is off
[    2.605556] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
[    2.606591] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[    2.639590]  sdb: sdb1
[    2.715507] sd 0:0:1:0: [sdb] Attached SCSI disk
[    2.716334]  sda: sda1
[    2.716881] sd 0:0:0:0: [sda] Attached SCSI disk
[    2.876309] ata4: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[    2.876349] ata3: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[    2.878227] ata3.00: ATA-8: Hitachi HDS5C3030ALA630, MEAOA5C0, max UDMA/133
[    2.878235] ata3.00: 5860533168 sectors, multi 16: LBA48 NCQ (depth 31/32), AA
[    2.878276] ata4.00: ATA-8: Hitachi HDS5C3030ALA630, MEAOA5C0, max UDMA/133
[    2.878284] ata4.00: 5860533168 sectors, multi 16: LBA48 NCQ (depth 31/32), AA
[    2.880099] ata6: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[    2.880136] ata5: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[    2.880508] ata3.00: configured for UDMA/133
[    2.880551] ata4.00: configured for UDMA/133
[    2.881014] scsi 2:0:0:0: Direct-Access     ATA      Hitachi HDS5C303 MEAO PQ: 0 ANSI: 5
[    2.881347] sd 2:0:0:0: [sdc] 5860533168 512-byte logical blocks: (3.00 TB/2.72 TiB)
[    2.881357] sd 2:0:0:0: Attached scsi generic sg2 type 0
[    2.881491] sd 2:0:0:0: [sdc] Write Protect is off
[    2.881497] sd 2:0:0:0: [sdc] Mode Sense: 00 3a 00 00
[    2.881538] sd 2:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[    2.881662] scsi 3:0:0:0: Direct-Access     ATA      Hitachi HDS5C303 MEAO PQ: 0 ANSI: 5
[    2.881698] ata5.00: ATA-8: Hitachi HDS5C3030ALA630, MEAOA5C0, max UDMA/133
[    2.881712] ata5.00: 5860533168 sectors, multi 16: LBA48 NCQ (depth 31/32), AA
[    2.881889] sd 3:0:0:0: Attached scsi generic sg3 type 0
[    2.882019] sd 3:0:0:0: [sdd] 5860533168 512-byte logical blocks: (3.00 TB/2.72 TiB)
[    2.882077] ata6.00: ATA-8: Hitachi HDS5C3030ALA630, MEAOA5C0, max UDMA/133
[    2.882082] ata6.00: 5860533168 sectors, multi 16: LBA48 NCQ (depth 31/32), AA
[    2.882133] sd 3:0:0:0: [sdd] Write Protect is off
[    2.882138] sd 3:0:0:0: [sdd] Mode Sense: 00 3a 00 00
[    2.882186] sd 3:0:0:0: [sdd] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[    2.883700] ata5.00: configured for UDMA/133
[    2.883749] ata6.00: configured for UDMA/133
[    2.884085] scsi 4:0:0:0: Direct-Access     ATA      Hitachi HDS5C303 MEAO PQ: 0 ANSI: 5
[    2.884425] sd 4:0:0:0: Attached scsi generic sg4 type 0
[    2.884612] sd 4:0:0:0: [sde] 5860533168 512-byte logical blocks: (3.00 TB/2.72 TiB)
[    2.884734] scsi 5:0:0:0: Direct-Access     ATA      Hitachi HDS5C303 MEAO PQ: 0 ANSI: 5
[    2.884750] sd 4:0:0:0: [sde] Write Protect is off
[    2.884756] sd 4:0:0:0: [sde] Mode Sense: 00 3a 00 00
[    2.884802] sd 4:0:0:0: [sde] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[    2.885040] sd 5:0:0:0: [sdf] 5860533168 512-byte logical blocks: (3.00 TB/2.72 TiB)
[    2.885075] sd 5:0:0:0: Attached scsi generic sg5 type 0
[    2.885143] sd 5:0:0:0: [sdf] Write Protect is off
[    2.885148] sd 5:0:0:0: [sdf] Mode Sense: 00 3a 00 00
[    2.885193] sd 5:0:0:0: [sdf] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[    2.931328]  sdc: sdc1
[    2.932348] sd 2:0:0:0: [sdc] Attached SCSI disk
[    2.933642]  sdd: sdd1
[    2.934507] sd 3:0:0:0: [sdd] Attached SCSI disk
[    2.961632]  sde: sde1
[    2.962203]  sdf: sdf1
[    2.962212] sd 4:0:0:0: [sde] Attached SCSI disk
[    2.963228] sd 5:0:0:0: [sdf] Attached SCSI disk
[    2.965593] Initializing USB Mass Storage driver...
[    2.971444] scsi6 : usb-storage 1-3:1.0
[    2.972846] usbcore: registered new interface driver usb-storage
[    2.972853] USB Mass Storage support registered.
[    2.980120] input: USB Mouse as /devices/pci0000:00/0000:00:12.0/usb4/4-1/4-1:1.0/input/input3
[    2.980390] generic-usb 0003:04F3:0216.0001: input,hidraw0: USB HID v1.11 Mouse [USB Mouse] on usb-0000:00:12.0-1/input0
[    2.980423] usbcore: registered new interface driver usbhid
[    2.980427] usbhid: USB HID core driver
[    3.102906] md: bind<sdd1>
[    3.156570] md: bind<sda1>
[    3.165458] md: bind<sde1>
[    3.170998] md: bind<sdb1>
[    3.181616] md: bind<sdf1>
[    3.188917] md: bind<sdc1>
[    3.194245] async_tx: api initialized (async)
[    3.260026] raid6: int64x1    619 MB/s
[    3.328073] raid6: int64x2    875 MB/s
[    3.396042] raid6: int64x4    769 MB/s
[    3.464082] raid6: int64x8    777 MB/s
[    3.532064] raid6: sse2x1    1039 MB/s
[    3.600007] raid6: sse2x2    1474 MB/s
[    3.668030] raid6: sse2x4    2184 MB/s
[    3.668034] raid6: using algorithm sse2x4 (2184 MB/s)
[    3.668847] xor: automatically using best checksumming function: generic_sse
[    3.688009]    generic_sse:  3234.000 MB/sec
[    3.688013] xor: using function: generic_sse (3234.000 MB/sec)
[    3.689582] md: raid6 personality registered for level 6
[    3.689588] md: raid5 personality registered for level 5
[    3.689591] md: raid4 personality registered for level 4
[    3.689922] bio: create slab <bio-1> at 1
[    3.689932] md/raid:md0: not clean -- starting background reconstruction
[    3.689956] md/raid:md0: device sdc1 operational as raid disk 0
[    3.689960] md/raid:md0: device sdf1 operational as raid disk 3
[    3.689964] md/raid:md0: device sdb1 operational as raid disk 5
[    3.689968] md/raid:md0: device sde1 operational as raid disk 2
[    3.689972] md/raid:md0: device sda1 operational as raid disk 4
[    3.689976] md/raid:md0: device sdd1 operational as raid disk 1
[    3.691005] md/raid:md0: allocated 6386kB
[    3.691314] md/raid:md0: raid level 5 active with 6 out of 6 devices, algorithm 2
[    3.691320] RAID conf printout:
[    3.691323]  --- level:5 rd:6 wd:6
[    3.691328]  disk 0, o:1, dev:sdc1
[    3.691332]  disk 1, o:1, dev:sdd1
[    3.691336]  disk 2, o:1, dev:sde1
[    3.691339]  disk 3, o:1, dev:sdf1
[    3.691342]  disk 4, o:1, dev:sda1
[    3.691346]  disk 5, o:1, dev:sdb1
[    3.691421] md0: detected capacity change from 0 to 15002957250560
[    3.691764] md: resync of RAID array md0
[    3.691772] md: minimum _guaranteed_  speed: 1000 KB/sec/disk.
[    3.691776] md: using maximum available idle IO bandwidth (but not more than 200000 KB/sec) for resync.
[    3.691788] md: using 128k window, over a total of 2930265088k.
[    3.691791] md: resuming resync of md0 from checkpoint.
[    3.761202]  md0: unknown partition table
[    3.974111] scsi 6:0:0:0: Direct-Access     MUSHKIN  MKNUFDMH16GB     PMAP PQ: 0 ANSI: 0 CCS
[    4.088365] sd 6:0:0:0: Attached scsi generic sg6 type 0
[    4.091212] sd 6:0:0:0: [sdg] 31277056 512-byte logical blocks: (16.0 GB/14.9 GiB)
[    4.091815] sd 6:0:0:0: [sdg] Write Protect is off
[    4.091824] sd 6:0:0:0: [sdg] Mode Sense: 23 00 00 00
[    4.092330] sd 6:0:0:0: [sdg] No Caching mode page present
[    4.092334] sd 6:0:0:0: [sdg] Assuming drive cache: write through
[    4.095043] sd 6:0:0:0: [sdg] No Caching mode page present
[    4.095050] sd 6:0:0:0: [sdg] Assuming drive cache: write through
[    4.096544]  sdg: sdg1 sdg2 < sdg5 >
[    4.099541] sd 6:0:0:0: [sdg] No Caching mode page present
[    4.099548] sd 6:0:0:0: [sdg] Assuming drive cache: write through
[    4.099554] sd 6:0:0:0: [sdg] Attached SCSI removable disk
[    4.171782] md: linear personality registered for level -1
[    4.176415] md: multipath personality registered for level -4
[    4.186803] md: raid0 personality registered for level 0
[    4.191691] md: raid1 personality registered for level 1
[    4.223785] md: raid10 personality registered for level 10
[   50.659752] EXT4-fs (dm-0): mounted filesystem with ordered data 
[   76.186194] NET: Registered protocol family 31
[   76.186198] Bluetooth: HCI device and connection manager initialized
[   76.186203] Bluetooth: HCI socket layer initialized
[   76.186206] Bluetooth: L2CAP socket layer initialized
[   76.189446] Bluetooth: SCO socket layer initialized
[   76.316538] Bluetooth: RFCOMM TTY layer initialized
[   76.316553] Bluetooth: RFCOMM socket layer initialized
[   76.316557] Bluetooth: RFCOMM ver 1.11
[   76.324402] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[   76.324411] Bluetooth: BNEP filters: protocol multicast
[   77.706698] init: plymouth-upstart-bridge main process (1301) killed by TERM signal
[  108.734974] EXT4-fs (dm-0): re-mounted. Opts: errors=remount-ro,commit=0
[  108.742205] EXT4-fs (sdg1): re-mounted. Opts: commit=0
[  108.759962] EXT4-fs (dm-1): re-mounted. Opts: commit=0
[  346.220560] i2c /dev entries driver
[  348.928621] i2c i2c-0: sendbytes: NAK bailout.
[  350.488648] i2c i2c-0: sendbytes: NAK bailout.
[  350.636161] i2c i2c-0: sendbytes: NAK bailout.
[  352.184537] i2c i2c-0: sendbytes: NAK bailout.
[  352.331923] i2c i2c-0: sendbytes: NAK bailout.
[  353.871487] i2c i2c-0: sendbytes: NAK bailout.
[  354.018895] i2c i2c-0: sendbytes: NAK bailout.
[  355.568879] i2c i2c-0: sendbytes: NAK bailout.
[  355.720199] i2c i2c-0: sendbytes: NAK bailout.
[  357.353794] i2c i2c-0: sendbytes: NAK bailout.
[ 1265.359652] i2c i2c-0: sendbytes: NAK bailout.
[ 1265.518857] i2c i2c-0: sendbytes: NAK bailout.
[ 1266.419717] i2c i2c-0: sendbytes: NAK bailout.
[ 1267.062207] i2c i2c-0: sendbytes: NAK bailout.
[ 1267.217750] i2c i2c-0: sendbytes: NAK bailout.
[ 1267.854196] i2c i2c-0: sendbytes: NAK bailout.
[ 1268.495825] i2c i2c-0: sendbytes: NAK bailout.
[ 1268.744543] i2c i2c-0: sendbytes: NAK bailout.
[ 1269.377457] i2c i2c-0: sendbytes: NAK bailout.
[ 1269.536511] i2c i2c-0: sendbytes: NAK bailout.
[ 1269.697657] i2c i2c-0: sendbytes: NAK bailout.
[ 1269.851857] i2c i2c-0: sendbytes: NAK bailout.
[ 1270.018280] i2c i2c-0: sendbytes: NAK bailout.
[ 1270.173515] i2c i2c-0: sendbytes: NAK bailout.
[ 1270.833890] i2c i2c-0: sendbytes: NAK bailout.
[ 1270.993022] i2c i2c-0: sendbytes: NAK bailout.
[ 1271.724705] i2c i2c-0: sendbytes: NAK bailout.
[ 1272.361551] i2c i2c-0: sendbytes: NAK bailout.
[ 1272.517879] i2c i2c-0: sendbytes: NAK bailout.
[ 1273.247219] i2c i2c-0: sendbytes: NAK bailout.
[ 1274.062400] i2c i2c-0: sendbytes: NAK bailout.
[ 1274.300100] i2c i2c-0: sendbytes: NAK bailout.
[ 1274.967518] i2c i2c-0: sendbytes: NAK bailout.
[ 1275.128149] i2c i2c-0: sendbytes: NAK bailout.
[ 1275.278238] i2c i2c-0: sendbytes: NAK bailout.
[ 1275.432780] i2c i2c-0: sendbytes: NAK bailout.
[ 1275.590118] i2c i2c-0: sendbytes: NAK bailout.
[ 1275.749947] i2c i2c-0: sendbytes: NAK bailout.
[ 1276.393739] i2c i2c-0: sendbytes: NAK bailout.
[ 1276.555611] i2c i2c-0: sendbytes: NAK bailout.
[ 1277.284217] i2c i2c-0: sendbytes: NAK bailout.
[ 1278.096950] i2c i2c-0: sendbytes: NAK bailout.
[ 1278.260360] i2c i2c-0: sendbytes: NAK bailout.
[ 1278.896362] i2c i2c-0: sendbytes: NAK bailout.
[ 1279.530444] i2c i2c-0: sendbytes: NAK bailout.
[ 1279.777846] i2c i2c-0: sendbytes: NAK bailout.
[ 1280.421293] i2c i2c-0: sendbytes: NAK bailout.
[ 1281.068678] i2c i2c-0: sendbytes: NAK bailout.
[ 1281.218510] i2c i2c-0: sendbytes: NAK bailout.
[ 1281.883589] i2c i2c-0: sendbytes: NAK bailout.
[ 1282.620450] i2c i2c-0: sendbytes: NAK bailout.
[ 1282.782710] i2c i2c-0: sendbytes: NAK bailout.
[ 1283.425543] i2c i2c-0: sendbytes: NAK bailout.
[ 1284.059621] i2c i2c-0: sendbytes: NAK bailout.
[ 1284.224828] i2c i2c-0: sendbytes: NAK bailout.
[ 1284.387293] i2c i2c-0: sendbytes: NAK bailout.
[ 1284.543353] i2c i2c-0: sendbytes: NAK bailout.
[ 1285.171120] i2c i2c-0: sendbytes: NAK bailout.
[ 1285.320075] i2c i2c-0: sendbytes: NAK bailout.
[ 1285.956249] i2c i2c-0: sendbytes: NAK bailout.
[ 1286.198569] i2c i2c-0: sendbytes: NAK bailout.
[ 1286.352095] i2c i2c-0: sendbytes: NAK bailout.
[ 1287.488209] i2c i2c-0: sendbytes: NAK bailout.
[ 1287.643538] i2c i2c-0: sendbytes: NAK bailout.
[ 1288.864330] i2c i2c-0: sendbytes: NAK bailout.
[ 1289.102732] i2c i2c-0: sendbytes: NAK bailout.
[ 1289.734081] i2c i2c-0: sendbytes: NAK bailout.
[ 1289.887633] i2c i2c-0: sendbytes: NAK bailout.
[ 1290.952799] i2c i2c-0: sendbytes: NAK bailout.
[ 1292.268550] i2c i2c-0: sendbytes: NAK bailout.
[ 1293.101669] i2c i2c-0: sendbytes: NAK bailout.
[ 1293.249703] i2c i2c-0: sendbytes: NAK bailout.
[ 1293.894269] i2c i2c-0: sendbytes: NAK bailout.
[ 1294.707913] i2c i2c-0: sendbytes: NAK bailout.
[ 1294.871096] i2c i2c-0: sendbytes: NAK bailout.
[ 1295.515474] i2c i2c-0: sendbytes: NAK bailout.
[ 1295.675668] i2c i2c-0: sendbytes: NAK bailout.
[ 1296.321057] i2c i2c-0: sendbytes: NAK bailout.
[ 1296.481568] i2c i2c-0: sendbytes: NAK bailout.
[ 1297.120573] i2c i2c-0: sendbytes: NAK bailout.
[ 1297.268995] i2c i2c-0: sendbytes: NAK bailout.
[ 1297.908710] i2c i2c-0: sendbytes: NAK bailout.
[ 1298.062045] i2c i2c-0: sendbytes: NAK bailout.
[ 1298.724633] i2c i2c-0: sendbytes: NAK bailout.
[ 1298.890137] i2c i2c-0: sendbytes: NAK bailout.
[ 1299.525743] i2c i2c-0: sendbytes: NAK bailout.
[ 1299.680583] i2c i2c-0: sendbytes: NAK bailout.
[ 1300.345497] i2c i2c-0: sendbytes: NAK bailout.
[ 1301.001041] i2c i2c-0: sendbytes: NAK bailout.
[ 1301.151781] i2c i2c-0: sendbytes: NAK bailout.
[ 1301.885502] i2c i2c-0: sendbytes: NAK bailout.
[ 1303.042572] i2c i2c-0: sendbytes: NAK bailout.
[ 1303.760381] i2c i2c-0: sendbytes: NAK bailout.
[ 1303.924203] i2c i2c-0: sendbytes: NAK bailout.
[ 1304.079689] i2c i2c-0: sendbytes: NAK bailout.
[ 1304.735598] i2c i2c-0: sendbytes: NAK bailout.
[ 1305.369459] i2c i2c-0: sendbytes: NAK bailout.
[ 1306.183580] i2c i2c-0: sendbytes: NAK bailout.
[ 1306.425534] i2c i2c-0: sendbytes: NAK bailout.
[ 1307.076525] i2c i2c-0: sendbytes: NAK bailout.
[ 1307.801878] i2c i2c-0: sendbytes: NAK bailout.
[ 1308.468283] i2c i2c-0: sendbytes: NAK bailout.
[ 1309.197646] i2c i2c-0: sendbytes: NAK bailout.
[ 1309.356520] i2c i2c-0: sendbytes: NAK bailout.
[ 1309.511831] i2c i2c-0: sendbytes: NAK bailout.
[ 1309.674873] i2c i2c-0: sendbytes: NAK bailout.
[ 1309.922353] i2c i2c-0: sendbytes: NAK bailout.
[ 1311.055354] i2c i2c-0: sendbytes: NAK bailout.
[ 1311.785431] i2c i2c-0: sendbytes: NAK bailout.
[ 1312.027839] i2c i2c-0: sendbytes: NAK bailout.
[ 1312.951811] i2c i2c-0: sendbytes: NAK bailout.
[ 1313.592698] i2c i2c-0: sendbytes: NAK bailout.
[ 1313.751726] i2c i2c-0: sendbytes: NAK bailout.
[ 1313.994855] i2c i2c-0: sendbytes: NAK bailout.
[ 1314.152511] i2c i2c-0: sendbytes: NAK bailout.
[ 1314.804112] i2c i2c-0: sendbytes: NAK bailout.
[ 1315.053824] i2c i2c-0: sendbytes: NAK bailout.
[ 1315.731944] i2c i2c-0: sendbytes: NAK bailout.
[ 1316.369685] i2c i2c-0: sendbytes: NAK bailout.
[ 1316.535130] i2c i2c-0: sendbytes: NAK bailout.
[ 1317.270234] i2c i2c-0: sendbytes: NAK bailout.
[ 1317.431499] i2c i2c-0: sendbytes: NAK bailout.
[ 1317.673887] i2c i2c-0: sendbytes: NAK bailout.
[ 1317.831638] i2c i2c-0: sendbytes: NAK bailout.
[ 1318.571123] i2c i2c-0: sendbytes: NAK bailout.
[ 1319.212121] i2c i2c-0: sendbytes: NAK bailout.
[ 1319.364194] i2c i2c-0: sendbytes: NAK bailout.
[ 1320.009694] i2c i2c-0: sendbytes: NAK bailout.
[ 1320.668259] i2c i2c-0: sendbytes: NAK bailout.
[ 1320.824684] i2c i2c-0: sendbytes: NAK bailout.
[ 1321.473844] i2c i2c-0: sendbytes: NAK bailout.
[ 1322.208817] i2c i2c-0: sendbytes: NAK bailout.
[ 1322.369261] i2c i2c-0: sendbytes: NAK bailout.
[ 1323.010415] i2c i2c-0: sendbytes: NAK bailout.
[ 1323.660133] i2c i2c-0: sendbytes: NAK bailout.
[ 1323.816871] i2c i2c-0: sendbytes: NAK bailout.
[ 1324.474609] i2c i2c-0: sendbytes: NAK bailout.
[ 1325.209087] i2c i2c-0: sendbytes: NAK bailout.
[ 1325.618480] i2c i2c-0: sendbytes: NAK bailout.
[ 1326.284219] i2c i2c-0: sendbytes: NAK bailout.
[ 1327.017176] i2c i2c-0: sendbytes: NAK bailout.
[ 1327.171145] i2c i2c-0: sendbytes: NAK bailout.
[ 1327.808392] i2c i2c-0: sendbytes: NAK bailout.
[ 1328.535461] i2c i2c-0: sendbytes: NAK bailout.
[ 1328.691861] i2c i2c-0: sendbytes: NAK bailout.
[ 1329.327444] i2c i2c-0: sendbytes: NAK bailout.
[ 1329.490218] i2c i2c-0: sendbytes: NAK bailout.
[ 1329.645189] i2c i2c-0: sendbytes: NAK bailout.
[ 1329.800388] i2c i2c-0: sendbytes: NAK bailout.
[ 1329.956377] i2c i2c-0: sendbytes: NAK bailout.
[ 1330.118557] i2c i2c-0: sendbytes: NAK bailout.
[ 1330.763510] i2c i2c-0: sendbytes: NAK bailout.
[ 1330.921987] i2c i2c-0: sendbytes: NAK bailout.
[ 1331.566825] i2c i2c-0: sendbytes: NAK bailout.
[ 1332.226454] i2c i2c-0: sendbytes: NAK bailout.
[ 1332.473956] i2c i2c-0: sendbytes: NAK bailout.
[ 1333.130409] i2c i2c-0: sendbytes: NAK bailout.
[ 1333.868092] i2c i2c-0: sendbytes: NAK bailout.
[ 1334.121108] i2c i2c-0: sendbytes: NAK bailout.
[ 1334.773665] i2c i2c-0: sendbytes: NAK bailout.
[ 1335.413187] i2c i2c-0: sendbytes: NAK bailout.
[ 1335.576438] i2c i2c-0: sendbytes: NAK bailout.
[ 1336.235514] i2c i2c-0: sendbytes: NAK bailout.
[ 1336.891752] i2c i2c-0: sendbytes: NAK bailout.
[ 1337.055406] i2c i2c-0: sendbytes: NAK bailout.
[ 1340.922334] i2c i2c-0: sendbytes: NAK bailout.
[ 1341.090720] i2c i2c-0: sendbytes: NAK bailout.
[ 1710.092054] usb 1-4: new high speed USB device number 4 using ehci_hcd
[ 1710.244375] scsi7 : usb-storage 1-4:1.0
[ 1711.263263] scsi 7:0:0:0: Direct-Access     Hitachi  HDS723030ALA640       PQ: 0 ANSI: 5
[ 1711.388854] sd 7:0:0:0: Attached scsi generic sg7 type 0
[ 1711.390361] sd 7:0:0:0: [sdh] 732566645 4096-byte logical blocks: (3.00 TB/2.72 TiB)
[ 1711.391298] sd 7:0:0:0: [sdh] Write Protect is off
[ 1711.391305] sd 7:0:0:0: [sdh] Mode Sense: 28 00 00 00
[ 1711.392269] sd 7:0:0:0: [sdh] No Caching mode page present
[ 1711.392276] sd 7:0:0:0: [sdh] Assuming drive cache: write through
[ 1711.394775] sd 7:0:0:0: [sdh] 732566645 4096-byte logical blocks: (3.00 TB/2.72 TiB)
[ 1711.397157] sd 7:0:0:0: [sdh] No Caching mode page present
[ 1711.397167] sd 7:0:0:0: [sdh] Assuming drive cache: write through
[ 1711.410962]  sdh: sdh1
[ 1711.414276] sd 7:0:0:0: [sdh] 732566645 4096-byte logical blocks: (3.00 TB/2.72 TiB)
[ 1711.416348] sd 7:0:0:0: [sdh] No Caching mode page present
[ 1711.416357] sd 7:0:0:0: [sdh] Assuming drive cache: write through
[ 1711.416363] sd 7:0:0:0: [sdh] Attached SCSI disk
[63219.945427] show_signal_msg: 12 callbacks suppressed
[63219.945436] nautilus[1993]: segfault at 18 ip 00000000004b5b5e sp 00007fff2ee926e0 error 4 in nautilus[400000+159000]
[64073.328192] python[8075]: segfault at 10 ip 000000000049c51b sp 00007ffffd0a8970 error 4 in python2.7[400000+233000]
 
Old 10-25-2011, 10:00 PM   #2
spwnt
Member
 
Registered: Jun 2006
Distribution: Linux Mint/Debian/Arch
Posts: 78

Original Poster
Rep: Reputation: 12
syslog outputs

"Oct 25 18:15:42 ubuntu-server mdadm[1531]: Rebuild80 event detected on md device /dev/md/0"

since i've just started this project starting over now rather than later would be prefered... before i have a lot of stuff on my raid. should i just let it rebuild itself, or should i just clear the raid and remake it myself? the drives should be fully functional.. i just got them a few days ago and i ran them through seatools. i didn't swap anything out, idont see why it would be rebuilding itself.

EDIT: few more details

mdadm --details /dev/md0

Code:
/dev/md0:
        Version : 1.2
  Creation Time : Fri Oct 21 16:27:29 2011
     Raid Level : raid5
     Array Size : 14651325440 (13972.59 GiB 15002.96 GB)
  Used Dev Size : 2930265088 (2794.52 GiB 3000.59 GB)
   Raid Devices : 6
  Total Devices : 6
    Persistence : Superblock is persistent

    Update Time : Tue Oct 25 19:32:56 2011
          State : active, resyncing
 Active Devices : 6
Working Devices : 6
 Failed Devices : 0
  Spare Devices : 0

         Layout : left-symmetric
     Chunk Size : 512K

 Rebuild Status : 83% complete

           Name : debian-server:0
           UUID : e967892d:e5006f45:8c97fdb4:9e3eab2d
         Events : 63

    Number   Major   Minor   RaidDevice State
       0       8       33        0      active sync   /dev/sdc1
       1       8       49        1      active sync   /dev/sdd1
       2       8       65        2      active sync   /dev/sde1
       3       8       81        3      active sync   /dev/sdf1
       4       8        1        4      active sync   /dev/sda1
       5       8       17        5      active sync   /dev/sdb1
Last edited by spwnt; 10-25-2011 at 10:06 PM.
 
Old 10-26-2011, 06:15 PM   #3
spankbot
Member
 
Registered: Aug 2007
Posts: 133

Rep: Reputation: 16
I don't have a direct answer for you since I gave up on software RAID many years ago, but I have a few tips...

First, never, ever, EVER use RAID 5.
http://www.miracleas.com/BAARF/

Second, software RAID 5 is even MORE of a disaster.

Third, you MUST have an UPS.
Last edited by spankbot; 10-26-2011 at 06:19 PM.
 
Old 10-26-2011, 08:39 PM   #4
spwnt
Member
 
Registered: Jun 2006
Distribution: Linux Mint/Debian/Arch
Posts: 78

Original Poster
Rep: Reputation: 12
can the write hole problem corrupt the entire drive or just that stripe? meaning a single file? is a UPS really that important? if there's just a small chance that my power might go out and corrupt a single file I don't really care, but if it'll corrupt the entire file system that would be annoying.

I'm using raid5 because I don't need that much redundancy. like i was going to use raid 0, but i figured raid5 will be just enough redundancy. everything i'm putting on this fileserver isn't anything that i don't either a: have backed up somewhere else already, or b: couldn't get again if things went wrong. it would just be inconvenient to have to build it again. i need all the storage i can get though, so raid 10 is out of the question.

this raid5 is somewhat temporary since i know it's kinda janky... i'm hoping by the time next debian stable is released btrfs will support encryption, parity based raid, and fsck. until then i'm pretty much stuck with raid5. it's fine though. definately don't have the money to go out and buy a hardware raid card, and wouldn't do it even if i did. downsides of hardware raid outweigh the downsides of software raid imo. being locked to a card, so that if it breaks i'm screwed unless i can find another isn't worth it.
 
Old 10-27-2011, 03:44 PM   #5
spankbot
Member
 
Registered: Aug 2007
Posts: 133

Rep: Reputation: 16
An UPS is a *must* with RAID (hardware or software).
 
Old 10-28-2011, 03:40 PM   #6
dalai lama
LQ Newbie
 
Registered: Dec 2009
Location: Amsterdam
Distribution: CentOS
Posts: 19

Rep: Reputation: 0
First, forget about 'spankbot's' posts (sorry spankbot ). You can read he us much against raid in any way so that won't solve your issue.

Can you tell some more about 'md0'? What mount point does it have? Also don't your log files so some more information?
The array is crashed for some reason, maybe you wrote some large files which made the array crash... Could you also provide the output of 'cat /proc/mdstat'? It will show at what speed the array is rebuilding and may be indicating a bad hard disk.
 
Old 10-29-2011, 07:49 PM   #7
spwnt
Member
 
Registered: Jun 2006
Distribution: Linux Mint/Debian/Arch
Posts: 78

Original Poster
Rep: Reputation: 12
well, the array has rebuilt... and it's running just fine now. low cpu-usage. everything is running just fine. if it starts acting up again i'll open this back up.
 
  


Reply



Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
LXer: How To Resize RAID Partitions (Shrink & Grow) (Software RAID) LXer Syndicated Linux News 1 05-01-2009 12:02 PM
LXer: Benchmarking hardware RAID vs. Linux kernel software RAID LXer Syndicated Linux News 0 07-15-2008 03:50 PM
Adding an old software-RAID array to a software-RAID installation.. Boot problems GarethM Linux - Hardware 2 05-05-2008 03:16 PM
Will a ex - Software Raid 1 disk boot without Raid software? carlosruiz Linux - Software 0 05-27-2006 01:12 PM
moving system from ide software raid to new box with scsi raid ftumsh Linux - General 0 10-28-2003 09:34 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Hardware

All times are GMT -5. The time now is 01:15 PM.

Contact Us - Advertising Info - Rules - Privacy - LQ Merchandise - Donations - Contributing Member - LQ Sitemap -
Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration