FS#16328 - fresh install populated /etc/fstab with wrong device
Attached to Project:
Release Engineering
Opened by chris (jugg) - Wednesday, 23 September 2009, 11:13 GMT
Last edited by Dieter Plaetinck (Dieter_be) - Thursday, 09 December 2010, 10:00 GMT
Opened by chris (jugg) - Wednesday, 23 September 2009, 11:13 GMT
Last edited by Dieter Plaetinck (Dieter_be) - Thursday, 09 December 2010, 10:00 GMT
|
Details
Description:
Fresh install on an old Toshiba Satellite 2805-s202 (p3-700mhz w/128mb ram) using: archlinux-2009.08-netinstall-i686.iso Got through the entire installation, rebooted into Arch, and got a JFS fsck error. I tracked the problem down using the recovery console that was provided after the error. /etc/fstab contained: /dev/hda1 /boot ext2 defaults 0 1 /dev/hda2 swap swap defaults 0 0 /dev/hda3 / jfs defaults 0 1 /dev/hda4 /home jfs defaults 0 1 However, on this system, the drive is /dev/sda meaning the fstab file should have contained: /dev/sda1 /boot ext2 defaults 0 1 /dev/sda2 swap swap defaults 0 0 /dev/sda3 / jfs defaults 0 1 /dev/sda4 /home jfs defaults 0 1 After fixing said problem and rebooting, everything appears to be working fine. I'm no linux guru and new to Arch, but if you ask for some additional information, I can probably provide it. |
This task depends upon
Closed by Dieter Plaetinck (Dieter_be)
Thursday, 09 December 2010, 10:00 GMT
Reason for closing: Fixed
Additional comments about closing: pick uuid/labelling
Thursday, 09 December 2010, 10:00 GMT
Reason for closing: Fixed
Additional comments about closing: pick uuid/labelling
Perhaps we should do away with the legacy boot option? Thomas, what configuration actually still needs legacy IDE, do you know?
However, it might just be our instructions that suck. Obviously, non-legacy works fine for you
Also, I believe the installation UI itself indicated that legacy ide should be used - something like "Legacy IDE, No SATA" - not just the manual/instructions.
So, it seems like there may be at least two issues here:
1. Installed with "legacy ide", but installed system booted without it and was "broken".
2. Documentation and Install UI (?) indicates one should use "legacy ide" if you don't use SATA.
I see two bugs here.
A) if booted with legacy IDE, we make sure the installed system uses the same boot method. This may actually be documented when configuring mkinitcpio during install.
B) the boot menu should expalin when to use legacy ide better
The bug:
I couldn't say why, but after installation, booting was throwing errors about the filesystem being unmountable due to filesystem types not matching. I did some digging from another distro installation, and found that the device files for the drives seemed to have rearranged ( I think this is some problem due to my hardware, I'm not totally certain )
I was wondering why not have fstab populated with drives listed by UUID, just have a comment above each giving the device that the installation detected? Changing my fstab to list drives by UUID was certainly how I solved the problem.
I wonder if the 2 problems said by Aaron are still relevant.
The workaround is just to remount the drive with write privileges, edit the /etc/fstab file and reboot. After that, the system behaves normally. It's a minor annoyance, but also a show-stopper if you're new to the Arch way, or if you overlook the possibility of the fstab being different from the drive labels. ;)
A) if booted with legacy IDE, we make sure the installed system uses the same boot method. This may actually be documented when configuring mkinitcpio during install.
-> is this still relevant?
B) the boot menu should expalin when to use legacy ide better
-> with isolinux, we don't even mention legacy ide anymore