xfs
[Top] [All Lists]

Re: Linux partitions is good , but XFS couldn't mount....

To: Seungsoo Lee <yiseungsu@xxxxxxxxxxx>
Subject: Re: Linux partitions is good , but XFS couldn't mount....
From: Eric Sandeen <sandeen@xxxxxxx>
Date: Sun, 14 Dec 2003 14:51:47 -0600 (CST)
Cc: linux-xfs@xxxxxxxxxxx
In-reply-to: <Law15-F215I8OZhbAKy00037bdc@hotmail.com>
Sender: linux-xfs-bounce@xxxxxxxxxxx
I'm sorry, the only thing I can see that is a problem is:

XFS: bad magic number
XFS: SB validate failed

which means that block 0 of the disk is corrupt.  I don't know how
this has happened, and there is nothing below to help me figure
out what went wrong, perhaps you have filtered too much out
of the logs.  You can try xfs_repair, it may be able
to correct this.

-Eric

On Sun, 14 Dec 2003, Seungsoo Lee wrote:

> Dear, Eric Sandeen<sandeen@xxxxxxx>
> 
> Hi. I need more help.
> 
> I got messages well. I am surfing the Web to find docs ,Until now I 'm also 
> testing  to restore XFS filesystem.
> Before I give up early, this time I have to solve the problem.
> 
> 
> I used to do to make xfs system.
> 
> let's assume that I attached a hard disk on the secondary slave.
> 
> ===================================================
> 1.fdisk /dev/hdd
> /dev/hdd1  * 1 21889 171703 Linux (83)
> 
> 2.mkfs -t ext2 /dev/hdd1
> 3.mkfs.xfs -f /dev/hdd1
> =====================================================
> Above ways is used for me.
> 
> (1),(2) is alright. but (3) has problem.

It has a problem at mkfs time?

> 
> you asked me why I'm sure that there is no errors in my physical hard disk.
> 
> My disk(hdd) is still alive as "Linux native" but xfs was removed.
> 
> /dev/hdd1  * 1 21889 171703 Linux (83)
> 
> just don't configure the former XFS filesystem.
> 
> If I'm doing mkfs.xfs on this hard disks. Hard disk will survive physically.
> But. Data on that will disappear. I'm afraid that.
> 
> 
> =========================================================================
> [root@localhost sbin]# ./fdisk /dev/hdd
> 
> The number of cylinders for this disk is set to 21889.
> There is nothing wrong with that, but this is larger than 1024,
> and could in certain setups cause problems with:
> 1) software that runs at boot time (e.g., old versions of LILO)
> 2) booting and partitioning software from other OSs
>    (e.g., DOS FDISK, OS/2 FDISK)
> 
> Command (m for help): m
> Command action
>    a   toggle a bootable flag
>    b   edit bsd disklabel
>    c   toggle the dos compatibility flag
>    d   delete a partition
>    l   list known partition types
>    m   print this menu
>    n   add a new partition
>    o   create a new empty DOS partition table
>    p   print the partition table
>    q   quit without saving changes
>    s   create a new empty Sun disklabel
>    t   change a partition's system id
>    u   change display/entry units
>    v   verify the partition table
>    w   write table to disk and exit
>    x   extra functionality (experts only)
> 
> Command (m for help): p
> 
> Disk /dev/hdd: 180.0 GB, 180045766656 bytes
> 255 heads, 63 sectors/track, 21889 cylinders
> Units = cylinders of 16065 * 512 = 8225280 bytes
> 
>    Device Boot    Start       End    Blocks   Id  System
> /dev/hdd1   *         1     21889 175823361   83  Linux
> ============================================================================
> The real state of my disk.Above
> 
> 
> 
> 
> =======================================================================
> #dmesg: the ones related with XFS.
> ------------------------------------
> ...............
> 
> UDF-fs: No VRS found
> ISO 9660 Extensions: Microsoft Joliet Level 3
> ISOFS: changing to secondary root
> Journalled Block Device driver loaded
> kjournald starting.  Commit interval 5 seconds
> EXT3 FS 2.4-0.9.19, 19 August 2002 on ide0(3,65), internal journal
> EXT3-fs: recovery complete.
> EXT3-fs: mounted filesystem with ordered data mode.
> XFS: bad magic number
> XFS: SB validate failed
> kjournald starting.  Commit interval 5 seconds
> EXT3 FS 2.4-0.9.19, 19 August 2002 on sd(8,1), internal journal
> EXT3-fs: mounted filesystem with ordered data mode.
> VFS: Can't find ext3 filesystem on dev ide1(22,65).
> VFS: Can't find ext2 filesystem on dev ide1(22,65).
> XFS: bad magic number
> XFS: SB validate failed
> XFS: bad magic number
> XFS: SB validate failed
> kjournald starting.  Commit interval 5 seconds
> EXT3 FS 2.4-0.9.19, 19 August 2002 on sd(8,1), internal journal
> EXT3-fs: mounted filesystem with ordered data mode.
> VFS: Can't find ext3 filesystem on dev sd(8,1).
> VFS: Can't find ext3 filesystem on dev sd(8,1).
> VFS: Can't find ext3 filesystem on dev sd(8,1).
> kjournald starting.  Commit interval 5 seconds
> EXT3 FS 2.4-0.9.19, 19 August 2002 on sd(8,0), internal journal
> EXT3-fs: mounted filesystem with ordered data mode.
> kjournald starting.  Commit interval 5 seconds
> EXT3 FS 2.4-0.9.19, 19 August 2002 on sd(8,0), internal journal
> EXT3-fs: mounted filesystem with ordered data mode.
> VFS: Can't find ext3 filesystem on dev sd(8,1).
> XFS mounting filesystem sd(8,1)
> Ending clean XFS mount for filesystem: sd(8,1)
> kjournald starting.  Commit interval 5 seconds
> EXT3 FS 2.4-0.9.19, 19 August 2002 on sd(8,0), internal journal
> EXT3-fs: mounted filesystem with ordered data mode.
> kjournald starting.  Commit interval 5 seconds
> EXT3 FS 2.4-0.9.19, 19 August 2002 on sd(8,0), internal journal
> EXT3-fs: mounted filesystem with ordered data mode.
> XFS: bad magic number
> XFS: SB validate failed
> XFS mounting filesystem sd(8,1)
> Ending clean XFS mount for filesystem: sd(8,1)
> XFS mounting filesystem sd(8,1)
> XFS: failed to read root inode
> XFS mounting filesystem sd(8,0)
> Ending clean XFS mount for filesystem: sd(8,0)
> XFS mounting filesystem sd(8,1)
> XFS: failed to read root inode
> XFS mounting filesystem sd(8,1)
> XFS: failed to read root inode
> XFS mounting filesystem sd(8,0)
> Ending clean XFS mount for filesystem: sd(8,0)
> XFS mounting filesystem sd(8,1)
> Ending clean XFS mount for filesystem: sd(8,1)
> EFSCORRUPTED returned from file xfs_ialloc.c line 1313
> XFS mounting filesystem sd(8,1)
> Ending clean XFS mount for filesystem: sd(8,1)
> XFS mounting filesystem sd(8,1)
> Ending clean XFS mount for filesystem: sd(8,1)
> XFS mounting filesystem sd(8,1)
> Ending clean XFS mount for filesystem: sd(8,1)
> XFS mounting filesystem sd(8,1)
> Ending clean XFS mount for filesystem: sd(8,1)
> XFS: bad magic number
> XFS: SB validate failed
> XFS: bad magic number
> XFS: SB validate failed
> XFS: bad magic number
> XFS: SB validate failed
> XFS: bad magic number
> XFS: SB validate failed
> XFS: bad magic number
> XFS: SB validate failed
> XFS: bad magic number
> XFS: SB validate failed
> XFS: bad magic number
> XFS: SB validate failed
> VFS: Can't find ext2 filesystem on dev ide1(22,65).
> [lss1@localhost lssbin]$
> ===========================================================================
> 
> notes: I 'm testing another 2G scsi disk for XFS filesystem. Above some kind 
> of lines will maybe
> show the test result. expecially lines included ext3. I only use xfs.
> 
> 
> 
> my result:
> 1.physical hard disk is alright one hundred percent.
> 2.Linux native partitions is exist on hard disk.
> 3.the only former XFS is .....
> 
> help me one more time...
> 
> do I have format this?
>                                                  Thanks ...
> 
> 
>                                                from "yiseungsu@xxxxxxxxxxx"
> 
> _________________________________________________________________
> Help STOP SPAM with the new MSN 8 and get 2 months FREE*  
> http://join.msn.com/?page=features/junkmail
> 


<Prev in Thread] Current Thread [Next in Thread>
  • Re: Linux partitions is good , but XFS couldn't mount...., Eric Sandeen <=