Bug#637784: installation-reports: Partition disks error: No root file system is defined.
Charles Plessy
>
> I started the network installer through GRUB in the Amazon Elastic Comptuter
> Cloud, and connected to it through a network console launched via preseeding.
>
> I gave a couple of details on my website: http://charles.plessy.org/Debian/debiâneries/nuage/
>
> While the detection of hard drives apparently went well (see attached
> partman log), the partition step fails with the following error.
>
>
> ┌────────────┤ [!!] Partition disks ├─────────────┐
> │ │
> │ No root file system │
> │ No root file system is defined. │
> │ │
> │ Please correct this from the partitioning menu. │
> │ │
> │ <Continue> │
> │ │
> └─────────────────────────────────────────────────┘
Hi all,
I have retried after commenting all partman preseeding. It allowed me to try
to manually partition the drive. I have only one choice for the drive,
‘Virtual disk 1, partition #1 (xvda1) - 1.1 GB Unknown’. The guided
partitionning then proposes me the following:
┌───────────────────────────────────────────────┤ [!!] Partition disks ├───────────────────────────────────────────────┐
│ │
│ If you continue, the changes listed below will be written to the disks. Otherwise, you will be able to make further │
│ changes manually. │
│ │
│ The partition tables of the following devices are changed: │
│ Virtual disk 1, partition #1 (xvda1) │
│ │
│ The following partitions are going to be formatted: │
│ partition #1 of Virtual disk 1, partition #1 (xvda1) as ext3 │
│ partition #5 of Virtual disk 1, partition #1 (xvda1) as swap │
│ │
│ Write the changes to disks? │
│ │
│ <Yes> <No> │
│ │
└──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────┘
I then fails with the following error:
Error informing the kernel about modifications to partition /dev/xvda1p1 --
Invalid argument. This means Linux won't know about any changes you made to
/dev/xvda1p1 until you reboot -- so you shouldn't mount it or use it in any way
before rebooting.
Using the shell console, I found that the partition table was the following:
Disk /dev/xvda1: 1073 MB, 1073741824 bytes
255 heads, 63 sectors/track, 130 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x0002dcf2
Device Boot Start End Blocks Id System
/dev/xvda1p1 * 1 118 947803+ 83 Linux
/dev/xvda1p2 119 130 96390 5 Extended
/dev/xvda1p5 119 130 96358+ 82 Linux swap / Solaris
However, the device files /dev/xvda1p1, p2 and p5 are not available. Do you have any idea ?
Have a nice week-end,
--
Charles Plessy
Tsurumi, Kanagawa, Japan
--
To UNSUBSCRIBE, email to debian-bugs-...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Charles Plessy
>
> Using the shell console, I found that the partition table was the following:
>
> Disk /dev/xvda1: 1073 MB, 1073741824 bytes
> 255 heads, 63 sectors/track, 130 cylinders
> Units = cylinders of 16065 * 512 = 8225280 bytes
> Sector size (logical/physical): 512 bytes / 512 bytes
> I/O size (minimum/optimal): 512 bytes / 512 bytes
> Disk identifier: 0x0002dcf2
>
> Device Boot Start End Blocks Id System
> /dev/xvda1p1 * 1 118 947803+ 83 Linux
> /dev/xvda1p2 119 130 96390 5 Extended
> /dev/xvda1p5 119 130 96358+ 82 Linux swap / Solaris
>
> However, the device files /dev/xvda1p1, p2 and p5 are not available. Do you have any idea ?
Dear all,
I hope that I am not too bothering with my insistance, but I am completely
blocked on this issue, and I would like to ask again for your help, as
I think that it would be beneficial to Debian as well if it were possible
to use the Debian installer on the Amazon Elastic Computer Cloud. Please
let me know how I can help the D-I team in return.
Have a nice day,
Charles Plessy
>
> I then fails with the following error:
>
> Error informing the kernel about modifications to partition /dev/xvda1p1 --
> Invalid argument. This means Linux won't know about any changes you made to
> /dev/xvda1p1 until you reboot -- so you shouldn't mount it or use it in any way
> before rebooting.
>
> Using the shell console, I found that the partition table was the following:
>
> Disk /dev/xvda1: 1073 MB, 1073741824 bytes
> 255 heads, 63 sectors/track, 130 cylinders
> Units = cylinders of 16065 * 512 = 8225280 bytes
> Sector size (logical/physical): 512 bytes / 512 bytes
> I/O size (minimum/optimal): 512 bytes / 512 bytes
> Disk identifier: 0x0002dcf2
>
> Device Boot Start End Blocks Id System
> /dev/xvda1p1 * 1 118 947803+ 83 Linux
> /dev/xvda1p2 119 130 96390 5 Extended
> /dev/xvda1p5 119 130 96358+ 82 Linux swap / Solaris
>
> However, the device files /dev/xvda1p1, p2 and p5 are not available. Do you have any idea ?
>
I have tested today's build of Debian-Installer, and the bug is still there.
To summarise:
- On that machine, the drive's name is /dev/xvda1.
- Partman handles this by making partitions called /dev/xvda1p1 /dev/xvda1p2 /dev/xvda1p5
- The installation then fails as there are no such devices.
Have a nice Sunday,
Charles Plessy
> Le Sat, Aug 20, 2011 at 06:26:45PM +0900, Charles Plessy a écrit :
> >
> > Using the shell console, I found that the partition table was the following:
> >
> > Disk /dev/xvda1: 1073 MB, 1073741824 bytes
> > 255 heads, 63 sectors/track, 130 cylinders
> > Units = cylinders of 16065 * 512 = 8225280 bytes
> > Sector size (logical/physical): 512 bytes / 512 bytes
> > I/O size (minimum/optimal): 512 bytes / 512 bytes
> > Disk identifier: 0x0002dcf2
> >
> > Device Boot Start End Blocks Id System
> > /dev/xvda1p1 * 1 118 947803+ 83 Linux
> > /dev/xvda1p2 119 130 96390 5 Extended
> > /dev/xvda1p5 119 130 96358+ 82 Linux swap / Solaris
> >
> > However, the device files /dev/xvda1p1, p2 and p5 are not available. Do you have any idea ?
>
>
> To summarise:
>
> - On that machine, the drive's name is /dev/xvda1.
> - Partman handles this by making partitions called /dev/xvda1p1 /dev/xvda1p2 /dev/xvda1p5
> - The installation then fails as there are no such devices.
I tried to modify the partition table by hand using fdisk, and after writing it
I see the following error message.
WARNING: Re-reading the partition table failed with error 22: Invalid argument.
The kernel still uses the old table. The new table will be used at
the next reboot or after you run partprobe(8) or kpartx(8)
Syncing disks.
So the scenario is:
- Partman partitions the disk,
- the kernel is not informed of the changes,
- udev does not create new links in /dev,
- formatting and installation are impossible.
Do you think that this bug should be re-assigned somewhere else ?
Have a nice day,
--
Charles
Charles Plessy
> Le Sun, Feb 12, 2012 at 04:40:38PM +0900, Charles Plessy a écrit :
> > Le Sat, Aug 20, 2011 at 06:26:45PM +0900, Charles Plessy a écrit :
> > >
> > > Using the shell console, I found that the partition table was the following:
> > >
> > > Disk /dev/xvda1: 1073 MB, 1073741824 bytes
> > > 255 heads, 63 sectors/track, 130 cylinders
> > > Units = cylinders of 16065 * 512 = 8225280 bytes
> > > Sector size (logical/physical): 512 bytes / 512 bytes
> > > I/O size (minimum/optimal): 512 bytes / 512 bytes
> > > Disk identifier: 0x0002dcf2
> > >
> > > Device Boot Start End Blocks Id System
> > > /dev/xvda1p1 * 1 118 947803+ 83 Linux
> > > /dev/xvda1p2 119 130 96390 5 Extended
> > > /dev/xvda1p5 119 130 96358+ 82 Linux swap / Solaris
> > >
> > > However, the device files /dev/xvda1p1, p2 and p5 are not available. Do you have any idea ?
>
> I see the following error message.
>
> WARNING: Re-reading the partition table failed with error 22: Invalid argument.
> The kernel still uses the old table. The new table will be used at
> the next reboot or after you run partprobe(8) or kpartx(8)
> Syncing disks.
>
> So the scenario is:
>
> - Partman partitions the disk,
> - the kernel is not informed of the changes,
> - udev does not create new links in /dev,
> - formatting and installation are impossible.
it looks like /dev/xvda1, where the Xen system is booted, is a special case and
that in contrary to the other devices, like /dev/xvdb, etc., it can not be
modified.
The problem is therefore that part of the toolchain does not recognise in
advance that it is impossible.
Do you think that partman can or should obtain this information by itself, or
that this bug should be reassigned to another package, which would be in charge
of issuing an error message that partman can understand, to make sure that
debian-installer does not assume that the disk has been partitionned
successfully ?
--
Charles Plessy
Tsurumi, Kanagawa, Japan
Charles Plessy
>
> reassign 693107 partman-auto
> reassign 670702 partman-auto
> reassign 615074 lvm2
> reassign 676172 partman
> severity 691046 wishlist
> retitle 644430 document the need for a bios boot partition when using GPT
> forcemerge 644430 691046
> reassign 691046 release-notes
> reassign 683747 partman-lvm
> reassign 671879 partman-base
> thanks
>
> Hi,
>
> thank you for submitting installation reports, much appreciated.
>
> I read through all the ("partman" related) bugs mentioned here and am closing
> them now as
> - they (finally) indicated success and/or
> - I know from first hand experience that the functionality is working in
> Wheezy and/or
> - they only contained very little information and/or
> - they were (very) old.
>
> If I've closed a bug incorrectly please do reply or just file a new one -
> thats often better, as the bug log will be more clear.
reopen 637784
reassign 637784 partman
severity 637784 wishlist
retitle 637784 Please support installing on partitionless drives.
Dear Holger and everybody,
I think that it would be great if somebody could extend debian-installer to
install Debian on partitionless drives (like /dev/xvdb instead of /dev/xvdb1).
This would open the possibility to use debian-installer for preparing some
preseeded cloud images in a very simple way. Currently, this is done with
ad-hoc tools developed from scratch. Using debian-installer would also
ease the convergence between cloud images and standard installations, which
is wanted (see <http://wiki.debian.org/Teams/DPL/OfficialImages>).
(and please forgive me if partman is not the best package to hold this bug report)
Have a nice day,