Superblock Issues and fsck log

If you are having a problem with getting any of your computer's hardware to work with MEPIS or you can't find the right driver, this is the forum to use. It's for newbies and regular users to post questions. Just make sure to post what hardware you are having problems with, in the subject and not just in the post's text area, please.
Message
Author
User avatar
moksha
Forum Regular
Forum Regular
Posts: 573
Joined: Sun Dec 09, 2007 4:19 am

Superblock Issues and fsck log

#1 Postby moksha » Thu Dec 29, 2011 6:39 am

About six months ago I had some issues with partition numbering after replacing my motherboard, drives not being recognised or found by fstab, messages about bad magic numbers in superblocks. At the time I could not find a solution. The problem poked its head up again after a scheduled fsck scan at boot, and I started researching again and found a solution. All the disk and partition information is held in a cache /etc/blkid.tab. A line can be inserted into fstab to point directly to the partiton using its UUID or a simple command can be issued
# blkid -g

will clear the cache. The tune2fsk command which ties in with this stores all instructions on the drive the details can be recovered with this command
#tune2fs -l /dev/sdb1

I have updated Fsck and Fstab in the wiki, I hope this is helpful down the track for someone.

User avatar
JBoman
Forum Guide
Forum Guide
Posts: 1483
Age: 58
Joined: Wed Jul 12, 2006 4:30 pm

Re: Superblock Issues and fsck log

#2 Postby JBoman » Thu Dec 29, 2011 12:46 pm

moksha, If someone has to do that do the instructions get rebuilt automatically upon a reboot?;..... just curious. :turtle: Jerry
http://patentabsurdity.com/
AMD 64x2 2.6GHz 4GB ram MX-15 regular updates
"beware a frequent flirt with potential disaster"

User avatar
Jerry3904
Forum Veteran
Forum Veteran
Posts: 15334
Joined: Wed Jul 19, 2006 6:13 am

Re: Superblock Issues and fsck log

#3 Postby Jerry3904 » Thu Dec 29, 2011 12:49 pm

I have updated Fsck and Fstab in the wiki


:heart:
Production: 4.2.0-0.bpo.1-amd64, MX-15 RC1, AMD FX-4130 Quad-Core, GeForce GT 630/PCIe/SSE2, 8 GB, Kingston SSD 120 GB and WesternDigital 1TB
Testing: AAO 722: 3.16-0-4-686-pae. MX-15, AMD C-60 APU, 4 GB

User avatar
Danum
Forum Guide
Forum Guide
Posts: 2688
Joined: Sun Mar 25, 2007 5:49 pm

Re: Superblock Issues and fsck log

#4 Postby Danum » Thu Dec 29, 2011 1:08 pm

Using just UUID in Mepis is not a good idea, because if you use the correct command to upgrade, it comes up with, "unrecognized bootloader"
in other words the system has not got a clue as to what the legacy bootloader is, (yes it will boot but for how long) it expects to find Grub2.
Hopefully within the next few hours I will post the correct commands to use UUID but it will mean installing Grub2. so as the system does know what it is doing,
Desktop.
Zalman Z11 Plus ATX PC Tower, AMD FX 8350 Black Edition Vishera, 8 Core 4.4 GHz, Kingston HyperX FURY Red 16GB, Nvidia GT740 Graphics, Pioneer BDR-209EBK Writer, 2 x Seagate 1TB SSHD SATA Hybrid Hard Drives. ASUS VS278Q 27 inch HD Monitor

User avatar
Danum
Forum Guide
Forum Guide
Posts: 2688
Joined: Sun Mar 25, 2007 5:49 pm

Re: Superblock Issues and fsck log

#5 Postby Danum » Thu Dec 29, 2011 2:55 pm

The main reason for using persistent naming is because the drive name never changes as it does now in Mepis,
the easy way is to run "dpkg-reconfigure linux-base" but that presents a problem, as the system does not recognise the legacy bootloader in Mepis, yes it will run and it will boot, but for how long is anybodys quess.
http://dl.dropbox.com/u/53792173/grub-edit10.png
so you have to install Grub2 first, which you would do like this.
disable the Mepis repo in Synaptic, reload search for grub-common and upgrade it.
In Konsole as root,
apt-get update
rm -rf /boot/grub
apt-get purge grub-gfxboot
apt-get install grub2 os-prober desktop-base

when the above is complete you can now enable persistent naming
dpkg-reconfigure linux-base
reboot and re-enable the Mepis repo
Last edited by Danum on Thu Dec 29, 2011 5:07 pm, edited 1 time in total.
Desktop.
Zalman Z11 Plus ATX PC Tower, AMD FX 8350 Black Edition Vishera, 8 Core 4.4 GHz, Kingston HyperX FURY Red 16GB, Nvidia GT740 Graphics, Pioneer BDR-209EBK Writer, 2 x Seagate 1TB SSHD SATA Hybrid Hard Drives. ASUS VS278Q 27 inch HD Monitor

User avatar
moksha
Forum Regular
Forum Regular
Posts: 573
Joined: Sun Dec 09, 2007 4:19 am

Re: Superblock Issues and fsck log

#6 Postby moksha » Thu Dec 29, 2011 4:06 pm

JBoman wrote:moksha, If someone has to do that do the instructions get rebuilt automatically upon a reboot?;..... just curious. :turtle: Jerry

If you are talking about tune2fs the instructions 'live' in the drive and can be seen with tune2fs -l, so in a chainloaded boot setup the tune2fs commands are at a hardware level and do not care about reboots simply partition mounts. I believe and I have yet to try it that the tune2fs -c xx /dev/sdx instruction would survive an OS reinstall - linux that is. The instructions are probably in the form of set bits on the partiton, that increment with each boot.
The blkid -g command flushes the /etc/blkid.tab, and creates a backup, this is where the kernel and fstab looks for mount info at boot (not quite sure how that process works yet), so yes it survives rebooting.

User avatar
moksha
Forum Regular
Forum Regular
Posts: 573
Joined: Sun Dec 09, 2007 4:19 am

Re: Superblock Issues and fsck log

#7 Postby moksha » Fri Dec 30, 2011 4:58 am

Danum wrote:Using just UUID in Mepis is not a good idea, because if you use the correct command to upgrade, it comes up with, "unrecognized bootloader"
in other words the system has not got a clue as to what the legacy bootloader is, (yes it will boot but for how long) it expects to find Grub2.
Hopefully within the next few hours I will post the correct commands to use UUID but it will mean installing Grub2. so as the system does know what it is doing,

Just trying to get some clarity here, the UUID is not being used in menu.lst but after in fstab. However as I note in the wiki entry blkid -g may also be used which means a UUID does not need to be used at all. Thank you I will go back and make sure no confusion can arise from what I have written in the wiki.


Return to “Hardware General”

Who is online

Users browsing this forum: No registered users and 1 guest