[Bug 2067] Re: Problems with partitioning

2010-12-22 Thread Launchpad Bug Tracker
[Expired for partman-base (Ubuntu) because there has been no activity
for 60 days.]

** Changed in: partman-base (Ubuntu)
   Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
https://bugs.launchpad.net/bugs/2067

Title:
  Problems with partitioning

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 2067] Re: Problems with partitioning

2010-09-14 Thread rusivi1
Thank you for posting this bug.

Does this occur in Lucid?

** Changed in: partman-base (Ubuntu)
   Status: Confirmed => Incomplete

-- 
Problems with partitioning
https://bugs.launchpad.net/bugs/2067
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 2067] Re: Problems with partitioning

2008-10-26 Thread zorpox
I have to report similar problems:

Partman failed recognize my partitions and just presented me with the
option to create new ones. The partition-structure was roughly similar
to the one mentioned in the bug report.

Unfortunately, my partition table was partially (!) corrupted anyway, so
I'm not sure whether this occurred because of the damage or because of
the distinct structure #1 mentioned. Yet, parted and fdisk were able to
read (and restore) it without problems so the problem seems to be with
partman.

-- 
Problems with partitioning
https://bugs.launchpad.net/bugs/2067
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 2067] Re: Problems with partitioning

2007-08-28 Thread Jim Qode
** Changed in: partman-base (Ubuntu)
   Status: Incomplete => Confirmed

-- 
Problems with partitioning
https://bugs.launchpad.net/bugs/2067
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 2067] Re: Problems with partitioning

2007-04-04 Thread jacubo
Hi,

Ubuntu Feisty the same problem as described. My partition table is:

Disk /dev/hda: 80.0 GB, 80026361856 bytes
255 heads, 63 sectors/track, 9729 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot  Start End  Blocks   Id  System
/dev/hda1   *   1255020482843+   c  W95 FAT32 (LBA)
/dev/hda2   *2551494019197675   83  Linux
/dev/hda34941972838459610f  W95 Ext'd (LBA)
/dev/hda45047972837608133+   7  HPFS/NTFS
/dev/hda549415046  851382   82  Linux swap / Solaris


Installator doesn't see my partition layout. 

Here is what dmesg shows:

[  102.070108] NET: Registered protocol family 10
[  102.070221] lo: Disabled Privacy Extensions
[  108.002062] input: Power Button (FF) as /class/input/input4
[  108.029135] ACPI: Power Button (FF) [PWRF]
[  108.092549] input: Power Button (CM) as /class/input/input5
[  108.119743] ACPI: Power Button (CM) [PWRB]
[  108.162020] No dock devices found.
[  108.184348] Using specific hotkey driver
[  108.238786] ibm_acpi: ec object not found
[  108.425088] pcc_acpi: loading...
[  112.807861] eth0: no IPv6 routers present
[  123.168331] lp0: using parport0 (interrupt-driven).
[  123.238220] ppdev: user-space parallel port driver
[  133.957343] apm: BIOS version 1.2 Flags 0x07 (Driver version 1.16ac)
[  133.957350] apm: overridden by ACPI.
[  134.582121] eth0: no IPv6 routers present
[  137.304656] Bluetooth: Core ver 2.11
[  137.304732] NET: Registered protocol family 31
[  137.304734] Bluetooth: HCI device and connection manager initialized
[  137.304738] Bluetooth: HCI socket layer initialized
[  137.533342] Bluetooth: L2CAP ver 2.8
[  137.533347] Bluetooth: L2CAP socket layer initialized
[  137.738930] Bluetooth: RFCOMM socket layer initialized
[  137.738946] Bluetooth: RFCOMM TTY layer initialized
[  137.738949] Bluetooth: RFCOMM ver 1.8
[  250.866026] kjournald starting.  Commit interval 5 seconds
[  250.866372] EXT3 FS on hda2, internal journal
[  250.866445] EXT3-fs: mounted filesystem with ordered data mode.
[  470.900610] NTFS driver 2.1.28 [Flags: R/O MODULE].
[  471.081416] JFS: nTxBlock = 8192, nTxLock = 65536
[  471.315287] SGI XFS with ACLs, security attributes, realtime, large block 
numbers, no debug enabled
[  471.315784] SGI XFS Quota Management subsystem
[  531.108908]  hda: hda1 hda3 < hda5 > hda4
[  533.119987]  hda: hda1 hda3 < hda5 > hda4
[  722.203990] QNX4 filesystem 0.2.3 registered.
[  722.280212] cramfs: wrong magic
[  722.505816] cramfs: wrong magic
[  722.510466] FAT: bogus number of reserved sectors
[  722.510474] VFS: Can't find a valid FAT filesystem on dev hda3.
[  722.515966] attempt to access beyond end of device
[  722.515974] hda3: rw=0, want=4, limit=2
[  722.516325] EXT3-fs: unable to read superblock
[  722.521507] attempt to access beyond end of device
[  722.521514] hda3: rw=0, want=66, limit=2
[  722.521853] isofs_fill_super: bread failed, dev=hda3, iso_blknum=16, block=32
[  722.526507] SQUASHFS error: Can't find a SQUASHFS superblock on hda3
[  722.543057] attempt to access beyond end of device
[  722.543066] hda3: rw=0, want=4, limit=2
[  722.543507] EXT2-fs: unable to read superblock
[  722.548793] NTFS-fs error (device hda3): read_ntfs_boot_sector(): Primary 
boot sector is invalid.
[  722.548802] NTFS-fs error (device hda3): read_ntfs_boot_sector(): Mount 
option errors=recover not used. Aborting without trying to recover.
[  722.548806] NTFS-fs error (device hda3): ntfs_fill_super(): Not an NTFS 
volume.
[  722.554560] attempt to access beyond end of device
[  722.554570] hda3: rw=0, want=72, limit=2
[  722.554929] attempt to access beyond end of device
[  722.554933] hda3: rw=0, want=128, limit=2
[  722.559592] attempt to access beyond end of device
[  722.559599] hda3: rw=0, want=18, limit=2
[  722.560638] ReiserFS: hda3: warning: sh-2006: read_super_block: bread failed 
(dev hda3, block 8, size 1024)
[  722.560868] attempt to access beyond end of device
[  722.560872] hda3: rw=0, want=130, limit=2
[  722.561134] ReiserFS: hda3: warning: sh-2006: read_super_block: bread failed 
(dev hda3, block 64, size 1024)
[  722.561139] ReiserFS: hda3: warning: sh-2021: reiserfs_fill_super: can not 
find reiserfs on hda3
[  722.565901] attempt to access beyond end of device
[  722.565908] hda3: rw=0, want=8, limit=2
[  722.571457] FAT: bogus number of reserved sectors
[  722.571465] VFS: Can't find a valid FAT filesystem on dev hda3.
[  722.577030] attempt to access beyond end of device
[  722.577037] hda3: rw=0, want=4, limit=2
[  722.577395] MINIX-fs: unable to read superblock
[  722.599683] attempt to access beyond end of device
[  722.599690] hda3: rw=0, want=3, limit=2
[  722.600699] hfs: unable to find HFS+ superblock
[  722.605577] qnx4: wrong fsid in superblock.
[  722.610759] You didn't specify the type of your ufs filesystem
[  722.610762] 
[  722.610763] mount -t ufs -o 
ufstyp

[Bug 2067] Re: Problems with partitioning

2006-10-06 Thread Colin Watson
** Changed in: partman-base (Ubuntu)
 Assignee: Colin Watson => (unassigned)

-- 
Problems with partitioning
https://launchpad.net/bugs/2067

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs