Debian Installation :: 'Squeeze' AMD64 Installer Fails To Detect Hard Disk
Apr 20, 2011
Having trouble installing 'Squeeze' 6.0.1a-amd64-netinst on a new AMD64 system.The installer boots and runs fine until it gets to hard disk detection. Then it hangs for about 20 minutes showing a blue screen, during which time the HDD-activity light flickers every 5 seconds. Eventually it says it can't detect a hard disk, and displays a (longish) list of possible drivers; no idea which, if any, would suit.Anyone else installed (successfully or otherwise) on this combo?
I have a ssd cosair harddisk with both usb and sata connecters. If I connect it with sata anything is working fine, and I managed to install Fedora core 13.
But I also want to be able to use the harddisk when it is connected with usb and that causes problems.
When I boot the Fedora Core 13 dvd It can't detect my usb harddisk.
When booting in install mode it just don't detect the harddisk.
When booting the dvd in rescue mode it don't detect the harddisk, and it don't create any entries in /dev/ for the harddisk. It is like there is no disk at all.
I have tested this on 3 different computers, so it is not a problem with my specific motherboard. So either it is a problem between my harddisk and Fedora Core 13, or there is some problems with the usb drivers in the boot image used by the Fedora core 13 dvd.
The disk is working fine if I connect it via usb to an existing Windows install, so the usb connection is working.
I installed Fedora core 13 with the harddisk connected to sata and then re-connected the harddisk to usb. It then boot up, but complain about missing root filesystem. Most likely caused by missing usb driver in my kernel.
But anyway, what I really want is the ability to boot from both sata and usb, so I can take the harddisk with me and boot it on other computers with usb.
So is there a command which allows me to build an kernel image which can boot from usb or am I trying to do something which is not really supported?
I did update my fstab to use LABEL=myroot
There is 1 Windows partition(NTFS) and 1 linux partition on the disk. (No seperate /boot partition and no swap)
The Install program is failing to see the hard disk!
Now heres the really weird bit. The live cd can see the drive just fine.
I have created partitions using gparted and the disktool also sees the drive just fine but as soon as I go back to the installer it shows no hard disk!
It's a SATA drive which I suspect might be a part of the problem.
Is there a way I can install without the install program?
Is there a way to make the install program see the drive?
“toshiba satellite u840w with hard disk drive and a solid state disk cache”
Debian 8 installer does not detect the hard drive during installation
I've recently tried to installed Debian 8. The problem is that the partition menu gives me these 3 options: 1. Configure iSCSI volumes 2. Undo changes to partitions 3. Finish partitioning and write changes to disk
There are no options for defining partitions or any hard drive during installation. After searching the internet i found that the problem because the solid state disk SSD cache. How I install a Debian 8 with computer which has a hard disk drive and a solid state disk cache.
more info: I want windows 7(64) and debian dual boot
I want to set the login to the old default of having to enter a username,password. I've tried to use the configuration editor to achieve this and have ticked the "disable-user-list" option under /apps/gdm/simple-greeter but it makes no difference, the greeter still starts with a user list. It appears that the default valuef TRUE for this function is overriding my choice, but I'm notre why. My next step appears to be to edit /etc/gdm3/greeter.gconf-defaults to change the default value. I haven't actually tried that yet so not sure if it would work but, even if it does, it doesn't seem a very elegant way of setting this up. Is there some simple way of changing the behaviour back to asking for username first?
I seem to remember the whole login process as being more configurable than it is now, with options to choose backgrounds, allow root accest finystem->administration->login_screen only gives a choice between selecting a user or automatic login of a particular user, with no further options available.On a general note, would the old method not be a more secure default than presenting an unauthorised user with a list of login id's to be tried?
I have a system with Windows installed. Now I got a second hard disk on which I want to install Debian. After installation I have a dual boot system or I have to manually configure GRUB? Thnak you and I'm sorry fo my inexperience.
Just loaded Squeeze (KDE) onto a partition on my desktop and am a bit alarmed by the disk thrashing thats going on? Damn light on constantly. if I didn't know better I'd think I was using Vista. Is this something to do with 'nepomukservices' that seems to be taking a fair amount of cpu time? Not used to KDE 4 so maybe this is normal.
I have a dual CPU Xeon machine that I have been using various versions of fedora on for years.
The machine has the following disk layout:
I currently have Fedora 10 and grub installed on hda and I had to jump through hoops to install such as disabling the promise controller and reassigning drives because that blasted /dev/mapper kept grabbing the Maxtor ATA drives although I didn't want it to.
Anyway, in the BIOS I can boot from the secondary IDE controller so I want to install Fedora 13 on hdb. Problem is, the Fedora installer won't detect the drive.
Its partition table is as follows:
There is approximately 69GB of free space on this disk but the blasted python based installer wont show the disk as a possible installation location. If I exit to a bash shell I see that the device nodes do exist and I can manually mount and manipulate the disk but the installer is brain dead where the disk is concerned.
I will mention that sdc, sdi, and sdj are used with mdadm to create high performance striped volumes. Also, sdc shows up under /dev/mapper and I don't want to use /dev/mapper at all. I want simple /dev/sd? mount points...no stinking /dev/mapper, and no stinkin volume manager wrappers...
Why I cannot get the installer to use /dev/sdb?
Is there a disk signature on /dev/hd[bc] that is causing them to be grabbed by /dev/mapper, and if so, how would I remove that signature from the drive? /dev/mapper is vacant under Fedora 10.
I have a Dell Poweredge 2970 2x3.0 GHz AMD 64bit dual core, Perc 5/i controller, and 2 brand new Fujitso SAS 15K 146GB drives.
Trying to install Ubuntu 10.04 Server 64 bit from USB. At the point of detecting disks, the installer only recognizes the USB. The installation was created using Pendriveinstaller ver1.8.0.1 per Ubuntu Server web site instructions. I have the drives configured as 2 separate raid 0 arrays using the bios raid configurator. The drives have been initialized. (Tried before with a single Raid 1 array, but had same issue and since have read Ubuntu support for hardware raid is not great, so was going to bypass hardware raid for now).
I've seen some chatter on here about opening a terminal at this point and removing dmraid but don't see an option for terminal only shell.
I have an Asus P5K motherboard with an Intel Core 2 Duo 8400. It has 2 SATA hard disks, a 250 GB Seagate and a 500GB Hitachi.
I've been running Fedora 10 x86_64 for 6 months on this computer without problems.
I'm trying to do a new Fedora 11 install on this computer but the installer (Anaconda?) only detects the Hitachi disk.
I've tried to make a new Fedora 10 install to check if it was a media or disk problem and it detects the two hard disks.
I've tried to install it via a Live CD, and the installer only detects the Hitachi disk. The LiveCD detects the two hard disks, I can access it, partition, format, write, but the installer only detects the Hitachi.
I've tried to change from Enhanced SATA (AHCI) to Compatible in BIOS without success and I've changed SATA cables from one disk to the other, changed the disk order and nothing.
Must I enter some boot parameters for Fedora 11? Has the LiveCD installer some options?
I have Asus Z87-PRO motherboard with i5-4670k and I'm trying to install Debian Testing with 64-bit architecture. My problem is mouse and keyboard (I guess USB in general) stop working after installer get loaded (the last thing I do is choose between text and graphical install). I found a few topics on different forums indicating that I should enable IOMMU (Intel VT-d) option in my bios.
The problem is that Intel k-series processors didn't use to have IOMMU support, so there's nothing I can do about it. I tried changing different bios options like disabling UEFI, enabling xHCI and EHCI with no luck. Passing "iommu=off" or "iommu=soft" to the boot command also doesn't work. However, I have LMDE 2 64-bit live cd (based on Debian Jessie) and it works fine, so I guess my problem may be related to some changes in 4.2 kernel.
I just installed Debian stable from the standard i386 DVD. When I booted up, I noticed that GRUB showed me that I had the amd64 version of Debian installed. However, I did not download an amd64 DVD, nor do I want that architecture installed on my system (even though my system can support it). The output from "uname -a" (which included both "amd64" and "x86_64") also seem to confirm this. However, I was able to install 32 bit packages and get them to work (gdebi wouldn't even let me do this when I had Ubuntu 32-bit).
The way I usually boot Linux distros, and this has worked for every distro I have tried up to Kubuntu 10.10, was to install Grub2 on an extended partition, run "dd if=/dev/sda5 of=linux.bin bs=512 count=1", and then adding that bin file to my Windows boot.ini. What usually happens after is that I get the Grub2 menu after selecting it from the Windows Bootloader.
The problem is, with the latest Squeeze AMD64, all I get when I do this is a static cursor and the computer is frozen and I have to hit the reset button.I mounted the Linux partition with Ext2IFS (mkfs.ext3 -I128 /dev/sda5 to get 128KB inodes), and I can see that the Squeeze installer did indeed install Grub2, because I can see the files in their respective directories.
My PC configuration is as follows: CPU: AMD Athlon II 245 X2 RAM: 2GB DDR2 MB: ASUS M2A74-AM SATA DVD-Writer WD 320GB SATA HDD.
SATA Controller is in AHCI mode in BIOS. Partition Table: 1. Pri. (Windows 7 Ultimate) 2. Log. (Data) 3. Log. 15GB free space (want to install Linux in this partition)
I want to install Debian 5.0.4 from DVD. But the installer is not showing any partitions, it says entire hard disk is blank. But I ran 'fdisk -l' in the console, it shows the partitions correctly.
I try to install Ubuntu on my new HTPC. I start Ubuntu with the Live CD and it boots fine. Then I want to start installing Ubuntu on my hard disk.Unfortunately the installer does not see my hard disk which has 1 empty ext4 partition. However, it can be seen and managed in GParted.
I downloaded this "debian-6.0.1a-amd64-netinst" iso image....But on the partitioning screen, after selecting the manual partitioning, it shows the whole hard disk without detecting the XP partitions.
I am trying to install Debian Lenny (64 bit) on my brand new Toshiba laptop (intel i3, 3 GB RAM) and for some reason the installer cannot detect the ethernet card. This is the error message I get:"No Ethernet card was detected. If you know the name of the driver needed by your Ethernet card, you can select it from the list."And then there's a list which is quite long -- and I cannot replicate it here. But I want to know why the installer cannot find the ethernet card on its own or find the appropriate driver. In any case how can I fix this problem?
I am trying to figure out where the harddisk power management can be found in Squeeze. Before it was in the scripts under /etc/acpi, but in Squeeze it's not. I'd like to be able to change the hdparm -B value from 128 to 200 when using battery.
"The installer encountered an eror copying files to the hard disk: [Errno 30] Read-only file system
This is often due to a faulty CD/DVD disk or drive, or a faulty hard disk. ..."
Before I try changing CD drives, re-formatting the hard drive (again), or cleaning the CD drive, I must add that Xubuntu did open. I got rid of all traces of the previous operating system (WinME), and Xubuntu seems to work pretty well. The installation stopped at 41% of copying files. Should I aim for a finished installation or is this fine?
Each time, different methods, I get this about 3/4 of the way through:
The installer encountered an error copying files to the hard disk:
[Errno 5] Input/output error
This is often due to a faulty CD/DVD disk or drive, or a faulty hard disk. It may help to clean the CD/DVD, to burn the CD/DVD at a lower speed, to clean the CD/DVD drive lens (cleaning kits are often available from electronics suppliers), to check whether the hard disk is old and in need of replacement, or to move the system to a cooler environment.
The only possibility of those is the CD being bad. But I've used it before, recently, and it was fine. I will burn another one from my other computer and try, but it shouldn't be doing this.
Question: If I plan to only use Ubuntu on this computer (no dual boot) should I make the /,swap and /home partitions all Primary or some logical, or does it even matter?
I have 2 machines packardbell p3/733 and a Gigabyte p4/1.9Ghz both are running well with Lenny.The Lenny installer (debian-500-i386-netinst.iso ) works fine on both machines.The all the copies of squeeze installer ( debian-6.0.1a-i386-netinst.iso ) work on the P4 but on the P3 it locks up / crashes video card / ??? when I select Graphical install.I have re downloaded the file and use gnomebaker to burn the iso image.could it be a hardware incompatibility ?
The installer for powerpc is broken in Squeeze. If yaboot is installed, it will break the whole boot process. I don't know exactly what goes wrong but it is a serious bug. I tried many times until I found out that yaboot is broken in Squeeze. In Lenny it still works luckily, so I could get something back after a complete sweep of my hard disk (the Lenny installer could not do anything with the ext4 partition of Squeeze as it is not supported in Lenny, so trying to put yaboot back did not work from there). Let this be a warning to people and a reminder for developers that there is a serious bug in yaboot.
I am still getting the error that no kernel modules are found when trying to load components from the CD on the multi-arch version of Squeeze. Are these even tested prior to releasing them? I mean I know it's testing but I thought we were reaching a release-date and the installer is 100% broken and has been for months. I have a pile of useless multi-arch CDs for Squeeze that won't install on 64bit or 32bit machines due to not finding the kernel modules. Can we get some testing on the installer portion of Squeeze?
I am attempting to iron out a detail that has been bugging me a long time.Does the procedure of providing the firmware during install actually work? Note: I am NOT asking how to install the firmware POST install. What I have done to attempt to resolve:
1. Searched forums with no luck on this specific question. 2. Google was likewise uninformative.
Steps performed:During the wheezy install, from cd (cd1 testing amd64, appx 680MB), it prompts for firmware, which it identifies as ucode15.fw. (This is only part of the file name, as I did not write the entire bit down during the install.)
Trying to install SUSE on a perfectly working PC that was running Windows. Blew away all the partitions and formated the drives.When trying to install SUSE, Installer will not detect my two hard disks. Tried with version 10.x, 11.1 and 11.2, without success.My Mobo is a XFX GeForce 8209, and my SATA drives are both Seagates (1x120GB, 1x320GB). I've tried different SATA mode selection (i.e. SATA, AHCI, and RAID) without any success either.I've tried to look for SATA controller drivers for my Mobo, to try to load on Installer startup, but failed there too.
I'm trying to install Debian Jessie beta2 on a UEFI laptop. The installation worked just fine before with setting in manual partitioning an EFI system partition and a root partition.But when I try to partition with root as an encrypted volume I get this error when I wanna write changes to disk:" the attempt to mount a file system with type vfat in scsi1 partition sda at /boot/efi failed"When I choose resume partitioning the installer then freezes at "detect file systems".
Because my harddrive needs specific alignment I've made beforehand in gdisk:EFI System Partition of 100mib at /dev/sda1/boot partition of 512mib at /dev/sda2/ (because I expect the installer to want a /boot too for an encrypted device)rest of harddrive reserved for root at /dev/sda3
As I have no blank cds handy right now, I had to go the way descirbed here:URL...But when I seect my partition and / (no sub dirs, an empty ext3 formated 6.8GB partition, exclusivly for that usage) it tells me there ws no installation media found and the search path got automagically adjusted to /imges/image.img.And ideas howto fix that? Or how to install fedora from harddisk (without big fuss)?
I just finished reinstalling Squeeze on my little netbook using the debian-6.0.0-i386-netinst.iso and accepting just about all defaults, including that for the Desktop environment in tasksel. It appeared upon rebooting that, much to my surprise, KDE had been installed -- not the usual Gnome. Of course, there's nothing inherently wrong with KDE, but changing the familiar behaviour of the Debian Installer (i.e. to install Gnome) without warning seems a bit much to this long-time Debian user...
This laptop has been in the mainstream news as the cheapest Windows laptop available. Unfortunately it has a 64-bit CPU with 32-bit UEFI that dumps to the grub shell before installation. In addition, the built-in keyboard does not work.
As far as the dump to shell problem, this seems like something is not setup correctly in the grub UEFI configuration. This "hybrid" notebook should be using the multi-arch as I understand the situation. I noticed there is no grub configuration file in the multi-arch netinst ISO when I mounted it and looked around. I also noticed the standard netinst ISO is not easily mountable: there are errors when I try to mount the individual partitions to inspect the grub configuration. Additionally, Kubuntu boots perfectly aside from the keyboard issue. Devuan also boots when I modify the netinst to bypass gummiboot and use grub directly. Finally, the multi-arch grub shell freezes up when autocompleting and searching through the drives for the grub config, leading to a forced reboot. As an extra note, I tried 2 different flash drives and CD install media with the same results.
I tried many, many grub kernel combinations to fix the keyboard issue. It works in grub, but not in Linux. I was ultimately going to try a newer kernel to fix it.I was in a hurry to get something set up so back to the store it goes.
