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

Re: ext3 file system mounted on device (sdc) rather than partition (sdc1)?



Michael Hannon wrote:
> Greetings.  We've got a machine at work that's running Fedora 8, i386.
> The machine has two external drives, both mounted to an eSATA controller
> (Silicon Image, Inc. SiI 3114 SATARaid Controller).
> 
> The disks are 750GB and 500GB, respectively, in size.
> 
> Everything seems to work as expected, except that the 750GB drive is
> somehow getting mounted on the device, rather than on a partition:
> 
>     /dev/sdc              688G  554G  100G  85% /local3
> 
> There IS a partition on the drive:
> 
>     # fdisk -l /dev/sdc
> 
>     Disk /dev/sdc: 750.1 GB, 750156374016 bytes
>     255 heads, 63 sectors/track, 91201 cylinders
>     Units = cylinders of 16065 * 512 = 8225280 bytes
>     Disk identifier: 0x3e863a4f
> 
>        Device Boot      Start         End      Blocks   Id  System
>     /dev/sdc1               1       91201   732572001   83  Linux
> 
> 
> But my attempt to mount the drive on sdc1 results in:
> 
>     # mount -t ext3 /dev/sdc1 /local3
>     mount: wrong fs type, bad option, bad superblock on /dev/sdc1,
>            missing codepage or helper program, or other error
>            In some cases useful info is found in syslog - try
>            dmesg | tail  or so
> 
> I don't really understand what's going on here or how the system got
> into this peculiar configuration.
> 
> I'm inclined to back up the data from the mounted /local3, then
> re-create the partition, then re-initialize the file system on sdc1,
> then restore the data.
> 
> But I was wondering if there might be some way to short-circuit that
> process, maybe by using dd to copy some information from /dev/sdc to
> /dev/sdc1.  Is this possible?  If so, is it risky?  Is there a better
> approach?
> 
> 
I don't think you will find a shortcut - the file system IS the
entire drive, so the offsets are all going to be wrong if you change
where the file system starts. (Superblocks in the wrong place.)

As for what happened, it looks like someone did mke2fs on /dev/sdc
instead of /dev/sdc1/ What I would be tempted to do is edit the
partition table and get rid of the partition, and leave it as
/dev/sdc instead. It will work fine - it only looks strange.

In any case, I would make a full backup before making any changes.

Mikkel
-- 

  Do not meddle in the affairs of dragons,
for thou art crunchy and taste good with Ketchup!

Attachment: signature.asc
Description: OpenPGP digital signature


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