Re: RAID array is gone, please help
Thank you very much or your reply. I naively thought that starting without partitions would be the best starting point, given 3 of the disks had been in a RAID5 array previously (possibly with partitions, not sure), but that looks like a bad choice, based on some other things I've googled. Lesson learned. I have an mdadm.conf file, but it could be a remnant of my previous array. I've already edited it trying to get things to work, so I'm not sure if it was updated when I created the new array or not. I see various people online have had success in my situation using madadm --create /dev/md0 --assume-clean --verbose --level=10 \ --raid-devices=4 /dev/sdc /dev/sdd /dev/sde /dev/sdf Some people used --assume-clean, and some didn't. Given my array wasn't done with its resync, maybe I should leave that out. If that would work, I guess then I need to get the data off the array, delete it, and recreate it with disk partitions, or risk this happening again at the next reboot, for whatever reason. Anyone think it's a bad idea to try mdadm --create at this point? Sorry, I'm not sure how to write 0's to sector 0... Thank you. On 3/23/2017 18:37, Lennart Sorensen wrote: On Thu, Mar 23, 2017 at 05:49:05PM +0100, r...@mueller.org wrote: I am hoping someone here will help me. Was reading this site... https://raid.wiki.kernel.org/index.php/Linux_Raid and it said to email this list if you've tried everything other than mdadm --create. I am running Ubuntu 16.04. Machine name is fred. I used webmin to create a 4 disk RAID10 array yesterday. I moved all my data onto the array. Today, I had to reboot my PC. The resync was still not done, but I read online that it's OK to boot during resync. After boot, my array was gone. I checked syslog, and it just has this line: DeviceDisappeared event detected on md device /dev/md0 I did not partition my disks before building the array. So I believe the array consisted of /dev/sdc, /dev/sdd, /dev/sde, and /dev/sdf. Here's some info... stephen@fred> lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:00 117.4G 0 disk ├─sda1 8:10 109.7G 0 part / ├─sda2 8:20 1K 0 part └─sda5 8:50 7.7G 0 part [SWAP] sdb 8:16 0 465.8G 0 disk └─sdb1 8:17 0 465.8G 0 part sdc 8:32 0 3.7T 0 disk sdd 8:48 0 3.7T 0 disk sde 8:64 0 3.7T 0 disk sdf 8:80 0 3.7T 0 disk stephen@fred> sudo mdadm --examine /dev/sdc [sudo] password for stephen: /dev/sdc: MBR Magic : aa55 Partition[0] : 4294967295 sectors at1 (type ee) stephen@fred> stephen@fred> sudo mdadm --examine /dev/sdc1 mdadm: cannot open /dev/sdc1: No such file or directory stephen@fred> stephen@fred> sudo mdadm --examine /dev/sdd /dev/sdd: MBR Magic : aa55 Partition[0] : 4294967295 sectors at1 (type ee) stephen@fred> stephen@fred> sudo mdadm --examine /dev/sde /dev/sde: MBR Magic : aa55 Partition[0] : 4294967295 sectors at1 (type ee) stephen@fred> stephen@fred> sudo mdadm --examine /dev/sdf /dev/sdf: MBR Magic : aa55 Partition[0] : 4294967295 sectors at1 (type ee) stephen@fred> sudo mdadm --assemble --force /dev/md0 /dev/sdc /dev/sdd /dev/sde /dev/sdf mdadm: Cannot assemble mbr metadata on /dev/sdc mdadm: /dev/sdc has no superblock - assembly aborted Thank you for any help you can provide. Did your disks have partitions previously? That output looks a lot like the protective MBR partition table for a disk with GPT partitions. Could that still existing in sector 0 be confusing mdadm? I have never personally done any md raid without partitions. To me they just make more sense. One way to test could be to save a copy of sector 0, then overwrite sector 0 with zeros and then run mdadm --examine again to see if that makes a difference. You can always put back the saved copy of sector 0 that way. My understanding is that the default is to put the raid superblock at offset 4k, so it would not overwrite an existing MBR partition table. If it also happens due to rounding that the end of the disk isn't overwritten (or even just because that part of the filesystem wasn't written to yet), then the backup GPT from before would still be intact, and could perhaps cause even more confussion later if gdisk or similar is pointed at the disk. Really want to be sure there is no trace left of the partition table before using it raw for md raid. Any chance the system saved an mdadm.conf file of your setup?
RAID array is gone, please help
I am hoping someone here will help me. Was reading this site... https://raid.wiki.kernel.org/index.php/Linux_Raid and it said to email this list if you've tried everything other than mdadm --create. I am running Ubuntu 16.04. Machine name is fred. I used webmin to create a 4 disk RAID10 array yesterday. I moved all my data onto the array. Today, I had to reboot my PC. The resync was still not done, but I read online that it's OK to boot during resync. After boot, my array was gone. I checked syslog, and it just has this line: DeviceDisappeared event detected on md device /dev/md0 I did not partition my disks before building the array. So I believe the array consisted of /dev/sdc, /dev/sdd, /dev/sde, and /dev/sdf. Here's some info... stephen@fred> lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:00 117.4G 0 disk ├─sda1 8:10 109.7G 0 part / ├─sda2 8:20 1K 0 part └─sda5 8:50 7.7G 0 part [SWAP] sdb 8:16 0 465.8G 0 disk └─sdb1 8:17 0 465.8G 0 part sdc 8:32 0 3.7T 0 disk sdd 8:48 0 3.7T 0 disk sde 8:64 0 3.7T 0 disk sdf 8:80 0 3.7T 0 disk stephen@fred> sudo mdadm --examine /dev/sdc [sudo] password for stephen: /dev/sdc: MBR Magic : aa55 Partition[0] : 4294967295 sectors at1 (type ee) stephen@fred> stephen@fred> sudo mdadm --examine /dev/sdc1 mdadm: cannot open /dev/sdc1: No such file or directory stephen@fred> stephen@fred> sudo mdadm --examine /dev/sdd /dev/sdd: MBR Magic : aa55 Partition[0] : 4294967295 sectors at1 (type ee) stephen@fred> stephen@fred> sudo mdadm --examine /dev/sde /dev/sde: MBR Magic : aa55 Partition[0] : 4294967295 sectors at1 (type ee) stephen@fred> stephen@fred> sudo mdadm --examine /dev/sdf /dev/sdf: MBR Magic : aa55 Partition[0] : 4294967295 sectors at1 (type ee) stephen@fred> sudo mdadm --assemble --force /dev/md0 /dev/sdc /dev/sdd /dev/sde /dev/sdf mdadm: Cannot assemble mbr metadata on /dev/sdc mdadm: /dev/sdc has no superblock - assembly aborted Thank you for any help you can provide.
Kernel 2.6.20.4 Unaligned address
[1] kernel errors reporting unaligned access of memory [2] The following two lines iterate twice a piece, about once every 2 minutes: Kernel unaligned access at TPC[79c344] arpt_do_table+0x3cc/0x640 Kernel unaligned access at TPC[79c33c] arpt_do_table+0x3c4/0x640 [3] ... [4] Linux version 2.6.20.4 ([EMAIL PROTECTED]) (gcc version 3.3.5 (Debian 1:3.3.5-13)) #3 Fri Apr 6 18:08:28 PDT 2007 [7] This is running on a Netra t1 105 (sparc) /proc/cpu: cpu : TI UltraSparc IIi (Sabre) fpu : UltraSparc IIi integrated FPU prom: OBP 3.10.27 2000/06/22 16:45 type: sun4u ncpus probed: 1 ncpus active: 1 D$ parity tl1 : 0 I$ parity tl1 : 0 Cpu0Bogo: 880.43 Cpu0ClkTck : 1a3a605f MMU Type: Spitfire I can attach my .config if necessary, but don't want to clutter this email with any unnecessary data. -brandon - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Maxtor 80gb slow on asus p2b-d ? (going to use it in raid5 config)
i'm going to build a raid5 config with 6*maxtor 80gb mainbord is an asus p2b-d (with dual 450 and 512mb ram) and 2 addon ultra66 promise controllers i did some tests using hdparm (4.1) and i get these result : (hda and hdc are on the onboard controller) /dev/hda: Timing buffered disk reads: 64 MB in 4.94 seconds = 12.96 MB/sec /dev/hdc: Timing buffered disk reads: 64 MB in 4.94 seconds = 12.96 MB/sec /dev/hde: Timing buffered disk reads: 64 MB in 2.26 seconds = 28.32 MB/sec /dev/hdg: Timing buffered disk reads: 64 MB in 2.25 seconds = 28.44 MB/sec /dev/hdi: Timing buffered disk reads: 64 MB in 2.25 seconds = 28.44 MB/sec /dev/hdk: Timing buffered disk reads: 64 MB in 2.25 seconds = 28.44 MB/sec kernel reports : hda: 160086528 sectors (81964 MB) w/2048KiB Cache, CHS=158816/16/63, UDMA(33) hdc: 160086528 sectors (81964 MB) w/2048KiB Cache, CHS=158816/16/63, UDMA(33) hde: 160086528 sectors (81964 MB) w/2048KiB Cache, CHS=158816/16/63, UDMA(66) hdg: 160086528 sectors (81964 MB) w/2048KiB Cache, CHS=158816/16/63, UDMA(66) hdi: 160086528 sectors (81964 MB) w/2048KiB Cache, CHS=158816/16/63, UDMA(66) hdk: 160086528 sectors (81964 MB) w/2048KiB Cache, CHS=158816/16/63, UDMA(66) and i use hdparm -m16 -c1 -d1 -a8 on all hd's so why do i only see 13mb/sec on the ultra33 controller (i thought 28mb/sec would be possible on the ultra33 controller) i also made a raid0 on the 6 disks and this gives me : /dev/md0: Timing buffered disk reads: 64 MB in 2.13 seconds = 30.05 MB/sec - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Maxtor 80gb slow on asus p2b-d ? (going to use it in raid5config)
oops : both tried kernel 2.4.4-pre5 (with ide patches) and kernel 2.2.14pre12 (with ide and raid patches) On Sun, 22 Apr 2001 [EMAIL PROTECTED] wrote: > i'm going to build a raid5 config with 6*maxtor 80gb > mainbord is an asus p2b-d (with dual 450 and 512mb ram) > and 2 addon ultra66 promise controllers > > i did some tests using hdparm (4.1) > and i get these result : > > (hda and hdc are on the onboard controller) > > /dev/hda: > Timing buffered disk reads: 64 MB in 4.94 seconds = 12.96 MB/sec > > /dev/hdc: > Timing buffered disk reads: 64 MB in 4.94 seconds = 12.96 MB/sec > > /dev/hde: > Timing buffered disk reads: 64 MB in 2.26 seconds = 28.32 MB/sec > > /dev/hdg: > Timing buffered disk reads: 64 MB in 2.25 seconds = 28.44 MB/sec > > /dev/hdi: > Timing buffered disk reads: 64 MB in 2.25 seconds = 28.44 MB/sec > > /dev/hdk: > Timing buffered disk reads: 64 MB in 2.25 seconds = 28.44 MB/sec > > kernel reports : > hda: 160086528 sectors (81964 MB) w/2048KiB Cache, CHS=158816/16/63, > UDMA(33) > hdc: 160086528 sectors (81964 MB) w/2048KiB Cache, CHS=158816/16/63, > UDMA(33) > hde: 160086528 sectors (81964 MB) w/2048KiB Cache, CHS=158816/16/63, > UDMA(66) > hdg: 160086528 sectors (81964 MB) w/2048KiB Cache, CHS=158816/16/63, > UDMA(66) > hdi: 160086528 sectors (81964 MB) w/2048KiB Cache, CHS=158816/16/63, > UDMA(66) > hdk: 160086528 sectors (81964 MB) w/2048KiB Cache, CHS=158816/16/63, > UDMA(66) > > and i use hdparm -m16 -c1 -d1 -a8 on all hd's > so why do i only see 13mb/sec on the ultra33 controller > (i thought 28mb/sec would be possible on the ultra33 controller) > > i also made a raid0 on the 6 disks > and this gives me : > > /dev/md0: > Timing buffered disk reads: 64 MB in 2.13 seconds = 30.05 MB/sec > > > > - > To unsubscribe from this list: send the line "unsubscribe linux-raid" in > the body of a message to [EMAIL PROTECTED] > - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
