# This configuration was auto-generated on Fri, 11:10:41 +0200 by mkconf # instruct the monitoring daemon where to send mail alertsĪRRAY /dev/md/0 metadata=1.2 UUID=a930b085:1e1a615b:93e209e6:08314607 name=tinas:0 # automatically tag new arrays as belonging to the local system # auto-create devices with Debian standard permissionsĬREATE owner=root group=disk mode=0660 auto=yes alternatively, specify devices to scan, using # by default (built-in), scan all partitions (/proc/partitions) and all # Please refer to nf(5) for information about this file. Raid1 is loaded because I added it to /etc/modules, otherwise, before, it was loaded. Search fr raid loaded modules grep -E 'md_mod|raid1' /proc/modules I uncommented the udev_log = info line in /etc/udev/nf but can't see anything new. ![]() If anyone knows how to get some traces from udev, it would be great. I tried dpkg-reconfigure mdadm : nothing new. Would that be because the raid1 module seems to be loaded after udev events are generated ? Here's the according log : avril 15 12:23:21 tinas mdadm-raid: Generating udev events for MD arrays.done.Īvril 15 12:23:22 tinas systemd-modules-load: Inserted module 'raid1'Īvril 15 12:23:22 tinas kernel: md: raid1 personality registered for level 1īut the array is still not assembled: cat /proc/mdstat Unused devices: I added the raid1 module to /etc/modules, issued an update-initramfs -u. I just realized that right after boot the raid1 module isn't loaded ! cat /proc/mdstat Here, I'm not sure if the type value is correct 'Linux RAID' as I've read that 0xFD is expected but that value doesn't seem available through fdisk with GPT partition table.įrom journalctl -xb I can find one trace : Apr 14 15:14:46 tinas mdadm-raid: Generating udev events for MD arrays.done.Īpr 14 15:35:03 tinas kernel: md: md0 stopped.Īpr 14 15:35:03 tinas kernel: md: bindĪpr 14 15:35:04 tinas kernel: md: raid1 personality registered for level 1Īpr 14 15:35:04 tinas kernel: md/raid1:md0: active with 2 out of 2 mirrorsĪpr 14 15:35:04 tinas kernel: created bitmap (15 pages) for device md0Īpr 14 15:35:04 tinas kernel: md0: bitmap initialized from disk: read 1 pages, set 0 of 29807 bitsĪpr 14 15:35:04 tinas kernel: md0: detected capacity change from 0 to 2000263643136Īpr 14 15:35:04 tinas kernel: md0: unknown partition tableĪpr 14 15:35:04 tinas kernel: BTRFS: device fsid b8a72591-040e-4ca1-a663-731a5dcbebc2 devid 1 transid 8 /dev/md0 Taille d'E/S (minimale / optimale) : 4096 octets / 4096 octets Taille de secteur (logique / physique) : 512 octets / 4096 octets Md0 : active (auto-read-only) raid1 sdc1 sdd1 ![]() When manually assembled, the array looks like this : cat /proc/mdstat Manually assembling it doesn't trigger any error. If that line in fstab is commented, then the boot process goes to the end BUT the RAID array isn't available. ![]() And thus, systemd falls back to some degraded shell after trying to mount the FS described in /etc/fstab. But it is not assembled automatically at boot time. I'm running Debian Jessie with a standard 3.16 kernel. First, I prefer to mention I've found and read this.
0 Comments
Leave a Reply. |