Your message dated Sat, 04 Oct 2014 23:26:26 +0100 with message-id <1412461586.9794.18.camel@decadent.org.uk> and subject line Re: Bug#764021: How are we going to boot with an empty etc/fstab? has caused the Debian Bug report #764021, regarding How are we going to boot with an empty etc/fstab? to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact owner@bugs.debian.org immediately.) -- 764021: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=764021 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: How are we going to boot with an empty etc/fstab?
- From: 積丹尼 Dan Jacobson <jidanni@jidanni.org>
- Date: Sun, 05 Oct 2014 05:04:24 +0800
- Message-id: <[🔎] 87ppe7r1gn.fsf@jidanni.org>
Package: initramfs-tools Version: 0.117 Severity: critical File: /usr/share/initramfs-tools/hooks/fsck How are we going to boot with an empty etc/fstab? It is the only empty file in the whole initrd.img ! dd if=/boot/initrd.img-3.16-2-686-pae skip=6|zcat| cpio -vt|perl -anwle 'next if /^d/; print unless $F[4]' 28648+1 records in 28648+1 records out 14667780 bytes (15 MB) copied, 1.00837 s, 14.5 MB/s 71060 blocks -rw-r--r-- 1 root root 0 Oct 5 03:38 etc/fstab Setting up initramfs-tools (0.117) ... update-initramfs: deferring update (trigger activated) Processing triggers for initramfs-tools (0.117) ... update-initramfs: Generating /boot/initrd.img-3.16-2-686-pae Warning: couldn't identify filesystem type for fsck hook, ignoring. OK in /etc/fstab I changed root's type from auto to ext4, reinstalled initramfs-tools, and the warning went away. But still couldn't boot, as etc/fstab as generated was still 0 bytes. Maybe one must take all the autos out completely. Here's my fstab. You can see if maybe that will fix it. UUID=355d426a-cbfc-4faf-91d6-4f9405199517 /home auto defaults,commit=222,noatime 0 2 UUID=34610b6a-70a3-48d9-b135-96907dc2ba16 /var auto defaults,commit=222,noatime 0 2 UUID=1d11e0e3-26d7-42be-89d2-00fbe939dc1c / ext4 defaults,commit=222,noatime,errors=remount-ro 0 1 UUID=4ff328e3-a3a7-44f7-a998-6c0404616e15 /music auto defaults,commit=222,noatime,user,noauto 0 2 /dev/cdrom5 /cdrom iso9660 defaults,ro,user,noauto 0 0 UUID=ce5499e2-019e-44cc-8f95-d027832b3d7d none swap sw 0 0 /dev/sr0 /mnt/usb/cdrom iso9660 defaults,user,noauto 0 0 tmpfs /tmp tmpfs defaults 0 0 UUID=00b63f91-edff-42db-8b45-81243ac43d44 /mnt/usb/cf auto noauto,noatime,errors=remount-ro 0 0 UUID=0000-006F /mnt/usb/s1mp3 vfat iocharset=ascii,shortname=mixed,noauto,noatime,nodiratime,user,fmask=133,uid=jidanni,gid=jidanni 0 0 UUID=26a1643a-011c-4d6b-8234-c327f9dc2495 /var/lib/apt/lists auto noauto,noatime,errors=remount-ro 0 0 UUID=82152152-fd1b-41f5-8860-a65f18de2275 /var/cache/apt/archives auto noauto,noatime,errors=remount-ro 0 0 I just don't see why initramfs-tools doesn't detect that it generated a 0 byte fstab and stop and think for a moment before exiting 0. When we try to boot we get lots of "-f: no such file or directory", "fsck: no such file or directory", "mount: Usage ..." etc. No init found, etc. P.S., other programs can deal with "auto". Indeed one must be able to use "auto" 100% in their fstabs! Does my using auto mean that my disks will no longer be checked?
--- End Message ---
--- Begin Message ---
- To: 764021-done@bugs.debian.org
- Subject: Re: Bug#764021: How are we going to boot with an empty etc/fstab?
- From: Ben Hutchings <ben@decadent.org.uk>
- Date: Sat, 04 Oct 2014 23:26:26 +0100
- Message-id: <1412461586.9794.18.camel@decadent.org.uk>
- In-reply-to: <[🔎] 87ppe7r1gn.fsf@jidanni.org>
- References: <[🔎] 87ppe7r1gn.fsf@jidanni.org>
On Sun, 2014-10-05 at 05:04 +0800, 積丹尼 Dan Jacobson wrote: > Package: initramfs-tools > Version: 0.117 > Severity: critical > File: /usr/share/initramfs-tools/hooks/fsck > > How are we going to boot with an empty etc/fstab? We don't; we use the one on the real root partition. It is only there to stop some utilities from warning. > It is the only empty file in the whole initrd.img ! > > dd if=/boot/initrd.img-3.16-2-686-pae skip=6|zcat| > cpio -vt|perl -anwle 'next if /^d/; print unless $F[4]' > 28648+1 records in > 28648+1 records out > 14667780 bytes (15 MB) copied, 1.00837 s, 14.5 MB/s > 71060 blocks > -rw-r--r-- 1 root root 0 Oct 5 03:38 etc/fstab > > Setting up initramfs-tools (0.117) ... > update-initramfs: deferring update (trigger activated) > Processing triggers for initramfs-tools (0.117) ... > update-initramfs: Generating /boot/initrd.img-3.16-2-686-pae > Warning: couldn't identify filesystem type for fsck hook, ignoring. > > OK in /etc/fstab I changed root's type from auto to ext4, reinstalled > initramfs-tools, and the warning went away. But still couldn't boot, as > etc/fstab as generated was still 0 bytes. > > Maybe one must take all the autos out completely. > > Here's my fstab. You can see if maybe that will fix it. > > UUID=355d426a-cbfc-4faf-91d6-4f9405199517 /home auto defaults,commit=222,noatime 0 2 > UUID=34610b6a-70a3-48d9-b135-96907dc2ba16 /var auto defaults,commit=222,noatime 0 2 > UUID=1d11e0e3-26d7-42be-89d2-00fbe939dc1c / ext4 defaults,commit=222,noatime,errors=remount-ro 0 1 > UUID=4ff328e3-a3a7-44f7-a998-6c0404616e15 /music auto defaults,commit=222,noatime,user,noauto 0 2 > /dev/cdrom5 /cdrom iso9660 defaults,ro,user,noauto 0 0 > UUID=ce5499e2-019e-44cc-8f95-d027832b3d7d none swap sw 0 0 > /dev/sr0 /mnt/usb/cdrom iso9660 defaults,user,noauto 0 0 > tmpfs /tmp tmpfs defaults 0 0 > UUID=00b63f91-edff-42db-8b45-81243ac43d44 /mnt/usb/cf auto noauto,noatime,errors=remount-ro 0 0 > UUID=0000-006F /mnt/usb/s1mp3 vfat iocharset=ascii,shortname=mixed,noauto,noatime,nodiratime,user,fmask=133,uid=jidanni,gid=jidanni 0 0 > UUID=26a1643a-011c-4d6b-8234-c327f9dc2495 /var/lib/apt/lists auto noauto,noatime,errors=remount-ro 0 0 > UUID=82152152-fd1b-41f5-8860-a65f18de2275 /var/cache/apt/archives auto noauto,noatime,errors=remount-ro 0 0 > > I just don't see why initramfs-tools doesn't detect that it generated a > 0 byte fstab and stop and think for a moment before exiting 0. > > When we try to boot we get lots of "-f: no such file or directory", > "fsck: no such file or directory", "mount: Usage ..." etc. No init > found, etc. Fixed in 0.118. Ben. > P.S., other programs can deal with "auto". Indeed one must be able to > use "auto" 100% in their fstabs! Does my using auto mean that my disks > will no longer be checked? > > -- Ben Hutchings One of the nice things about standards is that there are so many of them.Attachment: signature.asc
Description: This is a digitally signed message part
--- End Message ---