Ben Hutchings wrote, on 13/10/14 06:16:
On Mon, 2014-10-13 at 02:38 +1030, Arthur Marsh wrote:Package: initramfs-tools Version: 0.116 Followup-For: Bug #764572 Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? Another datapoint. I have a hard disk whose filesystems are *not* mounted at start-up, but after a corruption issue, the disk's state causes a lock-up requiring a hardware reset and a second start-up (not helpful if this was a remote machine). On the second (successful) start-up I saw these messages: $ dmesg|grep sdc [ 4.934246] sd 2:0:1:0: [sdc] 66055248 512-byte logical blocks: (33.8 GB/31.4 GiB) [ 4.934523] sd 2:0:1:0: [sdc] Write Protect is off [ 4.934580] sd 2:0:1:0: [sdc] Mode Sense: 00 3a 00 00 [ 4.934703] sd 2:0:1:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 4.967651] sdc: sdc1 sdc2 < sdc5 sdc6 sdc7 > sdc3 [ 4.968073] sdc: p3 size 13333950 extends beyond EOD, enabling native capacity[...] This means: your hard drive has an HPA <https://en.wikipedia.org/wiki/Host_Protected_Area> configured, but you actually use that area under Linux. Linux automatically enables access to the HPA when it detects this. This was implemented in 2.6.34 and backported to squeeze; you just didn't notice the messages before. Ben.
Hi, I still have the issue that with initramfstools later than 0.116 (ie 0.117 and 0.118) that with the disks corrupted, the boot process would hang.
With initramfs-tools 0.116, the boot process proceeded normally and successfully run fsck on the filesystems to be mounted (the disk above with a HPA was not listed in /etc/fstab to have any filesystems mounted).
I'm not sure how to reproduce this bug without resorting to somehow deliberately corrupting a filesystem and/or disk partition table.
Regards, Arthur. -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: https://lists.debian.org/[email protected]
