[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: dosfslabel finds problem, e2fsck does not



On Wed, Jul 21, 2010 at 08:28:59AM +0200, Florian Kulzer wrote:
> On Tue, Jul 20, 2010 at 20:09:27 -0400, Thomas H. George wrote:
> > On Tue, Jul 20, 2010 at 10:43:46PM +0200, Florian Kulzer wrote:
> > > On Tue, Jul 20, 2010 at 15:58:59 -0400, Thomas H. George wrote:
> > > > On Tue, Jul 20, 2010 at 07:23:31PM +0200, Florian Kulzer wrote:
> > > > > On Tue, Jul 20, 2010 at 11:25:42 -0400, Thomas H. George wrote:
> > > > > > My system, Squeeze, cannot install the latest kernel image because
> > > > > > dosfslabel finds a problem that prevents the installation of linux-base.
> > > > > > 
> > > > > > Trying to resolve this I used e2fsck to check each of the disk
> > > > > > partitions and e2fsck reported all the partitions clean.  However, the
> > > > > > result of running dosfslabel /dev/hda1 results in the following output:
> > > > > > 
> > > > > > 
> > > > > > There are differences between boot sector and its backup.
> > > > > > Differences: (offset:original/backup)
> > > 
> > > [...]
> > > 
> > > > > >   Not automatically fixing this.
> > > > > > NO NAME    
> > > > > > 
> > > > > > This hard drive used to have windoze installed and could be booted.  The
> > > > > > windoze partition was reformated to be an ext2 partition.
> > > 
> > > [...]
> > > 
> > > > > The first thing I would do is to check for signatures of other
> > > > > filesystems that were left behind on /dev/hda1:
> > > > > 
> > > > >   wipefs /dev/hda1
> > > 
> > > [...]
> > > 
> > > > No luck.  wipefs removed two bits
> > > 
> > > That is better in any case; such stale additional signatures cause
> > > problems for blkid.
> 
> Note: I misunderstood you here, assuming that you had actively removed
> the signatures yourself after checking that it made sense to do so.
> 
> [...]
> 
> > > I would like to see your output of
> > > 
> > >   wipefs /dev/hda1
> > 
> > No output.
> 
> That is not good; it should show at least the signature of the ext3
> filesystem.
> 
> # wipefs /dev/hda1
> offset               type
> ----------------------------------------------------------------
> 0x438                ext3   [filesystem]
>                      LABEL: root
>                      UUID:  51e39ea1-999d-4567-8e50-11ad53029e9c
> 
> >             There was output
> 
> I need to know exactly what this output was.
> 
> >                              before I ran wipe /dev/hda1 the first time.
> > It said it was removing two bits.
> 
> It should have done anything when run without options, unless you have a
> different version of until-linux than the current one for Squeeze. There
> was a reason for my explicitly asking you to read the manpage to make
> sure you understand what you are doing. I thought you understood the
> inherent risk of operations on the filesystem structure and that you
> would make an informed decision if that risk is worthwhile. I cannot
> make any more suggestions to you if you unquestioningly use the tools
> that I propose without regarding the caveats that I point out.

I did read the man page first.  It said wipefs -n /dev/hda1 would do
everything except the write call.  I ran it that way and the output was
much like the example you gave above with a message that two bits would
be removed.  I assumed the two bits were the leftover signature and ran
wipefs again without the -n option.  

Since then the computer was shutdown overnight.  Reboot this morning
stopped in maintenance mode reporting a bad superblock in /dev/hda1.  I
ran e2fsck -b xxxx /dev/hda1 where xxxx was the given alternate
superblock.  The systen then rebooted normally.

Now the output of wipefs -n /dev/hda1 is:


offset               type
----------------------------------------------------------------
0x438                ext2   [filesystem]
                     UUID:  2428f3c0-3098-448c-9484-587eb9f86e37

> 
> Does "blkid /dev/hda1" still return the correct label, UUID and type?
Yes

/dev/hda1: UUID="2428f3c0-3098-448c-9484-587eb9f86e37" TYPE="ext2" 

Installation of linux-base still fails as described previously and
dosfslabel /dev/hda1 still gives the error message posted prevously but
e2fsck /dev/hda1 says it is clean.

Tom
> 
> > > (to verify that the ext3 signature has the normal offset) and also the
> > > output of
> > > 
> > >   fdisk -l /dev/hda
> 
> [...]
> 
> > Disk /dev/hda: 30 GB, 30754321920 bytes
> > 255 heads, 63 sectors/track, 3739 cylinders
> > Units = cylinders of 16065 * 512 = 8225280 bytes
> > 
> >    Device Boot      Start         End      Blocks   Id  System 
> > /dev/hda1               1         243     1951866   83  Linux
> > /dev/hda2             244        3739    28073587    5  Extended
> > /dev/hda5             244        3739    28073587   83  Linux
> 
> That looks OK to me.
> 
> -- 
> Regards,            |
>           Florian   |
> 
> 
> -- 
> To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org 
> with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
> Archive: http://lists.debian.org/20100721062859.GA4305@isar.localhost
> 
> 


Reply to: