[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#764572: initramfs-tools: fails to finish booting with dirty filesystem(s)



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.

-- 
Ben Hutchings
It is easier to change the specification to fit the program than vice versa.

Attachment: signature.asc
Description: This is a digitally signed message part


Reply to: