View previous topic :: View next topic |
Author |
Message |
Perfect Gentleman Veteran
Joined: 18 May 2014 Posts: 1245
|
Posted: Fri Oct 24, 2014 6:11 am Post subject: fsck fat32 boot error or no mount |
|
|
got following situation:
1 - with this fstab, /boot is not mounting on boot
Code: | $ cat /etc/fstab
# <fs> <mountpoint> <type> <opts> <dump/pass>
# NOTE: If your BOOT partition is ReiserFS, add the notail option to opts.
/dev/sdd1 / ext4 rw,noatime,commit=777,discard 0 1
#
/dev/sde1 /boot vfat rw,noatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro 0 0
|
2 - with that fstab. I got fsck error on boot, so next services won't start.
Code: | $ cat /etc/fstab
# <fs> <mountpoint> <type> <opts> <dump/pass>
# NOTE: If your BOOT partition is ReiserFS, add the notail option to opts.
/dev/sdd1 / ext4 rw,noatime,commit=777,discard 0 1
#
/dev/sde1 /boot vfat rw,noatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro 0 2
|
vfat, codepage=437,iocharset=iso8859-1 are compiled as modules.
if compiled in kernel, would fsck error disappear? or problem is in another. |
|
Back to top |
|
|
RazielFMX l33t
Joined: 23 Apr 2005 Posts: 835 Location: NY, USA
|
Posted: Fri Oct 24, 2014 1:08 pm Post subject: |
|
|
You cannot have /boot or / FS as modules unless you have an initramfs. Start with compiling support into the kernel and see how it goes from there. _________________ I am not anti-systemd; I am pro-choice. If being the latter makes you feel that I am the former, then so be it. |
|
Back to top |
|
|
NeddySeagoon Administrator
Joined: 05 Jul 2003 Posts: 54097 Location: 56N 3W
|
Posted: Fri Oct 24, 2014 7:46 pm Post subject: |
|
|
RazielFMX,
/boot is OK as a module, as the kernel never reads it for itself
boot loaders have to make their own arrangements to read boot.
vfat is fragile. There should be nothing in /boot you dan't have elsewhere, except perhaps your boot loader config file.
If you feel lucky run fsck on it. It may make things worse. You could cut your losses and recreate /boot _________________ Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
Back to top |
|
|
Perfect Gentleman Veteran
Joined: 18 May 2014 Posts: 1245
|
Posted: Sat Oct 25, 2014 2:08 am Post subject: |
|
|
I use EFISTUB, kernel is stored on this UBS Flash which is FAT32. I got no bootloaders except efibootmgr. |
|
Back to top |
|
|
NeddySeagoon Administrator
Joined: 05 Jul 2003 Posts: 54097 Location: 56N 3W
|
Posted: Sat Oct 25, 2014 8:41 am Post subject: |
|
|
Perfect Gentleman,
The solution is still the same, fsck or rebuild /boot starting off by formatting it.
The vfat filesystem on /boot is broken. _________________ Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
Back to top |
|
|
Perfect Gentleman Veteran
Joined: 18 May 2014 Posts: 1245
|
Posted: Sat Oct 25, 2014 11:58 am Post subject: |
|
|
NeddySeagoon,
that's ok, it doesn't bother me much.
fsck.vfat doesn't find any non-recoverable problem, only problem with naming of non-existed file, it repairs it.
Code: | $ sudo fsck.vfat -a /dev/sde1
fsck.fat 3.0.26 (2014-03-07)
/
Bad short file name ().
Auto-renaming it.
Renamed to
/dev/sde1: 4 files, 1250/1954574 clusters
$ sudo fsck.vfat -aw /dev/sde1
fsck.fat 3.0.26 (2014-03-07)
/dev/sde1: 4 files, 1250/1954574 clusters
$ sudo fsck.vfat -aw /dev/sde1
fsck.fat 3.0.26 (2014-03-07)
/
Bad short file name ().
Auto-renaming it.
Renamed to
/dev/sde1: 4 files, 1250/1954574 clusters
|
|
|
Back to top |
|
|
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|