Not doing step 5 is something of an issue though. That should not happen. It most likely means that there was some kind of error during step 4. Could you output the result from
Code: Select all
tail /var/log/gentoo_install.log
Code: Select all
tail /var/log/gentoo_install.log
Code: Select all
fdisk /dev/sda -l
Code: Select all
umount /dev/sda3
umount /dev/sda4
Code: Select all
mkfs.ext4 -E lazy_itable_init=0,lazy_journal_init=0 -F -L "root" /dev/sda3
mkfs.ext4 -E lazy_itable_init=0,lazy_journal_init=0 -F -L "home" /dev/sda4
Code: Select all
emerge -O smartmontools
Code: Select all
smartctl -d ata -a /dev/sda | grep -i -E '(load_cycle|temp|Power_On_Hours|Device Model)'
This drive sat in my first B3 when I bought it about five years ago. I replaced it by a WD Red one and a half years ago, which was probably not a day too soon. Look at the ridiculous Load Cycle Count. It's almost double the number what the drive was designed to cope with. The drive also makes some rather noisy clicking sounds every few seconds and I'm kind of wondering whether that sound will increase, become more frequent or just simply stop when it gives up the ghost. For now it still does the job for testing installations though.b3 ~ # smartctl -d ata -a /dev/sda | grep -i -E '(load_cycle|temp|Power_On_Hours|Device Model)'
Device Model: WDC WD20EARS-00MVWB0
9 Power_On_Hours 0x0032 060 060 000 Old_age Always - 29834
193 Load_Cycle_Count 0x0032 003 003 000 Old_age Always - 591503
194 Temperature_Celsius 0x0022 119 093 000 Old_age Always - 31
b3 ~ #
Code: Select all
ACCEPT_KEYWORDS="**" emerge -avO1 idle3-tools
Code: Select all
idle3ctl -g /dev/sda
Code: Select all
idle3ctl -d /dev/sda
Code: Select all
idle3ctl -g /dev/sda