[opensuse] Trouble formatting a linux partition
Hello, Hope someone can shine some light on the problem I'm having. I've formatted several drives in the past and have not seen this problem. I'm trying to use a 500G drive which was a linux system with swap. I fdisk to delete all the old partitions and created one single partition. One strange thing is the partition starts at 2048. Had no choice. =========== The following is from fdisk Disk /dev/sdc: 465.8 GiB, 500107862016 bytes, 976773168 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: gpt Disk identifier: 0x000af975 Device Boot Start End Sectors Size Id Type /dev/sdc1 2048 976773167 976771120 465.8G 83 Linux ============= Try to format it with fsck.ext2 yields: e2fsck 1.43.3 (04-Sep-2016) ext2fs_open2: Bad magic number in super-block fsck.ext2: Superblock invalid, trying backup blocks... fsck.ext2: Bad magic number in super-block while trying to open /dev/sdc1 The superblock could not be read or does not describe a valid ext2/ext3/ext4 filesystem. If the device is valid and it really contains an ext2/ext3/ext4 filesystem (and not swap or ufs or something else), then the superblock is corrupt, and you might try running e2fsck with an alternate superblock: e2fsck -b 8193 <device> or e2fsck -b 32768 <device> /dev/sdc1 contains a swap file system ============= Any ideas how to format this drive for use and a data storage/backup drive? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 01/02/2017 03:26 PM, Terry Eck wrote:
Hello, Hope someone can shine some light on the problem I'm having. I've formatted several drives in the past and have not seen this problem.
I'm trying to use a 500G drive which was a linux system with swap.
I fdisk to delete all the old partitions and created one single partition. One strange thing is the partition starts at 2048. Had no choice. =========== The following is from fdisk
Disk /dev/sdc: 465.8 GiB, 500107862016 bytes, 976773168 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: gpt Disk identifier: 0x000af975
Device Boot Start End Sectors Size Id Type /dev/sdc1 2048 976773167 976771120 465.8G 83 Linux =============
Try to format it with fsck.ext2 yields: e2fsck 1.43.3 (04-Sep-2016) ext2fs_open2: Bad magic number in super-block fsck.ext2: Superblock invalid, trying backup blocks... fsck.ext2: Bad magic number in super-block while trying to open /dev/sdc1
The superblock could not be read or does not describe a valid ext2/ext3/ext4 filesystem. If the device is valid and it really contains an ext2/ext3/ext4 filesystem (and not swap or ufs or something else), then the superblock is corrupt, and you might try running e2fsck with an alternate superblock: e2fsck -b 8193 <device> or e2fsck -b 32768 <device>
/dev/sdc1 contains a swap file system
=============
Any ideas how to format this drive for use and a data storage/backup drive?
2048 is the correct default starting sector. I noticed your disk label says "gpt", and fdisk is not recommended for creating a GPT partition. For that, you want to use gdisk. In your case it the disk may be formatted as the traditional MBR format, and just has the gpt label so I would check on that to be sure. fdisk can create GPT partitions but you will see in the documentation that it's experimental. You need to specify mkfs to format a partition, not a block device. For instance:|`mkfs.ext4 /dev/sdc1` NOT |||`mkfs.ext4 /dev/sdc`. btrfs can handle formatting an entire block device without having first created a partition. Ext4 can't. Example: `mkfs.btrfs /dev/sdc` would create one large partition on a hard drive.| | -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Le 03/01/2017 à 00:42, sdm a écrit :
2048 is the correct default starting sector. I noticed your disk label says "gpt", and fdisk is not recommended for creating a GPT partition.
t(hat's wrong on openSUSE, fdisk was patched to be able to format gpt and I use it often. however, on openSUSE, better use YaST, you can even change partition table from GPT to DOS and vice-versa (expert options) jdd -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 01/02/2017 11:11 PM, jdd wrote:
t(hat's wrong on openSUSE, fdisk was patched to be able to format gpt and I use it often.
however, on openSUSE, better use YaST, you can even change partition table from GPT to DOS and vice-versa (expert options)
jdd
Someone else in this thread said that fdisk doesn't wipe gpt partition information at the end of the disk (only at the beginning), but I have a feeling this is incorrect as technically fdisk can manage gpt partitions. I just got used to using gdisk as fdisk used to warn that formatting a disk as gpt is experimental. I don't know if it still gives the same warning or not. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Le 03/01/2017 à 16:00, sdm a écrit :
Someone else in this thread said that fdisk doesn't wipe gpt partition information at the end of the disk (only at the beginning), but I have a feeling this is incorrect as technically fdisk can manage gpt partitions. I just got used to using gdisk as fdisk used to warn that formatting a disk as gpt is experimental. I don't know if it still gives the same warning or not.
there are several fdisk around... openSUSE specific default one was patched by openSUSE to allow GPT. I guess this is also upstream now, but my be not on every version. anyway, better use taST when you have openSUSE, there may be other protections against errors jdd -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 01/03/2017 09:00 AM, sdm wrote:
Someone else in this thread said that fdisk doesn't wipe gpt partition information at the end of the disk (only at the beginning), but I have a feeling this is incorrect as technically fdisk can manage gpt partitions. I just got used to using gdisk as fdisk used to warn that formatting a disk as gpt is experimental. I don't know if it still gives the same warning or not.
That was me, and it depends on the patches/version of fdisk. I was hit by this on arch within the last year or so as arch provides gdisk, parted, etc. for GPT handling and typically does not patch upstream for extended functionality. After attempting to change partition tables types, the secondary GPT table remained causing all kinds of havok when the underlying disks were assembled in linux-raid. 'wipefs' is your friend here -- it can remove the unused GPT tables without affecting your DOS partitioning. -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 02/01/17 23:42, sdm wrote:
You need to specify mkfs to format a partition, not a block device. For instance:|`mkfs.ext4 /dev/sdc1` NOT |||`mkfs.ext4 /dev/sdc`. btrfs can handle formatting an entire block device without having first created a partition. Ext4 can't. Example: `mkfs.btrfs /dev/sdc` would create one large partition on a hard drive.| |
That's wrong. If you give the command mkfs.ext4 /dev/sdc it will work fine. Which means it's **** dangerous :-) because if you've gone and partitioned your disk etc etc it will simply stomp all over it quite happily, including any data you may have put in other partitions. (I haven't played with it - hopfully it requires a -f option by default, but I doubt it :-( All mkfs expects is a block device, and I doubt it cares whether it's sdc or sdc1. It probably can't even tell! Although running mkfs on a bare drive such is sdc is a pretty stupid idea. Not because you shouldn't, but because nobody else does. And leaving nasty surprises like that for the next guy is exactly what will cause a catastrophic failure, as they do what they think should be safe and it does something nasty on your non-standard setup :-( Somebody modified a system of mine to do that, and every time I went there afterwards I had to watch out to make sure I didn't cause a disaster. Cheers, Wol -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 04/01/17 19:35, Wols Lists wrote:
On 02/01/17 23:42, sdm wrote:
You need to specify mkfs to format a partition, not a block device. For instance:|`mkfs.ext4 /dev/sdc1` NOT |||`mkfs.ext4 /dev/sdc`. btrfs can handle formatting an entire block device without having first created a partition. Ext4 can't. Example: `mkfs.btrfs /dev/sdc` would create one large partition on a hard drive.| |
That's wrong. If you give the command
mkfs.ext4 /dev/sdc
it will work fine. Which means it's **** dangerous :-) because if you've gone and partitioned your disk etc etc it will simply stomp all over it quite happily, including any data you may have put in other partitions. (I haven't played with it - hopfully it requires a -f option by default, but I doubt it :-( All mkfs expects is a block device, and I doubt it cares whether it's sdc or sdc1. It probably can't even tell!
Although running mkfs on a bare drive such is sdc is a pretty stupid idea. Not because you shouldn't, but because nobody else does. And leaving nasty surprises like that for the next guy is exactly what will cause a catastrophic failure, as they do what they think should be safe and it does something nasty on your non-standard setup :-( Somebody modified a system of mine to do that, and every time I went there afterwards I had to watch out to make sure I didn't cause a disaster.
Whoops. Re-reading your post, I think you know that, I just think you worded it wrong ... Sorry. Cheers, Wol -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Wednesday 2017-01-04 20:35, Wols Lists wrote:
On 02/01/17 23:42, sdm wrote:
You need to specify mkfs to format a partition, not a block device. For instance:|`mkfs.ext4 /dev/sdc1` NOT |||`mkfs.ext4 /dev/sdc`. btrfs can handle formatting an entire block device without having first created a partition. Ext4 can't. Example: `mkfs.btrfs /dev/sdc` would create one large partition on a hard drive.| |
That's wrong. If you give the command
mkfs.ext4 /dev/sdc
it will work fine. Which means it's **** dangerous :-) because if you've gone and partitioned your disk etc etc it will simply stomp all over it quite happily, including any data you may have put in other partitions. (I haven't played with it - hopfully it requires a -f option by default, but I doubt it :-( All mkfs expects is a block device, and I doubt it cares whether it's sdc or sdc1. It probably can't even tell!
Although running mkfs on a bare drive such is sdc is a pretty stupid idea. Not because you shouldn't, but because nobody else does. And
I do regularly. Exactly for /dev/sdc. It's my (scsi) floppy drive. never saw a partitioned floppy. ;)
leaving nasty surprises like that for the next guy is exactly what will cause a catastrophic failure, as they do what they think should be safe and it does something nasty on your non-standard setup :-( Somebody modified a system of mine to do that, and every time I went there afterwards I had to watch out to make sure I didn't cause a disaster.
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 01/04/2017 12:41 PM, Paul Neuwirth wrote:
Although running mkfs on a bare drive such is sdc is a pretty stupid idea. Not because you shouldn't, but because nobody else does. And
I do regularly. Exactly for /dev/sdc. It's my (scsi) floppy drive. never saw a partitioned floppy. ;)
I remember having to to use the bare drive once with RHEL on a raid array that exceeded 16-TB. This was almost 10-years ago, there must have been something funky with the partition labels. Filesystem was XFS and I remember having to manually load/install it on RHEL, it wasn't "cooked in". I never did like Red Hat, it's why I originally picked up SuSE 5.2. But that's another story. Regards, Lew -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 04/01/17 20:56, Lew Wolfgang wrote:
I never did like Red Hat, it's why I originally picked up SuSE 5.2. But that's another story.
ditto. Except iirc it was SuSE 5.4 for me :-) Cheers, Wol -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Le 04/01/2017 à 21:41, Paul Neuwirth a écrit :
I do regularly. Exactly for /dev/sdc. It's my (scsi) floppy drive. never saw a partitioned floppy. ;)
can be done (I did) but not likely :-) jdd -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Paul Neuwirth wrote:
On Wednesday 2017-01-04 20:35, Wols Lists wrote:
On 02/01/17 23:42, sdm wrote:
You need to specify mkfs to format a partition, not a block device. For instance:|`mkfs.ext4 /dev/sdc1` NOT |||`mkfs.ext4 /dev/sdc`. btrfs can handle formatting an entire block device without having first created a partition. Ext4 can't. Example: `mkfs.btrfs /dev/sdc` would create one large partition on a hard drive.| |
That's wrong. If you give the command
mkfs.ext4 /dev/sdc
it will work fine. Which means it's **** dangerous :-) because if you've gone and partitioned your disk etc etc it will simply stomp all over it quite happily, including any data you may have put in other partitions. (I haven't played with it - hopfully it requires a -f option by default, but I doubt it :-( All mkfs expects is a block device, and I doubt it cares whether it's sdc or sdc1. It probably can't even tell!
Although running mkfs on a bare drive such is sdc is a pretty stupid idea. Not because you shouldn't, but because nobody else does. And
I do regularly. Exactly for /dev/sdc. It's my (scsi) floppy drive. never saw a partitioned floppy. ;)
Wow, a SCSI floppy drive. Wow. As for formatting an entire drive, we do it all the time - mdraid devices. -- Per Jessen, Zürich (-1.4°C) http://www.dns24.ch/ - your free DNS host, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Thu, 05 Jan 2017 09:20:56 +0100 Per Jessen <per@computer.org> wrote:
As for formatting an entire drive, we do it all the time - mdraid devices.
I don't recommend that, myself. Too easy to accidentally overwrite the start with something else. I was bitten a couple of times and after that I started putting a small empty partition at the start of the disk, and at the end, to guard against such accidents. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Dave Howorth wrote:
On Thu, 05 Jan 2017 09:20:56 +0100 Per Jessen <per@computer.org> wrote:
As for formatting an entire drive, we do it all the time - mdraid devices.
I don't recommend that, myself. Too easy to accidentally overwrite the start with something else. I was bitten a couple of times and after that I started putting a small empty partition at the start of the disk, and at the end, to guard against such accidents.
We've been doing it since the beginning, around 2006. Sofar it has not caused any problems or accidents. Once in production, these systems are rarely touched. -- Per Jessen, Zürich (-0.6°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 05/01/17 12:07, Dave Howorth wrote:
On Thu, 05 Jan 2017 09:20:56 +0100 Per Jessen <per@computer.org> wrote:
As for formatting an entire drive, we do it all the time - mdraid devices.
I don't recommend that, myself. Too easy to accidentally overwrite the start with something else. I was bitten a couple of times and after that I started putting a small empty partition at the start of the disk, and at the end, to guard against such accidents.
You can't do it on your system disk(s), but any arrays that are data only, several high-profile raid kernel coders do it. (In order to boot from a disk, you need either space to install grub at the start, or an EFI partition. The first will stomp over the raid array and the second will, obviously, force you to partition :-) Cheers, Wol -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Wols Lists wrote:
On 05/01/17 12:07, Dave Howorth wrote:
On Thu, 05 Jan 2017 09:20:56 +0100 Per Jessen <per@computer.org> wrote:
As for formatting an entire drive, we do it all the time - mdraid devices.
I don't recommend that, myself. Too easy to accidentally overwrite the start with something else. I was bitten a couple of times and after that I started putting a small empty partition at the start of the disk, and at the end, to guard against such accidents.
You can't do it on your system disk(s), but any arrays that are data only, several high-profile raid kernel coders do it.
(In order to boot from a disk, you need either space to install grub at the start, or an EFI partition. The first will stomp over the raid array and the second will, obviously, force you to partition :-)
As an aside - I boot lilo from RAID1 arrays all the time, works very well. Seems to me grub ought to work too, but I'm not grub-literate. -- Per Jessen, Zürich (-5.6°C) http://www.dns24.ch/ - your free DNS host, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Mon, 2 Jan 2017 17:26:21 -0600 Terry Eck wrote:
Disklabel type: gpt
This is the problem, Terry. fdisk isn't compatible with GPT (GUID Partition Table). Here's a good overview: http://www.howtogeek.com/193669/whats-the-difference-between-gpt-and-mbr-whe... hth & regards, Carl -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 01/02/2017 05:46 PM, Carl Hartung wrote:
On Mon, 2 Jan 2017 17:26:21 -0600 Terry Eck wrote:
Disklabel type: gpt This is the problem, Terry. fdisk isn't compatible with GPT (GUID Partition Table). Here's a good overview:
http://www.howtogeek.com/193669/whats-the-difference-between-gpt-and-mbr-whe...
hth & regards,
Carl
Thanks Carl, but originally the Disklabel type: was DOS. I thought since my current system drive had a type of gpt I should change it. I could post the same information with Disklabel type : DOS and it would not change the problem. There is some other problem Terry -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Mon, 2 Jan 2017 17:58:00 -0600 Terry Eck wrote:
On 01/02/2017 05:46 PM, Carl Hartung wrote:
On Mon, 2 Jan 2017 17:26:21 -0600 Terry Eck wrote:
Disklabel type: gpt This is the problem, Terry. fdisk isn't compatible with GPT (GUID Partition Table). Here's a good overview:
http://www.howtogeek.com/193669/whats-the-difference-between-gpt-and-mbr-whe...
hth & regards,
Carl
Thanks Carl, but originally the Disklabel type: was DOS. I thought since my current system drive had a type of gpt I should change it. I could post the same information with Disklabel type : DOS and it would not change the problem. There is some other problem
Terry
You don't appear to be using the right tools. 'fsck' is filesystem check and repair, not "format." I think Patrick's suggestion makes the most sense in this case. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 01/02/2017 06:32 PM, Carl Hartung wrote:
On Mon, 2 Jan 2017 17:58:00 -0600 Terry Eck wrote:
On 01/02/2017 05:46 PM, Carl Hartung wrote:
On Mon, 2 Jan 2017 17:26:21 -0600 Terry Eck wrote:
Disklabel type: gpt This is the problem, Terry. fdisk isn't compatible with GPT (GUID Partition Table). Here's a good overview:
http://www.howtogeek.com/193669/whats-the-difference-between-gpt-and-mbr-whe...
hth & regards,
Carl
Thanks Carl, but originally the Disklabel type: was DOS. I thought since my current system drive had a type of gpt I should change it. I could post the same information with Disklabel type : DOS and it would not change the problem. There is some other problem
Terry
You don't appear to be using the right tools. 'fsck' is filesystem check and repair, not "format." I think Patrick's suggestion makes the most sense in this case.
I've tried to find the command which will format a HD. I believe fdformat is for floppy disks. Can you be more specific as to command name. Also, I not sure who Patrick is and what his suggestion was in this case. I've looked in /sbin /bin /usr/sbin and /usr/bin with little luck. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Terry Eck composed on 2017-01-02 18:58 (UTC-0600):
I've tried to find the command which will format a HD. I believe fdformat is for floppy disks. Can you be more specific as to command name. Also, I not sure who Patrick is and what his suggestion was in this case. I've looked in /sbin /bin /usr/sbin and /usr/bin with little luck.
"Format" means create (make, or mk) a filesystem (fs) on a partition or logical volume. So, mkfs is the tool you did not find. It has less than obvious variations, such as mkfs.ext4 and mkfs.vfat. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 01/02/2017 07:12 PM, Felix Miata wrote:
Terry Eck composed on 2017-01-02 18:58 (UTC-0600):
I've tried to find the command which will format a HD. I believe fdformat is for floppy disks. Can you be more specific as to command name. Also, I not sure who Patrick is and what his suggestion was in this case. I've looked in /sbin /bin /usr/sbin and /usr/bin with little luck.
"Format" means create (make, or mk) a filesystem (fs) on a partition or logical volume. So, mkfs is the tool you did not find. It has less than obvious variations, such as mkfs.ext4 and mkfs.vfat.
Thanks to all who replied, including Patrick who ended up in the spam folder. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Mon, 2 Jan 2017 18:58:13 -0600 Terry Eck wrote:
On 01/02/2017 06:32 PM, Carl Hartung wrote:
On Mon, 2 Jan 2017 17:58:00 -0600 Terry Eck wrote:
On 01/02/2017 05:46 PM, Carl Hartung wrote:
On Mon, 2 Jan 2017 17:26:21 -0600 Terry Eck wrote:
Disklabel type: gpt This is the problem, Terry. fdisk isn't compatible with GPT (GUID Partition Table). Here's a good overview:
http://www.howtogeek.com/193669/whats-the-difference-between-gpt-and-mbr-whe...
hth & regards,
Carl
Thanks Carl, but originally the Disklabel type: was DOS. I thought since my current system drive had a type of gpt I should change it. I could post the same information with Disklabel type : DOS and it would not change the problem. There is some other problem
Terry
You don't appear to be using the right tools. 'fsck' is filesystem check and repair, not "format." I think Patrick's suggestion makes the most sense in this case.
I've tried to find the command which will format a HD. I believe fdformat is for floppy disks. Can you be more specific as to command name. Also, I not sure who Patrick is and what his suggestion was in this case. I've looked in /sbin /bin /usr/sbin and /usr/bin with little luck.
No sense recreating the wheel, so to speak. :) Patrick also responded to your question. The entire thread can be viewed here: https://lists.opensuse.org/archive/opensuse/2017-01/msg00074.html -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 01/02/2017 07:13 PM, Carl Hartung wrote:
On Mon, 2 Jan 2017 18:58:13 -0600 Terry Eck wrote:
On 01/02/2017 06:32 PM, Carl Hartung wrote:
On Mon, 2 Jan 2017 17:58:00 -0600 Terry Eck wrote:
On 01/02/2017 05:46 PM, Carl Hartung wrote:
On Mon, 2 Jan 2017 17:26:21 -0600 Terry Eck wrote:
Disklabel type: gpt This is the problem, Terry. fdisk isn't compatible with GPT (GUID Partition Table). Here's a good overview:
http://www.howtogeek.com/193669/whats-the-difference-between-gpt-and-mbr-whe...
hth & regards,
Carl
Thanks Carl, but originally the Disklabel type: was DOS. I thought since my current system drive had a type of gpt I should change it. I could post the same information with Disklabel type : DOS and it would not change the problem. There is some other problem
Terry
You don't appear to be using the right tools. 'fsck' is filesystem check and repair, not "format." I think Patrick's suggestion makes the most sense in this case.
I've tried to find the command which will format a HD. I believe fdformat is for floppy disks. Can you be more specific as to command name. Also, I not sure who Patrick is and what his suggestion was in this case. I've looked in /sbin /bin /usr/sbin and /usr/bin with little luck.
No sense recreating the wheel, so to speak. :) Patrick also responded to your question. The entire thread can be viewed here:
https://lists.opensuse.org/archive/opensuse/2017-01/msg00074.html
I hate to say it but for some reason his email ended up in the spam folder, don't know why. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 01/02/2017 05:58 PM, Terry Eck wrote:
Thanks Carl, but originally the Disklabel type: was DOS. I thought since my current system drive had a type of gpt I should change it. I could post the same information with Disklabel type : DOS and it would not change the problem. There is some other problem
Terry
One option to look into is to use wipefs to remove the gpt tables (plural). You have one at each end of the disk and using fdisk will not remove the gpt table at the end of the disk. (which will cause tools to still report the gpt format even though you have overwritten the table at the beginning of the disk). wipefs allows you to take care of both. Running without options, wipefs will report the tables that can be removed, but not actually remove them. See the man page for the invocation for removal. -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
* Terry Eck <terry_eck@verizon.net> [01-02-17 18:28]:
Hello, Hope someone can shine some light on the problem I'm having. I've formatted several drives in the past and have not seen this problem.
I'm trying to use a 500G drive which was a linux system with swap.
I fdisk to delete all the old partitions and created one single partition. One strange thing is the partition starts at 2048. Had no choice. =========== The following is from fdisk
Disk /dev/sdc: 465.8 GiB, 500107862016 bytes, 976773168 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: gpt Disk identifier: 0x000af975
Device Boot Start End Sectors Size Id Type /dev/sdc1 2048 976773167 976771120 465.8G 83 Linux =============
Try to format it with fsck.ext2 yields: e2fsck 1.43.3 (04-Sep-2016) ext2fs_open2: Bad magic number in super-block fsck.ext2: Superblock invalid, trying backup blocks... fsck.ext2: Bad magic number in super-block while trying to open /dev/sdc1
The superblock could not be read or does not describe a valid ext2/ext3/ext4 filesystem. If the device is valid and it really contains an ext2/ext3/ext4 filesystem (and not swap or ufs or something else), then the superblock is corrupt, and you might try running e2fsck with an alternate superblock: e2fsck -b 8193 <device> or e2fsck -b 32768 <device>
/dev/sdc1 contains a swap file system
=============
Any ideas how to format this drive for use and a data storage/backup drive?
probably because "Disklabel type: gpt" try partitioning using parted/gparted -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 Photos: http://wahoo.no-ip.org/piwigo @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 01/02/2017 06:26 PM, Terry Eck wrote:
Try to format it with fsck.ext2 yields: e2fsck 1.43.3 (04-Sep-2016)
You don't format with fsck. FSCK is _F_ile _S_ystem _C_hec_K_
Any ideas how to format this drive for use and a data storage/backup drive?
Use MKFS which is _M_a_K_e _F_file _S_ysttem There's a whole family of mkfs.<fstype> just as there is a whole family of fsck.<fstype> Try "man mkfs" for a more complete explanation and a listing of the various options available, especially when it comes to dealing with ext4 on a large partition. You should also understand the context of the /etc/mke2fs.conf file as documented in the mke2fs(8) and mke2fs.conf(5) manual pages. PS: you could have found all this with the command apropos ext4 The 'apropos' command is one of the most useful when it comes to finding out how to do things and hot to find out clues for why the things you did didn't do what you quite expected. You may have to try 'apropos' with a variety of keywords, but it usually leads you down some enlightening avenues. -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 01/02/2017 07:20 PM, Anton Aylward wrote:
On 01/02/2017 06:26 PM, Terry Eck wrote:
You don't format with fsck. FSCK is _F_ile _S_ystem _C_hec_K_
Any ideas how to format this drive for use and a data storage/backup drive? Use MKFS which is _M_a_K_e _F_file _S_ysttem
PS: you could have found all this with the command
apropos ext4
Thanks for the tip on apropos. I just "love" acronyms. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 2017-01-03 00:26, Terry Eck wrote:
Hello, Hope someone can shine some light on the problem I'm having. I've formatted several drives in the past and have not seen this problem.
I'm trying to use a 500G drive which was a linux system with swap.
I fdisk to delete all the old partitions and created one single partition. One strange thing is the partition starts at 2048. Had no choice.
That is the correct setting.
Try to format it with fsck.ext2 yields:
fsck is filesystem check, not format. You need mkfs.* Best thing for you is to use gparted instead. - -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iF4EAREIAAYFAlhrDjEACgkQja8UbcUWM1x4TQEAjTVKvcICM0+ooORWfRQABi/x l1M6HBfy/OccOzVYbQIA/jJoZGnpBETKzGihABHjA/3mOU4BzN2lrOhyhi26zCdC =Mzt1 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (14)
-
Anton Aylward -
Carl Hartung -
Carlos E. R. -
Dave Howorth -
David C. Rankin -
Felix Miata -
jdd -
Lew Wolfgang -
Patrick Shanahan -
Paul Neuwirth -
Per Jessen -
sdm -
Terry Eck -
Wols Lists