Sometime in the last few days, swap has stopped working (it was on a raid1
device /dev/md3). Three other raid1 devices seem to be working normally.
I do not know what happened, but as it was swap nothing was lost. I am trying
to reset this up, but am running into dificulties.
As a starting point, I deleted the entry for /dev/md3 in /etc/mdadm.conf and
rebooted (I could not find any other way to stop /dev/md3). cat /proc/mdstat
showed only the three working raid1 devices.
Next, using the YaST Partitioner I create a new raid1 device and add /dev/sba6
and /dev/sdb6 (the same partitions used orignally) to the raid, format the
raid device as swap and set the mount point to swap (this is what I did at
initial installationas well). This now fails with an obscure error message:
Failure occured during follwing action:
Formatting software RAID /dev/md3 (2.0 GB) with swap
System error code was: -3004
At this point cat /proc/mdstat shows for the mew raid device
md3 : active (auto-read-only) raid1 sda6 sdb6
2104468 blocks super 1.0 [2/2] [UU]
bitmap: 9/9 pages [36KB], 128KB chunk
Looks like it needs to be resynced(?) but I don't understand. Isn't this a
new raid device, and wouldn't the formatting as swap initialize everything to
a correct state?
At the same time, the output from /var/log/messages at this time is
(sorry for the wrapping)
Jul 29 11:34:00 raboud-office2 kernel: Uniform Multi-Platform E-IDE driver
Jul 29 11:34:00 raboud-office2 kernel: ide: Assuming 33MHz system bus speed
for PIO modes; override with idebus=xx
Jul 29 11:34:00 raboud-office2 kernel: st: Version 20080221, fixed bufsize
32768, s/g segs 256
Jul 29 11:34:00 raboud-office2 kernel: Driver 'st' needs updating - please use
bus_type methodsroot 4221 0.0 0.0 0 0 ? S< 11:34
Jul 29 11:34:41 raboud-office2 kernel: md: bind<sdb6>
Jul 29 11:34:41 raboud-office2 kernel: md: bind<sda6>
Jul 29 11:34:41 raboud-office2 kernel: md: md3: raid array is not clean --
starting background reconstruction
Jul 29 11:34:41 raboud-office2 kernel: raid1: raid set md3 active with 2 out
of 2 mirrors
Jul 29 11:34:41 raboud-office2 kernel: md3: bitmap initialized from disk: read
1/1 pages, set 16442 bits
Jul 29 11:34:41 raboud-office2 kernel: created bitmap (9 pages) for device md3
It is now over two hours later and nothing has changed. There is a process
running that seems related but not promising (no memory, no cpu time).
root 4221 0.0 0.0 0 0 ? S< 11:34 0:00 [md3_raid1]
I am lost at this point. I would try to do this outside of Yast (just in case
it is a bug), but I don't know the right steps. Unfortunately I am not a
I would appreciate any insight on this.
To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse+help(a)opensuse.org