Re: recovering a partition table

4 Dominic Knight > > > > wrote: > > > > > Whilst trying to create one partition out of two (using > > > > > disks) I > > > > > appear to have accidentally deleted the partition table of > > > > > (almost) the whole drive. > &

Re: recovering a partition table

accidentally deleted the partition table of (almost) the whole drive. Then diverse methods for partition table recovery are open to you. All the best E.L. What the Doctor ordered: How to Recover a Disk Partition with TestDisk and GParted Live https://ubuverse.com/recover-a-disk-partition

Re: recovering a partition table

ve accidentally deleted the partition table of > > > (almost) the whole drive. > > Then diverse methods for partition table recovery are open to you. > > All the best > > E.L. > > > What the Doctor ordered: > How to Recover a Disk Partition with TestDisk and GPar

Re: recovering a partition table

On 09/07/2018 12:19 PM, Eike Lantzsch wrote: On Friday, September 7, 2018 5:34:00 PM -04 Dominic Knight wrote: Whilst trying to create one partition out of two (using disks) I appear to have accidentally deleted the partition table of (almost) the whole drive. It still has the swap partition

Re: recovering a partition table

On Friday, September 7, 2018 5:34:00 PM -04 Dominic Knight wrote: > Whilst trying to create one partition out of two (using disks) I > appear to have accidentally deleted the partition table of (almost) the > whole drive. It still has the swap partition and an unknown partition >

recovering a partition table

Whilst trying to create one partition out of two (using disks) I appear to have accidentally deleted the partition table of (almost) the whole drive. It still has the swap partition and an unknown partition of zero size apparently with 2tb of freespace. It was 10gb swap, 1tb, 50 gb, and two at

[SOLVED] Re: ISO file to sd card: Disk /dev/sdb doesn't contain a valid partition table

Aug 14, 2018, 2:30 PM by delop...@gmail.com: > > but why you don't run it in VM or VBox or extract, or use unetbootin? > Yes, eventually I installed unetbootin and got it working with it. Thanks to everyone who responded.

Re: ISO file to sd card: Disk /dev/sdb doesn't contain a valid partition table

Le 14/08/2018 à 15:31, local10 a écrit : The goal here is to create an sd card containg a bootable windows 7 image, I need to test something quick in windows. The iso file  is a windows 7 image. What kind of Windows 7 image ? An installation DVD image ? AFAIK these ISO images are not hybrid

Re: ISO file to sd card: Disk /dev/sdb doesn't contain a valid partition table

On Tue, 14 Aug 2018, local10 wrote: > Date: Tue, 14 Aug 2018 08:44:26 > From: local10 > To: debian-user@lists.debian.org > Subject: ISO file to sd card: Disk /dev/sdb doesn't contain a valid partition > table > Resent-Date: Tue, 14 Aug 2018 12:44:40 + (UTC) >

Re: ISO file to sd card: Disk /dev/sdb doesn't contain a valid partition table

local10 wrote: > The goal here is to create an sd card containg a bootable windows 7 image, > I need to test something quick in windows. The iso file  is a windows 7 > image. is it live windows7 - I have heard rumors that such thing exists? Is it recovery disk? but why you don't run it in VM or

Re: ISO file to sd card: Disk /dev/sdb doesn't contain a valid partition table

local10 (2018-08-14): > The goal here is to create an sd card containg a bootable windows 7 > image, I need to test something quick in windows. The iso file  is a > windows 7 image. Then I suspect you would have more luck asking people familiar with windows. Regards, -- Nicolas George sign

Re: ISO file to sd card: Disk /dev/sdb doesn't contain a valid partition table

Aug 14, 2018, 8:47 AM by geo...@nsup.org: > > You can try to mount /dev/sdb itself. > Yes, you're right, I can mount it on /dev/sdb. > > But you are probably doing something wrong in the first place. What is your > > endgame? > The goal here is to create an sd card containg a bootable windows 7

Re: ISO file to sd card: Disk /dev/sdb doesn't contain a valid partition table

perblock on > /dev/sdb1) and fdisk says "Disk /dev/sdb doesn't contain a valid > partition table". That's kind of strange as I can mount and read > /tmp/winfile.iso and it seems to be in good order. That is perfectly normal, an ISO file is an ISO-9660 filesystem image, i

ISO file to sd card: Disk /dev/sdb doesn't contain a valid partition table

;Disk /dev/sdb doesn't contain a valid partition table". That's kind of strange as I can mount and read /tmp/winfile.iso and it seems to be in good order. Any ideas? Thanks # fdisk -l /dev/sdb ... Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 5

Re: MBR partitioning, and content after partition table but before first partition

On Mon, Mar 13, 2017 at 08:36:59PM -0700, David Christensen wrote: > >and the destination ended up bigger, > >possibly because one or more of the backups on the source had been using some > >kind of hardlink de-dupe (I've ranted about hardlink trees being a problem in > >various backup topics on -u

Re: MBR partitioning, and content after partition table but before first partition

Hello, On Mon, Mar 13, 2017 at 08:36:59PM -0700, David Christensen wrote: > Is anyone aware of a utility that can walk a file system and replace > identical files with hard links? As an alternative to doing this, you could consider using a filesystem with block-level de-duplication support. ZFS

Re: MBR partitioning, and content after partition table but before first partition

On 03/14/2017 04:52 AM, The Wanderer wrote: On 2017-03-13 at 23:36, David Christensen wrote: Is anyone aware of a utility that can walk a file system and replace identical files with hard links? Try rdfind. It's in Debian; I don't use it myself, largely because the (accepted upstream years a

Re: MBR partitioning, and content after partition table but before first partition

On 03/14/2017 03:34 AM, David wrote: On 14 March 2017 at 14:36, David Christensen wrote: Doing a quick test, it appears that rsync copies hard linked files as if each were a different file: rsync -a hard-link-1/ hard-link-2 Here, 'man rsync' says: "Note that -a does not preserve hardlinks,

Re: MBR partitioning, and content after partition table but before first partition

On 2017-03-13 at 23:36, David Christensen wrote: > On 03/13/2017 02:01 AM, Jonathan Dowland wrote: > >> On Fri, Mar 10, 2017 at 10:00:45PM -0800, David Christensen wrote: >> and the destination ended up bigger, possibly because one or more >> of the backups on the source had been using some kind

Re: MBR partitioning, and content after partition table but before first partition

On 14 March 2017 at 14:36, David Christensen wrote: > > Doing a quick test, it appears that rsync copies hard linked files as if > each were a different file: > > rsync -a hard-link-1/ hard-link-2 Here, 'man rsync' says: "Note that -a does not preserve hardlinks, because finding multiply-linked f

Re: MBR partitioning, and content after partition table but before first partition

On 03/13/2017 02:01 AM, Jonathan Dowland wrote: On Fri, Mar 10, 2017 at 10:00:45PM -0800, David Christensen wrote: I'd always put a step 0) in there: is imaging what you want to do? Consider a file-level backup with rsync (etc etc, as discussed elsewhere in this thread) I do imaging for system

Re: MBR partitioning, and content after partition table but before first partition

On Fri, Mar 10, 2017 at 10:00:45PM -0800, David Christensen wrote: > >I'd always put a step 0) in there: is imaging what you want to do? Consider > >a file-level backup with rsync (etc etc, as discussed elsewhere in this > >thread) > > I do imaging for system disks. I do backups and archives for

Re: MBR partitioning, and content after partition table but before first partition

be this is some newer scheme I am not familiar with). My boot partition is also unencrypted. So, the moral of the story appears to be: When taking an image of a Debian system drive, be sure to copy the blocks between the partition table and the first partition, as there may be boot l

Re: MBR partitioning, and content after partition table but before first partition

ystem drive, be sure to copy the > blocks between the partition table and the first partition, as there > may be boot loader code there. I'd always put a step 0) in there: is imaging what you want to do? Consider a file-level backup with rsync (etc etc, as discussed elsewhere in

Re: MBR partitioning, and content after partition table but before first partition

the moral of the story appears to be: When taking an image of a Debian system drive, be sure to copy the blocks between the partition table and the first partition, as there may be boot loader code there. I can find plenty of "introductory" / "overview" documen

Re: MBR partitioning, and content after partition table but before first partition

On Wed, Mar 08, 2017 at 09:46:32PM -0800, David Christensen wrote: > What is in blocks 1-101? I believe it's part of grub. My limited understanding of how it works is it's split up into separate stages designed to fit within the "holes" in a typical MBR layout, each stage having enough code to ini

Re: MBR partitioning, and content after partition table but before first partition

Hi, David Christensen wrote: > Examining a Windows XP disk, the first partition (C:\) starts at block 63 > (track 1): > [...] > Number Start End SizeType File system Flags > 1 63s156296384s 156296322s primary ntfs boot That's an oldfashioned layout. Bad

Re: MBR partitioning, and content after partition table but before first partition

(logical/physical): 512B/512B Partition Table: msdos Disk Flags: Number Start EndSize Type File system Flags 1 2048s 976895s974848sprimary ext4 boot 2 976896s 1953791s 976896sprimary 3 1953792s 28125183s 26171392s primary

MBR partitioning, and content after partition table but before first partition

On 03/08/2017 03:02 AM, Thomas Schmitt wrote: David Christensen wrote: AFAIK when using MBR partitioning, the partition table (blocks 0-62) The MBR partition table resides in the first 512-bytes block. It may be extended by a chain of partitions starting at the Extended Partition of the MBR

Re: How to recovery disc partition table?

This is a summary of using TestDisk, it doesn't describe the same procedure I described, and it misses some important information that I included. Again, do your own research.

Re: How to recovery disc partition table?

El 24/10/15 a las 00:37, Serkan KURT escribió: Hi friends. I have a 1TB disc. - My disc formatted ext4 before. - I accidentally created new partition table on my disk. - Unfortunately, I accidentally formatted ntfs. Can I recovery my disc partition table and/or my directorys and

How to recovery disc partition table?

Hi friends. I have a 1TB disc. - My disc formatted ext4 before. - I accidentally created new partition table on my disk. - Unfortunately, I accidentally formatted ntfs. Can I recovery my disc partition table and/or my directorys and files smoothly?

Re: udev memory problem when trying to plug a disk with corrupted partition table

Le 02.12.2014 19:27, tv.deb...@googlemail.com a écrit : On 02/12/2014 20:48, berenger.mo...@neutralite.org wrote: [cut] Also, what is EBR (or EPBR, which seems to be some sort of enhanced whatever may be a EBR)? Extended Boot Record on DOS disks ? Where information about extended partition

Re: udev memory problem when trying to plug a disk with corrupted partition table

On 02/12/2014 20:48, berenger.mo...@neutralite.org wrote: [cut] Also, what is EBR (or EPBR, which seems to be some sort of enhanced whatever may be a EBR)? Extended Boot Record on DOS disks ? Where information about extended partition is stored. https://en.wikipedia.org/wiki/Extended_boot_r

Re: udev memory problem when trying to plug a disk with corrupted partition table

Le 20.11.2014 22:26, Scott Ferguson a écrit : On 21/11/14 06:45, Pascal Hambourg wrote: Scott Ferguson a écrit : Might be worth fscking the disk first in case that's where the problem lies. Why ? fsck works on filesystems, not disks or partition tables. Good question - because I didn't sp

Re: udev memory problem when trying to plug a disk with corrupted partition table

On 21/11/14 06:45, Pascal Hambourg wrote: > Scott Ferguson a écrit : >> >> Might be worth fscking the disk first in case that's where the problem lies. > > Why ? fsck works on filesystems, not disks or partition tables. > > Good question - because I didn't spend much time thinking about it, or, b

Re: udev memory problem when trying to plug a disk with corrupted partition table

Scott Ferguson a écrit : > > Might be worth fscking the disk first in case that's where the problem lies. Why ? fsck works on filesystems, not disks or partition tables. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas.

Re: udev memory problem when trying to plug a disk with corrupted partition table

ained extended partition tables. correct (again), they can be located anywhere on the disk > >> The somewhat good news is that it's fixable. > > Yes. If recovery tools such as testdisk or gpart cannot fix the loop, my > tool of choice would be sfdisk to export, edit by h

Re: udev memory problem when trying to plug a disk with corrupted partition table

does not contain the chained extended partition tables. > The somewhat good news is that it's fixable. Yes. If recovery tools such as testdisk or gpart cannot fix the loop, my tool of choice would be sfdisk to export, edit by hand (keep partitions 1 to 8 only) and recreate the partit

Re: udev memory problem when trying to plug a disk with corrupted partition table

Le Mon, 17 Nov 2014 16:56:51 +0100, berenger.mo...@neutralite.org a écrit : > Now, fact is that the hard-disk partition table is no longer correct, > and when I plug it (it is an USB HD) into a Debian system, it makes > udev eating all my memory, and more. Could you please open a

Re: udev memory problem when trying to plug a disk with corrupted partition table

On 20/11/14 12:45, Martin Read wrote: > On 20/11/14 01:03, Scott Ferguson wrote: On 20/11/14 04:06, "Morel Bérenger" wrote: > I think it's msdos. >> >> AFAIK mdos partition tables don't support anywhere near that number of >> slices. :( > > MSDOS extended partitions contain a linked lis

Re: udev memory problem when trying to plug a disk with corrupted partition table

On 20/11/14 01:03, Scott Ferguson wrote: On 20/11/14 04:06, "Morel Bérenger" wrote: I think it's msdos. AFAIK mdos partition tables don't support anywhere near that number of slices. :( MSDOS extended partitions contain a linked list of logical partitions. It looks, from the pattern of th

Re: udev memory problem when trying to plug a disk with corrupted partition table

>> On Mon, 17 Nov 2014, berenger.mo...@neutralite.org wrote: >>>> >>>> >>>>> So, what part of that disk should I extract, which could be usable >>>>> and sharable? Partition table, of course, which is probably at >>>>> disk's b

Re: udev memory problem when trying to plug a disk with corrupted partition table

t;> >>>> So, what part of that disk should I extract, which could be usable >>>> and sharable? Partition table, of course, which is probably at >>>> disk's beginning, but how long might it be? >>> >>> That depends. What kind of parti

Re: udev memory problem when trying to plug a disk with corrupted partition table

On 20/11/14 04:06, "Morel Bérenger" wrote: > Le Lun 17 novembre 2014 19:32, Henrique de Moraes Holschuh a écrit : >> On Mon, 17 Nov 2014, berenger.mo...@neutralite.org wrote: >> >>> So, what part of that disk should I extract, which could be usable >>&g

Re: udev memory problem when trying to plug a disk with corrupted partition table

Le Lun 17 novembre 2014 19:32, Henrique de Moraes Holschuh a écrit : > On Mon, 17 Nov 2014, berenger.mo...@neutralite.org wrote: > >> So, what part of that disk should I extract, which could be usable >> and sharable? Partition table, of course, which is probably at disk'

Re: udev memory problem when trying to plug a disk with corrupted partition table

On Mon, 17 Nov 2014, berenger.mo...@neutralite.org wrote: > So, what part of that disk should I extract, which could be usable > and sharable? Partition table, of course, which is probably at > disk's beginning, but how long might it be? That depends. What kind of partition tabl

Re: udev memory problem when trying to plug a disk with corrupted partition table

Le 17.11.2014 17:55, Henrique de Moraes Holschuh a écrit : On Mon, 17 Nov 2014, berenger.mo...@neutralite.org wrote: Now, fact is that the hard-disk partition table is no longer correct, and when I plug it (it is an USB HD) into a Debian system, it makes udev eating all my memory, and more

Re: udev memory problem when trying to plug a disk with corrupted partition table

On Mon, 17 Nov 2014, berenger.mo...@neutralite.org wrote: > Now, fact is that the hard-disk partition table is no longer > correct, and when I plug it (it is an USB HD) into a Debian system, > it makes udev eating all my memory, and more. Please image the partition table so that so

udev memory problem when trying to plug a disk with corrupted partition table

mail. Now, fact is that the hard-disk partition table is no longer correct, and when I plug it (it is an USB HD) into a Debian system, it makes udev eating all my memory, and more. The only way for me to have a chance to work with that drive plugged is to disable swap, because when the system swaps,

kernel spamming log -- "sda: unknown partition table"

noise bothering me. Nov 11 12:20:23 garbo kernel: [352931.388078] sda: unknown partition table Nov 11 12:20:25 garbo kernel: [352933.668659] sda: unknown partition table Nov 11 12:20:25 garbo kernel: [352933.902338] sdc: unknown partition table Nov 11 12:21:35 garbo kernel: [353003.971818]

Re: Who is systemd-gpt-auto-generator, and why does s/he not like my partition table?

r = blkid_probe_lookup_value(b, "PTTYPE", &pttype, NULL); | if (r != 0) { | if (errno == 0) | errno = EIO; | log_error("Failed to determine partition table type of %s: %m", node); | return -

Re: Who is systemd-gpt-auto-generator, and why does s/he not like my partition table?

r = blkid_probe_lookup_value(b, "PTTYPE", &pttype, NULL); | if (r != 0) { | if (errno == 0) | errno = EIO; | log_error("Failed to determine partition table type of %s: %m", node); | return -

Re: Who is systemd-gpt-auto-generator, and why does s/he not like my partition table?

", &pttype, NULL); | if (r != 0) { | if (errno == 0) | errno = EIO; | log_error("Failed to determine partition table type of %s: %m", node); | return -errno; ` Somebody who is familiar with libblki

Re: Who is systemd-gpt-auto-generator, and why does s/he not like my partition table?

pttype, NULL); > | if (r != 0) { > | if (errno == 0) > | errno = EIO; > | log_error("Failed to determine partition table type of %s: > %m", node); > | return -errno; > ` > &

Re: Who is systemd-gpt-auto-generator, and why does s/he not like my partition table?

hat. I'd > try running smartctl -a /dev/sda; or similar just to see whether any > errors have occured on the drive. It's possible that there's a bad > sector early on which is only exposed when something tries to find a gpt > partition table, or it could be a bug i

Re: Who is systemd-gpt-auto-generator, and why does s/he not like my partition table?

On 10/15/2014 11:53 AM, Don Armstrong wrote: On Wed, 15 Oct 2014, Jape Person wrote: From dmesg ...[4.853751] systemd-gpt-auto-generator[154]: Failed to determine partition table type of /dev/sda: Input/output error [4.854298] systemd[151]: /lib/systemd/system-generators/systemd-gpt

Re: Who is systemd-gpt-auto-generator, and why does s/he not like my partition table?

... systemd-gpt-auto-generator[152]: Failed to determine partition table type of /dev/sda: Input/output error ... So, I checked dmesg: From dmesg ...[4.853751] systemd-gpt-auto-generator[154]: Failed to determine partition table type of /dev/sda: Input/output error [4.854298] systemd[151

Re: Who is systemd-gpt-auto-generator, and why does s/he not like my partition table?

On Wed, 15 Oct 2014, Jape Person wrote: > From dmesg > ...[4.853751] systemd-gpt-auto-generator[154]: Failed to determine > partition table type of /dev/sda: Input/output error > [4.854298] systemd[151]: > /lib/systemd/system-generators/systemd-gpt-auto-generator failed with

Re: Who is systemd-gpt-auto-generator, and why does s/he not like my partition table?

pt-auto-generator[152]: Failed to determine partition table > type of /dev/sda: Input/output error > ... > > So, I checked dmesg: > > From dmesg > ...[4.853751] systemd-gpt-auto-generator[154]: Failed to determine > partition table type of /dev/sda: Input/output error > [

Who is systemd-gpt-auto-generator, and why does s/he not like my partition table?

TTY1 ... systemd-gpt-auto-generator[152]: Failed to determine partition table type of /dev/sda: Input/output error ... So, I checked dmesg: From dmesg ...[4.853751] systemd-gpt-auto-generator[154]: Failed to determine partition table type of /dev/sda: Input/output error [4.854298] system

Re: Clone GPT partition table - with Lenny ?

On Sun, Jul 6, 2014 at 5:53 PM, B wrote: > Rahhh, read too fast, former was for non-GPT, here's > one good pgm that does the trick (also exist as a pkg > in trudububu): > http://unix.stackexchange.com/questions/19047/how-can-i-quickly-copy-a-gpt-partition-scheme-from-one-hard-drive-to-another

Re: Clone GPT partition table - with Lenny ?

On Sun, Jul 6, 2014 at 5:49 PM, B wrote: > > Apparently, this is very easy: > http://unix.stackexchange.com/questions/12986/how-to-copy-the-partition-layout-of-a-whole-disk-using-standard-tools You can't uses sfdisk with gpt disks. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debi

Re: Clone GPT partition table - with Lenny ?

; on 7 of those partitions, again during Debian installation. The Debian > installer employed a GPT partition table for these discs; it also chose the > (precise) partition boundaries. > > The machine is no longer an active server on our network; its role has been > taken by a new-bui

Re: Clone GPT partition table - with Lenny ?

he new drive > - use dd if=/dev/zero to zero the first MiB of each partition. As Matt stated the size and places of the GPT partition table and its backup, using dd with count, bs AND seek (for the end of the partition) would be much faster. -- This universe shipped by weight, not by volume. So

Re: Clone GPT partition table - with Lenny ?

Other than not being fully automated, what would be wrong with: - use dd to copy the first 10MiB of the old drive to the new, - use dd to skip all but the last 10MiB of the old drive and seek to the same spot on the new drive - use dd if=/dev/zero to zero the first MiB of each partition.

Re: Clone GPT partition table - with Lenny ?

On 06/07/2014 22:49, B wrote: On Sun, 06 Jul 2014 22:35:03 +0100 Apparently, this is very easy: http://unix.stackexchange.com/questions/12986/how-to-copy-the-partition-layout-of-a-whole-disk-using-standard-tools I mentioned Lenny, because it matters. I'd found that page before posting,

Re: Clone GPT partition table - with Lenny ?

On Sun, 6 Jul 2014 23:49:38 +0200 B wrote: Rahhh, read too fast, former was for non-GPT, here's one good pgm that does the trick (also exist as a pkg in trudububu): http://unix.stackexchange.com/questions/19047/how-can-i-quickly-copy-a-gpt-partition-scheme-from-one-hard-drive-to-another --

Re: Clone GPT partition table - with Lenny ?

On Sun, 06 Jul 2014 22:35:03 +0100 Ron Leach wrote: > B, many thanks for thinking about this, Call me mâââsteeelll and bend over Igolll, so I can pet your hump *<;-) Apparently, this is very easy: http://unix.stackexchange.com/questions/12986/how-to-copy-the-partition-layout-of-a-whole-dis

Re: Clone GPT partition table - with Lenny ?

On 06/07/2014 21:56, B wrote: I think you also read too fast, apparently he just wanna have the same partition table. Which RAID doesn't care, eg: dsk0 partition = 100 (sectors, GB, whatever) dsk1 " = 101 or 4242.42 RAID will only pick 100 on dsk1 partition to achiev

Re: Clone GPT partition table - with Lenny ?

ector, etc. I can then repair the arrays using mdadm. You can still use dd to copy the partition table (others will tell you the right syntax); however, RAID easily copes with bigger partitions, as it only uses the place it needs. B, thank you. dd leads to problems with RAID, though. I di

Re: Clone GPT partition table - with Lenny ?

k you also read too fast, apparently he just wanna have the same partition table. Which RAID doesn't care, eg: dsk0 partition = 100 (sectors, GB, whatever) dsk1 " = 101 or 4242.42 RAID will only pick 100 on dsk1 partition to achieve its work. This was mandatory from the very beg

Re: Clone GPT partition table - with Lenny ?

oo fast, apparently he just wanna have the same partition table. Which RAID doesn't care, eg: dsk0 partition = 100 (sectors, GB, whatever) dsk1 " = 101 or 4242.42 RAID will only pick 100 on dsk1 partition to achieve its work. This was mandatory from the very beginning, as HDz, e

Re: Clone GPT partition table - with Lenny ?

On 7/6/2014 1:37 PM, Steve Litt wrote: On Sun, 6 Jul 2014 22:20:55 +0200 B wrote: On Sun, 06 Jul 2014 20:54:10 +0100 Ron Leach wrote: Is there, in Lenny, a command or tool for cloning a GPT? Use dd, it'll take a looong time but you'll have a bit copy. But... How do you know how much

Re: Clone GPT partition table - with Lenny ?

On Sun, 6 Jul 2014 22:20:55 +0200 B wrote: > On Sun, 06 Jul 2014 20:54:10 +0100 > Ron Leach wrote: > > > Is there, in Lenny, a command or tool for cloning a GPT? > > Use dd, it'll take a looong time but you'll have a bit copy. > But... How do you know how much to copy? GPT partitions va

Re: Clone GPT partition table - with Lenny ?

n repair > the arrays using mdadm. You can still use dd to copy the partition table (others will tell you the right syntax); however, RAID easily copes with bigger partitions, as it only uses the place it needs. -- Don't let people drive you crazy when you know it's in walkin

Re: Clone GPT partition table - with Lenny ?

On Sun, 06 Jul 2014 20:54:10 +0100 Ron Leach wrote: > Is there, in Lenny, a command or tool for cloning a GPT? Use dd, it'll take a looong time but you'll have a bit copy. -- ptinou: the only thing that surprised me with vi$ta was when it told me it was going to deactivate my k

Clone GPT partition table - with Lenny ?

installation. The Debian installer employed a GPT partition table for these discs; it also chose the (precise) partition boundaries. The machine is no longer an active server on our network; its role has been taken by a new-build Wheezy box. The end goal is to restore the RAID1 arrays, then

Re: Disk /dev/sdb doesn't contain a valid partition table

On 07/04/2014 11:58 AM, Guillermo Hernandez wrote: hi, you should use de option "n" to create a new partition. Regards, Guillermo The easiest partitioner I know of is gparted. You can download a bootable disk with gparted on it. * Perform actions with partitions such as: o create or d

Re: Re: Disk /dev/sdb doesn't contain a valid partition table

hi, you should use de option "n" to create a new partition. Regards,Guillermo

Debian Installer can't see my partition table

Hello Debian Mailing List, I am trying to go back from Debian Sid to Jessie or Wheezy, but when I run the installer (Latest Wheezy netinst disk image.) and go into manual partitioning, it does not see any of the partitions on my primary hard drive. fdisk sees them with no issue: /dev/sda1

Re: partition table not sticky

ou can reset it by > something like (assuming your disk is /dev/hdx): > $ sudo dd if=/dev/zero of=/dev/hdx bs=4k > $ sudo fdisk /dev/hdx > > This should work. > > You can also set partition table as msdos via parted. > $ sudo parted /dev/hdx mklabel msdos > [] tried bot

Re: partition table not sticky

ecause of gparted is creating GUID partition table (GPT) instaed of good old MBR. http://en.wikipedia.org/wiki/GUID_Partition_Table http://en.wikipedia.org/wiki/Master_boot_record > What is the problem with fdisk and cfdisk ??? I bet you used gparted first to create GPT and now trying to use

Re: partition table not sticky

J. B wrote: > I have repeatedly do the same but no luck. no luck with > cfdisk. Changes are not stored !!! > > only gparted is successful but it makes my 320 GB HDD to 280 > GB. 40GB lost !!! > > What is the problem with fdisk and cfdisk ??? Can you report the disk information from either smartc

partition table not sticky

Hello, I have tried to partition a new HDD. fidsk reports ``'''''''''''''''' Device contains neither a valid DOS partition table, nor Sun, SGI or OSF disklabel Building a new DOS disklabel with disk identifie

Re: Disk /dev/sdb doesn't contain a valid partition table

Kamaraju S Kusumanchi writes: > lee wrote: > > There are some warnings when I tried to use fdisk to create a new empty DOS > partition table. Do you know how to eliminate the warning? > > $fdisk -v > fdisk (util-linux 2.20.1) > > $sudo fdisk /dev/sdb > Devic

Re: Disk /dev/sdb doesn't contain a valid partition table

On Mi, 19 sep 12, 23:28:37, Kamaraju S Kusumanchi wrote: > > Warning: invalid flag 0x0000 of partition table 4 will be corrected by > w(rite) Have a look in the syslog for any errors during the create. Make sure the drive has sufficient power. Try partitioning it from a different

Re: Disk /dev/sdb doesn't contain a valid partition table

I once had an USB stick with a broken controller and couldn't partitioning it anymore. It was brand new, gets broken at the day when I used it the first time. It was warranted and I got another USB stick. Perhaps your drive isn't broken, but one cannot rule out the possibility that it's def

Re: Disk /dev/sdb doesn't contain a valid partition table

: 512 bytes / 512 bytes >> Disk identifier: 0x >> >> Disk /dev/sdb doesn't contain a valid partition table > > That is to be expected for a new disk. IIRC, fdisk (or was that > cfdisk?) has an option to start over with an empty partition table. > > Depe

Re: Disk /dev/sdb doesn't contain a valid partition table

Ralf Mardorf wrote: > On Tue, 2012-09-18 at 00:27 -0400, Kamaraju S Kusumanchi wrote: >> /dev/sdb: unrecognised disk label > >> 2) Is "msdos" a valid option to choose for this hard drive? > > Yes it is. > > Is there some output if you run > > # parted /dev/sdb > mklabel msdos > So, I did $s

Re: Disk /dev/sdb doesn't contain a valid partition table

On 9/18/2012 4:46 PM, lee wrote: Andrei POPESCU writes: On Ma, 18 sep 12, 19:24:45, lee wrote: 2) Is "msdos" a valid option to choose for this hard drive? Is "msdos" a useful partition type for you? Try "Linux", and if it works, you can try to change i

Re: Disk /dev/sdb doesn't contain a valid partition table

you? Try "Linux", and if it >>> works, you can try to change it to msdos. >> >> Partition *table*, not *type* ;) > > Are you sure there is such a thing as an "msdos" partition table? There > seem to be a couple types of partition tables, an

Re: Disk /dev/sdb doesn't contain a valid partition table

Andrei POPESCU writes: > On Ma, 18 sep 12, 19:24:45, lee wrote: >> >> > 2) Is "msdos" a valid option to choose for this hard drive? >> >> Is "msdos" a useful partition type for you? Try "Linux", and if it >> works, you can tr

Re: Disk /dev/sdb doesn't contain a valid partition table

On Ma, 18 sep 12, 19:24:45, lee wrote: > > > 2) Is "msdos" a valid option to choose for this hard drive? > > Is "msdos" a useful partition type for you? Try "Linux", and if it > works, you can try to change it to msdos. Partition *table*,

Re: Disk /dev/sdb doesn't contain a valid partition table

750156372992 bytes > 255 heads, 63 sectors/track, 91201 cylinders, total 1465149166 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 > Disk identifier: 0x0000 > > D

Re: Disk /dev/sdb doesn't contain a valid partition table

On Tue, 2012-09-18 at 00:27 -0400, Kamaraju S Kusumanchi wrote: > /dev/sdb: unrecognised disk label > 2) Is "msdos" a valid option to choose for this hard drive? Yes it is. Is there some output if you run # parted /dev/sdb mklabel msdos ? Regards, Ralf -- To UNSUBSCRIBE, email to debian

Disk /dev/sdb doesn't contain a valid partition table

ers, total 1465149166 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 Disk identifier: 0x Disk /dev/sdb doesn't contain a valid partition table When I tried gparted, it gives the follow

Re: Restoring partition table.

Tom Grace writes: > I would use Testdisk (should be in the repos), rather than try to copy > the partition table from another disk. Have a look at > http://www.cgsecurity.org/wiki/TestDisk_Step_By_Step#Partition_table_recovery > for some ideas. > > As ever with this stuff, be r

Re: Restoring partition table.

On 31/08/12 17:13, Malcolm Reed wrote: > > Hello, > bad news for me - I lost partition table in my 1Tb hard drive. All what > I have it's fdisk output of working drive: > > Can I convert fdisk output to sfdisk dump? How to convert count of > blocks to number of sec

Restoring partition table.

Hello, bad news for me - I lost partition table in my 1Tb hard drive. All what I have it's fdisk output of working drive: Disk /dev/sda: 1000.2 GB, 1000204886016 bytes 255 heads, 63 sectors/track, 121601 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Sector size (logical/phy

  1   2   3   4   >