Bug#962844: mdadm: Assembling RAID using IMSM in initrd fails due to lack of module efivarfs

2020-06-14 Thread Colin Fowler
Package: mdadm
Version: 4.1-1
Severity: critical
Justification: breaks the whole system

Dear Maintainer,

I created a RAID 5 volume over 4 disks using the BIOS support for Intel
RST. Install proceeded correctly, however after a reboot in to the
installed system, the root device was not found. Investigation in the
init shell found that the mdamd device had not been assembled correctly

The following error was encountered when looking for imsm capabilies on
the controller. 

mdadm --detail-platform
mdadm: imsm capabilities not found for controller: 
/sys/devices/pci:00/:00:1f.2 (type SATA)

I found that this occurred when mdadm could not read from 
/sys/firmware/efi/efivars/ due to it not being mounted. The efivarfs module was 
not found in the initrd

To resolve this, I booted in to a rescue CD and added efivarfs and
efivars to /etc/initramfs.conf/modules and ran an update-initramfs

This allowed the system to boot correctly

I suggest that mdadm ensures that these modules are added to the initrd
when the RAID array is using IMSM.


-- Package-specific info:
--- mdadm.conf
ARRAY metadata=imsm UUID=56bed0cd:2b07c313:c4651474:3a6b990c
ARRAY /dev/md/Volume0 container=56bed0cd:2b07c313:c4651474:3a6b990c member=0 
UUID=d0f942e0:fb69f9d0:bca65978:774a6c88
MAILADDR root

--- /etc/default/mdadm
AUTOCHECK=true
START_DAEMON=true
DAEMON_OPTIONS="--syslog"
VERBOSE=false

--- /proc/mdstat:
Personalities : [raid6] [raid5] [raid4] [linear] [multipath] [raid0] [raid1] 
[raid10] 
md126 : active raid5 sda[3] sdb[2] sdc[1] sdd[0]
  5567516672 blocks super external:/md127/0 level 5, 64k chunk, algorithm 0 
[4/4] []
  
md127 : inactive sdb[3](S) sdd[2](S) sdc[1](S) sda[0](S)
  20804 blocks super external:imsm
   
unused devices: 

--- /proc/partitions:
major minor  #blocks  name

   8   48 1953514584 sdd
   8   32 1953514584 sdc
   8   16 1953514584 sdb
   80 1953514584 sda
   9  126 5567516672 md126
 2590 525391 md126p1
 2591 5533714844 md126p2
 2592   33276403 md126p3

--- LVM physical volumes:
LVM does not seem to be used.
--- mount output
sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
udev on /dev type devtmpfs 
(rw,nosuid,relatime,size=16317648k,nr_inodes=4079412,mode=755)
devpts on /dev/pts type devpts 
(rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
tmpfs on /run type tmpfs (rw,nosuid,noexec,relatime,size=3266568k,mode=755)
/dev/md126p2 on / type ext4 (rw,relatime,errors=remount-ro,stripe=48)
securityfs on /sys/kernel/security type securityfs 
(rw,nosuid,nodev,noexec,relatime)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k)
tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,mode=755)
cgroup2 on /sys/fs/cgroup/unified type cgroup2 
(rw,nosuid,nodev,noexec,relatime,nsdelegate)
cgroup on /sys/fs/cgroup/systemd type cgroup 
(rw,nosuid,nodev,noexec,relatime,xattr,name=systemd)
pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime)
efivarfs on /sys/firmware/efi/efivars type efivarfs 
(rw,nosuid,nodev,noexec,relatime)
bpf on /sys/fs/bpf type bpf (rw,nosuid,nodev,noexec,relatime,mode=700)
cgroup on /sys/fs/cgroup/net_cls,net_prio type cgroup 
(rw,nosuid,nodev,noexec,relatime,net_cls,net_prio)
cgroup on /sys/fs/cgroup/rdma type cgroup (rw,nosuid,nodev,noexec,relatime,rdma)
cgroup on /sys/fs/cgroup/cpuset type cgroup 
(rw,nosuid,nodev,noexec,relatime,cpuset)
cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup 
(rw,nosuid,nodev,noexec,relatime,cpu,cpuacct)
cgroup on /sys/fs/cgroup/freezer type cgroup 
(rw,nosuid,nodev,noexec,relatime,freezer)
cgroup on /sys/fs/cgroup/pids type cgroup (rw,nosuid,nodev,noexec,relatime,pids)
cgroup on /sys/fs/cgroup/memory type cgroup 
(rw,nosuid,nodev,noexec,relatime,memory)
cgroup on /sys/fs/cgroup/blkio type cgroup 
(rw,nosuid,nodev,noexec,relatime,blkio)
cgroup on /sys/fs/cgroup/devices type cgroup 
(rw,nosuid,nodev,noexec,relatime,devices)
cgroup on /sys/fs/cgroup/perf_event type cgroup 
(rw,nosuid,nodev,noexec,relatime,perf_event)
systemd-1 on /proc/sys/fs/binfmt_misc type autofs 
(rw,relatime,fd=27,pgrp=1,timeout=0,minproto=5,maxproto=5,direct,pipe_ino=12482)
debugfs on /sys/kernel/debug type debugfs (rw,relatime)
mqueue on /dev/mqueue type mqueue (rw,relatime)
hugetlbfs on /dev/hugepages type hugetlbfs (rw,relatime,pagesize=2M)
/dev/md126p1 on /boot/efi type vfat 
(rw,relatime,fmask=0077,dmask=0077,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro)
tmpfs on /run/user/1000 type tmpfs 
(rw,nosuid,nodev,relatime,size=3266564k,mode=700,uid=1000,gid=1000)

--- initrd.img-4.19.0-9-amd64:
178049 blocks
192ccafcfe38eabf0f5184786764c4a9  ./scripts/local-bottom/mdadm
f3b648ca1c912da30940f0b821b7e9e6  ./scripts/local-block/mdadm
371839b6f84393a2c8d2988933b99f80  ./etc/mdadm/mdadm.conf
d3be82c0f275d6c25b04d388baf9e836  

Bug#738559: logrotate: Wildcard match first directory only

2014-02-11 Thread Colin Fowler

Can you send the output of ls -l /var/log/*/*.log please?


It was thousands of lines long, but comprised mostly of

/var/log/servername1/daemon.info.log
/var/log/servername2/daemon.info.log



Bear in mind that other installed programs may have a glob on *.log,
and a specific directory (eg. apache), and your pattern might
interfere with that.  I'd suggest logging into
/var/log/a-unique-name/xxx/yyy.log instead.


This works :)

Now logging to /var/log/servers/machinename/xxx.log

Thanks for the help!

Colin


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#738559: logrotate: Wildcard match first directory only

2014-02-10 Thread Colin Fowler
Package: logrotate
Version: 3.8.1-4
Severity: important

Dear Maintainer,

   * What exactly did you do (or not do) that was effective (or
 ineffective)?

Attempted to use /var/log/*/*.log to match /var/log/machinename/*.log on our 
central syslog server


   * What was the outcome of this action?

Logrotate only rotatated the first directory matched i.e.

/var/log/a/*.log was rotated

/var/log/b/*.log remained untouched

   * What outcome did you expect instead?

All logs in all directories under /var/log to be rotated


-- Package-specific info:
Contents of /etc/logrotate.d
total 24
-rw-r--r-- 1 root root 173 Jan 25  2011 apt
-rw-r--r-- 1 root root  79 Oct 16  2010 aptitude
-rw-r--r-- 1 root root 135 Jul 30  2012 consolekit
-rw-r--r-- 1 root root 232 Jan 30  2011 dpkg
-rw-r--r-- 1 root root 515 Mar  5  2013 rsyslog
-rw-r--r-- 1 root root 191 Dec  3 09:17 winbind


-- System Information:
Debian Release: 7.4
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.2.0-4-amd64 (SMP w/16 CPU cores)
Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages logrotate depends on:
ii  base-passwd 3.5.26
ii  cron [cron-daemon]  3.0pl1-124
ii  libc6   2.13-38+deb7u1
ii  libpopt01.16-7
ii  libselinux1 2.1.9-5

Versions of packages logrotate recommends:
ii  bsd-mailx [mailx]  8.1.2-0.2006cvs-1

logrotate suggests no packages.

-- Configuration Files:
/etc/logrotate.conf changed:
weekly
rotate 100
create
include /etc/logrotate.d
/var/log/wtmp {
missingok
monthly
create 0664 root utmp
rotate 1
}
/var/log/btmp {
missingok
monthly
create 0660 root utmp
rotate 1
}
/var/log/*/*.log {
daily
rotate 1114
create
compress
missingok
postrotate
invoke-rc.d rsyslog force-reload  /dev/null
endscript
}


-- no debconf information


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#632082: weka: Package version is out of date

2011-06-29 Thread Colin Fowler
Package: weka
Version: 3.6.0-3
Severity: wishlist


The version of Weka supplied in Debian is older than the base version required 
by the latest version of book Data Mining: Practical Machine Learning Tools 
and Techniques (Third Edition). The Stable book 3rd ed. version as listed at 
http://www.cs.waikato.ac.nz/ml/weka/  is 3.6.4. Can this please be updated?


-- System Information:
Debian Release: 6.0.1
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.32-5-amd64 (SMP w/3 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages weka depends on:
ii  cup0.11a+20060608-2  LALR parser generator for Java(tm)
ii  java-wrappers  0.1.16wrappers for java executables
ii  openjdk-6-jre  6b18-1.8.7-2~squeeze1 OpenJDK Java runtime, using Hotspo
ii  sun-java6-jre  6.24-1~squeeze1   Sun Java(TM) Runtime Environment (

weka recommends no packages.

weka suggests no packages.

-- no debconf information



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org