Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
Re: mdadm: No arrays found in config file or automatically
3,515 views
Skip to first unread message
Gary Dale
Jul 18, 2015, 4:10:04 PM7/18/15
to
On 18/07/15 04:01 PM, Emanuel Berg wrote:
> When I boot, it says:
>
> mdadm: No arrays found in config file or
> automatically
>
> What does that mean and how do I fix it?
>
run
mdadm --detail --scan >> /etc/mdadm.conf
after you have your arrays running. Then do:
update-initramfs -u
update-grub
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: https://lists.debian.org/55AAB254...@torfree.net
> When I boot, it says:
>
> mdadm: No arrays found in config file or
> automatically
>
> What does that mean and how do I fix it?
>
run
mdadm --detail --scan >> /etc/mdadm.conf
after you have your arrays running. Then do:
update-initramfs -u
update-grub
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: https://lists.debian.org/55AAB254...@torfree.net
Emanuel Berg
Jul 18, 2015, 4:10:05 PM7/18/15
to
When I boot, it says:
mdadm: No arrays found in config file or
automatically
What does that mean and how do I fix it?
--
mdadm: No arrays found in config file or
automatically
What does that mean and how do I fix it?
underground experts united
http://user.it.uu.se/~embe8573
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Gary Dale
Jul 18, 2015, 4:20:05 PM7/18/15
to
On 18/07/15 04:08 PM, Gary Dale wrote:
> On 18/07/15 04:01 PM, Emanuel Berg wrote:
>> When I boot, it says:
>>
>> mdadm: No arrays found in config file or
>> automatically
>>
>> What does that mean and how do I fix it?
>>
>
> run
>
> mdadm --detail --scan >> /etc/mdadm.conf
>
> after you have your arrays running. Then do:
>
> update-initramfs -u
> update-grub
>
>
Sorry, on Debian make that /etc/mdadm/mdadm.conf
> On 18/07/15 04:01 PM, Emanuel Berg wrote:
>> When I boot, it says:
>>
>> mdadm: No arrays found in config file or
>> automatically
>>
>> What does that mean and how do I fix it?
>>
>
> run
>
> mdadm --detail --scan >> /etc/mdadm.conf
>
> after you have your arrays running. Then do:
>
> update-initramfs -u
> update-grub
>
>
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Emanuel Berg
Jul 18, 2015, 8:00:03 PM7/18/15
to
Gary Dale <gary...@torfree.net> writes:
> run
>
> mdadm --detail --scan >> /etc/mdadm.conf
>
> after you have your arrays running. Then do:
>
> update-initramfs -u update-grub
It says, weirdly, "Invalid argument for option -k."
> run
>
> mdadm --detail --scan >> /etc/mdadm.conf
>
> after you have your arrays running. Then do:
>
> update-initramfs -u update-grub
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: https://lists.debian.org/87380lt...@nl106-137-147.student.uu.se
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Gary Dale
Jul 19, 2015, 12:10:05 AM7/19/15
to
On 18/07/15 07:52 PM, Emanuel Berg wrote:
> Gary Dale <gary...@torfree.net> writes:
>
>> run
>>
>> mdadm --detail --scan >> /etc/mdadm.conf
>>
>> after you have your arrays running. Then do:
>>
>> update-initramfs -u update-grub
> It says, weirdly, "Invalid argument for option -k."
>
That's because you've combined the two lines into one. Run the
> Gary Dale <gary...@torfree.net> writes:
>
>> run
>>
>> mdadm --detail --scan >> /etc/mdadm.conf
>>
>> after you have your arrays running. Then do:
>>
>> update-initramfs -u update-grub
> It says, weirdly, "Invalid argument for option -k."
>
update-initramfs first then run update-grub.
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Emanuel Berg
Jul 19, 2015, 4:30:06 AM7/19/15
to
OK:
$ sudo update-initramfs -u
update-initramfs: Generating /boot/initrd.img-3.16.0-4-amd64
W: mdadm: /etc/mdadm/mdadm.conf defines no arrays.
W: mdadm: no arrays defined in configuration file.
$ sudo update-grub
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-3.16.0-4-amd64
Found initrd image: /boot/initrd.img-3.16.0-4-amd64
Found memtest86+ image: /boot/memtest86+.bin
Found memtest86+ multiboot image: /boot/memtest86+_multiboot.bin
No volume groups found
done
I'll reboot and see what happens.
$ sudo update-initramfs -u
update-initramfs: Generating /boot/initrd.img-3.16.0-4-amd64
W: mdadm: /etc/mdadm/mdadm.conf defines no arrays.
W: mdadm: no arrays defined in configuration file.
$ sudo update-grub
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-3.16.0-4-amd64
Found initrd image: /boot/initrd.img-3.16.0-4-amd64
Found memtest86+ image: /boot/memtest86+.bin
Found memtest86+ multiboot image: /boot/memtest86+_multiboot.bin
No volume groups found
done
I'll reboot and see what happens.
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: https://lists.debian.org/87h9p0v...@nl106-137-147.student.uu.se
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Pascal Hambourg
Jul 19, 2015, 7:10:04 AM7/19/15
to
Emanuel Berg a écrit :
you may uninstall mdadm (unless reverse dependencies exist). However if
you think you have software RAID arrays, what's the output of the
following command ?
mdadm --detail --scan --verbose
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: https://lists.debian.org/55AB813A...@plouf.fr.eu.org
> When I boot, it says:
>
> mdadm: No arrays found in config file or
> automatically
If you don't have any software RAID arrays, that's perfectly normal and
>
> mdadm: No arrays found in config file or
> automatically
you may uninstall mdadm (unless reverse dependencies exist). However if
you think you have software RAID arrays, what's the output of the
following command ?
mdadm --detail --scan --verbose
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Pascal Hambourg
Jul 19, 2015, 7:20:04 AM7/19/15
to
Pascal Hambourg a écrit :
mdadm --examine --scan --verbose
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: https://lists.debian.org/55AB81CF...@plouf.fr.eu.org
> If you don't have any software RAID arrays, that's perfectly normal and
> you may uninstall mdadm (unless reverse dependencies exist). However if
> you think you have software RAID arrays, what's the output of the
> following command ?
>
> mdadm --detail --scan --verbose
Oops, the right command is
> you may uninstall mdadm (unless reverse dependencies exist). However if
> you think you have software RAID arrays, what's the output of the
> following command ?
>
> mdadm --detail --scan --verbose
mdadm --examine --scan --verbose
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Gary Dale
Jul 19, 2015, 11:10:05 AM7/19/15
to
On 19/07/15 04:14 AM, Emanuel Berg wrote:
> Gary Dale <gary...@torfree.net> writes:
>
>> Run the update-initramfs first then run update-grub.
> OK:
>
> $ sudo update-initramfs -u
> update-initramfs: Generating /boot/initrd.img-3.16.0-4-amd64
> W: mdadm: /etc/mdadm/mdadm.conf defines no arrays.
> W: mdadm: no arrays defined in configuration file.
>
> $ sudo update-grub
> Generating grub configuration file ...
> Found linux image: /boot/vmlinuz-3.16.0-4-amd64
> Found initrd image: /boot/initrd.img-3.16.0-4-amd64
> Found memtest86+ image: /boot/memtest86+.bin
> Found memtest86+ multiboot image: /boot/memtest86+_multiboot.bin
> No volume groups found
> done
>
> I'll reboot and see what happens.
>
Were your arrays running when you ran
> Gary Dale <gary...@torfree.net> writes:
>
>> Run the update-initramfs first then run update-grub.
> OK:
>
> $ sudo update-initramfs -u
> update-initramfs: Generating /boot/initrd.img-3.16.0-4-amd64
> W: mdadm: /etc/mdadm/mdadm.conf defines no arrays.
> W: mdadm: no arrays defined in configuration file.
>
> $ sudo update-grub
> Generating grub configuration file ...
> Found linux image: /boot/vmlinuz-3.16.0-4-amd64
> Found initrd image: /boot/initrd.img-3.16.0-4-amd64
> Found memtest86+ image: /boot/memtest86+.bin
> Found memtest86+ multiboot image: /boot/memtest86+_multiboot.bin
> No volume groups found
> done
>
> I'll reboot and see what happens.
>
mdadm --detail --scan >> /etc/mdadm/mdadm.conf
?
If they weren't then mdadm can't find them to add them to mdadm.conf.
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Pascal Hambourg
Jul 19, 2015, 2:50:04 PM7/19/15
to
Gary Dale a écrit :
find even inactive arrays.
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: https://lists.debian.org/55ABEC10...@plouf.fr.eu.org
>>
> Were your arrays running when you ran
> mdadm --detail --scan >> /etc/mdadm/mdadm.conf
> ?
>
> If they weren't then mdadm can't find them to add them to mdadm.conf.
That's why --examine is better than --detail for that purpose. It'll
> Were your arrays running when you ran
> mdadm --detail --scan >> /etc/mdadm/mdadm.conf
> ?
>
> If they weren't then mdadm can't find them to add them to mdadm.conf.
find even inactive arrays.
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Emanuel Berg
Jul 19, 2015, 7:20:04 PM7/19/15
to
Pascal Hambourg <pas...@plouf.fr.eu.org> writes:
> If you don't have any software RAID arrays, that's
> perfectly normal and you may uninstall mdadm (unless
> reverse dependencies exist). However if you think
> you have software RAID arrays, what's the output of
> the following command ?
>
> mdadm --detail --scan --verbose
This
> If you don't have any software RAID arrays, that's
> perfectly normal and you may uninstall mdadm (unless
> reverse dependencies exist). However if you think
> you have software RAID arrays, what's the output of
> the following command ?
>
> mdadm --detail --scan --verbose
$ sudo mdadm --detail --scan --verbose
doesn't produce any output.
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: https://lists.debian.org/874mkzp...@nl106-137-147.student.uu.se
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Emanuel Berg
Jul 19, 2015, 7:40:04 PM7/19/15
to
Gary Dale <gary...@torfree.net> writes:
> Were your arrays running when you ran
>
> mdadm --detail --scan >> /etc/mdadm/mdadm.conf ?
>
> If they weren't then mdadm can't find them to add
> them to mdadm.conf.
At this point, I don't know if I even have arrays.
> Were your arrays running when you ran
>
> mdadm --detail --scan >> /etc/mdadm/mdadm.conf ?
>
> If they weren't then mdadm can't find them to add
> them to mdadm.conf.
It is nothing I put there or ever mucked around with,
for sure.
/etc/mdadm/mdadm.conf looks like this:
# mdadm.conf
#
# Please refer to mdadm.conf(5) for information about this file.
#
# by default (built-in), scan all partitions (/proc/partitions) and all
# containers for MD superblocks. alternatively, specify devices to scan, using
# wildcards if desired.
#DEVICE partitions containers
# 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>
# instruct the monitoring daemon where to send mail alerts
MAILADDR root
# definitions of existing MD arrays
# This file was auto-generated on Wed, 14 Jan 2015 03:41:06 +0000
# by mkconf 3.2.5-5
Here is the output of:
$ find / -name \*mdadm\* 2> /dev/null
/sys/fs/cgroup/systemd/system.slice/mdadm-raid.service
/sbin/mdadm
/lib/systemd/system-shutdown/mdadm.shutdown
/lib/systemd/system/mdadm-waitidle.service
/lib/systemd/system/mdadm-last-resort@.timer
/lib/systemd/system/mdadm.service
/lib/systemd/system/mdadm-grow-continue@.service
/lib/systemd/system/mdadm-last-resort@.service
/var/lib/ucf/cache/:etc:aide:aide.conf.d:31_aide_mdadm
/var/lib/dpkg/info/mdadm.preinst
/var/lib/dpkg/info/mdadm.postinst
/var/lib/dpkg/info/mdadm.config
/var/lib/dpkg/info/mdadm.conffiles
/var/lib/dpkg/info/mdadm.list
/var/lib/dpkg/info/mdadm.prerm
/var/lib/dpkg/info/mdadm.md5sums
/var/lib/dpkg/info/mdadm.templates
/var/lib/dpkg/info/mdadm.postrm
/var/cache/apt/archives/mdadm_3.3.2-4_amd64.deb
/etc/rcS.d/S08mdadm-raid
/etc/modprobe.d/mdadm.conf
/etc/default/mdadm
/etc/logcheck/violations.d/mdadm
/etc/logcheck/ignore.d.server/mdadm
/etc/aide/aide.conf.d/31_aide_mdadm
/etc/rc5.d/S22mdadm
/etc/mdadm
/etc/mdadm/mdadm.conf
/etc/cron.d/mdadm
/etc/init.d/mdadm-waitidle
/etc/init.d/mdadm-raid
/etc/init.d/mdadm
/etc/rc4.d/S22mdadm
/etc/rc2.d/S22mdadm
/etc/rc3.d/S22mdadm
/etc/cron.daily/mdadm
/etc/rc1.d/K01mdadm
/etc/rc6.d/K11mdadm-raid
/etc/rc6.d/K12mdadm-waitidle
/etc/rc6.d/K01mdadm
/etc/rc0.d/K11mdadm-raid
/etc/rc0.d/K12mdadm-waitidle
/etc/rc0.d/K01mdadm
/usr/share/aide/config/aide/aide.conf.d/31_aide_mdadm
/usr/share/bug/mdadm
/usr/share/mdadm
/usr/share/doc-base/mdadm-readme-recipes
/usr/share/doc-base/mdadm-faq
/usr/share/zsh/functions/Completion/Linux/_mdadm
/usr/share/initramfs-tools/hooks/mdadm
/usr/share/initramfs-tools/scripts/local-top/mdadm
/usr/share/man-ooa/man8/mdadm.8
/usr/share/man-ooa/man5/mdadm.conf.5
/usr/share/doc/mdadm
/usr/share/doc/mdadm/examples/mdadm.conf-example
/usr/share/bash-completion/completions/mdadm
/run/systemd/generator.late/mdadm-raid.service
/run/systemd/generator.late/sysinit.target.wants/mdadm-raid.service
/run/mdadm
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: https://lists.debian.org/87vbdfo...@nl106-137-147.student.uu.se
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Emanuel Berg
Jul 19, 2015, 7:40:04 PM7/19/15
to
Pascal Hambourg <pas...@plouf.fr.eu.org> writes:
> mdadm --examine --scan --verbose
No output.
> mdadm --examine --scan --verbose
No output.
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: https://lists.debian.org/87zj2ro...@nl106-137-147.student.uu.se
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Arno Schuring
Jul 19, 2015, 7:50:04 PM7/19/15
to
> From: embe...@student.uu.se
> Date: Mon, 20 Jul 2015 01:05:08 +0200
>
> At this point, I don't know if I even have arrays.
> It is nothing I put there or ever mucked around with,
> for sure.
>
Assuming all your disks are online, just run blkid (as root). If you
have any (software) raid partitions, they will show up as:
/dev/sdc3: UUID="a6fad59a-fb65-69e0-c230-666b5103eba0" TYPE="linux_raid_member"
for a metadata 0.90 array member
/dev/sdc2: UUID="8c85fc73-c0f2-74f0-7fa0-20dd94538f5d" UUID_SUB="126427a1-e9c4-d5b6-29a6-609216e54318" LABEL="genie:0" TYPE="linux_raid_member"
for a metadata 1.2 array member
Regards,
Arno
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: https://lists.debian.org/DUB124-W181EFA513...@phx.gbl
Emanuel Berg
Jul 19, 2015, 8:00:07 PM7/19/15
to
Arno Schuring <aelsc...@hotmail.com> writes:
> Assuming all your disks are online, just run blkid
> (as root).
$ sudo blkid
> Assuming all your disks are online, just run blkid
> (as root).
/dev/sda1: UUID="e3dc978c-2ee3-4db8-a0cf-0a216a76930e" TYPE="ext4" PARTUUID="0006dea8-01"
/dev/sda5: UUID="abb7084e-c4da-4b9e-9477-3ae4aca56be8" TYPE="swap" PARTUUID="0006dea8-05"
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: https://lists.debian.org/87bnf7o...@nl106-137-147.student.uu.se
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Pascal Hambourg
Jul 20, 2015, 3:40:04 PM7/20/15
to
Emanuel Berg a écrit :
should know you do. So the message is normal, and you can uninstall
mdadm if it bothers you so much.
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: https://lists.debian.org/55AD49B...@plouf.fr.eu.org
>
> $ sudo blkid
> /dev/sda1: UUID="e3dc978c-2ee3-4db8-a0cf-0a216a76930e" TYPE="ext4" PARTUUID="0006dea8-01"
> /dev/sda5: UUID="abb7084e-c4da-4b9e-9477-3ae4aca56be8" TYPE="swap" PARTUUID="0006dea8-05"
Well, it seems that you don't have any software RAID. Otherwise, you
> $ sudo blkid
> /dev/sda1: UUID="e3dc978c-2ee3-4db8-a0cf-0a216a76930e" TYPE="ext4" PARTUUID="0006dea8-01"
> /dev/sda5: UUID="abb7084e-c4da-4b9e-9477-3ae4aca56be8" TYPE="swap" PARTUUID="0006dea8-05"
should know you do. So the message is normal, and you can uninstall
mdadm if it bothers you so much.
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Emanuel Berg
Jul 20, 2015, 7:20:04 PM7/20/15
to
Pascal Hambourg <pas...@plouf.fr.eu.org> writes:
> Well, it seems that you don't have any software
> RAID. Otherwise, you should know you do. So the
> message is normal, and you can uninstall mdadm if it
> bothers you so much.
OK :)
> Well, it seems that you don't have any software
> RAID. Otherwise, you should know you do. So the
> message is normal, and you can uninstall mdadm if it
> bothers you so much.
Thank you!
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: https://lists.debian.org/878uaat...@nl106-137-147.student.uu.se
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
0 new messages