Re: Duel Booting Debian on a Mac
Am 27.01.2015 um 13:00 schrieb Jonathan Copeland jonathan.mcopel...@icloud.com: Hi Debian Community I am a student at the University of Pretoria and I need to have Debian installed on my Mac for my degree, The only requirements that we’ve been notified of are that we’re meant to be able to run Debian in our Computers and that we are to be able to submit Projects. I’d like to partition the disk and install Debian in a duel boot using 100gb, like when you duel Boot to Windows. My Mac’s details are the following; 15” Macbook Pro retina 2,5 GHz Intel Core i7 16 GB 1600 MHz DDR3 Intel Iris Pro 1536 MB 500gb SSD It depends on the model of the Mac, the firmware and the version of OSX, if it is easy and works without problems. I did it following the usual HOWTOs [1] on a MacAir Mid 2013, installing reFind, shrinking the OSX partition on the 128 GB SSD to 60 GB, and installing Debian on the free space. Of course you should backup your disk before shrinking with e.g. TimeMachine. In the end I uninstalled Debian because of the following problems: 1. The brightness of the screen does not readjust after suspend/resume in Debian (I worked hard trying to solve this with some published hacks, but no full success). 2. Often the Mac got hot with closed lid, eating the battery. This seems caused by the above firmware manipulation hack. 3. Ugrades of OSX seem to damage the reFind configuration. Also there is a problem writing the hidden rescue partition during an upgrade of OSX. [1] http://www.howtogeek.com/187410/how-to-install-and-dual-boot-linux-on-a-mac/ What’s the best and safest way that I can do this? Install VirtualBox on OSX and install Debian in VirtualBox. This is the safest way. The disadvantage of a virtualized Debian are some restrictions in using hardware like USB-devices, and degraded performance. Another way, which I choosed, is doing your tasks directly in OSX, using e.g. homebrew, perlbrew. Many packages available for Debian can also be compiled and installed under OSX, but sometimes it is boring and time consuming. This depends on the tasks and details. But I am happy with this way, mainly developping in Perl, C, C++ in OSX on one of best lightweight (1 kg) laptops, with a battery allowing 9 hours of work. HTH Helmut Wollmersdorfer
Duel Booting Debian on a Mac
Hi Debian Community I am a student at the University of Pretoria and I need to have Debian installed on my Mac for my degree, The only requirements that we’ve been notified of are that we’re meant to be able to run Debian in our Computers and that we are to be able to submit Projects. I’d like to partition the disk and install Debian in a duel boot using 100gb, like when you duel Boot to Windows. My Mac’s details are the following; 15” Macbook Pro retina 2,5 GHz Intel Core i7 16 GB 1600 MHz DDR3 Intel Iris Pro 1536 MB 500gb SSD What’s the best and safest way that I can do this? Thanks:) ___ Jonathan Michael Copeland M // (+27) 82 857 1349 T // @jonmcopeland
Re: latest backports kernel not booting when LVM is involved
Gary Dale extremegroundmai...@gmail.com writes: On 25/11/14 02:14 PM, lee wrote: Hi, what could be the problem with the backport kernels? They never finish booting when the root fs is on an LVM volume. Do I need to take special precautions with the backports kernel to get it to boot? I have a separate /boot partition not on LVM and a biosgrub partition with the root fs on an LVM logical volume. The default Wheezy kernel boots just fine; the backports kernel gets stuck with the last message being that some random-thing has been initialized. The kernel is still alive then: I can plug/unplug USB devices and get messages about it on the console. I can also see that the LVM volumes are detected. What happens if you boot to a recovery console/single user mode instead of a normal boot? same result Even the default kernel wouldn't boot anymore. It was quite a pita to recover because one of the domUs handles the internet connection and I had to go to some lengths to be able to finally put the default kernel back. The Debian installer definitely needs to come with non-free firmware at least for network cards, and the rescue mode needs to be able to set up a pppoe connection just like the installer can when in expert mode. I really don't understand what the big deal with the non-free firmware is. If you need it, you need it, and having to load it from somewhere else (which doesn't really work anyway) sucks. Other than that it sucks, it doesn't make a difference whether it comes with the installer or not because when you do need it, you'll use it anyway. If I didn't happen to have added another network card anyway, I'd have been screwed because of Debians firmware issues. Or can you get to a console using Ctrl-Alt-F2? Oh, I didn't try that. The kernel didn't finish booting: I pressed Enter to see if there would be a login, and there wasn't. I could reboot with Ctrl+Alt+Del. Some of the domUs are running the backports kernel just fine, and it has been running fine on the same machine before the root fs was on an LVM partition. The problem really seems to be when LVM is involved. Perhaps there are some modules which mkinitramfs puts into the boot image while dracut omits them? Hoever, the LVM volumes were detected, yet shortly after, booting didn't proceed. -- Again we must be afraid of speaking of daemons for fear that daemons might swallow us. Finally, this fear has become reasonable. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/87h9xlepcs@gulltop.yagibdah.de
latest backports kernel not booting when LVM is involved
Hi, what could be the problem with the backport kernels? They never finish booting when the root fs is on an LVM volume. Do I need to take special precautions with the backports kernel to get it to boot? I have a separate /boot partition not on LVM and a biosgrub partition with the root fs on an LVM logical volume. The default Wheezy kernel boots just fine; the backports kernel gets stuck with the last message being that some random-thing has been initialized. The kernel is still alive then: I can plug/unplug USB devices and get messages about it on the console. I can also see that the LVM volumes are detected. -- Again we must be afraid of speaking of daemons for fear that daemons might swallow us. Finally, this fear has become reasonable. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/878uizrt1w@gulltop.yagibdah.de
Re: latest backports kernel not booting when LVM is involved
On 25/11/14 02:14 PM, lee wrote: Hi, what could be the problem with the backport kernels? They never finish booting when the root fs is on an LVM volume. Do I need to take special precautions with the backports kernel to get it to boot? I have a separate /boot partition not on LVM and a biosgrub partition with the root fs on an LVM logical volume. The default Wheezy kernel boots just fine; the backports kernel gets stuck with the last message being that some random-thing has been initialized. The kernel is still alive then: I can plug/unplug USB devices and get messages about it on the console. I can also see that the LVM volumes are detected. What happens if you boot to a recovery console/single user mode instead of a normal boot? Or can you get to a console using Ctrl-Alt-F2? -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/5475582f.4050...@torfree.net
Re: Jessie B2 Installer Not booting in Macbook Air
On Fri, Nov 21, 2014 at 09:17:09PM -0700, john.tiger wrote: Have followed both guided partitioning as well as trying manual partitions with efi boot as first partition. Install works fine but after completion does not boot (get ? folder image) - tried to boot into rescue mode but target partition not found partitions : free space 1 gb /efi 1 gb I think that 1 GB is huge for an EFI partition. Even Windows only uses a few hundred MB at most. Grub needs only a few kilobytes. Also, you probably need to mount it at /boot/efi, ensure that it's fat32-formatted and has a GUID of C12A7328-F81F-11D2-BA4B-00A0C93EC93B. / 30 gb swap 4 gb /home 80 gb free space 4 gb tried to put efi as first partition but installer automatically puts 1gb free space in front also tried Fedora 20 - it boots fine would prefer to use Jessie -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/54700e45.8040...@gmail.com signature.asc Description: Digital signature
Jessie B2 Installer Not booting in Macbook Air
Have followed both guided partitioning as well as trying manual partitions with efi boot as first partition. Install works fine but after completion does not boot (get ? folder image) - tried to boot into rescue mode but target partition not found partitions : free space 1 gb /efi 1 gb / 30 gb swap 4 gb /home 80 gb free space 4 gb tried to put efi as first partition but installer automatically puts 1gb free space in front also tried Fedora 20 - it boots fine would prefer to use Jessie -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/54700e45.8040...@gmail.com
Re: how to force chronyd to be online after booting
Dieter Deyke dieter.de...@gmail.com writes: On 09/26/2014 06:31 PM, lee wrote: is there an easy way to force chronyd to get into/remain in its online mode rather than going into offline mode? I had the same problem. My workaround was to run the following python script from /etc/cron.hourly/ #! /usr/bin/env python import os import time def main(): chronyd_running = False for line in os.popen(ps -ef, r).readlines(): if /usr/sbin/chronyd in line: chronyd_running = True sources_ok = False if chronyd_running: for line in os.popen(chronyc sources, r).readlines(): if line.startswith(^) and 10y not in line: sources_ok = True if not sources_ok: os.system(/etc/init.d/chrony stop) time.sleep(3) os.system(/etc/init.d/chrony start) if __name__ == __main__: main() Thank you, that should work fine :) Apparently more recent versions of chrony don't go offline like older versions do, i. e. they automatically retry to reach the servers in increasing time intervals. -- Hallowed are the Debians! -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/87k34bmrd3@yun.yagibdah.de
Re: how to force chronyd to be online after booting
Philippe Clérié phili...@gcal.net writes: On 09/27/2014 07:17 AM, lee wrote: Hm, you don't use UPSs? :-) It's a long story. I'll make it short: I'm in Haiti. Grid power is an iffy proposition. :-) So we have to have heavy backups. That means generators and large inverters. There is always a slight delay when switching to batteries. Some computers are more sensitive to that delay than others, particularly when the batteries are nearing end of life. My setup is not that critical and does not require the expense of a real UPS. You're much more in a situation that requires an UPS than I am. Still, I did get 50 days uptime once on a ARM system. Typically it's 5 to 7 days. Only 50? How do you store data? -- Hallowed are the Debians! -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/87fvezmr9l@yun.yagibdah.de
Re: Messages from starting services while booting
op 25-09-14 13:04, Paul van der Vlis schreef: Hello, I am using Wheezy, and on some machines I see messages from starting services while booting, and on some machines I don't see them. Can somebody explain me how this works? I have the idea that I don't see messages on fast machines. And can I control this? On some servers I like to see the messages from the services when the machine boots. The point was a wrong configured serial console. In /etc/default/grub I had this lines after the default lines: GRUB_TERMINAL=console serial GRUB_CMDLINE_LINUX=console=tty0 console=ttyS2,115200n81 GRUB_SERIAL_COMMAND=serial --unit=1 --speed=115200 --stop=1 But ttyS2 was wrong! The serial console is the second serial port, and that's ttyS1, counting from 0. Using ttyS2 gave strange problems, and this was one of them. Even an attached screen and bootlogd gave no messages of starting services. After changing to ttyS1 is everything OK now. With regards, Paul van der Vlis. -- Paul van der Vlis Linux systeembeheer, Groningen http://www.vandervlis.nl -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/542dbfdc.1030...@vandervlis.nl
Re: how to force chronyd to be online after booting
On 09/26/2014 06:31 PM, lee wrote: is there an easy way to force chronyd to get into/remain in its online mode rather than going into offline mode? I had the same problem. My workaround was to run the following python script from /etc/cron.hourly/ #! /usr/bin/env python import os import time def main(): chronyd_running = False for line in os.popen(ps -ef, r).readlines(): if /usr/sbin/chronyd in line: chronyd_running = True sources_ok = False if chronyd_running: for line in os.popen(chronyc sources, r).readlines(): if line.startswith(^) and 10y not in line: sources_ok = True if not sources_ok: os.system(/etc/init.d/chrony stop) time.sleep(3) os.system(/etc/init.d/chrony start) if __name__ == __main__: main() -- Dieter Deyke mailto:dieter.de...@gmail.com -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/87zjdjmx2o@deyke2.deyke.net
Re: how to force chronyd to be online after booting
Philippe Clérié phili...@gcal.net writes: On 09/26/2014 06:31 PM, lee wrote: So is there some simple way to just force chronyd to remain online? I think when there isn't an option for this, I'll just replace it with ntpd ... I'd like to second that question. I've used chronyd for a while and I thought it worked great. When it worked. Unfortunately, my location is subject to blackouts, and some computers are more sensitive to changes in power sources than others. Long story short: chronyd stops working. Hm, you don't use UPSs? I am now using openntpd. I would much rather use chrony. Perhaps we should make a feature request? IIUC, there's an offline option for chronyds configuration file that can be used with every server declaration. They could add an online option to have chronyd always poll the server instead of going into offline mode. It could have a timeout option like: server ntp-1.example.com online 3600 server ntp-2.example.com online 0 The first one would try to reach the server for 3600 seconds and then go into offline mode. The second one would try to reach the server indefinitely. Hm, make the retry-duration optional and assume a duration of 0 when it's omitted. Anyway, I have replaced chronyd with ntpd. Even if the feature will be added, it'll take quite a while until it arrives here. Ccing chrony-...@chrony.tuxfamily.org -- Knowledge is volatile and fluid. Software is power. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/87d2ahwgr7@yun.yagibdah.de
Re: how to force chronyd to be online after booting
On 09/27/2014 07:17 AM, lee wrote: Hm, you don't use UPSs? :-) It's a long story. I'll make it short: I'm in Haiti. Grid power is an iffy proposition. :-) So we have to have heavy backups. That means generators and large inverters. There is always a slight delay when switching to batteries. Some computers are more sensitive to that delay than others, particularly when the batteries are nearing end of life. My setup is not that critical and does not require the expense of a real UPS. Still, I did get 50 days uptime once on a ARM system. Typically it's 5 to 7 days. -- Philippe -- The trouble with common sense it that it is so uncommon. Anonymous -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/5426bef8.5090...@gcal.net
Re: how to force chronyd to be online after booting
Philippe Clérié wrote: On 09/27/2014 07:17 AM, lee wrote: Hm, you don't use UPSs? :-) It's a long story. I'll make it short: I'm in Haiti. Grid power is an iffy proposition. :-) So we have to have heavy backups. That means generators and large inverters. There is always a slight delay when switching to batteries. Some computers are more sensitive to that delay than others, particularly when the batteries are nearing end of life. My setup is not that critical and does not require the expense of a real UPS. Still, I did get 50 days uptime once on a ARM system. Typically it's 5 to 7 days. Have you asked this question on their mailinglist? chrony-us...@chrony.tuxfamily.org Hugo -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/m07ts3$71d$1...@ger.gmane.org
preseed from CD different to network booting
Hey Debianers, I am trying to compose a real basic preseed file, that will answer all the d-i questions so that the install is completely automated. This works on a PXE boot (with dhcp) but not with a CD boot (with dhcp). I still get asked to confirm my hostname, domain name and also if I want to install grub on the MBR with the CD install, but not the PXE install. What gives? Cheers Iain ### Preseed config ## Created by cpc ## Inspired by https://www.debian.org/releases/wheezy/example-preseed.txt ### Locale config d-i console-setup/ask_detect boolean false d-i debian-installer/locale string en_GB d-i keyboard-configuration/xkb-keymap select uk ### Network config d-i netcfg/enable boolean true d-i netcfg/choose_interface select auto d-i netcfg/disable_dhcp boolean false d-i netcfg/get_hostname string test d-i netcfg/get_domain string mydomain.lan d-i netcfg/wireless_wep string d-i hw-detect/load_firmware boolean true ### Mirror configuration d-i mirror/country string manual d-i mirror/http/hostname string mirror.ox.ac.uk d-i mirror/http/directory string /debian d-i mirror/suite string stable d-i mirror/http/proxy string ### Root account d-i passwd/root-password password hackmebaby d-i passwd/root-password-again password hackmebaby ### User config d-i passwd/user-fullname string Iain M Conochie d-i passwd/username string iain d-i passwd/user-password password r00tm3 d-i passwd/user-password-again password r00tm3 d-i passwd/user-uid string 1004 ### Clock, timezone and optionally ntp setup d-i clock-setup/utc boolean true d-i time/zone string UTC d-i clock-setup/ntp boolean true d-i clock-setup/ntp-server string 0.uk.pool.ntp.org ### Partition setup d-i partman-auto/disk string /dev/vda d-i partman-auto/method string regular d-i partman-lvm/device_remove_lvm boolean true d-i partman-md/device_remove_md boolean true d-i partman-auto/choose_recipe select atomic d-i partman-partitioning/confirm_write_new_label boolean true d-i partman/choose_partition select finish d-i partman/confirm boolean true d-i partman/confirm_nooverwrite boolean true d-i partman/mount_style select uuid ### Apt setup # You can choose to install non-free and contrib software. d-i apt-setup/non-free boolean true d-i apt-setup/contrib boolean true d-i apt-setup/services-select multiselect security, updates d-i apt-setup/security_host string security.debian.org ### Package selection tasksel tasksel/first multiselect standard popularity-contest popularity-contest/participate boolean false d-i pkgsel/include string openssh-server less locate ### Finish off the install d-i finish-install/reboot_in_progress note -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/5425aa51.5060...@thargoid.co.uk
Re: preseed from CD different to network booting
On Fri 26 Sep 2014 at 19:02:57 +0100, Iain M Conochie wrote: I am trying to compose a real basic preseed file, that will answer all the d-i questions so that the install is completely automated. This works on a PXE boot (with dhcp) but not with a CD boot (with dhcp). I still get asked to confirm my hostname, domain name and also if I want to install grub on the MBR with the CD install, but not the PXE install. What gives? For the hostname: d-i netcfg/get_hostname string test d-i netcfg/hostname string test For grub: d-i grub-installer/with_other_os boolean true d-i grub-installer/only_debian boolean true The domain name cannot be preseeded. This is recommended: https://www.debian.org/releases/wheezy/example-preseed.txt -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140926182432.gv4...@copernicus.demon.co.uk
Re: preseed from CD different to network booting
Hey Brian, On 26/09/14 19:24, Brian wrote: On Fri 26 Sep 2014 at 19:02:57 +0100, Iain M Conochie wrote: I am trying to compose a real basic preseed file, that will answer all the d-i questions so that the install is completely automated. This works on a PXE boot (with dhcp) but not with a CD boot (with dhcp). I still get asked to confirm my hostname, domain name and also if I want to install grub on the MBR with the CD install, but not the PXE install. What gives? For the hostname: d-i netcfg/get_hostname string test d-i netcfg/hostname string test For grub: d-i grub-installer/with_other_os boolean true d-i grub-installer/only_debian boolean true The domain name cannot be preseeded. This is recommended: https://www.debian.org/releases/wheezy/example-preseed.txt Yeah - I used that for inspiration. I guess I should add the grub parts so that the questions are not asked. Thanks for that. However, I am concerned why a CD d-i behaves differently to a PXE d-i. It, of course, could be that I am using different versions (the ISO image I have is old) so I will try the latest images and see what happens. I am using a netinst CD image if that makes any difference. Cheers Iain -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/5425b2ad.9060...@thargoid.co.uk
how to force chronyd to be online after booting
Hi, is there an easy way to force chronyd to get into/remain in its online mode rather than going into offline mode? So far, the documentation I found says it'll go and remain offline when it can't reach a server. When that happens, it can only be put into online mode via chronyc. The startup script is attempting to bring chronyd online in case a default route is set (which is the case). Yet chronyd remains offline, probably either because the script doesn't detect that a default route is set or because it's unable to put chronyd online (which is being denied when I run 'chronyc online' from the commandline). Since there's some indication that chronyd is considered to be a better choice than ntpd, I'd like to keep chronyd. But chronyd is useless when it remains offline, and I don't want to have to mess around with it a lot and rather replace it with ntpd. The server it uses is the dom0 of the VM chronyd is running in, so the server is even /granted/ to be online. When I restart chronyd manually after booting the VM, it works fine, proving that the server is reachable. So is there some simple way to just force chronyd to remain online? I think when there isn't an option for this, I'll just replace it with ntpd ... -- Knowledge is volatile and fluid. Software is power. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/87iokaxbcb@yun.yagibdah.de
Re: how to force chronyd to be online after booting
On 09/26/2014 06:31 PM, lee wrote: Hi, is there an easy way to force chronyd to get into/remain in its online mode rather than going into offline mode? So far, the documentation I found says it'll go and remain offline when it can't reach a server. When that happens, it can only be put into online mode via chronyc. The startup script is attempting to bring chronyd online in case a default route is set (which is the case). Yet chronyd remains offline, probably either because the script doesn't detect that a default route is set or because it's unable to put chronyd online (which is being denied when I run 'chronyc online' from the commandline). Since there's some indication that chronyd is considered to be a better choice than ntpd, I'd like to keep chronyd. But chronyd is useless when it remains offline, and I don't want to have to mess around with it a lot and rather replace it with ntpd. The server it uses is the dom0 of the VM chronyd is running in, so the server is even /granted/ to be online. When I restart chronyd manually after booting the VM, it works fine, proving that the server is reachable. So is there some simple way to just force chronyd to remain online? I think when there isn't an option for this, I'll just replace it with ntpd ... I'd like to second that question. I've used chronyd for a while and I thought it worked great. When it worked. Unfortunately, my location is subject to blackouts, and some computers are more sensitive to changes in power sources than others. Long story short: chronyd stops working. I am now using openntpd. I would much rather use chrony. -- Philippe -- The trouble with common sense it that it is so uncommon. Anonymous -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/5425fa38.8070...@gcal.net
Messages from starting services while booting
Hello, I am using Wheezy, and on some machines I see messages from starting services while booting, and on some machines I don't see them. Can somebody explain me how this works? I have the idea that I don't see messages on fast machines. And can I control this? On some servers I like to see the messages from the services when the machine boots. With regards, Paul van der Vlis. -- Paul van der Vlis Linux systeembeheer, Groningen http://www.vandervlis.nl -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/5423f6db.9000...@vandervlis.nl
Re: Messages from starting services while booting
On 9/25/14, Paul van der Vlis p...@vandervlis.nl wrote: Hello, I am using Wheezy, and on some machines I see messages from starting services while booting, and on some machines I don't see them. Can somebody explain me how this works? I have the idea that I don't see messages on fast machines. And can I control this? On some servers I like to see the messages from the services when the machine boots. Can't explain the how's and why's but an Internet search just found this at Debian Wiki: https://wiki.debian.org/bootlogd Mine at /etc/default/bootlogd only has two lines (just changed mine to yes): # Run bootlogd at startup ? BOOTLOGD_ENABLE=no If bootlogd's not installed, it's installable for *some* distros, if not all. A dry run at upgrading here shows it would be 4MB involving ~17 packages** BUT am seeing reference to sysvinit-utils. Later distros will surely reflect something else in place of that one *if* this package even exists at that point. As an aside, I'd be curious to hear if it's more or less files involved in install/upgrade if anyone happens to poke around in the same (again, *if* it even exists in later distros) Reading this search result page: http://forums.debian.net/viewtopic.php?f=30t=84590 It looks like that MIGHT have shared what you're directly seeking: Open /etc/default/rcS as root and you *should* find two lines similar to: # be more verbose during the boot process VERBOSE=no If yours says no, try changing it to yes and see what happens. or just try the log file first. That's my option as you can study at your leisure. Hope that helps.. :) Cindy ** On the chance knowing them might help your search for how and why, the ~17 packages affected during bootlogd install on *my* setup: bootlogd console-setup-linux console-setup ifupdown initramfs-tools initscripts keyboard-configuration klibc-utils libjson0 libklibc libudev0 lsb-base netbase sysvinit-utils udev upstart util-linux PS Searches to successfully land this kind of answer get tricky sometimes. These came up first 2 results on the first shot with a weirder than normal array of keywords: debian how do i want to see messages at boot -- Cindy-Sue Causey Talking Rock, Pickens County, Georgia, USA * I comment, therefore I am (procrastinating going out in the cold) * -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/cao1p-kcbpnixuvadvtfk2waxb+w6pqf6pavkz_jon8ymdte...@mail.gmail.com
Re: Messages from starting services while booting
Hello Cindy-Sue, op 25-09-14 15:08, Cindy-Sue Causey schreef: On 9/25/14, Paul van der Vlis p...@vandervlis.nl wrote: Hello, I am using Wheezy, and on some machines I see messages from starting services while booting, and on some machines I don't see them. Can somebody explain me how this works? I have the idea that I don't see messages on fast machines. And can I control this? On some servers I like to see the messages from the services when the machine boots. Can't explain the how's and why's but an Internet search just found this at Debian Wiki: https://wiki.debian.org/bootlogd Bootlogd is about logging those messages in a logfile. I am talking about showing the messages on the screen while booting. If bootlogd's not installed, it's installable for *some* distros, if not all. Maybe bootlogd does not work with systemd, what's the default in newer Debian versions. I am talking about Wheezy. Open /etc/default/rcS as root and you *should* find two lines similar to: # be more verbose during the boot process VERBOSE=no I've checked the settings of this file, but it is on all machines the default, a disabled line. So this cannot be the point. With regards, Paul van der Vlis. -- Paul van der Vlis Linux systeembeheer, Groningen http://www.vandervlis.nl -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/54241ffb.5080...@vandervlis.nl
Re: Messages from starting services while booting
On 2014-09-25 13:04 +0200, Paul van der Vlis wrote: I am using Wheezy, and on some machines I see messages from starting services while booting, and on some machines I don't see them. Can somebody explain me how this works? I have the idea that I don't see messages on fast machines. Are you sure about that? They should be visible for some time, although that period can be rather short if you boot from an SSD. And can I control this? On some servers I like to see the messages from the services when the machine boots. The behavior of getty(8) has changed (IIRC since util-linux 2.20), it now clears the terminal by default which means that the boot messages disappear as soon as you see the login prompt. To change that, edit /etc/inittab and start getty with the --noclear option on tty1. Cheers, Sven -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/87r3yz69vl@turtle.gmx.de
Re: Messages from starting services while booting
On Thu, 25 Sep 2014 13:04:59 +0200 Paul van der Vlis p...@vandervlis.nl wrote: Hello, I am using Wheezy, and on some machines I see messages from starting services while booting, and on some machines I don't see them. Can somebody explain me how this works? I have the idea that I don't see messages on fast machines. And can I control this? On some servers I like to see the messages from the services when the machine boots. With regards, Paul van der Vlis. Disable lightdm and you'll start seeing the messages. The right way is to put an exit command early in the lightdm config file. The easy way is to rename lightdm to lightdm.unused. Don't actually delete it in case you want to put things back. Be forewarned that after doing that, you'll be logging into tty1, and then running startx to run your gui, and you might need to exec your gui (lxde or whatever) as the last command of !/.xinitrc. HTH, SteveT Steve Litt* http://www.troubleshooters.com/ Troubleshooting Training * Human Performance -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140925113034.6ff19...@mydesq2.domain.cxm
Re: Messages from starting services while booting
op 25-09-14 17:30, Steve Litt schreef: On Thu, 25 Sep 2014 13:04:59 +0200 Paul van der Vlis p...@vandervlis.nl wrote: Hello, I am using Wheezy, and on some machines I see messages from starting services while booting, and on some machines I don't see them. Can somebody explain me how this works? I have the idea that I don't see messages on fast machines. And can I control this? On some servers I like to see the messages from the services when the machine boots. Disable lightdm and you'll start seeing the messages. I don't use Lightdm or any other dm, it's a server without GUI. With regards, Paul van der Vlis. -- Paul van der Vlis Linux systeembeheer, Groningen http://www.vandervlis.nl -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/54243e0a.4090...@vandervlis.nl
Re: Messages from starting services while booting
op 25-09-14 16:41, Sven Joachim schreef: On 2014-09-25 13:04 +0200, Paul van der Vlis wrote: I am using Wheezy, and on some machines I see messages from starting services while booting, and on some machines I don't see them. Can somebody explain me how this works? I have the idea that I don't see messages on fast machines. Are you sure about that? I am sure there are no messages from starting services. They should be visible for some time, although that period can be rather short if you boot from an SSD. It's from harddisks (raid1). But the processor is fast. And can I control this? On some servers I like to see the messages from the services when the machine boots. The behavior of getty(8) has changed (IIRC since util-linux 2.20), it now clears the terminal by default which means that the boot messages disappear as soon as you see the login prompt. To change that, edit /etc/inittab and start getty with the --noclear option on tty1. I've tried: 1:2345:respawn:/sbin/getty --noclear 38400 tty1 And the screen is not cleared. But I see only messages from grub2, then a few messages from the kernel starting with a number like in dmesg, then the welcome message and a login prompt. So no messages from starting services, like SSH. With regards, Paul van der VLis. -- Paul van der Vlis Linux systeembeheer, Groningen http://www.vandervlis.nl -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/5424419b.6060...@vandervlis.nl
Re: Messages from starting services while booting
Am 25.09.2014 um 17:30 schrieb Steve Litt: Disable lightdm and you'll start seeing the messages. The right way is to put an exit command early in the lightdm config file. The easy way That's actually entirely the wrong way to disable a (SysV) init script. Please use invoke-rc.d lightdm disable instead. -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Re: Messages from starting services while booting
On Thu, 25 Sep 2014 18:08:42 +0200 Paul van der Vlis p...@vandervlis.nl wrote: op 25-09-14 17:30, Steve Litt schreef: On Thu, 25 Sep 2014 13:04:59 +0200 Paul van der Vlis p...@vandervlis.nl wrote: Hello, I am using Wheezy, and on some machines I see messages from starting services while booting, and on some machines I don't see them. Can somebody explain me how this works? I have the idea that I don't see messages on fast machines. And can I control this? On some servers I like to see the messages from the services when the machine boots. Disable lightdm and you'll start seeing the messages. I don't use Lightdm or any other dm, it's a server without GUI. With regards, Paul van der Vlis. Then what do you see instead of the bootup messages? I assume you see your system count memory, and perhaps you get a boot menu. What do you see after that? SteveT Steve Litt* http://www.troubleshooters.com/ Troubleshooting Training * Human Performance -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140925132032.5d947...@mydesq2.domain.cxm
Re: Messages from starting services while booting
op 25-09-14 19:20, Steve Litt schreef: On Thu, 25 Sep 2014 18:08:42 +0200 Paul van der Vlis p...@vandervlis.nl wrote: op 25-09-14 17:30, Steve Litt schreef: On Thu, 25 Sep 2014 13:04:59 +0200 Paul van der Vlis p...@vandervlis.nl wrote: Hello, I am using Wheezy, and on some machines I see messages from starting services while booting, and on some machines I don't see them. Can somebody explain me how this works? I have the idea that I don't see messages on fast machines. And can I control this? On some servers I like to see the messages from the services when the machine boots. Disable lightdm and you'll start seeing the messages. I don't use Lightdm or any other dm, it's a server without GUI. With regards, Paul van der Vlis. Then what do you see instead of the bootup messages? I assume you see your system count memory, and perhaps you get a boot menu. What do you see after that? Some messages from initrd (like in dmesg), then a welcome message from Debian, then a login prompt. With regards, Paul van der Vlis. -- Paul van der Vlis Linux systeembeheer, Groningen http://www.vandervlis.nl -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/54245445.6030...@vandervlis.nl
Re: Messages from starting services while booting
On Jo, 25 sep 14, 18:30:53, Michael Biebl wrote: Am 25.09.2014 um 17:30 schrieb Steve Litt: Disable lightdm and you'll start seeing the messages. The right way is to put an exit command early in the lightdm config file. The easy way That's actually entirely the wrong way to disable a (SysV) init script. +1 Please use invoke-rc.d lightdm disable instead. Michael surely meant 'update-rc.d', not 'invoke-rc.d'. Kind regards, Andrei -- http://wiki.debian.org/FAQsFromDebianUser Offtopic discussions among Debian users and developers: http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic http://nuvreauspam.ro/gpg-transition.txt signature.asc Description: Digital signature
Re: Messages from starting services while booting
On Thu 25 Sep 2014 at 23:46:15 +0300, Andrei POPESCU wrote: On Jo, 25 sep 14, 18:30:53, Michael Biebl wrote: Am 25.09.2014 um 17:30 schrieb Steve Litt: Disable lightdm and you'll start seeing the messages. The right way is to put an exit command early in the lightdm config file. The easy way That's actually entirely the wrong way to disable a (SysV) init script. +1 Please use invoke-rc.d lightdm disable instead. Michael surely meant 'update-rc.d', not 'invoke-rc.d'. He most surely did. As a test of knowledge and understanding of what is involved in understanding sysvinit in Debian, you passed with flying colours. Self-appointed experts on init systems might struggle to appreciate the difference in the two commands. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140925210846.gu4...@copernicus.demon.co.uk
Re: Messages from starting services while booting
Am 25.09.2014 um 22:46 schrieb Andrei POPESCU: On Jo, 25 sep 14, 18:30:53, Michael Biebl wrote: Am 25.09.2014 um 17:30 schrieb Steve Litt: Disable lightdm and you'll start seeing the messages. The right way is to put an exit command early in the lightdm config file. The easy way That's actually entirely the wrong way to disable a (SysV) init script. +1 Please use invoke-rc.d lightdm disable instead. Michael surely meant 'update-rc.d', not 'invoke-rc.d'. Indeed, thanks for the correction. -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Re: Booting Debian GNU/kFreeBSD on MacBookPro 8.2
On Sun, 21 Sep 2014 19:02:39 +0300 Lars Noodén lars.noo...@gmail.com wrote: On 09/21/2014 06:54 PM, Chris Bannister wrote: On Sun, Sep 21, 2014 at 03:43:40PM +0300, Lars Noodén wrote: I've installed Debian GNU/kFreeBSD 7.6 (wheezy) from a mini.iso CD image on a MacBookPro 8.2. The installation seemed to go smoothly, including What was url from where you got the mini.iso CD? From the link on the Debian wiki: http.debian.net/debian/dists/wheezy/main/installer-kfreebsd-amd64/current/images/netboot/mini.iso Regards, /Lars I tried again with a more recent installation image. http://d-i.debian.org/daily-images/kfreebsd-amd64/ The one from 2014-09-20 figured out Grub properly. It takes a while to find Grub but other than that it boots fine. Regards, /Lars -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140922164832.13f640e7dd07e268bbf70...@gmail.com
Re: Booting Debian GNU/kFreeBSD on MacBookPro 8.2
On Sun, Sep 21, 2014 at 07:02:39PM +0300, Lars Noodén wrote: On 09/21/2014 06:54 PM, Chris Bannister wrote: On Sun, Sep 21, 2014 at 03:43:40PM +0300, Lars Noodén wrote: I've installed Debian GNU/kFreeBSD 7.6 (wheezy) from a mini.iso CD image on a MacBookPro 8.2. The installation seemed to go smoothly, including What was url from where you got the mini.iso CD? From the link on the Debian wiki: http.debian.net/debian/dists/wheezy/main/installer-kfreebsd-amd64/current/images/netboot/mini.iso Mmmm Ok, maybe the kFreeBSD guys might be able to help. -- If you're not careful, the newspapers will have you hating the people who are being oppressed, and loving the people who are doing the oppressing. --- Malcolm X -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140922152416.GI21153@tal
Booting Debian GNU/kFreeBSD on MacBookPro 8.2
I've installed Debian GNU/kFreeBSD 7.6 (wheezy) from a mini.iso CD image on a MacBookPro 8.2. The installation seemed to go smoothly, including installing Grub, but when it is time to boot, the machine only ever shows a blinking folder with a question mark, indicating no system. The system can be booted from the installation CD via the choice to boot from first hard disk, so that part of the installation worked. What additional step is needed so that the system boots on its own from the internal drive without intervention from the installation CD? Regards, /Lars -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/541ec7fc.9090...@gmail.com
Re: Booting Debian GNU/kFreeBSD on MacBookPro 8.2
On Sun, Sep 21, 2014 at 03:43:40PM +0300, Lars Noodén wrote: I've installed Debian GNU/kFreeBSD 7.6 (wheezy) from a mini.iso CD image on a MacBookPro 8.2. The installation seemed to go smoothly, including What was url from where you got the mini.iso CD? -- If you're not careful, the newspapers will have you hating the people who are being oppressed, and loving the people who are doing the oppressing. --- Malcolm X -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140921155423.GC26772@tal
Re: Booting Debian GNU/kFreeBSD on MacBookPro 8.2
On 09/21/2014 06:54 PM, Chris Bannister wrote: On Sun, Sep 21, 2014 at 03:43:40PM +0300, Lars Noodén wrote: I've installed Debian GNU/kFreeBSD 7.6 (wheezy) from a mini.iso CD image on a MacBookPro 8.2. The installation seemed to go smoothly, including What was url from where you got the mini.iso CD? From the link on the Debian wiki: http.debian.net/debian/dists/wheezy/main/installer-kfreebsd-amd64/current/images/netboot/mini.iso Regards, /Lars -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/541ef69f.7020...@gmail.com
Re: Booting Debian GNU/kFreeBSD on MacBookPro 8.2
On Sunday, September 21, 2014 05:43:40 AM Lars Noodén wrote: I've installed Debian GNU/kFreeBSD 7.6 (wheezy) from a mini.iso CD image on a MacBookPro 8.2. The installation seemed to go smoothly, including installing Grub, but when it is time to boot, the machine only ever shows a blinking folder with a question mark, indicating no system. The system can be booted from the installation CD via the choice to boot from first hard disk, so that part of the installation worked. What additional step is needed so that the system boots on its own from the internal drive without intervention from the installation CD? Regards, /Lars It sounds like the install went okay, but the mac is unsure what device to boot from. Try holding down the left 'option' key during boot and see if you can select your hard disk from the list that appears. Andrew signature.asc Description: This is a digitally signed message part.
Re: Booting Debian GNU/kFreeBSD on MacBookPro 8.2
On 09/21/2014 09:05 PM, Andrew Winnenberg wrote: On Sunday, September 21, 2014 05:43:40 AM Lars Noodén wrote: I've installed Debian GNU/kFreeBSD 7.6 (wheezy) from a mini.iso CD image on a MacBookPro 8.2. The installation seemed to go smoothly, including installing Grub, but when it is time to boot, the machine only ever shows a blinking folder with a question mark, indicating no system. The system can be booted from the installation CD via the choice to boot from first hard disk, so that part of the installation worked. What additional step is needed so that the system boots on its own from the internal drive without intervention from the installation CD? Regards, /Lars It sounds like the install went okay, but the mac is unsure what device to boot from. Try holding down the left 'option' key during boot and see if you can select your hard disk from the list that appears. Andrew That was one of the first things I did try. There might be some problem related to EFI or UEFI and it needing a special /boot partition. But that is a new area for me. Regards, /Lars -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/541f2384.9060...@gmail.com
Re: Debian 7.X : 2TB HD installation successful but not booting
On Wed, Sep 03, 2014 at 10:43:50AM +0500, Muhammad Yousuf Khan wrote: i have a 2TB hard disk and installation went fine no errors. however i can not manage to boot it from hard disk. What happens when you try? Any error messages? Do you just get a blinking cursor? Does the PC explode in a ball of flames each time you try? my partitions are like this. 1. /boot : Boot Flag ON. 1. Swap : Boot Flag Off. 1. / : Boot Flag off. I'm going to assume that this is an MBR partition table and that those partitions are actually 1, 2 and 3 (that is, the first three primary partitions). Did you install grub into the MBR of the drive? The installation should have asked if you wanted that. but the weird part is when i press F10 and select harddrive to boot it amazingly boot. it seems like more of a BIOS issue but the same system is booting fine with a 250GB drive. BIOS can only ever boot from one device. Typically, this is defined in the Boot Order menu, somewhere in the BIOS menu. The normal procedure for a BIOS with several options is to try the various boot devices in the specified order and look for a valid boot loader. So, for example, it'll check the floppy drive and boot from the disk there if there is one. If not, it'll check the CD drive for a disk. Finally it'll look at the hard disks. Now, if it finds a valid boot loader on the first disk it looks at, then it's not going to look at the other disks. The boot loader it looks at is, of course, free to do whatever it likes. So a common thing to do is put GRUB onto one disk, nominate that as the master (i.e. the one that the BIOS jumps to) and have that copy of grub either load operating systems from other disks or to chain-load the bootloader on the other disks. any idea what is going on. Thanks, MYK signature.asc Description: Digital signature
Debian 7.X : 2TB HD installation successful but not booting
i have a 2TB hard disk and installation went fine no errors. however i can not manage to boot it from hard disk. my partitions are like this. 1. /boot : Boot Flag ON. 1. Swap : Boot Flag Off. 1. / : Boot Flag off. but the weird part is when i press F10 and select harddrive to boot it amazingly boot. it seems like more of a BIOS issue but the same system is booting fine with a 250GB drive. any idea what is going on. Thanks, MYK
Re: Debian freezes while booting
fa-ml fa-ml at ariis.it writes: The problem is that more often than not, when I boot debian, after typing the password for the encrypted volume, the boot process hangs (black-but-not-off screen, unresponsive to key presses). I say more often than not because once in, say, 20 boots everything goes smoothly (so I can login in a terminal, start x, etc.). After many attempts, I found a solution. Add idle=halt to kernel booting options. I wish I had explanation for that too, but ref. doc [1] is pretty dry. [1] https://www.kernel.org/doc/Documentation/kernel-parameters.txt -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/loom.20140212t043153-...@post.gmane.org
Debian freezes while booting
Hello Debian users, I recently bought a gluglug X60s laptop and once received I installed Debian on it (wheezy i386). The installation was done using the netinstall CD; I only installed base system plus laptop programs and apt-get install'd other stuff (xorg, alsa, etc.) later on. The problem is that more often than not, when I boot debian, after typing the password for the encrypted volume, the boot process hangs (black-but-not-off screen, unresponsive to key presses). I say more often than not because once in, say, 20 boots everything goes smoothly (so I can login in a terminal, start x, etc.). I documented my actions during boot taking pictures [1] (resized them via command line, I hope they are readable enough). After browsing for solutions, I found that putting 'nomodeset' as a kernel boot option allows me to reach login without any error. Unfortunately, after logging in, I cannot 'startx' (error: no screens found, I attach /var/log/Xorg.0.log). I am puzzled about this and am not sure what to do next to diagnose the problem. Any idea on how to address the matter is welcome! Thanks -F [1] http://ariis.it/share/dump/debian-boot-bug/ [34.899] X.Org X Server 1.12.4 Release Date: 2012-08-27 [34.899] X Protocol Version 11, Revision 0 [34.900] Build Operating System: Linux 3.2.0-4-amd64 i686 Debian [34.900] Current Operating System: Linux x60s 3.2.0-4-686-pae #1 SMP Debian 3.2.54-2 i686 [34.900] Kernel command line: BOOT_IMAGE=/vmlinuz-3.2.0-4-686-pae root=/dev/mapper/x60s-root ro nomodeset [34.900] Build Date: 17 December 2013 08:37:13PM [34.900] xorg-server 2:1.12.4-6+deb7u2 (Julien Cristau jcris...@debian.org) [34.900] Current version of pixman: 0.26.0 [34.900]Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. [34.900] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [34.901] (==) Log file: /var/log/Xorg.0.log, Time: Mon Feb 10 05:26:44 2014 [34.905] (==) Using system config directory /usr/share/X11/xorg.conf.d [34.906] (==) No Layout section. Using the first Screen section. [34.906] (==) No screen section available. Using defaults. [34.907] (**) |--Screen Default Screen Section (0) [34.907] (**) | |--Monitor default monitor [34.910] (==) No monitor specified for screen Default Screen Section. Using a default monitor configuration. [34.910] (==) Automatically adding devices [34.910] (==) Automatically enabling devices [34.919] (WW) The directory /usr/share/fonts/X11/cyrillic does not exist. [34.919]Entry deleted from font path. [34.926] (WW) The directory /var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType does not exist. [34.926]Entry deleted from font path. [34.926] (==) FontPath set to: /usr/share/fonts/X11/misc, /usr/share/fonts/X11/100dpi/:unscaled, /usr/share/fonts/X11/75dpi/:unscaled, /usr/share/fonts/X11/Type1, /usr/share/fonts/X11/100dpi, /usr/share/fonts/X11/75dpi, built-ins [34.926] (==) ModulePath set to /usr/lib/xorg/modules [34.926] (II) The server relies on udev to provide the list of input devices. If no devices become available, reconfigure udev or disable AutoAddDevices. [34.926] (II) Loader magic: 0xb77235a0 [34.927] (II) Module ABI versions: [34.927]X.Org ANSI C Emulation: 0.4 [34.927]X.Org Video Driver: 12.1 [34.927]X.Org XInput driver : 16.0 [34.927]X.Org Server Extension : 6.0 [34.928] (--) PCI:*(0:0:2:0) 8086:27a2:17aa:201a rev 3, Mem @ 0xe430/524288, 0xd000/268435456, 0xe440/262144, I/O @ 0x50a0/8 [34.928] (--) PCI: (0:0:2:1) 8086:27a6:17aa:201a rev 3, Mem @ 0xe438/524288 [34.928] (II) Open ACPI successful (/var/run/acpid.socket) [34.928] (II) LoadModule: extmod [34.930] (II) Loading /usr/lib/xorg/modules/extensions/libextmod.so [34.934] (II) Module extmod: vendor=X.Org Foundation [34.934]compiled for 1.12.4, module version = 1.0.0 [34.934]Module class: X.Org Server Extension [34.934]ABI class: X.Org Server Extension, version 6.0 [34.934] (II) Loading extension SELinux [34.934] (II) Loading extension MIT-SCREEN-SAVER [34.934] (II) Loading extension XFree86-VidModeExtension [34.934] (II) Loading extension XFree86-DGA [34.934] (II) Loading extension DPMS [34.934] (II) Loading extension XVideo [34.934] (II) Loading extension XVideo-MotionCompensation [34.934] (II) Loading extension X-Resource [34.934] (II) LoadModule: dbe [34.935] (II) Loading /usr/lib/xorg/modules/extensions/libdbe.so [34.936] (II) Module dbe: vendor=X.Org Foundation [34.936]compiled for 1.12.4, module version = 1.0.0 [34.936]Module
Re: zenbook not booting after failed suspend/resume (debian/testing)
Dear all, Zenbook bootable again. The fix was actually really easy: apt-get install --reinstall grub-efi-amd64 The question remains what led to this error, but I guess I will never find out ;) Regards! -- j.hofmüller mur.sat -- a space art projecthttp://sat.mur.at/ signature.asc Description: OpenPGP digital signature
Re: zenbook not booting after failed suspend/resume (debian/testing)
Jogi Hofmüller, 28.01.2014: Dear all, Zenbook bootable again. The fix was actually really easy: apt-get install --reinstall grub-efi-amd64 If the machine wasn't booting, how did you get to a state where you could run that? Did you use a rescue usb/cd? -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20140128140745.ga32...@cs.utexas.edu
Re: zenbook not booting after failed suspend/resume (debian/testing)
On Tue, 2014-01-28 at 08:07 -0600, Selim T. Erdogan wrote: Jogi Hofmüller, 28.01.2014: Dear all, Zenbook bootable again. The fix was actually really easy: apt-get install --reinstall grub-efi-amd64 If the machine wasn't booting, how did you get to a state where you could run that? Did you use a rescue usb/cd? Or the OP has got a multi-boot as I've got. [rocketmouse@archlinux ~]$ sudo systemd-nspawn -D /mnt/debi386/ Spawning namespace container on /mnt/debi386 (console is /dev/pts/1). Init process in the container running as PID 3351. root@debi386:~# apt-get update [snip] Fetched 884 kB in 38s (23.2 kB/s) Reading package lists... Done root@debi386:~# apt-get install mc Reading package lists... Done Building dependency tree Reading state information... Done The following extra packages will be installed: mc-data Suggested packages: arj dbview odt2txt gv catdvi djvulibre-bin python-boto python-tz The following NEW packages will be installed: mc mc-data 0 upgraded, 2 newly installed, 0 to remove and 11 not upgraded. [snip] Setting up mc-data (3:4.8.3-10) ... Setting up mc (3:4.8.3-10) ... update-alternatives: using /usr/bin/mcview to provide /usr/bin/view (view) in auto mode Processing triggers for menu ... root@debi386:~# :) Regards, Ralf -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1390919339.686.43.camel@archlinux
Re: zenbook not booting after failed suspend/resume (debian/testing)
On Tue, 2014-01-28 at 15:28 +0100, Ralf Mardorf wrote: On Tue, 2014-01-28 at 08:07 -0600, Selim T. Erdogan wrote: Jogi Hofmüller, 28.01.2014: Dear all, Zenbook bootable again. The fix was actually really easy: apt-get install --reinstall grub-efi-amd64 If the machine wasn't booting, how did you get to a state where you could run that? Oops, than a multi-boot wouldn't work :D. Did you use a rescue usb/cd? Seems to be the only solution. And than to chroot or systemd-nspawn. Or the OP has got a multi-boot as I've got. [rocketmouse@archlinux ~]$ sudo systemd-nspawn -D /mnt/debi386/ Spawning namespace container on /mnt/debi386 (console is /dev/pts/1). Init process in the container running as PID 3351. root@debi386:~# apt-get update [snip] Fetched 884 kB in 38s (23.2 kB/s) Reading package lists... Done root@debi386:~# apt-get install mc Reading package lists... Done Building dependency tree Reading state information... Done The following extra packages will be installed: mc-data Suggested packages: arj dbview odt2txt gv catdvi djvulibre-bin python-boto python-tz The following NEW packages will be installed: mc mc-data 0 upgraded, 2 newly installed, 0 to remove and 11 not upgraded. [snip] Setting up mc-data (3:4.8.3-10) ... Setting up mc (3:4.8.3-10) ... update-alternatives: using /usr/bin/mcview to provide /usr/bin/view (view) in auto mode Processing triggers for menu ... root@debi386:~# :) Regards, Ralf -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1390919465.686.45.camel@archlinux
Re: zenbook not booting after failed suspend/resume (debian/testing)
Am 2014-01-28 15:07, schrieb Selim T. Erdogan: apt-get install --reinstall grub-efi-amd64 If the machine wasn't booting, how did you get to a state where you could run that? Did you use a rescue usb/cd? Booted the machine using the rescue feature from a debian netboot on usb stick. Cheers! -- j.hofmüller mur.sat -- a space art projecthttp://sat.mur.at/ signature.asc Description: OpenPGP digital signature
zenbook not booting after failed suspend/resume (debian/testing)
Dear all, First of all let me state that I believe that what I am experiencing is not necessarily a Debian problem. I direct my questions to this list because I expect the most relevant answers here and I have been using Debian now for more than 10 years. I have been using this ASUS Zenbook (UX32V) now for almost a year and have been running Debian testing on it since with great success. That is, until last Saturday. Then I did an upgrade to the most recent testing packages. Since kernel 3.12. suspend/resume did not work properly (the machine froze upon resume) I rebooted right after the upgrade and tested suspend/resume. Still no luck on resume, machine is frozen. So I hit the power button. Instead of booting, the machine goes straight into the BIOS setup utility. There, no EFI boot option is available anymore. What I did since then is: * configure a boot option pointing to fs0:\EFI\debian\grubx64.efi: machine still does not boot * upgrade BIOS to the latest version: no changes * reboot the system using the latest testing netboot image to ensure that file system and EFI partition are OK: everything looks fine * check the contents of pstore following [1]: empty * install Shell.efi [2] and poke around with it: great experience ;) * tested setup using efibootmgr None of the things I tried led me to a solution that would boot the machine again. So I am asking for help/hints/clues that would enable me to use the zenbook again. As I stated at the beginning, this does not necessarily have to be the cause of a bug in Debian and/or Linux. Still, I would like to explore every possible way and try to fix it myself (with help that is). [1] http://mjg59.dreamwidth.org/23554.html [2] https://svn.code.sf.net/p/edk2/code/trunk/edk2/ShellBinPkg/UefiShell/X64/Shell.efi Regards! -- j.hofmüllerhttp://users.mur.at/thesix/ signature.asc Description: OpenPGP digital signature
sudo umount hangs when booting with systemd
I have a directory /media/USB01 Nothing is mounted on this directory. When I run the following, after booting up with systemd, the command hangs: sudo umount /media/USB01 A Ctrl-C breaks the hang. $ cat /etc/fstab # /etc/fstab: static file system information. # # Use 'blkid' to print the universally unique identifier for a # device; this may be used with UUID= as a more robust way to name devices # that works even if disks are added and removed. See fstab(5). # # file system mount point type options dump pass # / was on /dev/sda5 during installation UUID=e73a71d3-a391-40bc-9d45-55fa72f245c1 / ext4 errors=remount-ro,nodiratime,noatime,user_xattr,journal_async_commit,min_batch_time=1000 0 1 # /boot was on /dev/sda3 during installation UUID=75e1d222-c9df-4d10-93de-9da4cf005158 /boot ext2 defaults 0 2 # swap was on /dev/sda6 during installation UUID=25d4ff20-1c78-4e1d-bd2a-2a0060e85f9a none swap sw # The following is done by /etc/default/rcS RAMTMP=yes option #tmpfs /tmp tmpfs defaults,nodiratime,noatime,mode=1777 #/zenlocal/zen/justa /home/justa none bind,comment=systemd.automount /zenlocal/zen/justa /home/justa none bind /zenlocal/zen/ /home/justa/zen none bind UUID=9E18AD0C18ACE50D /media/c ntfs-3g defaults,uid=1000,gid=1000,noauto UUID=3EE6330B1FADCDD2 /media/SNAP01 ntfs-3g defaults,uid=1000,gid=1000,posixovl,nodiratime,noatime,comment=systemd.automount UUID=6fce0b79-b658-4072-af58-376a5630c190 /media/z55 ext3 user,nodiratime,noatime,comment=systemd.automount /dev/sr0/media/cdrom0 udf,iso9660 user,noauto /dev/sdb1 /media/usb0 auto rw,user,noauto,nodiratime,noatime 0 0 /dev/sdb2 /media/usb1 auto rw,user,noauto,nodiratime,noatime 0 0 /dev/sdb3 /media/usb2 auto rw,user,noauto,nodiratime,noatime 0 0 /dev/sdb4 /media/usb3 auto rw,user,noauto,nodiratime,noatime 0 0 /dev/sdb5 /media/usb4 auto rw,user,noauto,nodiratime,noatime 0 0 Perhaps these two lines above are causing a problem for systemd's auto- stuff?: /zenlocal/zen/justa /home/justa none bind /zenlocal/zen/ /home/justa/zen none bind Also, ls /media/ works, but ls -l /media/ similarly hangs! Again, Ctrl-C aborts the hung command. Any ideas? Zenaan -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/caosgnst4jij-bbmu+d3fo0wbt5_9hctfdgooyesjcuatfcp...@mail.gmail.com
Re: sudo umount hangs when booting with systemd
On 12/15/13, Zenaan Harkness z...@freedbms.net wrote: /etc/fstab : /zenlocal/zen/justa /home/justa none bind /zenlocal/zen/ /home/justa/zen none bind Removing these solved the problem. I have unwound my two bind mount mounts (with the sequence as above - not recursive, but the latter bind mounted inside the former bind mount), and systemd no longer borks in its hanging way. I now just use a single bind mount. I had things set up the way I did, to assist in the days when I had multiple debian and ubuntu installs, and would choose here and there between them. Another small issue that arose when I uncommented the first of the above two lines, was that ls -lF / would hand, similarly to the mount hang. That problem's gone too now. SOLVED Zenaan -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/caosgnsqgriw4mroyeaht1eaonjqszuqomsuqtbac-smzhqt...@mail.gmail.com
Re: sudo umount hangs when booting with systemd
On 12/15/13, Zenaan Harkness z...@freedbms.net wrote: On 12/15/13, Zenaan Harkness z...@freedbms.net wrote: /etc/fstab : /zenlocal/zen/justa /home/justa none bind /zenlocal/zen/ /home/justa/zen none bind Removing these solved the problem. Another small issue that arose when I uncommented the first of the above two lines, was that ls -lF / would hand, similarly to the mount hang. That problem's gone too now. would hang that should be. Notably, ls -l / would not hang, only ls -lF / . So it was the -F or --classify option to ls which stumbled upon systemd's mount internals, it seems. Zenaan -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CAOsGNSTLS9TKJ=zfisbscebxxntpra1cm0gqtqvsshwg8wo...@mail.gmail.com
startx - X : no permissions to start x session (or some such) when booting with systemd
After my recent sid upgrade, when I test boot with systemd, startx ends with an error saying something (I think it is X) is lacking permissions. Any systemd users knowledgeable on how to user startx manually after booting with systemd? I tested systemd a few times after my upgrade, and have reverted back to sysvinit due to lack of graphical desktop. By the way, does anyone know if there is a xinerama equivalent for the Linux console? :) TIA Zenaan -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CAOsGNSTh4Uid=ZxdrL0mps3sZ8G6GFEYWkBKgX9Q6A8KHG=s...@mail.gmail.com
Re: startx - X : no permissions to start x session (or some such) when booting with systemd
On 12/10/13, Zenaan Harkness z...@freedbms.net wrote: After my recent sid upgrade, when I test boot with systemd, startx ends with an error saying something (I think it is X) is lacking permissions. Just rebooted (to test other changes), and my laptop is now auto-booting with systemd (looks like some grub customization has been lost), but on the other hand, startx now works! Happy me :) No idea what changed - I certainly have not modified any permissions today... Zenaan -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/caosgnsqvh0tgsmtq88bjo2d2+jzung11yaynnucqgktnkjz...@mail.gmail.com
Re: startx - X : no permissions to start x session (or some such) when booting with systemd
Am Dienstag, 10. Dezember 2013, 19:24:14 schrieb Zenaan Harkness: On 12/10/13, Zenaan Harkness z...@freedbms.net wrote: After my recent sid upgrade, when I test boot with systemd, startx ends with an error saying something (I think it is X) is lacking permissions. Just rebooted (to test other changes), and my laptop is now auto-booting with systemd (looks like some grub customization has been lost), but on the other hand, startx now works! Happy me :) No idea what changed - I certainly have not modified any permissions today... Zenaan Had thisu problem some time ago when starting LXDE. After this, KDE would not start any more. The reason was, that .ICEauthority was set to owner root by LXDE. This should be fixed already. Just an idea.. Happy Hacking! Hans -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1964099.sRWlc9iNQm@protheus2
Re: Booting from USB stick - SOLVED
- Original Message - From: Andrei POPESCU To: Cc: Sent:Tue, 26 Nov 2013 13:04:24 +0200 Subject:Re: Booting from USB stick On Lu, 25 nov 13, 23:40:44, erosenberg@hygeiabiomedicalcom [1] wrote: Dear List - There is a problem with my Lenovo 8189-58U. It will not boot from the CDROM. According to Google, it is a problem with the older BIOS. I need to flash the BIOS, but I cannot boot from a USB stick.so [2]... How do I use GRUB to boot from a USB stick? Any other suggestions? If the USB is available to Grub you should be able to boot from it like with any other storage device. If this is a Debian machine insert the USB stick and run 'update-grub' as root. If everything works fine you should have a new entry in the Grub menu with the USB stick OS. If you can't boot it please try to reproduce any error messages as faithfully as possible and copy-paste the relevant part from /boot/grub/grub.cfg [3], somewhere between the ### BEGIN /etc/grub.d/30_os-prober ### ### END /etc/grub.d/30_os-prober ### markers. If in doubt just attach the whole file. Kind regards, Andrei -- http://wiki.debian.org/FAQsFromDebianUser [4] Offtopic discussions among Debian users and developers: http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic [5] http://nuvreauspam.ro/gpg-transition.txt [6] THANKS to ALL!! Updated grub and booted from CD. Clean Boot. See my eml re: No Video for more details. Links: -- [1] mailto:erosenb...@hygeiabiomedical.com [2] http://stick.so [3] http://grub.cfg [4] http://wiki.debian.org/FAQsFromDebianUser [5] http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic [6] http://nuvreauspam.ro/gpg-transition.txt
Re: Booting from USB stick
On Lu, 25 nov 13, 23:40:44, erosenb...@hygeiabiomedical.com wrote: Dear List - There is a problem with my Lenovo 8189-58U. It will not boot from the CDROM. According to Google, it is a problem with the older BIOS. I need to flash the BIOS, but I cannot boot from a USB stick.so... How do I use GRUB to boot from a USB stick? Any other suggestions? If the USB is available to Grub you should be able to boot from it like with any other storage device. If this is a Debian machine insert the USB stick and run 'update-grub' as root. If everything works fine you should have a new entry in the Grub menu with the USB stick OS. If you can't boot it please try to reproduce any error messages as faithfully as possible and copy-paste the relevant part from /boot/grub/grub.cfg, somewhere between the ### BEGIN /etc/grub.d/30_os-prober ### ### END /etc/grub.d/30_os-prober ### markers. If in doubt just attach the whole file. Kind regards, Andrei -- http://wiki.debian.org/FAQsFromDebianUser Offtopic discussions among Debian users and developers: http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic http://nuvreauspam.ro/gpg-transition.txt signature.asc Description: Digital signature
Re: Booting from USB stick
On Mon, 25 Nov 2013, erosenb...@hygeiabiomedical.com wrote: Dear List - There is a problem with my Lenovo 8189-58U. It will not boot from the CDROM. According to Google, it is a problem with the older BIOS. I need to flash the BIOS, but I cannot boot from a USB stick.so... How do I use GRUB to boot from a USB stick? Any other suggestions? TIA First, check the BIOS boot order, and that USB is listed. And that it and the CDROM are listed before the hrd drive, etc. B -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20131126083554.66887...@debian7.boseck208.net
Booting from USB stick
Dear List - There is a problem with my Lenovo 8189-58U. It will not boot from the CDROM. According to Google, it is a problem with the older BIOS. I need to flash the BIOS, but I cannot boot from a USB stick.so... How do I use GRUB to boot from a USB stick? Any other suggestions? TIA Ethan
Booting netinst via PXE
Hello *, I've followed this guide [1] and now I have my PXE server up and running, however that guide doesn't tell how to configure tftp-hpa menus for Debian, let alone the netinst version. This other guide [2] tell something about Lenny, but I couldn't find the debian-installer folder in the wheezy netinst ISO image. I've tried adapting the instructions in both guides with a few guesses: now Debian boots but after asking the language and keyboard tries to mount a CDROM (which obviously does not exist) instead of going networked, and the show stops. The PXE menu for Debian is as follows: LABEL 6 MENU LABEL Debian 7.2.0 (64-bit) KERNEL debian/7/amd64/vmlinuz APPEND boot=install netboot=nfs \ nfsroot=10.151.44.254:/cache/debian/7/amd64/loop \ initrd=debian/7/amd64/initrd.gz \ method=nfs:10.151.44.254:/cache/debian/7/amd64/loop lang=it keymap=it ip=dhcp\ noipv6 ramdisk_size=1 TEXT HELP Installa Debian 7.2.0 64-bit ENDTEXT Obviously the server has address 10.151.44.254 and is sharing /, /cache and everything below those via NFS. Please note that the sheer amount of items after APPEND is the result of many trials, but I bet they aren't all required. Please note also that a similar configuration does work for ubuntu netinst (except in that case I have boot=casper option instead of boot=install). What am I doing wrong? [1]. https://help.ubuntu.com/community/PXEInstallMultiDistro [2]. http://www.howtoforge.com/setting-up-a-pxe-install-server-for-multiple-linux-distributions-on-debian-lenny-p2 -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/2109417.Br4mLknz2c@fx
Re: Booting netinst via PXE [more or less SOLVED]
In data mercoledì 6 novembre 2013 16:09:42, Lucio Crusca ha scritto: What am I doing wrong? I still don't know what, but switching to the minimal ISO (mini.iso) instead of the one with the debian installer bundled did the trick. That suggests me that the same problem would show up with Ubuntu or other distros, except that my PXE server was already using mini.iso for Ubuntu... -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1598802.PE2g1BRyXH@fx
Re: Booting netinst via PXE
Lucio Crusca wrote: I've followed this guide [1] and now I have my PXE server up and running, however that guide doesn't tell how to configure tftp-hpa menus for Debian, let alone the netinst version. [1]. https://help.ubuntu.com/community/PXEInstallMultiDistro Note that the guide above does things slightly different than the way Debian usually suggests to set up a PXE install of Debian. Note that I said different not wrong. There are many good valid ways to do this task. But I think that difference may be at the source of the confusion. APPEND boot=install netboot=nfs \ nfsroot=10.151.44.254:/cache/debian/7/amd64/loop \ initrd=debian/7/amd64/initrd.gz \ method=nfs:10.151.44.254:/cache/debian/7/amd64/loop lang=it keymap=it ip=dhcp\ noipv6 ramdisk_size=1 The above guide sets up an NFS mount to the installation image. Basically the machine boots as an NFS disk client. For Fedora and OpenSUSE it mounts the installation media that way. Instead of booting a local cdrom it is booting a remote nfs mounted cdrom image. And since those were netinst images the installation proceeds from there downloading from the network. I think. I didn't actually set it up to try it. But definitely it sets up an NFS client mount. The Ubuntu installation in the above guide is yet again different. It sets up the NFS client mount again. But it uses a live cd image for the system. The live cd has support for installing Debian and that is how they are going about it. Boot what is effectively an NFS diskless client and then use the running live cd system's launch point for installing Debian. This other guide [2] tell something about Lenny, but I couldn't find the debian-installer folder in the wheezy netinst ISO image. [2]. http://www.howtoforge.com/setting-up-a-pxe-install-server-for-multiple-linux-distributions-on-debian-lenny-p2 That article follows the more traditional Debian approach to network installation. It is older and written for Lenny 5 and so specific version numbers and strings have changed but the concepts are still the same and valid. In that article there is no NFS used anywhere. I've tried adapting the instructions in both guides with a few guesses: Since those two guides use different strategies to accomplish the task I think that is the source of the issue. It is hard to combine the techniques because they are doing things in such completely different ways. now Debian boots but after asking the language and keyboard tries to mount a CDROM (which obviously does not exist) instead of going networked, and the show stops. Yes. You have mixed strategies. The installation is part one way and part another way. After spending as much time on this as I am sure that you have spent already I think you will hate me for suggesting this. I think you should abandon the nfs diskless client mount strategy. At least initially. It is very useful to have a bootable nfs diskless client. I definitely have a simple nfs diskless client environment and it is very useful. It is a good building block for other things such as FAI which uses it too. But the debian-install has built in support for network installation and doesn't need it. It is very much simpler to set up. You will still use the same tftp server and dhcp server that you already have set up now. The official guide is here: http://www.debian.org/releases/stable/i386/ch04s05 This uses the redirector to automatically pick a close mirror to you. Use it to download the netboot.tar.gz file for your architecture. It is architecture specific. You may want to rename it to something with amd64 in the name so that you can also set up an i386 flavor too. wget http://http.debian.net/debian/dists/wheezy/main/installer-amd64/current/images/netboot/netboot.tar.gz Unpack that into the tftp directory. This is the instructions from the second howto reference you were following. Wherever you have set up your tftp files that is the directory to unpack the above netboot.tar.gz file. I have mine at /srv/tftp (using this in /etc/default/tftpd-hpa file: TFTP_DIRECTORY=/srv/tftp) and so I end up with files like this partial list: ... /srv/tftp/pxeboot/debian-installer/amd64/boot-screens/menu.c32 /srv/tftp/pxeboot/debian-installer/amd64/initrd.gz /srv/tftp/pxeboot/debian-installer/amd64/linux /srv/tftp/pxeboot/debian-installer/amd64/pxelinux.0 ... Unpack the netboot.tar.gz file so that in your environment the files are available over tftp. This could be at /var if you set yours up that way. That part does not matter. I like /srv for such things rather than /var but it is arbitrary. however that guide doesn't tell how to configure tftp-hpa menus for Debian, let alone the netinst version. Then for the menu system the documentation is basically all in the syslinux and pxelinux documentation. http://www.syslinux.org/wiki/index.php/PXELINUX I am using various menus that I like using. I have a sub
Re: booting from raid1 fails after upgrading from kernel-3,2 to 3,10-3 amd64
e.waelde wrote:
Hello,
my main workstation runs its root-filesystem on lvm
on crypt_luks on raid1 (software raid). Everything
works flawless with kernel-image-3.2.0-4-amd64
However, all later kernels that I tried fail to boot,
e.g. kernel-image-3.10-3-amd64
+ grub2 starts the kernel
+ the kernel starts quering all hw.
It somehow fails to assemble the raid, it seems. At least
I do not see any raid related messages (even after adding verbose
debug to the kernel argument list.
I inspected the contents of the initial ramdisks (3.2 and 3.10) and did
not find anything sufficiently different in conf, etc, scripts.
Can anyone confirm this setup is working on amd64 with kernel 3.10 say?
Any pointers, on how to better debug this? I once managed to get a shell
in the initramfs stage. I could load raid1, assemble the raid manually,
luksOpen the crypted partition, start lvm ... but the I did something
which locked the system (unfortunately I cannot remember, how I got
there). Unfortunately all further attempts to drop into a shell in
initramfs have failed on me.
FWIW: I was able to reproduce this problem by installing wheezy on two
empty disks, then upgrade to unstable and trying to boot the newer kernel.
So I suspect I missed something during the upgrade ...
cpu: AMD Phenom(tm) 9550 Quad-Core Processor
disks: connected through SATA
OS: Debian unstable
Any ideas on how to proceed?
Erich
Hi no one answered for a while so I will try to help
I had similar issues but lets get a common ground
I assume you have a plain boot partition and encrypted lvm on raid where
your other partitions reside. This would be the recommended setup.
So after installing a new kernel (and initramfs file) there are few cases
where it can go wrong.
1. the initramfs is not recreated or not recreated properly.
- check for this your /etc/initramfs-tools config files
- make sure the modules (md etc) are included in the initramfs
(In my setup the raid modules are compiled in the kernel)
/etc/initramfs-tools/modules
# List of modules that you want to include in your initramfs.
#
# Syntax: module_name [args ...]
#
# You must run update-initramfs(8) to effect this change.
#
# Examples:
#
# raid1
# sd_mod
dm-mod
loop
- boot with a working kernel and recreate the initramfs file for the 3.10
kernel
2. It can fail because of switching from /dev/sd* to UID
- check here the grub.cfg or menu.lst files in /boot/grub
3. I was getting frequently
root(hd0,msdos1)
- changed to (hd0,1) or whatever value matches your disk drive and
partition solves
For fixing issues with initramfs change the kernel command line in grub by
pressing 'e' to execute /bin/sh instead of init and debug
linux /vmlinuz-3.10.9eko2 root=UUID=d48838a6-4c46-452a--1fa624eb1c6e
ro init=/bin/sh
you usually will load md-mod friends, activate the lvm and mount the root
partition. You would then need to init the system
mount -t ext3 -o ro /dev/mapper/root /new
cd /new
exec usr/sbin/chroot . /bin/sh - EOF dev/console 21
exec /sbin/init ${CMDLINE}
EOF
If you fail better press CTRL+ALT+DEL instead of exit
I hope this helps
I also have this problem I am running testing with a raid1 root fs (no crypt
or lvm). If I do a system upgrade then kernel 3.10-2-amd64 fails to boot
completely with a message that it can't find the root file system. In the
busybox shell the raid devices don't appear to be created.
If I do a dpkg-reconfigure linux-image-3.10-2-amd64 after the failure (and
booting into the still working 3.2.0-4-amd64 kernel) it will boot successfully
into 3.10 until I do another upgrade. I have told grub not to use uuids and
still no go. I just assumed that a fix would filter through eventually so I
just muddle through by using the dpkg-reconfigure command. I am actually in
3.10 now.
...Bob
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/523f08f9.2080...@gmail.com
SOLVED: booting from raid1 fails after upgrading from kernel-3,2 to 3,10-3 amd64
For the records, On 09/13/2013 10:07 PM, e.waelde wrote: Hello, my main workstation runs its root-filesystem on lvm on crypt_luks on raid1 (software raid). Everything works flawless with kernel-image-3.2.0-4-amd64 However, all later kernels that I tried fail to boot, e.g. kernel-image-3.10-3-amd64 + grub2 starts the kernel + the kernel starts quering all hw. It somehow fails to assemble the raid, it seems. At least I do not see any raid related messages (even after adding verbose debug to the kernel argument list. I inspected the contents of the initial ramdisks (3.2 and 3.10) and did not find anything sufficiently different in conf, etc, scripts. Can anyone confirm this setup is working on amd64 with kernel 3.10 say? Any pointers, on how to better debug this? I once managed to get a shell in the initramfs stage. I could load raid1, assemble the raid manually, luksOpen the crypted partition, start lvm ... but the I did something which locked the system (unfortunately I cannot remember, how I got there). Unfortunately all further attempts to drop into a shell in initramfs have failed on me. FWIW: I was able to reproduce this problem by installing wheezy on two empty disks, then upgrade to unstable and trying to boot the newer kernel. So I suspect I missed something during the upgrade ... cpu: AMD Phenom(tm) 9550 Quad-Core Processor disks: connected through SATA OS: Debian unstable Any ideas on how to proceed? I got a hint off-list to add rootdelay=5 to the kernel command line in grub. This did help! Thanks, Erich -- open-pgp key-id: D7551350 signature.asc Description: OpenPGP digital signature
Re: booting from raid1 fails after upgrading from kernel-3,2 to 3,10-3 amd64
e.waelde wrote:
Hello,
my main workstation runs its root-filesystem on lvm
on crypt_luks on raid1 (software raid). Everything
works flawless with kernel-image-3.2.0-4-amd64
However, all later kernels that I tried fail to boot,
e.g. kernel-image-3.10-3-amd64
+ grub2 starts the kernel
+ the kernel starts quering all hw.
It somehow fails to assemble the raid, it seems. At least
I do not see any raid related messages (even after adding verbose
debug to the kernel argument list.
I inspected the contents of the initial ramdisks (3.2 and 3.10) and did
not find anything sufficiently different in conf, etc, scripts.
Can anyone confirm this setup is working on amd64 with kernel 3.10 say?
Any pointers, on how to better debug this? I once managed to get a shell
in the initramfs stage. I could load raid1, assemble the raid manually,
luksOpen the crypted partition, start lvm ... but the I did something
which locked the system (unfortunately I cannot remember, how I got
there). Unfortunately all further attempts to drop into a shell in
initramfs have failed on me.
FWIW: I was able to reproduce this problem by installing wheezy on two
empty disks, then upgrade to unstable and trying to boot the newer kernel.
So I suspect I missed something during the upgrade ...
cpu: AMD Phenom(tm) 9550 Quad-Core Processor
disks: connected through SATA
OS: Debian unstable
Any ideas on how to proceed?
Erich
Hi no one answered for a while so I will try to help
I had similar issues but lets get a common ground
I assume you have a plain boot partition and encrypted lvm on raid where
your other partitions reside. This would be the recommended setup.
So after installing a new kernel (and initramfs file) there are few cases
where it can go wrong.
1. the initramfs is not recreated or not recreated properly.
- check for this your /etc/initramfs-tools config files
- make sure the modules (md etc) are included in the initramfs
(In my setup the raid modules are compiled in the kernel)
/etc/initramfs-tools/modules
# List of modules that you want to include in your initramfs.
#
# Syntax: module_name [args ...]
#
# You must run update-initramfs(8) to effect this change.
#
# Examples:
#
# raid1
# sd_mod
dm-mod
loop
- boot with a working kernel and recreate the initramfs file for the 3.10
kernel
2. It can fail because of switching from /dev/sd* to UID
- check here the grub.cfg or menu.lst files in /boot/grub
3. I was getting frequently
root(hd0,msdos1)
- changed to (hd0,1) or whatever value matches your disk drive and
partition solves
For fixing issues with initramfs change the kernel command line in grub by
pressing 'e' to execute /bin/sh instead of init and debug
linux /vmlinuz-3.10.9eko2 root=UUID=d48838a6-4c46-452a--1fa624eb1c6e
ro init=/bin/sh
you usually will load md-mod friends, activate the lvm and mount the root
partition. You would then need to init the system
mount -t ext3 -o ro /dev/mapper/root /new
cd /new
exec usr/sbin/chroot . /bin/sh - EOF dev/console 21
exec /sbin/init ${CMDLINE}
EOF
If you fail better press CTRL+ALT+DEL instead of exit
I hope this helps
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/l1l6rr$9g4$1...@ger.gmane.org
booting from raid1 fails after upgrading from kernel-3,2 to 3,10-3 amd64
Hello, my main workstation runs its root-filesystem on lvm on crypt_luks on raid1 (software raid). Everything works flawless with kernel-image-3.2.0-4-amd64 However, all later kernels that I tried fail to boot, e.g. kernel-image-3.10-3-amd64 + grub2 starts the kernel + the kernel starts quering all hw. It somehow fails to assemble the raid, it seems. At least I do not see any raid related messages (even after adding verbose debug to the kernel argument list. I inspected the contents of the initial ramdisks (3.2 and 3.10) and did not find anything sufficiently different in conf, etc, scripts. Can anyone confirm this setup is working on amd64 with kernel 3.10 say? Any pointers, on how to better debug this? I once managed to get a shell in the initramfs stage. I could load raid1, assemble the raid manually, luksOpen the crypted partition, start lvm ... but the I did something which locked the system (unfortunately I cannot remember, how I got there). Unfortunately all further attempts to drop into a shell in initramfs have failed on me. FWIW: I was able to reproduce this problem by installing wheezy on two empty disks, then upgrade to unstable and trying to boot the newer kernel. So I suspect I missed something during the upgrade ... cpu: AMD Phenom(tm) 9550 Quad-Core Processor disks: connected through SATA OS: Debian unstable Any ideas on how to proceed? Erich -- open-pgp key-id: D7551350 -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/5233706c.10...@nassur.net
Re: Installing and booting Debian from large hard drives in a RAID without GPT
Hi Darac, Am 06.09.2013 um 14:45 schrieb Darac Marjal mailingl...@darac.org.uk: If you're getting an error saying root couldn't be mounted then I'm assuming that: - BIOS has found GRUB - GRUB has found the kernel - the kernel has booted BUT - the kernel couldn't find the rootfs, so therefore couldn't start init If that's the case, try adding rootdelay=30 to your kernel command line (the best way is to append it to GRUB_CMDLINE_LINUX in /etc/default/grub and re-run update-grub, but you can temporarily add it at grub's command line editor). Spot on, works fine for me now! Entered just that on the GRUB command line to see if that would make a difference, and there it is :-) Maybe it would be a great idea if the Debian installer did this automatically when RAID and / or LVM boot partitions are being configured during installation? Many thanks! Robin -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/d60c3ec4-eea7-4a8d-a365-7bbd7370a...@robin-kipp.net
Re: Installing and booting Debian from large hard drives in a RAID without GPT
Hello Shane, Am 06.09.2013 um 15:49 schrieb Shane Johnson s...@rasmussenequipment.com: I have had problems with the initrd not having the LVM modules loaded in it. I had to make sure LVM was installed then run: update-initramfs -u -k all then : update-grub to get it to play nice with the system. Other than that I would just make sure your /etc/fstab file is correct. Thanks for your advice! I've had this kind of issue once when installing a system using Debootstrap, so I can see how this can be an issue. However, in my case it seems like the rootdelay=30 completely solved the issue :-). Robin -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/3ebaa6ba-2561-41a6-88cb-1c26de807...@robin-kipp.net
Installing and booting Debian from large hard drives in a RAID without GPT
Hi list, I just purchased an HP ProLiant Micro Server G2020T. As for the hard drives, I installed 4 3TB Western Digital HDs. So far so good, but volumes with a capacity greater than 2TB require a GPT partition table. Unfortunately, the server does not support UEFI, and thus can't boot from GPT partitions natively. So, when I ran the Debian installer, I used the following partitioning scheme on all drives since I wanted to combine them in a software RAID: 1MB BIOS Boot Partition (BBP) for GRUB 512MB dedicated /boot partition partition with all the remaining disk space. I then proceeded to setup software RAID: no RAID on the 1MB BIOS boot partition (not sure if this is correct) RAID1 for the 512MB /boot partition including all the HDs. RAID5 for the large partition that remained for file storage. I then set up the /boot partition (/dev/md0) to contain an EXT3 file system and also configured the mount point to be / boot. For the large partition, I setup LVM and created logical volumes for the root and SWAP partition. I also configured those partitions accordingly so the installer would know how to use them. Once I finished, the installation went through without any problems. After the system was installed, I used the 'Install the GRUB boot loader' option to install GRUB on all HDS (/dev/sda through /dev/sdd), which worked just fine. However, when I rebooted the system I got an error message saying the root file system could not be mounted. I suspected the LVM to cause issues, so I re-installed everything but this time without LVM. Unfortunately, the same issue persists… Has anyone here ever been in a similar situation and could suggest a fix? I have a feeling I may be missing something important, but just can't find the right path to take… Thanks a lot for any help / ideas! Robin -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/893c7264-bc42-4153-941a-16a0357a1...@robin-kipp.net
Re: Installing and booting Debian from large hard drives in a RAID without GPT
On Fri, Sep 06, 2013 at 02:29:55PM +0200, Robin Kipp wrote: Hi list, I just purchased an HP ProLiant Micro Server G2020T. As for the hard drives, I installed 4 3TB Western Digital HDs. So far so good, but volumes with a capacity greater than 2TB require a GPT partition table. Unfortunately, the server does not support UEFI, and thus can't boot from GPT partitions natively. So, when I ran the Debian installer, I used the following partitioning scheme on all drives since I wanted to combine them in a software RAID: 1MB BIOS Boot Partition (BBP) for GRUB 512MB dedicated /boot partition partition with all the remaining disk space. I then proceeded to setup software RAID: no RAID on the 1MB BIOS boot partition (not sure if this is correct) RAID1 for the 512MB /boot partition including all the HDs. RAID5 for the large partition that remained for file storage. I then set up the /boot partition (/dev/md0) to contain an EXT3 file system and also configured the mount point to be / boot. For the large partition, I setup LVM and created logical volumes for the root and SWAP partition. I also configured those partitions accordingly so the installer would know how to use them. Once I finished, the installation went through without any problems. After the system was installed, I used the 'Install the GRUB boot loader' option to install GRUB on all HDS (/dev/sda through /dev/sdd), which worked just fine. However, when I rebooted the system I got an error message saying the root file system could not be mounted. I suspected the LVM to cause issues, so I re-installed everything but this time without LVM. Unfortunately, the same issue persists… Has anyone here ever been in a similar situation and could suggest a fix? I have a feeling I may be missing something important, but just can't find the right path to take… If you're getting an error saying root couldn't be mounted then I'm assuming that: - BIOS has found GRUB - GRUB has found the kernel - the kernel has booted BUT - the kernel couldn't find the rootfs, so therefore couldn't start init If that's the case, try adding rootdelay=30 to your kernel command line (the best way is to append it to GRUB_CMDLINE_LINUX in /etc/default/grub and re-run update-grub, but you can temporarily add it at grub's command line editor). rootdelay should cause the kernel to wait a few moments for all drives to become ready, the raid to assemble and so on, before it tries to mount rootfs. signature.asc Description: Digital signature
Re: Installing and booting Debian from large hard drives in a RAID without GPT
On Fri, Sep 6, 2013 at 6:45 AM, Darac Marjal mailingl...@darac.org.ukwrote: On Fri, Sep 06, 2013 at 02:29:55PM +0200, Robin Kipp wrote: Hi list, I just purchased an HP ProLiant Micro Server G2020T. As for the hard drives, I installed 4 3TB Western Digital HDs. So far so good, but volumes with a capacity greater than 2TB require a GPT partition table. Unfortunately, the server does not support UEFI, and thus can't boot from GPT partitions natively. So, when I ran the Debian installer, I used the following partitioning scheme on all drives since I wanted to combine them in a software RAID: 1MB BIOS Boot Partition (BBP) for GRUB 512MB dedicated /boot partition partition with all the remaining disk space. I then proceeded to setup software RAID: no RAID on the 1MB BIOS boot partition (not sure if this is correct) RAID1 for the 512MB /boot partition including all the HDs. RAID5 for the large partition that remained for file storage. I then set up the /boot partition (/dev/md0) to contain an EXT3 file system and also configured the mount point to be / boot. For the large partition, I setup LVM and created logical volumes for the root and SWAP partition. I also configured those partitions accordingly so the installer would know how to use them. Once I finished, the installation went through without any problems. After the system was installed, I used the 'Install the GRUB boot loader' option to install GRUB on all HDS (/dev/sda through /dev/sdd), which worked just fine. However, when I rebooted the system I got an error message saying the root file system could not be mounted. I suspected the LVM to cause issues, so I re-installed everything but this time without LVM. Unfortunately, the same issue persists… Has anyone here ever been in a similar situation and could suggest a fix? I have a feeling I may be missing something important, but just can't find the right path to take… If you're getting an error saying root couldn't be mounted then I'm assuming that: - BIOS has found GRUB - GRUB has found the kernel - the kernel has booted BUT - the kernel couldn't find the rootfs, so therefore couldn't start init If that's the case, try adding rootdelay=30 to your kernel command line (the best way is to append it to GRUB_CMDLINE_LINUX in /etc/default/grub and re-run update-grub, but you can temporarily add it at grub's command line editor). rootdelay should cause the kernel to wait a few moments for all drives to become ready, the raid to assemble and so on, before it tries to mount rootfs. I have had problems with the initrd not having the LVM modules loaded in it. I had to make sure LVM was installed then run: update-initramfs -u -k all then : update-grub to get it to play nice with the system. Other than that I would just make sure your /etc/fstab file is correct. -- Shane D. Johnson IT Administrator Rasmussen Equipment
Re: new install - not booting solved - but questions remain
Miles Fidelman wrote: So problem is solved but 2 questions remain: - what's going on? - why didn't the installer put things in the right places? I read your posting but don't understand it. Basic setup: - PXEboot into installer You have set up a PXEboot on your network? That is sophisticated. But that should be normal in all other ways. - a pretty standard install - had to fiddle a little at the end to get the MBR into the right places (RAIDed disks, USB stick mounts as /dev/sda) How does the USB stick figure into things? But why do you have a usb stick in your machine at install time? You said you were PXE booting so you aren't using it for the installation image. Try installing without it since it would just be adding noise to the problem. For me my raided sata disks show up as sda and sdb. I think the answer to your question lies in what is different about your setup here that your raid disks are not sda and sdb. - now it boots, but ends up at a grub prompt on the (remote) console You are using a remote console? Remote in what way? This also sounds special. - attempt a boot and get the error no kernel loaded You have too many special cases to guess. Bob signature.asc Description: Digital signature
Re: Booting degraded software raid1 with failed /dev/sda
Tad Bak wrote: I have Debian Wheezy 64bit installed on a machine with 2 SATA drives. On the hard drives I have two software RAID1 partitions, md0 and md1. The bigger md1 uses LVM and has separate volumes for swap, /tmp, /var, /opt, /usr, and /home. Everything was working fine, A typical configuration. until one day the sda disc crashed and the system was not bootable anymore. This is how I have learned that by default Debian installs grub only on /dev/sda in RAID1 configuration. Despite the fact that /dev/sdb was still fine, I had no working system, as I couldn't boot it. After two days of Google search I have found a solution, which might be of interest to somebody in similar situation. That is a common situation that seems to be discussed here every month or so. A recurring topic. Sorry to hear that you have had this trouble too. Solution. First, I downloaded the debian-live-7.0.0-amd64-rescue.iso, it fits on one CDROM. I could boot from it into a live system. To get a root privileges I set root pasword: sudo passwd root and then su to root. Because BIOS already reported first HD error, cfdisk was I personally think it is easier to use the debian-installer in rescue mode to recover in this situation. I have written about hte process here often. Here is one recent posting of mine on the topic. http://lists.debian.org/debian-user/2013/06/msg00770.html But perhaps this one is better. https://lists.debian.org/debian-user/2013/01/msg00218.html I recommend using one of the smaller debian-installer images such as the netinst image. It is small to download and can be burned to cdrom or copied to a usb disk and booted. showing me only one HD, /dev/sda (before crash it was /dev/sdb). However, RAID1 was still alive, cat /proc/mdstat reported two degraded partitions, md126 and md127, the first one was my former md0 and the second the former md1. As I didn't have LVM on md0 I could mount it directly: mount /md126 /mnt. Volumes on md1 were also fine, lvscan listed all of them. I have mounted one by one: mount /dev/vol/usr /mnt/usr, mount /dev/vol/var /mnt/var, mount /dev/vol/tmp /mnt/tmp. It is this point that I think makes the debian-installer easier to use. It has a helper dialog for assembling raid and lvm. Simply activate automatic raid assembly. Then activate lvm. Then select the root partition. After that and chrooting into the system you can do 'mount -a' to mount all of the additional partitions all at once. And then you can repair your system. Fixing grub was a matter of the command: grub-install /dev/sda, which didn't report any errors. Ctrl-D returned me to the live system, from which I have rebooted. Fingers crossed -- after some delay caused by errors generated by the failed HD (which is still inside the computer) I was finally greeted by login screen. My system is running fine now with the degraded RAID array, waiting for the arrival of a new drive. Glad to hear that you were able to recover okay! Software RAID1 worked and even though you had a failure none of your data was lost. Now don't delay and replace that bad disk! And check that your backup is still working and current because RAID is no substitute for backup. Bob signature.asc Description: Digital signature
RE: Booting degraded software raid1 with failed /dev/sda
Bob Proulx [b...@proulx.com] wrote: I personally think it is easier to use the debian-installer in rescue mode to recover in this situation. I have written about hte process here often. Here is one recent posting of mine on the topic. [...] Thanks Bob! Yes, that looks easier. I have saved your e-mail in my tips tricks folder, in case I need it again in the future. Regards, Tad -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/e2cb61cacd6ecc46a6fbd0296822a23755521...@hirt.ad.uws.edu.au
Re: Booting degraded software raid1 with failed /dev/sda
- Original Message - From: Tad Bak t@uws.edu.au Background. I have Debian Wheezy 64bit installed on a machine with 2 SATA drives. On the hard drives I have two software RAID1 partitions, md0 and md1. The bigger md1 uses LVM and has separate volumes for swap, /tmp, /var, /opt, /usr, and /home. Everything was working fine, until one day the sda disc crashed and the system was not bootable anymore. This is how I have learned that by default Debian installs grub only on /dev/sda in RAID1 configuration. Despite the fact that /dev/sdb was still fine, I had no working system, as I couldn't boot it. After two days of Google search I have found a solution, which might be of interest to somebody in similar situation. Would super grub boot disk have worked for you? I have used it plenty of times to boot a system w/ a messed up grub, but I don't know if I've ever tried it on a system that used software RAID 1. -Rob -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1715114947.63688002.1375713720777.javamail.r...@ptd.net
RE: Booting degraded software raid1 with failed /dev/sda
Rob, I have tried that (super grub boot disk) first, but I couldn't fix my problem. It’s very likely that I was doing something wrong, as I have started more serious RTFM only after that first failed attempt :-). Then the Debian live CD route worked for me. Thanks, Tad From: Rob Owens [row...@ptd.net] Sent: Tuesday, 6 August 2013 00:42 To: debian-user@lists.debian.org Cc: debian-user@lists.debian.org Subject: Re: Booting degraded software raid1 with failed /dev/sda - Original Message - From: Tad Bak t@uws.edu.au Background. I have Debian Wheezy 64bit installed on a machine with 2 SATA drives. On the hard drives I have two software RAID1 partitions, md0 and md1. The bigger md1 uses LVM and has separate volumes for swap, /tmp, /var, /opt, /usr, and /home. Everything was working fine, until one day the sda disc crashed and the system was not bootable anymore. This is how I have learned that by default Debian installs grub only on /dev/sda in RAID1 configuration. Despite the fact that /dev/sdb was still fine, I had no working system, as I couldn't boot it. After two days of Google search I have found a solution, which might be of interest to somebody in similar situation. Would super grub boot disk have worked for you? I have used it plenty of times to boot a system w/ a messed up grub, but I don't know if I've ever tried it on a system that used software RAID 1. -Rob -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/e2cb61cacd6ecc46a6fbd0296822a23755521...@hirt.ad.uws.edu.au
Booting degraded software raid1 with failed /dev/sda
Background. I have Debian Wheezy 64bit installed on a machine with 2 SATA drives. On the hard drives I have two software RAID1 partitions, md0 and md1. The bigger md1 uses LVM and has separate volumes for swap, /tmp, /var, /opt, /usr, and /home. Everything was working fine, until one day the sda disc crashed and the system was not bootable anymore. This is how I have learned that by default Debian installs grub only on /dev/sda in RAID1 configuration. Despite the fact that /dev/sdb was still fine, I had no working system, as I couldn't boot it. After two days of Google search I have found a solution, which might be of interest to somebody in similar situation. Solution. First, I downloaded the debian-live-7.0.0-amd64-rescue.iso, it fits on one CDROM. I could boot from it into a live system. To get a root privileges I set root pasword: sudo passwd root and then su to root. Because BIOS already reported first HD error, cfdisk was showing me only one HD, /dev/sda (before crash it was /dev/sdb). However, RAID1 was still alive, cat /proc/mdstat reported two degraded partitions, md126 and md127, the first one was my former md0 and the second the former md1. As I didn't have LVM on md0 I could mount it directly: mount /md126 /mnt. Volumes on md1 were also fine, lvscan listed all of them. I have mounted one by one: mount /dev/vol/usr /mnt/usr, mount /dev/vol/var /mnt/var, mount /dev/vol/tmp /mnt/tmp. Then, in preparation for chrooted environment I also mounted proc and dev: mount -t proc none /mnt/proc and /mount -o bind /dev /mnt/dev. After that chroot /mnt and I was in my installed system. Fixing grub was a matter of the command: grub-install /dev/sda, which didn't report any errors. Ctrl-D returned me to the live system, from which I have rebooted. Fingers crossed -- after some delay caused by errors generated by the failed HD (which is still inside the computer) I was finally greeted by login screen. My system is running fine now with the degraded RAID array, waiting for the arrival of a new drive. Cheers, Tad -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/e2cb61cacd6ecc46a6fbd0296822a23755520...@hirt.ad.uws.edu.au
new install - not booting
Hi Folks, Just did a new install of Wheezy on a server, but having problems trying to boot. Basic setup: - PXEboot into installer - a pretty standard install - had to fiddle a little at the end to get the MBR into the right places (RAIDed disks, USB stick mounts as /dev/sda) - now it boots, but ends up at a grub prompt on the (remote) console - attempt a boot and get the error no kernel loaded Diagnostics - restarted the installer in rescue mode, executed a shell in the newly built root directory - mounted everything - looked in /boot and all I could find is /boot/grub - no vmlinuz, no config, ... nothing Note that this is my first Wheezy install, and I understand the installer and boot process have changed - but can't figure out how. This has to be something stupid on my part, but what am I missing here? Thanks very much, Miles Fidelman -- In theory, there is no difference between theory and practice. In practice, there is. Yogi Berra -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/51fcde66.1070...@meetinghouse.net
Re: new install - not booting, a little more info
Miles Fidelman wrote: Just did a new install of Wheezy on a server, but having problems trying to boot. Basic setup: - PXEboot into installer - a pretty standard install - had to fiddle a little at the end to get the MBR into the right places (RAIDed disks, USB stick mounts as /dev/sda) - now it boots, but ends up at a grub prompt on the (remote) console - attempt a boot and get the error no kernel loaded Diagnostics - restarted the installer in rescue mode, executed a shell in the newly built root directory - mounted everything - looked in /boot and all I could find is /boot/grub - no vmlinuz, no config, ... nothing Note that this is my first Wheezy install, and I understand the installer and boot process have changed - but can't figure out how. Ok.. learning a bit about grub2, from the grub prompt: - discover that all the files are in (md/0) #raided boot device - try to set the paths manually and get some weird results - grub ls (md/0)/ lost+found/ System.map-3.2.0-4-rt-amd64 config-3.2.0-4-rt-amd64 grub/ vmlinuz-3 .2.0-4-rt-amd64 initrd.img-3.2.0-4-rt-amd64 grub ls (md/0)/grub/grub.cfg grub.cfg grub set prefix=(md/0)/boot/grub grub set root=(md/2) grub boot error: no loaded kernel. grub linux (md/0)/vmlinuz-3.2.0-4-rt-amd64 error: file not found. grub initrd (md/0)/initrd.img-3.2.0-4-rt-amd64 error: file not found. grub ls -l (md/0)/ DIR 20130803023241 lost+found/ 2115221 20130609193606 System.map-3.2.0-4-rt-amd64 128550 20130609193606 config-3.2.0-4-rt-amd64 DIR 20130803042226 grub/ 2885152 20130609192519 vmlinuz-3.2.0-4-rt-amd64 3673059 20130803034148 initrd.img-3.2.0-4-rt-amd64 - So the question becomes: why does grub see the various files for ls commands and autocompletion, but give file not found for the linux and initrd commands? Any ideas or suggestions? Thanks, Miles -- In theory, there is no difference between theory and practice. In practice, there is. Yogi Berra -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/51fce6b9.8090...@meetinghouse.net
Re: new install - not booting, a little more info, and yet more
Miles Fidelman wrote: Miles Fidelman wrote: Just did a new install of Wheezy on a server, but having problems trying to boot. Basic setup: - PXEboot into installer - a pretty standard install - had to fiddle a little at the end to get the MBR into the right places (RAIDed disks, USB stick mounts as /dev/sda) - now it boots, but ends up at a grub prompt on the (remote) console - attempt a boot and get the error no kernel loaded Diagnostics - restarted the installer in rescue mode, executed a shell in the newly built root directory - mounted everything - looked in /boot and all I could find is /boot/grub - no vmlinuz, no config, ... nothing Note that this is my first Wheezy install, and I understand the installer and boot process have changed - but can't figure out how. Ok.. learning a bit about grub2, from the grub prompt: - discover that all the files are in (md/0) #raided boot device - try to set the paths manually and get some weird results - grub ls (md/0)/ lost+found/ System.map-3.2.0-4-rt-amd64 config-3.2.0-4-rt-amd64 grub/ vmlinuz-3 .2.0-4-rt-amd64 initrd.img-3.2.0-4-rt-amd64 grub ls (md/0)/grub/grub.cfg grub.cfg grub set prefix=(md/0)/boot/grub grub set root=(md/2) grub boot error: no loaded kernel. grub linux (md/0)/vmlinuz-3.2.0-4-rt-amd64 error: file not found. grub initrd (md/0)/initrd.img-3.2.0-4-rt-amd64 error: file not found. grub ls -l (md/0)/ DIR 20130803023241 lost+found/ 2115221 20130609193606 System.map-3.2.0-4-rt-amd64 128550 20130609193606 config-3.2.0-4-rt-amd64 DIR 20130803042226 grub/ 2885152 20130609192519 vmlinuz-3.2.0-4-rt-amd64 3673059 20130803034148 initrd.img-3.2.0-4-rt-amd64 - after typing: set prefix=(md/0)/boot/grub set root=(md/2) insmod normal normal up comes the boot menu, and after the timeout, everything loads just fine now I just need to figure out - what's going on here? - how to configure things so everything loads automatically Can someone explain what's happening here? Thanks very much, Miles Fidelman -- In theory, there is no difference between theory and practice. In practice, there is. Yogi Berra -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/51fd13cf.2040...@meetinghouse.net
Re: new install - not booting solved - but questions remain
Miles Fidelman wrote: Miles Fidelman wrote: Miles Fidelman wrote: Just did a new install of Wheezy on a server, but having problems trying to boot. Basic setup: - PXEboot into installer - a pretty standard install - had to fiddle a little at the end to get the MBR into the right places (RAIDed disks, USB stick mounts as /dev/sda) - now it boots, but ends up at a grub prompt on the (remote) console - attempt a boot and get the error no kernel loaded Diagnostics - restarted the installer in rescue mode, executed a shell in the newly built root directory - mounted everything - looked in /boot and all I could find is /boot/grub - no vmlinuz, no config, ... nothing Note that this is my first Wheezy install, and I understand the installer and boot process have changed - but can't figure out how. Ok.. learning a bit about grub2, from the grub prompt: - discover that all the files are in (md/0) #raided boot device - try to set the paths manually and get some weird results - grub ls (md/0)/ lost+found/ System.map-3.2.0-4-rt-amd64 config-3.2.0-4-rt-amd64 grub/ vmlinuz-3 .2.0-4-rt-amd64 initrd.img-3.2.0-4-rt-amd64 grub ls (md/0)/grub/grub.cfg grub.cfg grub set prefix=(md/0)/boot/grub grub set root=(md/2) grub boot error: no loaded kernel. grub linux (md/0)/vmlinuz-3.2.0-4-rt-amd64 error: file not found. grub initrd (md/0)/initrd.img-3.2.0-4-rt-amd64 error: file not found. grub ls -l (md/0)/ DIR 20130803023241 lost+found/ 2115221 20130609193606 System.map-3.2.0-4-rt-amd64 128550 20130609193606 config-3.2.0-4-rt-amd64 DIR 20130803042226 grub/ 2885152 20130609192519 vmlinuz-3.2.0-4-rt-amd64 3673059 20130803034148 initrd.img-3.2.0-4-rt-amd64 - after typing: set prefix=(md/0)/boot/grub set root=(md/2) insmod normal normal up comes the boot menu, and after the timeout, everything loads just fine Well, after booting - ran update-grub and grub-install on all drives, and on the /dev/md0 (boot) and /dev/md2 (root) for good measure rebooted - everything came up fine So problem is solved but 2 questions remain: - what's going on? - why didn't the installer put things in the right places? Miles -- In theory, there is no difference between theory and practice. In practice, there is. Yogi Berra -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/51fd165b.4010...@meetinghouse.net
Re: Debian machine not booting
Hi, Got the problems solved. I couldn't solve the problem by using the rescue disk, as it wouldn't let me stop the raid array. What I did was drop into the maintenance mode: mdadm --assemble /dev/md1 /dev/sdd1 /dev/sde1 //This should recreate the array mdadm --detail --scan /etc/mdadm/mdadm.conf //edit the file to remove duplicates dpkg-reconfigure linux-image-$(uname -r) then reboot. Huge amount of thanks go to Bob Proulx for all the help along the way, James On 7 July 2013 21:53, James Allsopp jamesaalls...@googlemail.com wrote: Hello, I've been too nervous to reboot, so I've left it in the rescue mode at the point where I assembled the raid arrays and went into boot at the \ partition. Tried to run: mdadm --stop /dev/md127 but got a mdadm: failed to stop array /dev/md127: Device or resource busy. Perhaps a running process, mounted filesustem or active volume group? I tried unmounting /home which stretches onto this disk via LVM, but this made no difference. Any idea how I should proceed? Thanks, James On 5 July 2013 01:10, Bob Proulx b...@proulx.com wrote: James Allsopp wrote: I'd like to hear about the optimisations, but I think I'll wait till I get the system rebuilt! Basically I had expected you to use either rescue mode of the d-i or a livecd or other to assemble the arrays. You did. But neither array came up completely correct. One came up with one disk degraded. The split brain clone came up on md127 instead of md0. The other one came up on md126. So you should fix those using the discussed instructions. I was thinking you would do that from the same system boot that you had posted that information from. But your recent mail implies that you shut the system down and went away for a while. So now it appears you need to rescue the system again by the same method you used to get that information you posted. All of that is fine. Except now we already know the information you posted. And so now we know how those arrays are supposed to go together. But that is okay. You can go through rescue mode and assemble the arrays exactly as you did before. And then --stop the arrays and assemble them correctly. But since we know how they are supposed to be assembled now you could skip the assembly of them in rescue mode or livecd mode or whatever you used and simply assemble the arrays correctly the first time. Basically I think you are going to do: * rescue * assemble arrays * stop arrays * assemble arrays correctly Which is perfectly acceptable. The result will be fine. But now that we know what we need to do you could simply do this: * rescue * assemble arrays correctly But I don't want to distract you with complications like this! :-) And then after you get everything working you should visit the partitioning on that second array. Your partitioning starts at the sector 1. But that won't be aligned. It will cause all writes to be a read-modify-write and performance will suffer. Device Boot Start End Blocks Id System /dev/sdd1 1 243201 1953512001 fd Linux raid autodetect Partition 1 does not start on physical sector boundary. Device Boot Start End Blocks Id System /dev/sde1 1 243201 1953512001 fd Linux raid autodetect Partition 1 does not start on physical sector boundary. Instead of using the entire disk starting at 1 it would be much better if you started at sector 2048 as is the new standard for Advanced Format 4k sector drives. I would expect that to be a large performance lever on your system. But fix that after you have your data up and available. Bob
Re: Debian machine not booting
Hello, I've been too nervous to reboot, so I've left it in the rescue mode at the point where I assembled the raid arrays and went into boot at the \ partition. Tried to run: mdadm --stop /dev/md127 but got a mdadm: failed to stop array /dev/md127: Device or resource busy. Perhaps a running process, mounted filesustem or active volume group? I tried unmounting /home which stretches onto this disk via LVM, but this made no difference. Any idea how I should proceed? Thanks, James On 5 July 2013 01:10, Bob Proulx b...@proulx.com wrote: James Allsopp wrote: I'd like to hear about the optimisations, but I think I'll wait till I get the system rebuilt! Basically I had expected you to use either rescue mode of the d-i or a livecd or other to assemble the arrays. You did. But neither array came up completely correct. One came up with one disk degraded. The split brain clone came up on md127 instead of md0. The other one came up on md126. So you should fix those using the discussed instructions. I was thinking you would do that from the same system boot that you had posted that information from. But your recent mail implies that you shut the system down and went away for a while. So now it appears you need to rescue the system again by the same method you used to get that information you posted. All of that is fine. Except now we already know the information you posted. And so now we know how those arrays are supposed to go together. But that is okay. You can go through rescue mode and assemble the arrays exactly as you did before. And then --stop the arrays and assemble them correctly. But since we know how they are supposed to be assembled now you could skip the assembly of them in rescue mode or livecd mode or whatever you used and simply assemble the arrays correctly the first time. Basically I think you are going to do: * rescue * assemble arrays * stop arrays * assemble arrays correctly Which is perfectly acceptable. The result will be fine. But now that we know what we need to do you could simply do this: * rescue * assemble arrays correctly But I don't want to distract you with complications like this! :-) And then after you get everything working you should visit the partitioning on that second array. Your partitioning starts at the sector 1. But that won't be aligned. It will cause all writes to be a read-modify-write and performance will suffer. Device Boot Start End Blocks Id System /dev/sdd1 1 243201 1953512001 fd Linux raid autodetect Partition 1 does not start on physical sector boundary. Device Boot Start End Blocks Id System /dev/sde1 1 243201 1953512001 fd Linux raid autodetect Partition 1 does not start on physical sector boundary. Instead of using the entire disk starting at 1 it would be much better if you started at sector 2048 as is the new standard for Advanced Format 4k sector drives. I would expect that to be a large performance lever on your system. But fix that after you have your data up and available. Bob
Re: Debian machine not booting
Thanks Bob, like I say, very much appreciated and I'll let you know how it goes! I'd like to hear about the optimisations, but I think I'll wait till I get the system rebuilt! James On 4 July 2013 00:47, Bob Proulx b...@proulx.com wrote: James Allsopp wrote: Thanks Bob, really can't thank you enough. Just to be clear about this, I'd do these commands from the rescue disk after I have assembled the arrays and gone to the bash shell? Short answer: Yes. Go for it! Longer answer: There are all kinds of things I want to say here. And I already said a lot! There are some optimizations that could be made. But if you do what is outlined it should work. But I don't want to make things more confusing by talking about minor things. I have my fingers crossed for you! :-) Bob
Re: Debian machine not booting
James Allsopp wrote: I'd like to hear about the optimisations, but I think I'll wait till I get the system rebuilt! Basically I had expected you to use either rescue mode of the d-i or a livecd or other to assemble the arrays. You did. But neither array came up completely correct. One came up with one disk degraded. The split brain clone came up on md127 instead of md0. The other one came up on md126. So you should fix those using the discussed instructions. I was thinking you would do that from the same system boot that you had posted that information from. But your recent mail implies that you shut the system down and went away for a while. So now it appears you need to rescue the system again by the same method you used to get that information you posted. All of that is fine. Except now we already know the information you posted. And so now we know how those arrays are supposed to go together. But that is okay. You can go through rescue mode and assemble the arrays exactly as you did before. And then --stop the arrays and assemble them correctly. But since we know how they are supposed to be assembled now you could skip the assembly of them in rescue mode or livecd mode or whatever you used and simply assemble the arrays correctly the first time. Basically I think you are going to do: * rescue * assemble arrays * stop arrays * assemble arrays correctly Which is perfectly acceptable. The result will be fine. But now that we know what we need to do you could simply do this: * rescue * assemble arrays correctly But I don't want to distract you with complications like this! :-) And then after you get everything working you should visit the partitioning on that second array. Your partitioning starts at the sector 1. But that won't be aligned. It will cause all writes to be a read-modify-write and performance will suffer. Device Boot Start End Blocks Id System /dev/sdd1 1 243201 1953512001 fd Linux raid autodetect Partition 1 does not start on physical sector boundary. Device Boot Start End Blocks Id System /dev/sde1 1 243201 1953512001 fd Linux raid autodetect Partition 1 does not start on physical sector boundary. Instead of using the entire disk starting at 1 it would be much better if you started at sector 2048 as is the new standard for Advanced Format 4k sector drives. I would expect that to be a large performance lever on your system. But fix that after you have your data up and available. Bob signature.asc Description: Digital signature
Re: Debian machine not booting
Thanks Bob, really can't thank you enough. Just to be clear about this, I'd do these commands from the rescue disk after I have assembled the arrays and gone to the bash shell? Much appreciated, James On 2 July 2013 22:44, Bob Proulx b...@proulx.com wrote: James Allsopp wrote: One other point sda isn't the boot hard drive, that's the partitions /sdb1 and sdc1, but these should be the same (I thought I'd mirrored them to be honest). I don't see sda anywhere. It might be a dual booting Windows disk? Or other. But the BIOS will boot the first disk from the BIOS boot order. BIOS boot order may be different from OS disk order. It can be confusing. I might assume that BIOS sata0 is the same as the OS disk sda but actually it often is different. Let's ignore this for now. You have sdb1 and sdc1 mirrored into md1. I can see that because the UUID is identical. /dev/md1: Version : 1.2 Creation Time : Thu Jan 31 22:43:49 2013 Raid Level : raid1 Array Size : 1953510841 (1863.01 GiB 2000.40 GB) Used Dev Size : 1953510841 (1863.01 GiB 2000.40 GB) Raid Devices : 2 Total Devices : 1 Persistence : Superblock is persistent Update Time : Tue Jul 2 13:49:55 2013 State : clean, degraded Active Devices : 1 Working Devices : 1 Failed Devices : 0 Spare Devices : 0 Name : Hawaiian:1 (local to host Hawaiian) UUID : a544829f:33778728:79870439:241c5c51 Events : 112 Number Major Minor RaidDevice State 0 000 removed 1 8 651 active sync /dev/sde1 That info is the same as: /dev/md127: Version : 1.2 Creation Time : Thu Jan 31 22:43:49 2013 Raid Level : raid1 Array Size : 1953510841 (1863.01 GiB 2000.40 GB) Used Dev Size : 1953510841 (1863.01 GiB 2000.40 GB) Raid Devices : 2 Total Devices : 1 Persistence : Superblock is persistent Update Time : Tue Jul 2 13:49:29 2013 State : clean, degraded Active Devices : 1 Working Devices : 1 Failed Devices : 0 Spare Devices : 0 Name : Hawaiian:1 (local to host Hawaiian) UUID : a544829f:33778728:79870439:241c5c51 Events : 106 Number Major Minor RaidDevice State 0 8 490 active sync /dev/sdd1 1 001 removed The UUIDs are identical. Therefore those two disks are mirrors of each other. And note: /dev/md1: (/dev/sde1) Update Time : Tue Jul 2 13:49:55 2013 /dev/md127: (/dev/sdd1) Update Time : Tue Jul 2 13:49:29 2013 sde1 is newer than sdd1. This seems consistent with it being the best copy to keep. If it were the other way around I would think about using the other one. But selecting the right master is important since it is a component of the lvm. How should I proceed from here? I would proceed as previously suggested. I would do this: mdadm --stop /dev/md127 mdadm --manage /dev/md1 --add /dev/sdd1 watch cat /proc/mdstat That will discard the older stale copy of the mirror on sdd1. It will use sdd1 as a mirror of sde1. After doing the add the mirror will sync and you can watch the progress using 'watch cat /proc/mdstat'. Use control-c to interrupt it when you want to stop it. For ruther information: /dev/sdb3: Preferred Minor : 126 ... /dev/sdc3: Preferred Minor : 126 ... That further information looked _okay_ to me. But I would still change the md126 back to md0. mdadm --stop /dev/md126 mdadm --assemble /dev/md0 --update=super-minor /dev/sdb1 /dev/sdc1 cat /proc/mdstat Since it is clean now it will be stopped cleanly and reassembled cleanly and no sync will be needed. The --update=super-minor will reset the superblock with the updated md0 minor device number. Then update /etc/mdadm/mdadm.conf and rebuild the initrd. Bob
Re: Debian machine not booting
James Allsopp wrote: Thanks Bob, really can't thank you enough. Just to be clear about this, I'd do these commands from the rescue disk after I have assembled the arrays and gone to the bash shell? Short answer: Yes. Go for it! Longer answer: There are all kinds of things I want to say here. And I already said a lot! There are some optimizations that could be made. But if you do what is outlined it should work. But I don't want to make things more confusing by talking about minor things. I have my fingers crossed for you! :-) Bob signature.asc Description: Digital signature
Tripple Booting win 7, ubuntu and Debian in whatever order
Ok..I installed Ubuntu from Win 7 and I am using it ok...I later tried installing Debian just to get a feel of the two Linux. Did the Grub booter thing in both cases but could not find Debian in the list just ubuntu and Win 7 options. How do I go about fixing this i.e been able to see debian in the list. Thanks all.
Re: Debian machine not booting
Thanks Bob, I'll get back to after I've followed your instructions. I think
I'm going to have to learn to type with crossed fingers!
I think I initially sorted out all my partitions manually, rather than
directly using the installer to do it automatically,
Really appreciated,
James
On 2 July 2013 00:46, Bob Proulx b...@proulx.com wrote:
James Allsopp wrote:
Personalities : [raid0] [raid1] [raid6] [raid5] [raid4]
md126 : active raid1 sdb3[0] sdc3[1]
972550912 blocks [2/2] [UU]
So sdb3 and sdc3 are assembled into /dev/md126. That seems good. One
full array is assembled.
Is /dev/md126 your preferred name for that array? I would guess not.
Usually it is /dev/md0 or some such. But when that name is not
available because it is already in use then mdadm will rotate up to a
later name like /dev/md126.
You can fix this by using mdadm with --update=super-minor to force it
back to the desired name. Something like this using your devices:
mdadm --assemble /dev/md0 --update=super-minor /dev/sdb3 /dev/sdc3
But that can only be done at assembly time. If it is already
assembled then you would need to stop the array first and then
assemble it again.
md127 : active raid1 sdd1[0]
1953510841 blocks super 1.2 [2/1] [U_]
md1 : active raid1 sde1[1]
1953510841 blocks super 1.2 [2/1] [_U]
I think this array is now has a split brain problem. At this point
the original single mirrored array has had both halves of the mirror
assembled and both are running. So now you have two clones of each
other and both are active. Meaning that each think they are newer
than the other. Is that right? In which case you will eventually
need to pick one and call it the master. I think the sde1 is the
natural master since it is assembled on /dev/md1.
cat /etc/mdadm/mdadm.conf
...
# definitions of existing MD arrays
ARRAY /dev/md0 UUID=a529cd1b:c055887e:bfe78010:bc810f04
Only one array specified. That is definitely part of your problem.
You should have at least two arrays specified there.
mdadm --detail --scan:
ARRAY /dev/md/0_0 metadata=0.90 UUID=a529cd1b:c055887e:bfe78010:bc810f04
That mdadm --scan only found one array is odd.
fdisk -l
Disk /dev/sda: 120.0 GB, 120033041920 bytes
255 heads, 63 sectors/track, 14593 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: 0x0002ae52
Device Boot Start End Blocks Id System
/dev/sda1 1 14593 117218241 83 Linux
I take it that this is your boot disk? Your boot disk is not RAID?
I don't like that the first used sector is 1. That would have been 63
using the previous debian-installer to leave space for the MBR and
other things. But that is a different issue.
Disk /dev/sdd: 2000.4 GB, 2000398934016 bytes
255 heads, 63 sectors/track, 243201 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
That is an Advanced Format 4k sector drive. Meaning that the
partitions should start on a 4k sector alignment. The
debian-installer would do this automatically.
Disk identifier: 0xe044b9be
Device Boot Start End Blocks Id System
/dev/sdd1 1 243201 1953512001 fd Linux raid
autodetect
^
/dev/sde1 1 243201 1953512001 fd Linux raid
autodetect
^
Partition 1 does not start on physical sector boundary.
I don't recall if the first sector is 0 or 1 but I think the first
sector is 0 for the partition table. Meaning that sector 1 is not
going to be 4k aligned. (Can someone double check me on this?)
Meaning that this will require a lot of read-modify-write causing
performance problems for those drives.
The new standard for sector alignment would start at 2048 to leave
space for the partition table and other things and still be aligned
properly.
I don't know if this helps or where to go from here, but I think I need
to
get the mdadm up and running properly before I do anything.
Probably a good idea.
If there's any commands you need me to run, please ask,
How are you booted now? Are you root on the system through something
like the debian-installer rescue boot? Or did you use a live cd or
something?
Please run:
# mdadm --detail /dev/sdd1
# mdadm --detail /dev/sde1
Those are what look to be the split brain of the second array. They
will list something at the bottom that will look like:
Number Major Minor RaidDevice State
this 1 8 171 active sync /dev/sdb1
0 0 810 active sync /dev/sda1
1 1
Re: Tripple Booting win 7, ubuntu and Debian in whatever order
On Tue 02 Jul 2013 at 07:38:55 +0100, Lagun Adeshina wrote: Ok..I installed Ubuntu from Win 7 and I am using it ok...I later tried installing Debian just to get a feel of the two Linux. Did the Grub booter thing in both cases but could not find Debian in the list just ubuntu and Win 7 options. How do I go about fixing this i.e been able to see debian in the list. Thanks all. Let's see if Ubuntu knows about your Debian install. Execute os-prober and post its output. Are you able to boot at all into Debian? -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130702123520.GB3423@desktop
Re: Debian machine not booting
One other point sda isn't the boot hard drive, that's the partitions /sdb1 and sdc1, but these should be the same (I thought I'd mirrored them to be honest). I tried mdadm --detail /dev/sdd1 but it didn't work. I have these results if they help? /dev/md1: Version : 1.2 Creation Time : Thu Jan 31 22:43:49 2013 Raid Level : raid1 Array Size : 1953510841 (1863.01 GiB 2000.40 GB) Used Dev Size : 1953510841 (1863.01 GiB 2000.40 GB) Raid Devices : 2 Total Devices : 1 Persistence : Superblock is persistent Update Time : Tue Jul 2 13:49:55 2013 State : clean, degraded Active Devices : 1 Working Devices : 1 Failed Devices : 0 Spare Devices : 0 Name : Hawaiian:1 (local to host Hawaiian) UUID : a544829f:33778728:79870439:241c5c51 Events : 112 Number Major Minor RaidDevice State 0 000 removed 1 8 651 active sync /dev/sde1 /dev/md127: Version : 1.2 Creation Time : Thu Jan 31 22:43:49 2013 Raid Level : raid1 Array Size : 1953510841 (1863.01 GiB 2000.40 GB) Used Dev Size : 1953510841 (1863.01 GiB 2000.40 GB) Raid Devices : 2 Total Devices : 1 Persistence : Superblock is persistent Update Time : Tue Jul 2 13:49:29 2013 State : clean, degraded Active Devices : 1 Working Devices : 1 Failed Devices : 0 Spare Devices : 0 Name : Hawaiian:1 (local to host Hawaiian) UUID : a544829f:33778728:79870439:241c5c51 Events : 106 Number Major Minor RaidDevice State 0 8 490 active sync /dev/sdd1 1 001 removed How should I proceed from here? James On 2 July 2013 09:50, James Allsopp jamesaalls...@googlemail.com wrote: Thanks Bob, I'll get back to after I've followed your instructions. I think I'm going to have to learn to type with crossed fingers! I think I initially sorted out all my partitions manually, rather than directly using the installer to do it automatically, Really appreciated, James On 2 July 2013 00:46, Bob Proulx b...@proulx.com wrote: James Allsopp wrote: Personalities : [raid0] [raid1] [raid6] [raid5] [raid4] md126 : active raid1 sdb3[0] sdc3[1] 972550912 blocks [2/2] [UU] So sdb3 and sdc3 are assembled into /dev/md126. That seems good. One full array is assembled. Is /dev/md126 your preferred name for that array? I would guess not. Usually it is /dev/md0 or some such. But when that name is not available because it is already in use then mdadm will rotate up to a later name like /dev/md126. You can fix this by using mdadm with --update=super-minor to force it back to the desired name. Something like this using your devices: mdadm --assemble /dev/md0 --update=super-minor /dev/sdb3 /dev/sdc3 But that can only be done at assembly time. If it is already assembled then you would need to stop the array first and then assemble it again. md127 : active raid1 sdd1[0] 1953510841 blocks super 1.2 [2/1] [U_] md1 : active raid1 sde1[1] 1953510841 blocks super 1.2 [2/1] [_U] I think this array is now has a split brain problem. At this point the original single mirrored array has had both halves of the mirror assembled and both are running. So now you have two clones of each other and both are active. Meaning that each think they are newer than the other. Is that right? In which case you will eventually need to pick one and call it the master. I think the sde1 is the natural master since it is assembled on /dev/md1. cat /etc/mdadm/mdadm.conf ... # definitions of existing MD arrays ARRAY /dev/md0 UUID=a529cd1b:c055887e:bfe78010:bc810f04 Only one array specified. That is definitely part of your problem. You should have at least two arrays specified there. mdadm --detail --scan: ARRAY /dev/md/0_0 metadata=0.90 UUID=a529cd1b:c055887e:bfe78010:bc810f04 That mdadm --scan only found one array is odd. fdisk -l Disk /dev/sda: 120.0 GB, 120033041920 bytes 255 heads, 63 sectors/track, 14593 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: 0x0002ae52 Device Boot Start End Blocks Id System /dev/sda1 1 14593 117218241 83 Linux I take it that this is your boot disk? Your boot disk is not RAID? I don't like that the first used sector is 1. That would have been 63 using the previous debian-installer to leave space for the MBR and other things. But that is a different issue. Disk /dev/sdd: 2000.4 GB, 2000398934016 bytes 255 heads, 63 sectors/track, 243201 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096
Re: Debian machine not booting
For ruther information:
/dev/sdb3:
Magic : a92b4efc
Version : 0.90.00
UUID : a529cd1b:c055887e:bfe78010:bc810f04
Creation Time : Fri Nov 20 09:37:34 2009
Raid Level : raid1
Used Dev Size : 972550912 (927.50 GiB 995.89 GB)
Array Size : 972550912 (927.50 GiB 995.89 GB)
Raid Devices : 2
Total Devices : 2
Preferred Minor : 126
Update Time : Tue Jul 2 13:49:18 2013
State : clean
Active Devices : 2
Working Devices : 2
Failed Devices : 0
Spare Devices : 0
Checksum : 6203fa40 - correct
Events : 1036616
Number Major Minor RaidDevice State
this 0 8 190 active sync /dev/sdb3
0 0 8 190 active sync /dev/sdb3
1 1 8 351 active sync /dev/sdc3
/dev/sdc3:
Magic : a92b4efc
Version : 0.90.00
UUID : a529cd1b:c055887e:bfe78010:bc810f04
Creation Time : Fri Nov 20 09:37:34 2009
Raid Level : raid1
Used Dev Size : 972550912 (927.50 GiB 995.89 GB)
Array Size : 972550912 (927.50 GiB 995.89 GB)
Raid Devices : 2
Total Devices : 2
Preferred Minor : 126
Update Time : Tue Jul 2 13:49:18 2013
State : clean
Active Devices : 2
Working Devices : 2
Failed Devices : 0
Spare Devices : 0
Checksum : 6203fa52 - correct
Events : 1036616
Number Major Minor RaidDevice State
this 1 8 351 active sync /dev/sdc3
0 0 8 190 active sync /dev/sdb3
1 1 8 351 active sync /dev/sdc3
/dev/sdd1:
Magic : a92b4efc
Version : 1.2
Feature Map : 0x0
Array UUID : a544829f:33778728:79870439:241c5c51
Name : Hawaiian:1 (local to host Hawaiian)
Creation Time : Thu Jan 31 22:43:49 2013
Raid Level : raid1
Raid Devices : 2
Avail Dev Size : 3907021954 (1863.01 GiB 2000.40 GB)
Array Size : 3907021682 (1863.01 GiB 2000.40 GB)
Used Dev Size : 3907021682 (1863.01 GiB 2000.40 GB)
Data Offset : 2048 sectors
Super Offset : 8 sectors
State : clean
Device UUID : 1e0de6be:bbcc874e:e00e2caa:593de9b1
Update Time : Tue Jul 2 13:51:19 2013
Checksum : a8cf720f - correct
Events : 108
Device Role : Active device 0
Array State : A. ('A' == active, '.' == missing)
/dev/sde1:
Magic : a92b4efc
Version : 1.2
Feature Map : 0x0
Array UUID : a544829f:33778728:79870439:241c5c51
Name : Hawaiian:1 (local to host Hawaiian)
Creation Time : Thu Jan 31 22:43:49 2013
Raid Level : raid1
Raid Devices : 2
Avail Dev Size : 3907021954 (1863.01 GiB 2000.40 GB)
Array Size : 3907021682 (1863.01 GiB 2000.40 GB)
Used Dev Size : 3907021682 (1863.01 GiB 2000.40 GB)
Data Offset : 2048 sectors
Super Offset : 8 sectors
State : clean
Device UUID : 926788c3:9dfbf62b:26934208:5a72d05d
Update Time : Tue Jul 2 13:51:05 2013
Checksum : 94e2b4a1 - correct
Events : 114
Device Role : Active device 1
Array State : .A ('A' == active, '.' == missing)
Thanks
James
On 2 July 2013 13:52, James Allsopp jamesaalls...@googlemail.com wrote:
One other point sda isn't the boot hard drive, that's the partitions /sdb1
and sdc1, but these should be the same (I thought I'd mirrored them to be
honest).
I tried mdadm --detail /dev/sdd1 but it didn't work. I have these results
if they help?
/dev/md1:
Version : 1.2
Creation Time : Thu Jan 31 22:43:49 2013
Raid Level : raid1
Array Size : 1953510841 (1863.01 GiB 2000.40 GB)
Used Dev Size : 1953510841 (1863.01 GiB 2000.40 GB)
Raid Devices : 2
Total Devices : 1
Persistence : Superblock is persistent
Update Time : Tue Jul 2 13:49:55 2013
State : clean, degraded
Active Devices : 1
Working Devices : 1
Failed Devices : 0
Spare Devices : 0
Name : Hawaiian:1 (local to host Hawaiian)
UUID : a544829f:33778728:79870439:241c5c51
Events : 112
Number Major Minor RaidDevice State
0 000 removed
1 8 651 active sync /dev/sde1
/dev/md127:
Version : 1.2
Creation Time : Thu Jan 31 22:43:49 2013
Raid Level : raid1
Array Size : 1953510841 (1863.01 GiB 2000.40 GB)
Used Dev Size : 1953510841 (1863.01 GiB 2000.40 GB)
Raid Devices : 2
Total Devices : 1
Persistence : Superblock is persistent
Update Time : Tue Jul 2 13:49:29 2013
State : clean, degraded
Active Devices : 1
Working Devices : 1
Failed Devices : 0
Spare Devices : 0
Name : Hawaiian:1 (local to host Hawaiian)
UUID : a544829f:33778728:79870439:241c5c51
Events : 106
Number Major Minor RaidDevice State
0 8 490 active sync /dev/sdd1
Re: Tripple Booting win 7, ubuntu and Debian in whatever order
Hi, I don't have a Ubuntu at hand, so I can't tell the version of grub Ubuntu is using. Suppose the grub-pc is used just as debian did. You can simply do that by executing: $ sudo update-grub2 this command will probe all installation in your machine, and generate a new grub config file at: /boot/grub/grub.cfg On Tue, Jul 2, 2013 at 2:38 PM, Lagun Adeshina lagun_...@yahoo.com wrote: Ok..I installed Ubuntu from Win 7 and I am using it ok...I later tried installing Debian just to get a feel of the two Linux. Did the Grub booter thing in both cases but could not find Debian in the list just ubuntu and Win 7 options. How do I go about fixing this i.e been able to see debian in the list. Thanks all.
Re: Debian machine not booting
James Allsopp wrote: One other point sda isn't the boot hard drive, that's the partitions /sdb1 and sdc1, but these should be the same (I thought I'd mirrored them to be honest). I don't see sda anywhere. It might be a dual booting Windows disk? Or other. But the BIOS will boot the first disk from the BIOS boot order. BIOS boot order may be different from OS disk order. It can be confusing. I might assume that BIOS sata0 is the same as the OS disk sda but actually it often is different. Let's ignore this for now. You have sdb1 and sdc1 mirrored into md1. I can see that because the UUID is identical. /dev/md1: Version : 1.2 Creation Time : Thu Jan 31 22:43:49 2013 Raid Level : raid1 Array Size : 1953510841 (1863.01 GiB 2000.40 GB) Used Dev Size : 1953510841 (1863.01 GiB 2000.40 GB) Raid Devices : 2 Total Devices : 1 Persistence : Superblock is persistent Update Time : Tue Jul 2 13:49:55 2013 State : clean, degraded Active Devices : 1 Working Devices : 1 Failed Devices : 0 Spare Devices : 0 Name : Hawaiian:1 (local to host Hawaiian) UUID : a544829f:33778728:79870439:241c5c51 Events : 112 Number Major Minor RaidDevice State 0 000 removed 1 8 651 active sync /dev/sde1 That info is the same as: /dev/md127: Version : 1.2 Creation Time : Thu Jan 31 22:43:49 2013 Raid Level : raid1 Array Size : 1953510841 (1863.01 GiB 2000.40 GB) Used Dev Size : 1953510841 (1863.01 GiB 2000.40 GB) Raid Devices : 2 Total Devices : 1 Persistence : Superblock is persistent Update Time : Tue Jul 2 13:49:29 2013 State : clean, degraded Active Devices : 1 Working Devices : 1 Failed Devices : 0 Spare Devices : 0 Name : Hawaiian:1 (local to host Hawaiian) UUID : a544829f:33778728:79870439:241c5c51 Events : 106 Number Major Minor RaidDevice State 0 8 490 active sync /dev/sdd1 1 001 removed The UUIDs are identical. Therefore those two disks are mirrors of each other. And note: /dev/md1: (/dev/sde1) Update Time : Tue Jul 2 13:49:55 2013 /dev/md127: (/dev/sdd1) Update Time : Tue Jul 2 13:49:29 2013 sde1 is newer than sdd1. This seems consistent with it being the best copy to keep. If it were the other way around I would think about using the other one. But selecting the right master is important since it is a component of the lvm. How should I proceed from here? I would proceed as previously suggested. I would do this: mdadm --stop /dev/md127 mdadm --manage /dev/md1 --add /dev/sdd1 watch cat /proc/mdstat That will discard the older stale copy of the mirror on sdd1. It will use sdd1 as a mirror of sde1. After doing the add the mirror will sync and you can watch the progress using 'watch cat /proc/mdstat'. Use control-c to interrupt it when you want to stop it. For ruther information: /dev/sdb3: Preferred Minor : 126 ... /dev/sdc3: Preferred Minor : 126 ... That further information looked _okay_ to me. But I would still change the md126 back to md0. mdadm --stop /dev/md126 mdadm --assemble /dev/md0 --update=super-minor /dev/sdb1 /dev/sdc1 cat /proc/mdstat Since it is clean now it will be stopped cleanly and reassembled cleanly and no sync will be needed. The --update=super-minor will reset the superblock with the updated md0 minor device number. Then update /etc/mdadm/mdadm.conf and rebuild the initrd. Bob signature.asc Description: Digital signature
Re: Debian machine not booting
: 512 bytes Disk identifier: 0x Disk /dev/md126: 995.9 GB, 995892133888 bytes 2 heads, 4 sectors/track, 243137728 cylinders Units = cylinders of 8 * 512 = 4096 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x Disk /dev/dm-0: 10.5 GB, 1048576 bytes 255 heads, 63 sectors/track, 1274 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: 0x Disk /dev/dm-1: 36.7 GB, 3670016 bytes 255 heads, 63 sectors/track, 4461 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: 0x Disk /dev/dm-2: 1375.7 GB, 1375731712000 bytes 255 heads, 63 sectors/track, 167256 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Alignment offset: 512 bytes Disk identifier: 0x Disk /dev/dm-3: 10.5 GB, 1048576 bytes 255 heads, 63 sectors/track, 1274 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: 0x -- I don't know if this helps or where to go from here, but I think I need to get the mdadm up and running properly before I do anything. I get some errors running those commands but they didn't get written to the file. E.g. mdadm --detail --scan mdadm: cannot open /dev/md/Hawaiian:1: No such file or directory mdadm: cannot open /dev/md/1: No such file or directory ARRAY /dev/md/0_0 metadata=0.90 UUID=a529cd1b:c055887e:bfe78010:bc810f04 If there's any commands you need me to run, please ask, Thanks, James On 18 June 2013 20:47, Bob Proulx b...@proulx.com wrote: James Allsopp wrote: I have a debian machine which was on for a long time (~months). Just moved house and rebooted and now it doesn't boot. Bummer. My 4 harddrives are organised in pairs of RAID 1 (Mirrored) with LVM spanning them. Originally there was just one pair, but then I got two new hard drives and added them. I then increased the space of VolGroup-LogVol03 to cover these new drives and increase the space of Home (/ wass on one of the other logical volume groups). This all worked fine for ages. Sounds fine. Assuming that it booted after those changes. When I boot all four drives are detected in BIOS and I've check all the connections. Good. It gets to 3 logical volumes in volume group VolGroup now active which sounds good. That does sound good. Then here's the error: fsck.ext4: No such file or directory while trying to open /dev/mapper/VolGroup-LogVol03 /dev/mapper/VolGroup-LogVol03: The superblock could not be read or does not describe a correct ext2 . Hmm... I am not familiar with that error. But searching the web found several stories about it. Most concerned recent changes to the system that prevented it from booting. I have a debian machine which was on for a long time (~months). Just moved house and rebooted and now it doesn't boot. My 4 harddrives are organised in pairs of RAID 1 (Mirrored) with LVM spanning them. Originally there was just one pair, but then I got two new hard drives and added them. I then increased the space of VolGroup-LogVol03 to cover these new drives and increase the space of Home (/ wass on one of the other logical volume groups). This all worked fine for ages. And you rebooted in that time period? Otherwise these changes, if not done completely correct, seem prime to have triggered your current problem independent of any other action. You say it was on for a long time. If you had not rebooted in that long time then this may have been a hang-fire problem for all of that time. I'm wondering if some of the drive id's have been switched. If you mean the drive UUIDs then no those would not have changed. Any help would be really appreciated. I'm worried I've lost all my data on home First, do not despair. You should be able to get your system working again. You are probably simply missing the extra raid pair configuration. I strongly recommend using the debian-installer rescue mode to gain control of your system again. It works well and is readily available. Use a standard Debian installation disk. Usually we recommend the netinst disk because it is the smallest image. But any of the netinst or CD#1 or DVD#1 images will work fine for rescue mode since it is not actually installing but booting your system at that point so the difference between them does not matter. You have a disk? Go fish it out and boot it. Here is the official
Re: Debian machine not booting
James Allsopp wrote: Personalities : [raid0] [raid1] [raid6] [raid5] [raid4] md126 : active raid1 sdb3[0] sdc3[1] 972550912 blocks [2/2] [UU] So sdb3 and sdc3 are assembled into /dev/md126. That seems good. One full array is assembled. Is /dev/md126 your preferred name for that array? I would guess not. Usually it is /dev/md0 or some such. But when that name is not available because it is already in use then mdadm will rotate up to a later name like /dev/md126. You can fix this by using mdadm with --update=super-minor to force it back to the desired name. Something like this using your devices: mdadm --assemble /dev/md0 --update=super-minor /dev/sdb3 /dev/sdc3 But that can only be done at assembly time. If it is already assembled then you would need to stop the array first and then assemble it again. md127 : active raid1 sdd1[0] 1953510841 blocks super 1.2 [2/1] [U_] md1 : active raid1 sde1[1] 1953510841 blocks super 1.2 [2/1] [_U] I think this array is now has a split brain problem. At this point the original single mirrored array has had both halves of the mirror assembled and both are running. So now you have two clones of each other and both are active. Meaning that each think they are newer than the other. Is that right? In which case you will eventually need to pick one and call it the master. I think the sde1 is the natural master since it is assembled on /dev/md1. cat /etc/mdadm/mdadm.conf ... # definitions of existing MD arrays ARRAY /dev/md0 UUID=a529cd1b:c055887e:bfe78010:bc810f04 Only one array specified. That is definitely part of your problem. You should have at least two arrays specified there. mdadm --detail --scan: ARRAY /dev/md/0_0 metadata=0.90 UUID=a529cd1b:c055887e:bfe78010:bc810f04 That mdadm --scan only found one array is odd. fdisk -l Disk /dev/sda: 120.0 GB, 120033041920 bytes 255 heads, 63 sectors/track, 14593 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: 0x0002ae52 Device Boot Start End Blocks Id System /dev/sda1 1 14593 117218241 83 Linux I take it that this is your boot disk? Your boot disk is not RAID? I don't like that the first used sector is 1. That would have been 63 using the previous debian-installer to leave space for the MBR and other things. But that is a different issue. Disk /dev/sdd: 2000.4 GB, 2000398934016 bytes 255 heads, 63 sectors/track, 243201 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes That is an Advanced Format 4k sector drive. Meaning that the partitions should start on a 4k sector alignment. The debian-installer would do this automatically. Disk identifier: 0xe044b9be Device Boot Start End Blocks Id System /dev/sdd1 1 243201 1953512001 fd Linux raid autodetect ^ /dev/sde1 1 243201 1953512001 fd Linux raid autodetect ^ Partition 1 does not start on physical sector boundary. I don't recall if the first sector is 0 or 1 but I think the first sector is 0 for the partition table. Meaning that sector 1 is not going to be 4k aligned. (Can someone double check me on this?) Meaning that this will require a lot of read-modify-write causing performance problems for those drives. The new standard for sector alignment would start at 2048 to leave space for the partition table and other things and still be aligned properly. I don't know if this helps or where to go from here, but I think I need to get the mdadm up and running properly before I do anything. Probably a good idea. If there's any commands you need me to run, please ask, How are you booted now? Are you root on the system through something like the debian-installer rescue boot? Or did you use a live cd or something? Please run: # mdadm --detail /dev/sdd1 # mdadm --detail /dev/sde1 Those are what look to be the split brain of the second array. They will list something at the bottom that will look like: Number Major Minor RaidDevice State this 1 8 171 active sync /dev/sdb1 0 0 810 active sync /dev/sda1 1 1 8 171 active sync /dev/sdb1 Except in your case each will list one drive and will probably have the other drive listed as removed. But importantly it will list the UUID of the array in the listing. Magic : a914bfec Version : 0.90.00 UUID : b8eb34b1:bcd37664:2d9e4c59:117ab348 Creation Time : Fri Apr 30 17:21:12 2010 Raid Level : raid1 Used Dev Size :
Debian machine not booting
Hi, I have a debian machine which was on for a long time (~months). Just moved house and rebooted and now it doesn't boot. My 4 harddrives are organised in pairs of RAID 1 (Mirrored) with LVM spanning them. Originally there was just one pair, but then I got two new hard drives and added them. I then increased the space of VolGroup-LogVol03 to cover these new drives and increase the space of Home (/ wass on one of the other logical volume groups). This all worked fine for ages. When I boot all four drives are detected in BIOS and I've check all the connections. It gets to 3 logical volumes in volume group VolGroup now active which sounds good. Then Activating lvm and md swap.. done Checking file sysmtes...fsck from util-linux-ng 2.17.2 Says /dev/sde1: clean /dev/sda1:clean /dev/mapper/VolGroup-LogVol01: clean /dev/mapper/VolGroup-LogVol02: clean Then here's the error: fsck.ext4: No such file or directory while trying to open /dev/mapper/VolGroup-LogVol03 /dev/mapper/VolGroup-LogVol03: The superblock could not be read or does not describe a correct ext2 . NB. All partitions are Ext4, from memory. It then drops to a maintenance shell. and says to check a log (/var/log/fsck/checkfs) but I don't even have a log directory at this point in the boot process. I'm wondering if some of the drive id's have been switched. Apologies for quoting, I'm not using the computer in question. Any help would be really appreciated. I'm worried I've lost all my data on home Thanks, James
Re: Debian machine not booting
James Allsopp wrote: I have a debian machine which was on for a long time (~months). Just moved house and rebooted and now it doesn't boot. Bummer. My 4 harddrives are organised in pairs of RAID 1 (Mirrored) with LVM spanning them. Originally there was just one pair, but then I got two new hard drives and added them. I then increased the space of VolGroup-LogVol03 to cover these new drives and increase the space of Home (/ wass on one of the other logical volume groups). This all worked fine for ages. Sounds fine. Assuming that it booted after those changes. When I boot all four drives are detected in BIOS and I've check all the connections. Good. It gets to 3 logical volumes in volume group VolGroup now active which sounds good. That does sound good. Then here's the error: fsck.ext4: No such file or directory while trying to open /dev/mapper/VolGroup-LogVol03 /dev/mapper/VolGroup-LogVol03: The superblock could not be read or does not describe a correct ext2 . Hmm... I am not familiar with that error. But searching the web found several stories about it. Most concerned recent changes to the system that prevented it from booting. I have a debian machine which was on for a long time (~months). Just moved house and rebooted and now it doesn't boot. My 4 harddrives are organised in pairs of RAID 1 (Mirrored) with LVM spanning them. Originally there was just one pair, but then I got two new hard drives and added them. I then increased the space of VolGroup-LogVol03 to cover these new drives and increase the space of Home (/ wass on one of the other logical volume groups). This all worked fine for ages. And you rebooted in that time period? Otherwise these changes, if not done completely correct, seem prime to have triggered your current problem independent of any other action. You say it was on for a long time. If you had not rebooted in that long time then this may have been a hang-fire problem for all of that time. I'm wondering if some of the drive id's have been switched. If you mean the drive UUIDs then no those would not have changed. Any help would be really appreciated. I'm worried I've lost all my data on home First, do not despair. You should be able to get your system working again. You are probably simply missing the extra raid pair configuration. I strongly recommend using the debian-installer rescue mode to gain control of your system again. It works well and is readily available. Use a standard Debian installation disk. Usually we recommend the netinst disk because it is the smallest image. But any of the netinst or CD#1 or DVD#1 images will work fine for rescue mode since it is not actually installing but booting your system at that point so the difference between them does not matter. You have a disk? Go fish it out and boot it. Here is the official documentation for it: http://www.debian.org/releases/stable/i386/ch08s07.html.en But that is fairly terse. Let me say that the rescue mode looks just like the install mode initially. It will ask your keyboard and locale questions and you might wonder if you are rescuing or installing! But it will have Rescue in the upper left corner so that you can tell that you are not in install mode and be assured. Get the tool set up with keyboard, locale, timezone, and similar and eventually it will give you a menu with a list of actions. Here is a quick run-through. Advanced options... Rescue mode keyboard dialog ...starts networking... hostname dialog domainname dialog ...apt update release files... ...loading additional components, Retrieving udebs... ...detecting disks... Then eventually it will get to a menu Enter rescue mode that will ask what device to use as a root file system. It will list the partitions that it has automatically detected. If you have used a RAID then one of the menu entry items near the bottom will be Assemble RAID array and you should assemble the raid at that point. That will bring up the next dialog menu asking for partitions to assemble. Select the appropriate for your system. Then continue. Since you have two RAID configurations I think you will need to do this twice. Once for each. I believe that you won't be able to use the automatically select partitions option but not sure. In any case get both raid arrays up and online at this step before proceeding. At that point it presents a menu Execute a shell in /dev/ That should get you a shell on your system with the root partition mounted. It is a /bin/sh shell. I usually at that point start bash so as to have bash command line recall and editing. Then mount all of the additional disks. # /bin/bash root@hostname:~# mount -a At that point you have a root superuser shell on the system and can make system changes. After doing what needs doing you can reboot to the system. Remove the Debian install media and boot to the normal system and see if the changes were able
Booting Wheezy Install on Software Raid 6
Hi Folks, I'm in the process of assembling a storage system, and am running into an issue while testing the setup in a VM. The setup has 6 three terabyte harddrives that I'd like to put in RAID 6 (Eventually more will be added, expanding the array). I'd like everything to be on there, with every HD capable of booting the system. Ultimately the RAID 6 array will host an LVM partition that will be used for the whole system (unless /boot is put a separate array). I've made several attempts with the current Wheezy (testing) installer, but all have failed at installing a bootloader. I've tried using the whole disk as a RAID partition, setting up the disks with two partitions (one small one as part of a RAID 1 array for boot, the rest of the drive for the raid 6 array), and the same but with a gap at the front of the drive (I've read that Grub sometimes needs this?). Any suggestions or pointers? Most of what I've found seems to assume you have a separate boot drive. - PaulNM -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/516be3ad.6060...@paulscrap.com
Re: Booting Wheezy Install on Software Raid 6
On 15/04/13 07:25 AM, deb...@paulscrap.com wrote: Hi Folks, I'm in the process of assembling a storage system, and am running into an issue while testing the setup in a VM. The setup has 6 three terabyte harddrives that I'd like to put in RAID 6 (Eventually more will be added, expanding the array). I'd like everything to be on there, with every HD capable of booting the system. Ultimately the RAID 6 array will host an LVM partition that will be used for the whole system (unless /boot is put a separate array). I've made several attempts with the current Wheezy (testing) installer, but all have failed at installing a bootloader. I've tried using the whole disk as a RAID partition, setting up the disks with two partitions (one small one as part of a RAID 1 array for boot, the rest of the drive for the raid 6 array), and the same but with a gap at the front of the drive (I've read that Grub sometimes needs this?). Any suggestions or pointers? Most of what I've found seems to assume you have a separate boot drive. - PaulNM There are few significant differences between booting from a RAID array and booting from any other type of media. The major one I believe is that the physical boot device is actually multiple pieces of hardware. This can mean that each physical drive must be bootable and must contain the bootloader. You can ensure this by installing grub on each physical drive (/dev/sda, /dev/sdb, etc.). Should the normal boot drive fail, booting will fallback onto another drive. Wheezy can boot from RAID arrays so I recommend partitioning each drive into a single large partition and use those to create a large RAID array. You can partition this array as you like. If the boot still fails, try to track down why it is failing. /etc/mdadm/mdadm.conf should contain the UUIDs for the RAID array(s). /boot/grub/grub.cfg should have the UUID for the / partition. If you have a partitioned array, these should be different. Verify that the arrays and partitions are identified correctly. It rarely hurts to update-initramfs -u and update-grub afterwards. This will ensure that any changes you have made are reflected in the boot process (Squeeze doesn't generate the correct UUIDs for partitioned RAID arrays but Wheezy should). -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/516bf4aa.5010...@rogers.com
