Debian Installation :: Jessie RC1 Installer Hangs On Formatting Partition
Mar 21, 2015Tried to install Jessie RC1,but installer hangs on formatting the partition,at 33%.
View 7 RepliesTried to install Jessie RC1,but installer hangs on formatting the partition,at 33%.
View 7 RepliesI have an issue with Gparted v0.19.0 (Jessie) which has replaced v0.12.1 (Wheezy) which works fine. I had hoped to ask this question in Gparted's own forum, but after three weeks and multiple attempts no-one has approved my account there.
Unfortunately, my existing partition structure (on two different laptops) seems to be invisible to the new version of Gparted. Since parted seems to be used by the Debian installer, the Jessie installer cannot install on these machines without repartitioning the entire disk. That means that on such machines, the only option is to wipe everything or install Wheezy, then edit sources.list to upgrade to Jessie.
Both Gparted v0.19.0 and the Jessie installer report the entire hard disk as a single Fat16 partition,The same partitions which are invisible to Gparted appear as normal in the Places sidebar, of either Thunar or the PCManFM file manager. They can be mounted and used, seemingly without issue (I have experienced the same problem under Ubuntu/Lubuntu 15.10). Below, is the shell output of fdisk, which can see the partition structure and parted, which cannot:
Code: Select all$ sudo fdisk -lu
Disk /dev/sda: 74.5 GiB, 80026361856 bytes, 156301488 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
[code]...
I'm trying to install Ubuntu 10.10 on a brand new 500GB hard drive I just purchased and installed in my machine. I boot from the CD and instruct Ubuntu to install to this drive and tell it to "erase and use the entire disk" for this 500GB drive. After moving forward from that, I see it saying a message about creating an ext4 partition for root "/" and then shortly after the entire install dialogue goes away. All I am left with is the little circle cursors spinning round (mouse input still works) and the installation background. The HDD activity light was still on though. I gave it about 3 hours before I finally gave up and tried again.
When I tried again, I saw that it did create two partitions (root and swap) during the last attempt. The same thing happened, although now even mouse input isn't responding so my system is completely locked up. HDD activity remains active this time as well. Running Ubuntu from the CD works fine. The only problem I saw with it was when I ran gparted from the CD and tried to manually create a ext3 partition on my new disk drive. When I tried that, I ran into a similar occurrence (couldn't run any programs, eventually system locked up) and had to reboot.
I have a second hard disk but I have a lot of valuable data on that and don't want to mess around with it. It could be a hardware failure, but that seems unlikely to me as this is a brand new Seagate disk drive. I suppose I could try installing it on a spare partition on my other drive and see what happens, but other than that I'm out of ideas.
I wrote the hybrid DVD image for DI b2 (Jessie) on the USB drive and booted from it (UEFI mode). But I don't see KDE there in the advanced options. Was it removed from the image, or desktop environment selection is moved to some late stage now?
View 2 Replies View RelatedI am installing Jessie to a dual-boot Dell Inspiron 1150 laptop currently booting Windows XP + Ubuntu 9.04. I downloaded the small installation image:
Code:
Select all//cdimage.debian.org/debian-cd/8.1.0/i386/iso-cd/debian-8.1.0-i386-netinst.iso
and created a live dvd using growisofs.
The Jessie install documentation says: "If you downloaded an iso image, check that the md5sum of that image matches the one listed for the image in the MD5SUMS file that should be present in the same location as where you downloaded the image from." For the downloaded image this produced the result
Code:
Select all~$ md5sum debian-8.1.0-i386-netinst.iso
095a83b715e1b74b6d30b2259275f4af debian-8.1.0-i386-netinst.iso
There is no MD5SUMS file in the download directory. There is an md5sum.txt file included in the iso image: this lists the md5sum of every file in the image, but not that of the image itself. The check for the burned dvd was successful :
Code:
Select all~$ dd if=/dev/cdrom | head -c `stat --format=%s debian-8.1.0-i386-netinst.iso` | md5sum
645120+0 records in
645120+0 records out
330301440 bytes (330 MB) copied, 1.28047 s, 258 MB/s
095a83b715e1b74b6d30b2259275f4af -
Is this a documentation error ? I next booted the laptop from the live installer dvd. After generating a number of messages, it stopped displaying a message along the lines of: "Invalid video mode - press Enter to select a mode".
I assumed it would wait for me but it soon rushed on, producing screeds of segmentation fault error messages, eventually slowing down to a rythmic display of:
Code: Select all*** Error in Xorg:free() invalid pointer: 0xb7101ce3
***Surely it should have waited for me to press Enter?
I've not jumped on the Alpha/Beta upgrade's this time round so have decided to upgrade by doing a fresh install. I'm using the normal desktop install cd via usb. On the drive setup I choose to manually setup the partitions. I deleted the partition which help Lucid. Created a new partition with the root path. All good so far. I selected my home partition and selected use as 'ext2', entered /home as the mount point. Clicking ok to return, showed the /home partition as marked to be formatted, I was unable to change this ... so I decided to quit the installer and reboot ...
1st problem ... the root partition for Lucid was deleted, and a new empty partition created, despite the fact I had not confirmed the actions.
2nd problem ... rebooting with the live cd (which I'm on now) and running the installer, it hangs when I select manual partitioning.
I am trying to clean install Jessie 8.3.0 onto an old PC, where I already have wheezy 7.7 working. I am using the 3 DVD- i386, which passed the integrity check.
Installation goes on smoothly till completing the "Select and Install SW" stage from 1st and 2nd DVD. At this point I get the warning that "Installation step failed, ..", giving the choice to repeat.
When repeated, the process gets completed (without asking for 2nd DVD), the new installation boots normally, but the KDE desktop opens irregularly, with some basic applications missing, and some flaws during certain operations.
The APT does not show any missing/broken link. I tried and repeat the installation with different choices as for kernels and/or desktops, but got the same result. I cannot guess where the problem originates, nor whether it is a known bug of the installer.
I had Debian 7.9 up and running like a charm until yesterday. Today I did the upgrade to 8.2, now boot hangs. I see 3 boot entries for the new kernel now -
Debian GNU/Linux, with Linux 3.16.0-4-amd64
Debian GNU/Linux, with Linux 3.16.0-4-amd64 (sysvinit)
Debian GNU/Linux, with Linux 3.16.0-4-amd64 (recovery mode)
The latter 2 entries have no problem booting up. So do the previous kernel(3.2.0.4) entries. Only the first one hangs, for which I see these 6 lines on the console:
[ 0.214704] pnp 00:04: can't evaluate _CRS: 12298
Loading, please wait...
fsck from util-linux 2.25.2
/dev/mapper/myhost-root: clean, 198627/61000000 files, 2160052/24412 blocks
[ 0.047141] kvm: disabled by bios
[ 0.000985] kvm: disabled by bios
How can I make it boot up like others?
I'm trying to install Wheezy (amd64) from the daily netinst image with the text-based installer. The PC will lock up randomly at some point in the process (usually after about 5-10 minutes). The video signal cuts out, keyboard lights are unresponsive, and I have to hard-reset the machine.I was previously trying to install Linux Mint Debian Edition and had the same problem. Another user reports that this is due to a bug in the nouveau nVidia driver, but I can't confirm it.URL...
I assume the Debian text installer isn't using nouveau, so it seems unlikely that would be the problem. The random timing does suggest an overheating problem, though, and the fact that the video signal drops out would seem to implicate the video card. I had no lockups at all with the OS that was previously installed (Ubuntu 11.04).
I have done on previous releases, but this time it hangs on me. It's "only" a Virtualbox, so I can reproduce it.
The wheezy already runs systemd, and is fully updated to to latest packages. Does not run any graphical.
Edits the source.list and does
$ apt-get update
$ apt-get upgrade # Did on one upgrade
$ apt-get dist-upgrade
It starts to upgrade (complains about missing version in libpgp-error), libc is installed, but at some point the systemd is running at high CPU and a dpkg seems to be stalled.
Should I disable systemd on wheezy before? This might not have been tested so much.
There seems to be no documentation on how to automount partitions and USB devices under systemd in Jessie. (Overall, systemd entirely lacks any useful documentation or GUI configuration tools -- all very cryptic and hidden.)
I created custom files to enable automounting. I put them in /etc/systemd/system -- this may not be the right place, but it works.
Kernel note:
This does not work under the old Wheezy kernel linux-image-3.2.0-4.
To automount my Windows partition so I can access its files, I created:
/etc/systemd/system/media-windows.mount
The name of the file must match the mount point -- in this case, /media/windows
My file notes the device and file type, plus an fmask option so all the Windows files don't seem to be executable:
[Unit]
Description = windows mount to /media/windows
[Mount]
What=/dev/sda1
Where=/media/windows
Type=ntfs-3g
Options=fmask=111
[Install]
WantedBy=multi-user.target
The file ownership must be root.root. Apparently it doesn't need to be executable.
After creating, enable with:
sudo systemctl enable media-windows.mount
and it will mount on the next boot.
I read elsewhere that the before running the enable command you should run a start command:
sudo systemctl start media-windows.mount
but that didn't work for me.
I created a bootable Debian installer on my USB flash drive. The Debian Installation Guide advises;
The hybrid image on the stick does not occupy all the storage space, so it may be worth considering using the free space to hold firmware files or packages or any other files of your choice. This could be useful if you have only one stick or just want to keep everything you need on one device. Create a second, FAT partition on the stick, mount the partition and copy or unpack the firmware onto it.
I want to put non free firmware packages on the stick but when I try to create a FAT partition in the free space using Disk Utility I get the following error;
Error creating partition: helper exited with exit code 1: In part_add_partition: device_file=/dev/sdb, start=661837824, size=7507093504, type=
Entering MS-DOS parser (offset=0, size=8168931328)
MSDOS_MAGIC found
looking at part 0 (offset 0, size 657457152, type 0x00)
new part entry
[Code] ....
I formatted the drive to clear it, created a new FAT partition and copied the Debian.iso to it again. When I tried again to create a partition in the free space the same error occurred.
After my most recent update, the boot sequence hangs at:"a start job is running for Create Volatile files and directories" with a timer and no limit .. I let it go for 12 minutes, but nothing.It seems as long as this sequence remains, the boot process does not finish and just hangs here.I haven't been able to find anything specific to this. I currently cannot boot into this machine, though do have access to files via dual boot.
View 8 Replies View RelatedI installed Jessie day before yesterday on a freshly formatted partition. After a random time, it hangs. If I am playing music at the time, the music continues for a few more seconds _after_ the mouse and keyboard become unresponsive, if that is useful.
Sine I did not understand how to pick the desktop during the installation, I installed Gnome. Afterwards, I installed KDE. Now I have a lot of Gnome stuff around I don't really need. But they are in principle compatible, right?
This morning, the hang was almost immediate after logging on. Only Iceweasl and Amarok and a Konsole were running. I attempted to start Icedove, when everything hung.
Here is the relevant part of the syslog.
Dec 8 07:41:38 jon-desktop rsyslogd:
[origin software="rsyslogd" swVersion="8.4.2" x-pid="775" x-info="http://www.rsyslog.com"]
rsyslogd was HUPed
^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^
[Code] .....
My clock said 07:41 at the time of the hang.
The Ubuntu installer hangs on step 3 0f 6, the stage in which you select the keyboard layout. The computer it is being installed on is a Toshiba Satellite.disk had previously worked to install on a macbook for dualbooting.
View 6 Replies View Relatedtrying to install ubuntu on a 2nd partition on a Dell D630. The OS currently on it is Windows 7 Enterprise. I've used Windows 7 to repartition and have 80GB available for the Ubuntu install but when I put the CD in to run it gets detected as a bootable CD and starts to boot but freezes after Loading...I've left it for 2 hrs and it never progressed past that screen. I've also downloaded and burnt the ISO three times (twice in the 64 bit version and once in the 32). In all cases the install never advances. I've also tried a USB install but couldn't get that to boot
View 5 Replies View RelatedI can boot up 11.04 amd64 to an sd card, and in the early alphas I could install it fine. Older versions of ubuntu install fine (10.10), too.
But since about beta 1 or so of 11.04 (and with the final release), it boots up and I see the installer and it says, yes, you have enough disk space and so forth. But then I click the 'forward' button to proceed with the install and it just hangs with a spinning cursor.
Any one else have this problem or know a workaround/fix? Or know how I can turn on debug messages or so forth to see where exactly it is hanging?
I'm trying to install to an hp tm2t (no cd drive).
I am trying to install 9.1. On bootup the CD loads and gives me the options on Installation, Try Ub etc. However after I choose install the BW logo shows up but nothing happens after that.
Incidentally i have 2 of these machines with 9.1 and 10.04 installing fine in the other one. In this one the main difference is a newer DVD burner. The other one also has a DVD burner but older.
The DVD burner is about 7 months old - purchases earlier in the year.
So wondering if loading the driver is an issue? if so how does the CD load and even the logo loads after Install is selected?
Or is it a different issue and would there be different options to try when installing? I would rather not have to replace the DVD burner.
Just bought a new computer that I will use as server:
Gigabyte 890GPA-UD3H motherboard
AMD Phenon II 1090T
16 Gb RAM
4 x Seagate 2Tb hard disks
I tried to install Ubuntu server 10.04 and 10.10, both 64 bit, having similar results. Also I have tried enabling and disabling the RAID card. On 10.04 installer hangs preparing disk partitioning phase at 43%, on 10.10 hangs at the same stage 45%. Must I download something and apply before that phase?
I've just decided to downgrade from 64-bit to 32-bit Ubuntu. I created a live USB from the most recent (as of today) 11.04 download, booted up, and selected the option to replace Ubuntu. (Also on my HDD are a Windows partition and a shared partition for documents.)The installer hung at the timezone select page - and, foolishly, I hard-restarted the PC. I can get into 'try Ubuntu' without problems, but every time I try to actually install, it hangs. I can't boot into Windows, since GRUB seems to have been overwritten in my failed partial install. (I can get to a 'grub rescue' prompt, though.)
I suspected it might have something to do with my internet connection - I need to go through a university proxy script, so I'm not sure whether the installer will actually have internet access, even after I've been able to apply proxy settings while running Ubuntu from the USB.
Sometimes it does this and other times it does not. It has happened with 2 hard drives. When it formats the partition the bar stops and the mouse pointer graphics stops.
View 3 Replies View RelatedI formatted 56 GBs of my hard disk space into fat32 and it seems that 27 gbs of it is used! Though direct checking from the volume itself shows nothing like this, gparted still insists 27 gbs are used.
View 4 Replies View Relatedi use a 3rd party boot mgr.i installed jessie over etch on my old computer & only choice i saw for grub was sda & sdb where i wanted to install on sdb9.i tried installing it from my wheezy partition & it did but i ended up with 2 boots to wheezy.so i went back to etch.
my question is how to get grub on sdb9 like it was on etch.is there a trick or did i miss a prompt? on another note, that bug where the format hangs if you try & install over an old system is a little irritating. can't believe it hasn't been fixed.
I update Jessie "stable" 8.2 to 8.4 and now I get 5 minute interval kernel messages:
Apr 18 06:39:52 OraHost kernel: [131985.494726] sdc: unknown partition table
Apr 18 06:45:03 OraHost kernel: [132295.755942] sdc: unknown partition table
Apr 18 06:50:03 OraHost kernel: [132595.946564] sdc: unknown partition table
Apr 18 06:55:13 OraHost kernel: [132906.139327] sdc: unknown partition table
Apr 18 07:00:23 OraHost kernel: [133216.340555] sdc: unknown partition table
I believe this has something to do with an mdadm update which was included in the release. When I configured the array, I didn't partition the disk devices, so maybe that has something to do with it. I am thinking of rebuilding the array and partitioning prior to build, but a quick fix would be referable.
And also something appears to have happened to the raid device since the update.
Prior to update, the array was /dev/md0 - now it is /dev/md/0 which is a symbolic link back to /dev/md0.
mdadm --detail --scan now reports /dev/md/0 where previously it reported /dev/md0
I created a new RAID1 array on a fresh system and immediately after the create, these messages appear at 5 minute intervals.
i cant install 10.04 on my desktop with the 32bit or 64bit versions of 10.04 desktop.
i get to step 4 and there is nothing listed for partitions or any information and if i click forward, i get that message "no root file system is defined" "please correct this from the partition menu"
When using the manual partitioner on the fedora 11 installer on the live cd, both for 64 bit and 32 bit, it will not allow me to create a new partition. I understand that I have four primary partitions and it cannot have more than that, so I tried deleting one of the partitions, then creating the new ext4 partition for F11. It still fails and gives me the same bugsee attachment)
how to read this, especially since there is so much there. I see at the top it says that there are 4 primary partitions, could it possibly still be seeing 4 primary partitions when trying to create the new one, even though I am deleting one of them? Other than this, I truly have no idea what else I can do.
EDIT: Attachment wont load up for some reason, here is some of the error file:
anaconda 11.5.0.59-1.fc11 exception report
Traceback (most recent call first):
File "/usr/lib64/python2.6/site-packages/parted/disk.py", line 183, in addPartition
constraint.getPedConstraint())
[Code]....
This is maybe the 15th time I've installed an Ubuntu OS in the past two years, and it's the first time I've really been stuck.Not long ago I installed 10.10, with no problems, but a couple days ago I did a fresh install of windows 7, and I planned to re-install ubuntu 10.10 alongside it.Before I installed windows, I created a partition on my 320gb HD, half and half, but while doing this I noticed that gparted would crash if a USB key was plugged in. I mention this because I'm convinced this is related to the problem.
After having installed windows, I went and created a bootable usb key with 10.10 using unetbootin (which I've used once before, but along time ago). I'm unable to make an actual live CD because my disk drive has been broken for the past year - a fact that has never stopped me from installing different distros with a usb key.So the installer starts as usual, but after the 2nd (or 3rd) step (where it says "for best results, make sure that your computer is plugged in, that you have an internet connection, and at least [...] of free space), I click forward, and the little wheel just spins forever,it never advances.I tried everything again with 10.04.1 and I got the same thing, this time after choosing my keyboard layout.
When I simply go to the live distro and then go to install, I see that at that moment, there's a crash report, something about gparted, which I'm assuming is a built-in part of the next step.
To sum up
-gparted doesn't seem to like USB keys
-installer won't advance to partition table
-can't use a disk because drive is broken!
My computer is an Acer Aspire 4530, AMD64. The 10.10 and the 10.04.1 installations were both 64bit.
This is my first time using Fedora. My previous experience is from Ubuntu. However I want to give a try for Fedora so I went ahead to install it on my new computer. Problem is that Fedora Installer (Live CD) wiped out my NTFS Partition. Causing my computer unable to recover Vista from factory DVD because it lost system partition as well. I want to know if this is my error or a bug in installer.
Original partition setup:
220 GB - Vista System Partition (NTFS)
14 GB - Recovery Partition (NTFS)
First I resized system partition under Windows Management in Vista:
170 GB - System
50 GB - Unallocated
14 GB - Recovery
Using GParted from Ubuntu 9.04 Live CD, moved recovery to the left:
170 GB - System
14 GB - Recovery
50 GB - Unallocated
Rebooted into Vista, make sure everything is fine. Then put in FC 11 Live CD, using custom layout setup in partition, intended partition layout is:
170 GB - System (NTFS) - Primary sda1
14 GB - Recovery (NTFS) - Primary sda2
200 MB - /boot (ext3) - Primary sda3
sda4 - Extended Partition
45.8 GB - / (ext4) - sda5
4 GB - swap - sda6
After I check my setup and pressed enter, it returned with unable to format /boot error: -1. Restart FC installer, it tells me that my hard drive needs to be re-initialized. I clicked no and reboot. BIOS tells me that no OS is found. Attempting to recover from factory DVD failed, telling me that system partition is gone. I want to know did I do something wrong or is this a bug in FC installer.
Trying into install fedora. I am setting up my system as a dual boot over two drives. I have set up a custom layout and whenever I get to the step to write changes to disc it crashes with an unhandled exception. I have tried multiple times now, it always crashes.
Here is the first line from the exception report:
anaconda 15:31 exception report
Traceback (most recent call first):
File "/usr/lib/python2.7/site-packagees/pyanaconda/storage/devicelibs/swap.py", raise SwapError("swapon failed for '%s'" % device)
I have win 7 installed on a primary partition along with two other primary partitions containing a recovery partition and system files partitions. (don't know exactly what the latter is for.) I made a defrag and resized the win partition to make some free space for a primary ubuntu partition.I then inserted the 10.10 live disc and created a fat32 shared partition, a root (/), a /home Nd a swap in the advanced gparted menu, BUT every time I try to initiate the installation I get an error message saying that installer couldn't create the fat32.
View 4 Replies View Related