FS#28679 - [mkinitcpio] the fsck hook fails if the / fileystem is other than /usr filesystem

Attached to Project: Arch Linux
Opened by Dikiy (dikiy) - Monday, 27 February 2012, 11:51 GMT
Last edited by Dave Reisner (falconindy) - Sunday, 18 March 2012, 18:57 GMT
Task Type Bug Report
Category Arch Projects
Status Closed
Assigned To Dave Reisner (falconindy)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

The fsck hook fails if the / fileystem is other than /usr filesystem

Steps to reproduce:

1. Create / FS with ext2
2. Create /usr FS with ext4
3. Do mkinitcpio whith fsck and autodetect hooks
4. reboot
This task depends upon

Closed by  Dave Reisner (falconindy)
Sunday, 18 March 2012, 18:57 GMT
Reason for closing:  Fixed
Comment by Karol Błażewicz (karol) - Monday, 27 February 2012, 14:46 GMT
Is it the same as  FS#28653  ?
Comment by Dikiy (dikiy) - Monday, 27 February 2012, 15:46 GMT
No, it isn't. The ugly workaround worked for me:

build() {
local added=0

###workaround
fs_autodetect_failed=1
###

if (( ! fs_autodetect_failed )) && [[ $rootfstype ]]; then
add_binary /sbin/fsck.$rootfstype && (( ++added ))
else
for fsck in "$BASEDIR"/sbin/fsck.*; do
[[ -f $fsck ]] || continue
add_binary "${fsck#$BASEDIR}" && (( ++added ))
done
fi

if (( added )); then
add_binary /sbin/fsck
else
warning "No fsck helpers found. fsck will not be run on boot."
fi
}
Comment by Dave Reisner (falconindy) - Monday, 27 February 2012, 17:38 GMT
Zero mention of the version -- this should already be fixed in testing.
Comment by Dave Reisner (falconindy) - Saturday, 17 March 2012, 02:46 GMT
Retest? This is in core
Comment by Dikiy (dikiy) - Sunday, 18 March 2012, 18:56 GMT
Tested. Work's fine. Bug can be closed.

Loading...