Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #240773
| From | Tim Woodall <debianuser@woodall.me.uk> |
|---|---|
| Newsgroups | linux.debian.user |
| Subject | Re: New mdadm RAID1 gets renamed from md3 to md127 after each reboot |
| Date | 2021-10-02 07:40 +0200 |
| Message-ID | <D3FUB-6sB-1@gated-at.bofh.it> (permalink) |
| References | <D3mRX-3hh-7@gated-at.bofh.it> <D3ryh-67d-1@gated-at.bofh.it> <D3sNK-6Nj-39@gated-at.bofh.it> <D3z2N-2c0-3@gated-at.bofh.it> <D3ABz-2Xh-3@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On Fri, 1 Oct 2021, Joe Pfeiffer wrote: > Tim Woodall <debianuser@woodall.me.uk> writes: > >> On Fri, 1 Oct 2021, Reiner Buehl wrote: >> >>> On 01.10.2021 16:11, Felix Miata wrote: >>>> Mine (old) is like so: >>>> # head -n3 /etc/mdadm.conf >>>> HOMEHOST <ignore> >>>> DEVICE containers partitions >>>> ARRAY /dev/md0 metadata=1.0 name=msi85:0tmp UUID=... >>> I tried changing the HOMEHOST from <system> to <ignore> but that did >>> not help. >>> >>> >> >> I've solved this but I don't recall how. > > Same here... FWIW my /etc/mdadm/mdadm.conf contains the line > ARRAY /dev/md/1 metadata=1.2 UUID=67d3c233:96a0737c:5f88ed9b:936ea3ae name=snowball:1 > > and my array is indeed /dev/md1 (I've got *no* recollection why I didn't > make it md0!). > > Is it possible you need to update your init ramdisk? Maybe your changes > to your mdadm.conf aren't being seen? > Don't think it's anything to do with the config file: root@debootstrap17:~# mdadm --examine --scan ARRAY /dev/md/debootstrap17 metadata=1.2 UUID=5e7d0dca:9f579eef:afb81eec:b0060281 name=debootstrap17 ARRAY /dev/md/5 metadata=1.2 UUID=1cdac5e5:c9fcac40:5e738a68:0a650b23 name=test:5 ARRAY /dev/md/test5 metadata=1.2 UUID=46ced7db:4b422364:1938cce3:6561f99d name=test5 That's with no arrays defined in the config file. After these commands: dd if=/dev/zero of=mdadm.blk bs=1M count=50 losetup -f mdadm.blk mdadm --create /dev/md/test:5 --metadata=1.2 --bitmap=internal --force --level=1 --raid-devices=1 /dev/loop0 mdadm --stop /dev/md/test\:5 dd if=/dev/zero of=mdadm2.blk bs=1M count=50 losetup -f mdadm2.blk mdadm --create /dev/md/test5 --metadata=1.2 --bitmap=internal --force --level=1 --raid-devices=1 /dev/loop1 mdadm --stop /dev/md/test5 mdadm --examine --scan
Back to linux.debian.user | Previous | Next — Previous in thread | Find similar | Unroll thread
New mdadm RAID1 gets renamed from md3 to md127 after each reboot Reiner Buehl <reiner.buehl@gmail.com> - 2021-10-01 11:20 +0200
Re: New mdadm RAID1 gets renamed from md3 to md127 after each reboot Linux-Fan <Ma_Sys.ma@web.de> - 2021-10-01 16:00 +0200
Re: New mdadm RAID1 gets renamed from md3 to md127 after each reboot Reiner Buehl <reiner.buehl@gmail.com> - 2021-10-01 17:40 +0200
Re: New mdadm RAID1 gets renamed from md3 to md127 after each reboot Felix Miata <mrmazda@earthlink.net> - 2021-10-01 16:20 +0200
Re: New mdadm RAID1 gets renamed from md3 to md127 after each reboot Reiner Buehl <reiner.buehl@gmail.com> - 2021-10-01 17:40 +0200
Re: New mdadm RAID1 gets renamed from md3 to md127 after each reboot Tim Woodall <debianuser@woodall.me.uk> - 2021-10-02 00:20 +0200
Re: New mdadm RAID1 gets renamed from md3 to md127 after each reboot Joe Pfeiffer <pfeiffer@cs.nmsu.edu> - 2021-10-02 02:00 +0200
Re: New mdadm RAID1 gets renamed from md3 to md127 after each reboot Reiner Buehl <reiner.buehl@gmail.com> - 2021-10-02 05:10 +0200
Re: New mdadm RAID1 gets renamed from md3 to md127 after each reboot Joe Pfeiffer <pfeiffer@cs.nmsu.edu> - 2021-10-04 04:10 +0200
Re: New mdadm RAID1 gets renamed from md3 to md127 after each reboot Reiner Buehl <reiner.buehl@gmail.com> - 2021-10-04 08:40 +0200
Re: New mdadm RAID1 gets renamed from md3 to md127 after each reboot Tim Woodall <debianuser@woodall.me.uk> - 2021-10-02 07:40 +0200
csiph-web