Re: Need help recovering hard drive
On Sun, 09 Dec 2012 14:42:48 -0600 Dennis Wicks w...@mgssub.com wrote: Greetings; One of my hard drives quit working, and as luck would have it, just before the scheduled backup! So I need to recover some info that has been updated/added since the last backup. First, is there any thing I can do to get the system to mount that drive even with errors? As it is right now I get error messages at boot time and the drive isn't recognized. Apparently doesn't make any difference whether the drive is on controller 0 or 1 or is master or slave. Second, is there any program that I can use to get data of off that drive? TIA for any help! Dennis Hi, Dennis Have you looked at testdisk? -- 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/20121211100127.4c8cb...@speeduke.wildblue.com
Re: Laptop fan control
On Sat, 22 Dec 2012 19:33:31 +1100 Daniel Dalton d.dal...@iinet.net.au wrote: Hello, I'm using a Dell vostro 3350 machine. At times I feel the intensity of the fan is unnecessarily high. This occurs when for example using firefox or watching flash. It seems most times when I restart the gui the fan returns to normal speed. This is a concern because it obviously will effect battery life. So I'm wondering if this is unusual behaviour, and if so how to maybe correct it? I've looked at thinkafan but no idea what I'm doing to be honest. Thanks in advance for any help. Cheers, Dan Hey,Daniel Try i8kutils, Dell laptops do their own thing!! Jack -- 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/20121222113304.3e847...@speeduke.wildblue.com
Re: Moving from a proprietary OS - unnecessarily inful experience -- was [Re: I wish to advocate linux]
On Fri, 01 Mar 2013 14:37:32 -0500 Miles Fidelman mfidel...@meetinghouse.net wrote: Brian wrote: On Fri 01 Mar 2013 at 08:34:57 -0500, Miles Fidelman wrote: Fair enough, but... I have to say it Back in my day, we not only had to walk to school, uphill, in both directions, in the snow, but we also had to build our computers by hand, from TTL logic gates. :-) You had TTL logic gates? Boy, you were lucky! We were given relay switches from cast-off telephone equipment. And we had to buy our own electrodes and lemons to power the machine. Ahh yes, programmable relay logic. Still around, by the way. :-) Ok, anybody here played with really old IBM card sorters - the kind that you programmed with patch cords? (Not me, I might add.) Like an IBM 1400? 'Musing along Jack -- 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/20130301154612.7bd1a...@speeduke.wildblue.com
Printing problem jpeg file size gets multiplied???
Hi, All I have two jpeg files on my desktop. Both show correct file sizes in Properties. Running Debian Squeeze Up2date. Printer is Lexmark C540 Xl, printer properties shows connected to printer. via my local network. Using Gthumb to print, it sends to queue and hangs... never prints... Lexmark printer eventually goes to powersave mode top of list is processing Looking at queue for one image shows a file size of 25megs for a 2.2 meg jpeg file. Both file sizes seem to be up by a factor of 10 Where can I look for a start??? TIA, Jack -- 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/20110711162548.71aa765f@Speeduke
Grub2 reinstall on raid1 system.
I have a raid1 based W/S running Debian Squeeze uptodate. (was until ~7 days ago) There are 4 drives, 2 of which had never been used or formatted. I configured a new array using Disk Utility from a live Ubuntu CD. That's where I screwed up... The end result was the names of the arrays were changed on the working 2 drives. IE: /dev/md0 to /dev/126 and /dev/md1 became md127. Strangely the md2 array which I setup on the added drives remains as /dev/md2. My root partition is/was on /dev/md0. The result is that Grub2 fails to boot the / array. I have tried three REINSTALLING GRUB procedures from Sysresccd online docs and many others GNU.org, Ubuntu etc. The errors occur when I try to mount the partition with the /boot directory. 'Complains about file system type 'linux_raid_member' This machine has worked for 3 years flawlessly.. Can anyone help with this? Or point me to a place or link to get this fixed. Google doesn't help... I can't find a article/posting where it ended successfully. I have considered a full reinstall after Squeeze goes stable, since this O/S is a crufty upgrade from sarge over time. But useless now.. TIA, Jack -- 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/20110113082311.6ad80...@torrid.volunteerwireless.net
Re: Grub2 reinstall on raid1 system.
On Thu, 13 Jan 2011 17:43:53 -0500 Rob Owens row...@ptd.net wrote: On Thu, Jan 13, 2011 at 08:23:11AM -0600, Jack Schneider wrote: I have a raid1 based W/S running Debian Squeeze uptodate. (was until ~7 days ago) There are 4 drives, 2 of which had never been used or formatted. I configured a new array using Disk Utility from a live Ubuntu CD. That's where I screwed up... The end result was the names of the arrays were changed on the working 2 drives. IE: /dev/md0 to /dev/126 and /dev/md1 became md127. Strangely the md2 array which I setup on the added drives remains as /dev/md2. My root partition is/was on /dev/md0. The result is that Grub2 fails to boot the / array. I have tried three REINSTALLING GRUB procedures from Sysresccd online docs and many others GNU.org, Ubuntu etc. The errors occur when I try to mount the partition with the /boot directory. 'Complains about file system type 'linux_raid_member' This machine has worked for 3 years flawlessly.. Can anyone help with this? Or point me to a place or link to get this fixed. Google doesn't help... I can't find a article/posting where it ended successfully. I have considered a full reinstall after Squeeze goes stable, since this O/S is a crufty upgrade from sarge over time. But useless now.. You might want to try configuring grub and fstab to use UUID's instead of /dev/mdX. That removes the possibility that the kernel will change the mdX designations. Use blkid to find out the UUID's of your partitions. -Rob Thanks for the reply, Rob. What grub file do I change? grub.cfg? grub *.map? I seem to have UUIDs for both disks and LVM partitions, change both? TIA, Jack -- 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/20110114060617.5dfa8...@torrid.volunteerwireless.net
Re: Grub2 reinstall on raid1 system.
On Fri, 14 Jan 2011 06:06:17 -0600 Jack Schneider p...@dp-indexing.com wrote: On Thu, 13 Jan 2011 17:43:53 -0500 Rob Owens row...@ptd.net wrote: On Thu, Jan 13, 2011 at 08:23:11AM -0600, Jack Schneider wrote: I have a raid1 based W/S running Debian Squeeze uptodate. (was until ~7 days ago) There are 4 drives, 2 of which had never been used or formatted. I configured a new array using Disk Utility from a live Ubuntu CD. That's where I screwed up... The end result was the names of the arrays were changed on the working 2 drives. IE: /dev/md0 to /dev/126 and /dev/md1 became md127. Strangely the md2 array which I setup on the added drives remains as /dev/md2. My root partition is/was on /dev/md0. The result is that Grub2 fails to boot the / array. I have tried three REINSTALLING GRUB procedures from Sysresccd online docs and many others GNU.org, Ubuntu etc. The errors occur when I try to mount the partition with the /boot directory. 'Complains about file system type 'linux_raid_member' This machine has worked for 3 years flawlessly.. Can anyone help with this? Or point me to a place or link to get this fixed. Google doesn't help... I can't find a article/posting where it ended successfully. I have considered a full reinstall after Squeeze goes stable, since this O/S is a crufty upgrade from sarge over time. But useless now.. You might want to try configuring grub and fstab to use UUID's instead of /dev/mdX. That removes the possibility that the kernel will change the mdX designations. Use blkid to find out the UUID's of your partitions. -Rob Thanks for the reply, Rob. What grub file do I change? grub.cfg? grub *.map? I seem to have UUIDs for both disks and LVM partitions, change both? TIA, Jack Whoops!! UUIDs for Not just disks, LVM volumes RAID arrays.. Jack -- 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/20110114063014.3d4c5...@torrid.volunteerwireless.net
Re: Grub2 reinstall on raid1 system.
On Fri, 14 Jan 2011 12:16:37 -0500 Tom H tomh0...@gmail.com wrote: [BIG SNIP] You might want to try configuring grub and fstab to use UUID's instead of /dev/mdX. That removes the possibility that the kernel will change the mdX designations. Use blkid to find out the UUID's of your partitions. Thanks for the reply, Rob. What grub file do I change? grub.cfg? grub *.map? I seem to have UUIDs for both disks and LVM partitions, change both? So you have LVM over RAID, not just RAID. Hi, Tom. Well, not really, not all of the disks are LVM2. The first two disks raid1 /dev/sda /dev/sdc are partitioned with 1 small /(root) partition, /dev/md0 - 10 gigs. The balance of the disk is /dev/md1 under LVM2 with seven logical volumes. /home,/var,/swap etc The next two disks sdb and sdd are raid1 as /dev/md2 which I need to use as an extension of the LVM. More info, when I boot the machine, I see the GRUB loading. WELCOME to GRUB! info. Then it enters the rescue mode with a grub rescue prompt. So the kernel is found/finding the / partition. Right? For grub2, you're only supposed to edit /etc/default/grub. I started interpreting that as simply needing a update-grub type of fix.. I was/am wrong... So I resorted to systemrescuecd-2.0.0.. to fix up Grub.. Thanks, Jack -- 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/20110115072451.00d25...@torrid.volunteerwireless.net
Re: Grub2 reinstall on raid1 system.
On Fri, 14 Jan 2011 05:25:45 -0700 Bob Proulx b...@proulx.com wrote: Jack Schneider wrote: I have a raid1 based W/S running Debian Squeeze uptodate. (was until ~7 days ago) There are 4 drives, 2 of which had never been used or formatted. I configured a new array using Disk Utility from a live Ubuntu CD. That's where I screwed up... The end result was the names of the arrays were changed on the working 2 drives. IE: /dev/md0 to /dev/126 and /dev/md1 became md127. Something else must have happened too. Because normally just adding arrays will not rename the existing arrays. I am not familiar with the Disk Utility that you mention. Next time instead you might just use mdadm directly. It really is quite easy to create new arrays using it. Here is an example that will create a new device /dev/md9 mirrored from two other devices /dev/sdy5 and /dev/sdz5. mdadm --create /dev/md9 --level=mirror --raid-devices=2 /dev/sdy5 /dev/sdz5 This is how I created /dev/md2. Strangely the md2 array which I setup on the added drives remains as /dev/md2. My root partition is/was on /dev/md0. The result is that Grub2 fails to boot the / array. You may have to boot a rescue cd. I recommend booting the Debian install disk in rescue mode. Then you can inspect and fix the problem. But as of yet you haven't said enough to let us know what the problem might be yet. I have tried three REINSTALLING GRUB procedures from Sysresccd online docs and many others GNU.org, Ubuntu etc. This isn't encouraging. I can tell that you are grasping at straws. You have my sympathy. But unfortunately that doesn't help diagnose the problem. Remain calm. And repeat exactly the problem that you are seeing and the steps you have taken to correct it. I have not made any changes to any files on the root partition. I have only used the procedures from SystemRescueCD and then backed out. All seem to fail with the same linux_raid_member error. The errors occur when I try to mount the partition with the /boot directory. 'Complains about file system type 'linux_raid_member' I haven't seen that error before. Maybe someone else will recognize it. I don't understand why you would get an error mounting /boot that would prevent the system from coming online. Because by the time the system has booted enough to mount /boot it has already practically booted completely. The system doesn't actually need /boot mounted to boot. Grub reads the files from /boot and sets things in motion and then /etc/fstab instructs the system to mount /boot. I get that when using the live rescue disk. Usually when the root device cannot be assembled the error I see is that the system is Waiting for root filesystem and can eventually get to a recovery shell prompt. This machine has worked for 3 years flawlessly.. Can anyone help with this? Or point me to a place or link to get this fixed. Google doesn't help... I can't find a article/posting where it ended successfully. I have considered a full reinstall after Squeeze goes stable, since this O/S is a crufty upgrade from sarge over time. But useless now.. The partitions for raid volumes should be 'autodetect' 0xFD. This will enable mdadm to assemble then into raid at boot time. You can inspect the raid partitions with --detail and --examine. mdadm --examine /dev/sda1 mdadm --detail /dev/md0 That will list information about the devices. Replace with your own series of devices. I would boot a rescue image and then inspect the current configuration using the above commands. Hopefully that will show something wrong that can be fixed after you know what it is. A couple of other hints: If you are not booting a rescue system but using something like a live boot then you may need to load the kernel modules manually. You may need to load the dm_mod and md_mod modules. modprobe md_mod You might get useful information from looking at the /proc/mdstat status. cat /proc/mdstat There is a configuration file /etc/mdadm/mdadm.conf that holds the UUIDs of the configured devices. If those have become corrupted then mdadm won't be able to assemble the /dev/md* devices. Check that file and compare against what you see with the --detail output. The initrd contains a copy of the mdadm.conf file with the components needed to assemble the root filesystem. If the UUIDs change over what is recorded in the initrd then the initrd will need to be rebuilt. To do that make sure that the /etc/mdadm/mdadm.conf file is correct and then reconfigure the kernel with dpkg-reconfigure. dpkg-reconfigure linux-image-2.6.32-5-i686 Good luck! Bob Thanks, Bob I will do as you suggest shortly.. BTW, A little more info in my reply to Tom.. TIA, Jack -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive
Re: Grub2 reinstall on raid1 system.
On Sat, 15 Jan 2011 12:06:11 -0200 Henrique de Moraes Holschuh h...@debian.org wrote: On Sat, 15 Jan 2011, Jack Schneider wrote: You might want to try configuring grub and fstab to use UUID's instead of /dev/mdX. That removes the possibility that the kernel will change the mdX designations. Use blkid to find out the UUID's of your partitions. Whatever you do, NEVER use the UUIDs of partitions, use the UUID of the md devices. The worst failure scenario involving MD and idiotic tools is for a tool to cause a component device to be mounted instead of the MD array. This is one of the reasons why the new MD formats that offset the data inside the component devices exists. Thanks, Henrique!!! That gives me a new place to start this AM... Jack -- 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/20110115082823.28019...@torrid.volunteerwireless.net
Re: Grub2 reinstall on raid1 system.
On Fri, 14 Jan 2011 05:25:45 -0700 Bob Proulx b...@proulx.com wrote: Jack Schneider wrote: I have a raid1 based W/S running Debian Squeeze uptodate. (was until ~7 days ago) There are 4 drives, 2 of which had never been used or formatted. I configured a new array using Disk Utility from a live Ubuntu CD. That's where I screwed up... The end result was the names of the arrays were changed on the working 2 drives. IE: /dev/md0 to /dev/126 and /dev/md1 became md127. Something else must have happened too. Because normally just adding arrays will not rename the existing arrays. I am not familiar with the Disk Utility that you mention. Hi, Bob Thanks for your encouraging advice... As I mentioned in a prior post,Grub was leaving me at a Grub rescueprompt. I followed this procedure: http://www.gnu.org/software/grub/manual/html_node/GRUB-only-offers-a-rescue-shell.html#GRUB-only-offers-a-rescue-shell Booting now leaves me at a busy box: However the Grub menu is correct. With the correct kernels. So it appears that grub is now finding the root/boot partitions and files. Next time instead you might just use mdadm directly. It really is quite easy to create new arrays using it. Here is an example that will create a new device /dev/md9 mirrored from two other devices /dev/sdy5 and /dev/sdz5. mdadm --create /dev/md9 --level=mirror --raid-devices=2 /dev/sdy5 /dev/sdz5 Strangely the md2 array which I setup on the added drives remains as /dev/md2. My root partition is/was on /dev/md0. The result is that Grub2 fails to boot the / array. You may have to boot a rescue cd. I recommend booting the Debian install disk in rescue mode. Then you can inspect and fix the problem. But as of yet you haven't said enough to let us know what the problem might be yet. I have tried three REINSTALLING GRUB procedures from Sysresccd online docs and many others GNU.org, Ubuntu etc. This isn't encouraging. I can tell that you are grasping at straws. You have my sympathy. But unfortunately that doesn't help diagnose the problem. Remain calm. And repeat exactly the problem that you are seeing and the steps you have taken to correct it. The errors occur when I try to mount the partition with the /boot directory. 'Complains about file system type 'linux_raid_member' I haven't seen that error before. Maybe someone else will recognize it. I don't understand why you would get an error mounting /boot that would prevent the system from coming online. Because by the time the system has booted enough to mount /boot it has already practically booted completely. The system doesn't actually need /boot mounted to boot. Grub reads the files from /boot and sets things in motion and then /etc/fstab instructs the system to mount /boot. Usually when the root device cannot be assembled the error I see is that the system is Waiting for root filesystem and can eventually get to a recovery shell prompt. This machine has worked for 3 years flawlessly.. Can anyone help with this? Or point me to a place or link to get this fixed. Google doesn't help... I can't find a article/posting where it ended successfully. I have considered a full reinstall after Squeeze goes stable, since this O/S is a crufty upgrade from sarge over time. But useless now.. The partitions for raid volumes should be 'autodetect' 0xFD. This will enable mdadm to assemble then into raid at boot time. You can inspect the raid partitions with --detail and --examine. mdadm --examine /dev/sda1 mdadm --detail /dev/md0 mdadm --examine /dev/sda1 /dev/sda2 gives I think a clean result I have posted the output at : http://pastebin.com/pHpKjgK3 mdadm --detail /dev/md0 -- gives mdadm: md device /dev/md0 does not appear to be active. There is no /proc/mdstat data output. That will list information about the devices. Replace with your own series of devices. I would boot a rescue image and then inspect the current configuration using the above commands. Hopefully that will show something wrong that can be fixed after you know what it is. A couple of other hints: If you are not booting a rescue system but using something like a live boot then you may need to load the kernel modules manually. You may need to load the dm_mod and md_mod modules. modprobe md_mod You might get useful information from looking at the /proc/mdstat status. cat /proc/mdstat There is a configuration file /etc/mdadm/mdadm.conf that holds the UUIDs of the configured devices. If those have become corrupted then mdadm won't be able to assemble the /dev/md* devices. Check that file and compare against what you see with the --detail output. The initrd contains a copy of the mdadm.conf file with the components needed to assemble the root filesystem. If the UUIDs change over what is recorded in the initrd then the initrd will need to be rebuilt. To do that make
Re: Grub2 reinstall on raid1 system.
On Sat, 15 Jan 2011 16:57:46 -0700 Bob Proulx b...@proulx.com wrote: Jack Schneider wrote: Bob Proulx wrote: Jack Schneider wrote: I have a raid1 based W/S running Debian Squeeze uptodate. (was until ~7 days ago) There are 4 drives, 2 of which had never been used or formatted. I configured a new array using Disk Utility from a live Ubuntu CD. That's where I screwed up... The end result was the names of the arrays were changed on the working 2 drives. IE: /dev/md0 to /dev/126 and /dev/md1 became md127. Something else must have happened too. Because normally just adding arrays will not rename the existing arrays. I am not familiar with the Disk Utility that you mention. Hi, Bob Thanks for your encouraging advice... I believe you should be able to completely recover from the current problems. But it may be tedious and not completely trivial. You will just have to work through it. Now that there is more information available, and knowing that you are using software raid and lvm, let me guess. You added another physical extent (a new /dev/md2 partition) to the root volume group? If so that is a common problem. I have hit it myself on a number of occasions. You need to update the mdadm.conf file and rebuild the initrd. I will say more details about it as I go here in this message. As I mentioned in a prior post,Grub was leaving me at a Grub rescueprompt. I followed this procedure: http://www.gnu.org/software/grub/manual/html_node/GRUB-only-offers-a-rescue-shell.html#GRUB-only-offers-a-rescue-shell That seems reasonable. It talks about how to drive the grub boot prompt to manually set up the boot. But you were talking about using a disk utility from a live cd to configure a new array with two new drives and that is where I was thinking that you had been modifying the arrays. It sounded like it anyway. Gosh it would be a lot easier if we could just pop in for a quick peek at the system in person. But we will just have to make do with the correspondence course. :-) Booting now leaves me at a busy box: However the Grub menu is correct. With the correct kernels. So it appears that grub is now finding the root/boot partitions and files. That sounds good. Hopefully not too bad off then. Next time instead you might just use mdadm directly. It really is quite easy to create new arrays using it. Here is an example that will create a new device /dev/md9 mirrored from two other devices /dev/sdy5 and /dev/sdz5. mdadm --create /dev/md9 --level=mirror --raid-devices=2 /dev/sdy5 /dev/sdz5 Strangely the md2 array which I setup on the added drives remains as /dev/md2. My root partition is/was on /dev/md0. The result is that Grub2 fails to boot the / array. This is how I created /dev/md2. Then that explains why it didn't change. Probably the HOMEHOST parameter is involved on the ones that changed. Using mdadm from the command line doesn't set that parameter. There was just a long discussion about this topic just recently. You might want to jump into it in the middle here and read our learnings with HOMEHOST. http://lists.debian.org/debian-user/2010/12/msg01105.html mdadm --examine /dev/sda1 /dev/sda2 gives I think a clean result I have posted the output at : http://pastebin.com/pHpKjgK3 That looks good to me. And healthy and normal. Looks good to me for that part. But that is only the first partition. That is just /dev/md0. Do you have any information on the other partitions? You can look at /proc/partitions to get a list of all of the partitions that the kernel knows about. cat /proc/partitions Then you can poke at the other ones too. But it looks like the filesystems are there okay. mdadm --detail /dev/md0 -- gives mdadm: md device /dev/md0 does not appear to be active. There is no /proc/mdstat data output. So it looks like the raid data is there on the disks but that the multidevice (md) module is not starting up in the kernel. Because it isn't starting then there aren't any /dev/md* devices and no status output in /proc/mdstat. I would boot a rescue image and then inspect the current configuration using the above commands. Hopefully that will show something wrong that can be fixed after you know what it is. I still think this is the best course of action for you. Boot a rescue disk into the system and then go from there. Do you have a Debian install disk #1 or Debian netinst or other installation disk? Any of those will have a rescue system that should boot your system okay. The Debian rescue disk will automatically search for raid partitions and automatically start the md modules. So it appears that I must rebuild my arrays. I think your arrays might be fine. More information is needed. You said your boot partition was /dev/md0. I assume that your
Re: Grub2 reinstall on raid1 system.
On Sat, 15 Jan 2011 16:57:46 -0700 Bob Proulx b...@proulx.com wrote: Jack Schneider wrote: Bob Proulx wrote: Jack Schneider wrote: I have a raid1 based W/S running Debian Squeeze uptodate. (was until ~7 days ago) There are 4 drives, 2 of which had never been used or formatted. I configured a new array using Disk Utility from a live Ubuntu CD. That's where I screwed up... The end result was the names of the arrays were changed on the working 2 drives. IE: /dev/md0 to /dev/126 and /dev/md1 became md127. Something else must have happened too. Because normally just adding arrays will not rename the existing arrays. I am not familiar with the Disk Utility that you mention. Hi, Bob Thanks for your encouraging advice... I believe you should be able to completely recover from the current problems. But it may be tedious and not completely trivial. You will just have to work through it. Now that there is more information available, and knowing that you are using software raid and lvm, let me guess. You added another physical extent (a new /dev/md2 partition) to the root volume group? If so that is a common problem. I have hit it myself on a number of occasions. You need to update the mdadm.conf file and rebuild the initrd. I will say more details about it as I go here in this message. As I mentioned in a prior post,Grub was leaving me at a Grub rescueprompt. I followed this procedure: http://www.gnu.org/software/grub/manual/html_node/GRUB-only-offers-a-rescue-shell.html#GRUB-only-offers-a-rescue-shell That seems reasonable. It talks about how to drive the grub boot prompt to manually set up the boot. But you were talking about using a disk utility from a live cd to configure a new array with two new drives and that is where I was thinking that you had been modifying the arrays. It sounded like it anyway. Gosh it would be a lot easier if we could just pop in for a quick peek at the system in person. But we will just have to make do with the correspondence course. :-) Booting now leaves me at a busy box: However the Grub menu is correct. With the correct kernels. So it appears that grub is now finding the root/boot partitions and files. That sounds good. Hopefully not too bad off then. Next time instead you might just use mdadm directly. It really is quite easy to create new arrays using it. Here is an example that will create a new device /dev/md9 mirrored from two other devices /dev/sdy5 and /dev/sdz5. mdadm --create /dev/md9 --level=mirror --raid-devices=2 /dev/sdy5 /dev/sdz5 Strangely the md2 array which I setup on the added drives remains as /dev/md2. My root partition is/was on /dev/md0. The result is that Grub2 fails to boot the / array. This is how I created /dev/md2. Then that explains why it didn't change. Probably the HOMEHOST parameter is involved on the ones that changed. Using mdadm from the command line doesn't set that parameter. There was just a long discussion about this topic just recently. You might want to jump into it in the middle here and read our learnings with HOMEHOST. http://lists.debian.org/debian-user/2010/12/msg01105.html mdadm --examine /dev/sda1 /dev/sda2 gives I think a clean result I have posted the output at : http://pastebin.com/pHpKjgK3 That looks good to me. And healthy and normal. Looks good to me for that part. But that is only the first partition. That is just /dev/md0. Do you have any information on the other partitions? You can look at /proc/partitions to get a list of all of the partitions that the kernel knows about. cat /proc/partitions Then you can poke at the other ones too. But it looks like the filesystems are there okay. mdadm --detail /dev/md0 -- gives mdadm: md device /dev/md0 does not appear to be active. There is no /proc/mdstat data output. So it looks like the raid data is there on the disks but that the multidevice (md) module is not starting up in the kernel. Because it isn't starting then there aren't any /dev/md* devices and no status output in /proc/mdstat. I would boot a rescue image and then inspect the current configuration using the above commands. Hopefully that will show something wrong that can be fixed after you know what it is. I still think this is the best course of action for you. Boot a rescue disk into the system and then go from there. Do you have a Debian install disk #1 or Debian netinst or other installation disk? Any of those will have a rescue system that should boot your system okay. The Debian rescue disk will automatically search for raid partitions and automatically start the md modules. So it appears that I must rebuild my arrays. I think your arrays might be fine. More information is needed. You said your boot partition was /dev/md0. I assume that your
Re: Grub2 reinstall on raid1 system. Corrections!!!!!
On Sat, 15 Jan 2011 16:57:46 -0700 Bob Proulx b...@proulx.com wrote: Jack Schneider wrote: Bob Proulx wrote: Jack Schneider wrote: I have a raid1 based W/S running Debian Squeeze uptodate. (was until ~7 days ago) There are 4 drives, 2 of which had never been used or formatted. I configured a new array using Disk Utility from a live Ubuntu CD. That's where I screwed up... The end result was the names of the arrays were changed on the working 2 drives. IE: /dev/md0 to /dev/126 and /dev/md1 became md127. Something else must have happened too. Because normally just adding arrays will not rename the existing arrays. I am not familiar with the Disk Utility that you mention. Hi, Bob Thanks for your encouraging advice... I believe you should be able to completely recover from the current problems. But it may be tedious and not completely trivial. You will just have to work through it. Now that there is more information available, and knowing that you are using software raid and lvm, let me guess. You added another physical extent (a new /dev/md2 partition) to the root volume group? If so that is a common problem. I have hit it myself on a number of occasions. You need to update the mdadm.conf file and rebuild the initrd. I will say more details about it as I go here in this message. As I mentioned in a prior post,Grub was leaving me at a Grub rescueprompt. I followed this procedure: http://www.gnu.org/software/grub/manual/html_node/GRUB-only-offers-a-rescue-shell.html#GRUB-only-offers-a-rescue-shell That seems reasonable. It talks about how to drive the grub boot prompt to manually set up the boot. But you were talking about using a disk utility from a live cd to configure a new array with two new drives and that is where I was thinking that you had been modifying the arrays. It sounded like it anyway. Gosh it would be a lot easier if we could just pop in for a quick peek at the system in person. But we will just have to make do with the correspondence course. :-) Booting now leaves me at a busy box: However the Grub menu is correct. With the correct kernels. So it appears that grub is now finding the root/boot partitions and files. That sounds good. Hopefully not too bad off then. Next time instead you might just use mdadm directly. It really is quite easy to create new arrays using it. Here is an example that will create a new device /dev/md9 mirrored from two other devices /dev/sdy5 and /dev/sdz5. mdadm --create /dev/md9 --level=mirror --raid-devices=2 /dev/sdy5 /dev/sdz5 Strangely the md2 array which I setup on the added drives remains as /dev/md2. My root partition is/was on /dev/md0. The result is that Grub2 fails to boot the / array. This is how I created /dev/md2. Then that explains why it didn't change. Probably the HOMEHOST parameter is involved on the ones that changed. Using mdadm from the command line doesn't set that parameter. There was just a long discussion about this topic just recently. You might want to jump into it in the middle here and read our learnings with HOMEHOST. http://lists.debian.org/debian-user/2010/12/msg01105.html mdadm --examine /dev/sda1 /dev/sda2 gives I think a clean result I have posted the output at : http://pastebin.com/pHpKjgK3 That looks good to me. And healthy and normal. Looks good to me for that part. But that is only the first partition. That is just /dev/md0. Do you have any information on the other partitions? You can look at /proc/partitions to get a list of all of the partitions that the kernel knows about. cat /proc/partitions Then you can poke at the other ones too. But it looks like the filesystems are there okay. mdadm --detail /dev/md0 -- gives mdadm: md device /dev/md0 does not appear to be active. There is no /proc/mdstat data output. So it looks like the raid data is there on the disks but that the multidevice (md) module is not starting up in the kernel. Because it isn't starting then there aren't any /dev/md* devices and no status output in /proc/mdstat. I would boot a rescue image and then inspect the current configuration using the above commands. Hopefully that will show something wrong that can be fixed after you know what it is. I still think this is the best course of action for you. Boot a rescue disk into the system and then go from there. Do you have a Debian install disk #1 or Debian netinst or other installation disk? Any of those will have a rescue system that should boot your system okay. The Debian rescue disk will automatically search for raid partitions and automatically start the md modules. So it appears that I must rebuild my arrays. I think your arrays might be fine. More information is needed. You said your boot partition was /dev/md0. I assume that your
Re: Grub2 reinstall on raid1 system. Corrections!!!!!
On Sun, 16 Jan 2011 18:42:49 -0700 Bob Proulx b...@proulx.com wrote: Jack, With your pastebin information and the mdstat information (that last information in your mail and pastebins was critical good stuff) and I found this old posting from you too: :-) http://lists.debian.org/debian-user/2009/10/msg00808.html With all of that I deduce the following: /dev/md125 /dev/sda1 /dev/sdc1 (10G) root partition with no lvm /dev/md126 /dev/sda5 /dev/sdc5 (288G) LVM for /home, /var, swap, ... /dev/md127 /dev/sdb /dev/sdd (465G) as yet unformatted Jack, If that is wrong please correct me. But I think that is right. That is Exactly correct. The mdstat data showed that the arrays are sync'd. The UUIDs are as follows. ARRAY /dev/md/125_0 metadata=0.90 UUID=e45b34d8:50614884:1f1d6a6a:d9c6914c ARRAY /dev/md/126_0 metadata=0.90 UUID=c06c0ea6:5780b170:ea2fd86a:09558bd1 ARRAY /dev/md/Speeduke:2 metadata=1.2 name=Speeduke:2 UUID=91ae6046:969bad93:92136016:116577fd The desired state: /dev/md0 /dev/sda1 /dev/sdc1 (10G) root partition with no lvm /dev/md1 /dev/sda5 /dev/sdc5 (288G) LVM for /home, /var, swap, ... Will get to /dev/md2 later... My thinking is that I should rerun mdadm and reassemble the arrays to the original definitions... /md0 from sda1 sdc1 /md1 from sda5 sdc5 note: sda2 sdc2 are legacy msdos extended partitions. I would not build a md device with msdos extended partitions under LVM2 at this time.. Agree? Agreed. You want to rename the arrays. Don't touch the msdos partitions. Is the above doable? If I can figure the right mdadm commands...8-) Yes. It is doable. You can rename the array. First stop the array. Then assemble it again with the new desired name. Here is what you want to do. Tom, Henrique, others, Please double check me on these. mdadm --stop /dev/md125 mdadm --assemble /dev/md0 --update=super-minor /dev/sda1 /dev/sdc1 mdadm --stop /dev/126 mdadm --assemble /dev/md1 --update=super-minor /dev/sda5 /dev/sdc5 That should by itself be enough to get the arrays going. But, and this is an important but, did you previously add the new disk array to the LVM volume group on the above array? If so then you are not done yet. The LVM volume group won't be able to assemble without the new disk. If you did then you need to fix up LVM next. NO! I did NOT add /dev/sdb and /dev/sdd to the LVM.. So that is not a problem.. I was about to do that when the machine failed.. I think you should try to get back to where you were before when your system was working. Therefore I would remove the new disks from the LVM volume group. But I don't know if you did or did not add it yet. So I must stop here and wait for further information from you. I don't know if your rescue disk has lvm automatically configured or not. You may need to load the device mapper module dm_mod. I don't know. If you do then here is a hint: modprobe dm_mod To scan for volume groups: vgscan Found volume group Speeduke using metadata type lvm2 To activate a volume group: vgchange -ay 5 logical volume(s) in volume group Speeduke now active To display the physical volumes associated with a volume group: pvdisplay PV Name /dev/md126 VG Name Speeduke Other data ommited PV UUID kUoBgV-R9n6-exZ1-fdIk-aqlb-7Ue1-R3B1PD If the new disks haven't been added to the volume group (I am hoping not) then you should be home free. But if they are then I think you will need to remove them first. I don't know if the LVM actions above are going to be needed. I am just trying to proactively give some possible hints. Bob Bob, You cannot know how much I appreciate the time and effort you and others have given to this, hopefully a few more steps and all will be well.. I have not done the things you have suggested above. I'll wait for your response and then go!!! One other thing I am bothered by, md0, md1 were built using mdadm v0.90, md2 was built with the current mdadm v 3.1.4. which changed the md names. Does this matter Jack Jack -- 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/20110117071903.09664...@torrid.volunteerwireless.net
Re: Grub2 reinstall on raid1 system. 2nd Corrections!!!!!
On Mon, 17 Jan 2011 07:19:03 -0600 Jack Schneider p...@dp-indexing.com wrote: On Sun, 16 Jan 2011 18:42:49 -0700 Bob Proulx b...@proulx.com wrote: Jack, With your pastebin information and the mdstat information (that last information in your mail and pastebins was critical good stuff) and I found this old posting from you too: :-) http://lists.debian.org/debian-user/2009/10/msg00808.html With all of that I deduce the following: /dev/md125 /dev/sda1 /dev/sdc1 (10G) root partition with no lvm /dev/md126 /dev/sda5 /dev/sdc5 (288G) LVM for /home, /var, swap, ... /dev/md127 /dev/sdb /dev/sdd (465G) as yet unformatted Jack, If that is wrong please correct me. But I think that is right. That is Exactly correct. The mdstat data showed that the arrays are sync'd. The UUIDs are as follows. ARRAY /dev/md/125_0 metadata=0.90 UUID=e45b34d8:50614884:1f1d6a6a:d9c6914c ARRAY /dev/md/126_0 metadata=0.90 UUID=c06c0ea6:5780b170:ea2fd86a:09558bd1 ARRAY /dev/md/Speeduke:2 metadata=1.2 name=Speeduke:2 UUID=91ae6046:969bad93:92136016:116577fd The desired state: /dev/md0 /dev/sda1 /dev/sdc1 (10G) root partition with no lvm /dev/md1 /dev/sda5 /dev/sdc5 (288G) LVM for /home, /var, swap, ... Will get to /dev/md2 later... My thinking is that I should rerun mdadm and reassemble the arrays to the original definitions... /md0 from sda1 sdc1 /md1 from sda5 sdc5 note: sda2 sdc2 are legacy msdos extended partitions. I would not build a md device with msdos extended partitions under LVM2 at this time.. Agree? Agreed. You want to rename the arrays. Don't touch the msdos partitions. Is the above doable? If I can figure the right mdadm commands...8-) Yes. It is doable. You can rename the array. First stop the array. Then assemble it again with the new desired name. Here is what you want to do. Tom, Henrique, others, Please double check me on these. mdadm --stop /dev/md125 mdadm --assemble /dev/md0 --update=super-minor /dev/sda1 /dev/sdc1 mdadm --stop /dev/126 mdadm --assemble /dev/md1 --update=super-minor /dev/sda5 /dev/sdc5 That should by itself be enough to get the arrays going. But, and this is an important but, did you previously add the new disk array to the LVM volume group on the above array? If so then you are not done yet. The LVM volume group won't be able to assemble without the new disk. If you did then you need to fix up LVM next. NO! I did NOT add /dev/sdb and /dev/sdd to the LVM.. So that is not a problem.. I was about to do that when the machine failed.. I think you should try to get back to where you were before when your system was working. Therefore I would remove the new disks from the LVM volume group. But I don't know if you did or did not add it yet. So I must stop here and wait for further information from you. I don't know if your rescue disk has lvm automatically configured or not. You may need to load the device mapper module dm_mod. I don't know. If you do then here is a hint: modprobe dm_mod To scan for volume groups: vgscan Found volume group Speeduke using metadata type lvm2 To activate a volume group: vgchange -ay 5 logical volume(s) in volume group Speeduke now active To display the physical volumes associated with a volume group: pvdisplay PV Name /dev/md126 VG Name Speeduke Other data ommited PV UUID kUoBgV-R9n6-exZ1-fdIk-aqlb-7Ue1-R3B1PD If the new disks haven't been added to the volume group (I am hoping not) then you should be home free. But if they are then I think you will need to remove them first. I don't know if the LVM actions above are going to be needed. I am just trying to proactively give some possible hints. Bob Bob, You cannot know how much I appreciate the time and effort you and others have given to this, hopefully a few more steps and all will be well.. I have not done the things you have suggested above. I'll wait for your response and then go!!! One other thing I am bothered by, md0, md1 were built using md metadata v0.90, md2 was built with the current mdadm metadata v 1.3 which changed the md names. Does this matter Jack -- 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/20110117132946.06f98...@torrid.volunteerwireless.net
Re: Grub2 reinstall on raid1 system. Corrections!!!!!
On Mon, 17 Jan 2011 12:48:29 -0700 Bob Proulx b...@proulx.com wrote: Jack Schneider wrote: Bob Proulx wrote: will be well.. I have my fingers crossed for you that it will all be okay. I have not done the things you have suggested above. I'll wait for your response and then go!!! Please go ahead and do the above commands to rename the arrays and to reboot to the previous system. I believe that should work. Hope so. These things can be finicky though. One other thing I am bothered by, md0, md1 were built using mdadm v0.90, md2 was built with the current mdadm v 3.1.4. which changed the md names. Does this matter Yes. I am a little worried about that problem too. But we were at a good stopping point and I didn't want to get ahead of things. But let's assume that the above renaming of the raid arrays works and you can boot to your system again. Then what should be done about the new disks? Let me talk about the new disks. But hold off working this part of the problem until you have the first part done. Just do one thing at a time. /dev/md127 /dev/sdb /dev/sdd (465G) as yet unformatted ARRAY /dev/md/Speeduke:2 metadata=1.2 name=Speeduke:2 UUID=91ae6046:969bad93:92136016:116577fd This was created using newer metadata. I think that is going to be a problem for Lenny/Sqeeze. It says 1.2 but Lenny/Squeeze is 0.90. (A major difference is where the metadata is located. 1.0 is in a similar location to 0.90 but 1.1 and 1.2 use locations near the start of the device.) Plus you assigned the entire drive (/dev/sdb) instead of using a partition for it (/dev/sdb1). I personally don't prefer that and always set up using a partition instead of the whole disk. I am not sure the best course of action for the new disks. I suggest stopping the new array, partitioning the drives to a partion instead of the raw disk, then recreating it using the newly created partitions. Do that under your (hopefully now booting) Squeeze system and then you are assured of compatibility. It is perhaps possible that because of the new metadata that the metadata=1.2 array won't be recognized under Squeeze. I don't know. I haven't been in that situation yet. I think that would be good though because it would mean that they would just look like raw disks again without needing to stop the array, if it never got started. Then you could partition and so forth. The future is hard to see here. So that is my advice. If the new array is running then I would stop it. (mdadm --stop /dev/md127) Then partition it, partition /dev/sdb into /dev/sdb1 and /dev/sdd into /dev/sdd1. Then create the array using the new sdb1 and sdd1 partitions. Then decide how to make use of it. Note that if you add new disk to the lvm root volume group then you also need to rebuild the initrd or your system won't be able to assemble the array at boot time and will fail to boot. (Saying that mostly for people who find this in the archive later.) Bob Thanks, Bob What is the command to rebuild initrd? From what directory? Just mostly for people who find this in the archive later. 8-) Jack -- 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/20110117151918.6acbb...@torrid.volunteerwireless.net
Re: Grub2 reinstall on raid1 system. Corrections!!!!!
On Mon, 17 Jan 2011 12:48:29 -0700 Bob Proulx b...@proulx.com wrote: Jack Schneider wrote: Bob Proulx wrote: But, and this is an important but, did you previously add the new disk array to the LVM volume group on the above array? If so then you are not done yet. The LVM volume group won't be able to assemble without the new disk. If you did then you need to fix up LVM next. NO! I did NOT add /dev/sdb and /dev/sdd to the LVM.. So that is not a problem.. I was about to do that when the machine failed.. Oh good. Then you are good to go. Run these commands to stop the arrays and to reassemble them with the new names. mdadm --stop /dev/md125 mdadm --assemble /dev/md0 --update=super-minor /dev/sda1 /dev/sdc1 mdadm --stop /dev/126 mdadm --assemble /dev/md1 --update=super-minor /dev/sda5 /dev/sdc5 Then try rebooting to the system. I think at that point that all should be okay and that it should boot up into the previous system. Bob, You cannot know how much I appreciate the time and effort you and others have given to this, hopefully a few more steps and all will be well.. I have my fingers crossed for you that it will all be okay. I have not done the things you have suggested above. I'll wait for your response and then go!!! Please go ahead and do the above commands to rename the arrays and to reboot to the previous system. I believe that should work. Hope so. These things can be finicky though. One other thing I am bothered by, md0, md1 were built using mdadm v0.90, md2 was built with the current mdadm v 3.1.4. which changed the md names. Does this matter Yes. I am a little worried about that problem too. But we were at a good stopping point and I didn't want to get ahead of things. But let's assume that the above renaming of the raid arrays works and you can boot to your system again. Then what should be done about the new disks? Let me talk about the new disks. But hold off working this part of the problem until you have the first part done. Just do one thing at a time. /dev/md127 /dev/sdb /dev/sdd (465G) as yet unformatted ARRAY /dev/md/Speeduke:2 metadata=1.2 name=Speeduke:2 UUID=91ae6046:969bad93:92136016:116577fd This was created using newer metadata. I think that is going to be a problem for Lenny/Sqeeze. It says 1.2 but Lenny/Squeeze is 0.90. (A major difference is where the metadata is located. 1.0 is in a similar location to 0.90 but 1.1 and 1.2 use locations near the start of the device.) Plus you assigned the entire drive (/dev/sdb) instead of using a partition for it (/dev/sdb1). I personally don't prefer that and always set up using a partition instead of the whole disk. I am not sure the best course of action for the new disks. I suggest stopping the new array, partitioning the drives to a partion instead of the raw disk, then recreating it using the newly created partitions. Do that under your (hopefully now booting) Squeeze system and then you are assured of compatibility. It is perhaps possible that because of the new metadata that the metadata=1.2 array won't be recognized under Squeeze. I don't know. I haven't been in that situation yet. I think that would be good though because it would mean that they would just look like raw disks again without needing to stop the array, if it never got started. Then you could partition and so forth. The future is hard to see here. So that is my advice. If the new array is running then I would stop it. (mdadm --stop /dev/md127) Then partition it, partition /dev/sdb into /dev/sdb1 and /dev/sdd into /dev/sdd1. Then create the array using the new sdb1 and sdd1 partitions. Then decide how to make use of it. Note that if you add new disk to the lvm root volume group then you also need to rebuild the initrd or your system won't be able to assemble the array at boot time and will fail to boot. (Saying that mostly for people who find this in the archive later.) Bob Bob, a small glitch. mdadm:/dev/sda1 exists but is not an md array. mdadm --stop was successful, before the above. It appears that a --create-like command is needed. Looks like md125 is md0 overwritten somewhere... One of the problems of my no problem found mentality.. Jack -- 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/20110117155012.7c001...@torrid.volunteerwireless.net
Re: Grub2 reinstall on raid1 system. Corrections!!!!!
On Mon, 17 Jan 2011 15:50:12 -0600 Jack Schneider p...@dp-indexing.com wrote: On Mon, 17 Jan 2011 12:48:29 -0700 Bob Proulx b...@proulx.com wrote: Jack Schneider wrote: Bob Proulx wrote: But, and this is an important but, did you previously add the new disk array to the LVM volume group on the above array? If so then you are not done yet. The LVM volume group won't be able to assemble without the new disk. If you did then you need to fix up LVM next. NO! I did NOT add /dev/sdb and /dev/sdd to the LVM.. So that is not a problem.. I was about to do that when the machine failed.. Oh good. Then you are good to go. Run these commands to stop the arrays and to reassemble them with the new names. mdadm --stop /dev/md125 mdadm --assemble /dev/md0 --update=super-minor /dev/sda1 /dev/sdc1 mdadm --stop /dev/126 mdadm --assemble /dev/md1 --update=super-minor /dev/sda5 /dev/sdc5 Then try rebooting to the system. I think at that point that all should be okay and that it should boot up into the previous system. Bob, You cannot know how much I appreciate the time and effort you and others have given to this, hopefully a few more steps and all will be well.. I have my fingers crossed for you that it will all be okay. I have not done the things you have suggested above. I'll wait for your response and then go!!! Please go ahead and do the above commands to rename the arrays and to reboot to the previous system. I believe that should work. Hope so. These things can be finicky though. One other thing I am bothered by, md0, md1 were built using mdadm v0.90, md2 was built with the current mdadm v 3.1.4. which changed the md names. Does this matter Yes. I am a little worried about that problem too. But we were at a good stopping point and I didn't want to get ahead of things. But let's assume that the above renaming of the raid arrays works and you can boot to your system again. Then what should be done about the new disks? Let me talk about the new disks. But hold off working this part of the problem until you have the first part done. Just do one thing at a time. /dev/md127 /dev/sdb /dev/sdd (465G) as yet unformatted ARRAY /dev/md/Speeduke:2 metadata=1.2 name=Speeduke:2 UUID=91ae6046:969bad93:92136016:116577fd This was created using newer metadata. I think that is going to be a problem for Lenny/Sqeeze. It says 1.2 but Lenny/Squeeze is 0.90. (A major difference is where the metadata is located. 1.0 is in a similar location to 0.90 but 1.1 and 1.2 use locations near the start of the device.) Plus you assigned the entire drive (/dev/sdb) instead of using a partition for it (/dev/sdb1). I personally don't prefer that and always set up using a partition instead of the whole disk. I am not sure the best course of action for the new disks. I suggest stopping the new array, partitioning the drives to a partion instead of the raw disk, then recreating it using the newly created partitions. Do that under your (hopefully now booting) Squeeze system and then you are assured of compatibility. It is perhaps possible that because of the new metadata that the metadata=1.2 array won't be recognized under Squeeze. I don't know. I haven't been in that situation yet. I think that would be good though because it would mean that they would just look like raw disks again without needing to stop the array, if it never got started. Then you could partition and so forth. The future is hard to see here. So that is my advice. If the new array is running then I would stop it. (mdadm --stop /dev/md127) Then partition it, partition /dev/sdb into /dev/sdb1 and /dev/sdd into /dev/sdd1. Then create the array using the new sdb1 and sdd1 partitions. Then decide how to make use of it. Note that if you add new disk to the lvm root volume group then you also need to rebuild the initrd or your system won't be able to assemble the array at boot time and will fail to boot. (Saying that mostly for people who find this in the archive later.) Bob Bob, a small glitch. mdadm:/dev/sda1 exists but is not an md array. mdadm --stop was successful, before the above. It appears that a --create-like command is needed. Looks like md125 is md0 overwritten somewhere... One of the problems of my no problem found mentality.. Jack Additionally, maybe I'm in the wrong config. Running from a sysrescuecd. I do have a current Debian-AMD64-rescue-live cd. Which I made this AM. I need to find out what's there... further: Can I execute the mdadm commands from a su out of a busybox prompt? Jack -- 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
Re: Grub2 reinstall on raid1 system. Corrections!!!!!
On Mon, 17 Jan 2011 20:43:16 -0700 Bob Proulx b...@proulx.com wrote: Jack Schneider wrote: Bob Proulx wrote: mdadm --stop /dev/md125 mdadm --assemble /dev/md0 --update=super-minor /dev/sda1 /dev/sdc1 mdadm --stop /dev/126 mdadm --assemble /dev/md1 --update=super-minor /dev/sda5 /dev/sdc5 Bob, a small glitch. mdadm:/dev/sda1 exists but is not an md array. mdadm --stop was successful, before the above. If mdadm --stop was successful then it must have been an array before that point. So that doesn't make sense. Double check everything. mdadm --examine /dev/sda1 mdadm --examine /dev/sdc1 mdadm --detail /dev/md0 It appears that a --create-like command is needed. Looks like md125 is md0 overwritten somewhere... If you create an array it will destroy the data that is on the array. Unless you want to discard your data you don't want to do that. You want to assemble an array from the components. That is an important distinction. You really want to be able to assemble the array. Do so with one disk only if that is the only way (would need the mdadm forcing options to start an array without all of the components) and then add the other disk back in. But if the array was up a moment before then it should still be okay. So I am suspicious about the problem. Poke around a little more with --examine and --detail first. Something does seem right. Additionally, maybe I'm in the wrong config. Running from a sysrescuecd. I do have a current Debian-AMD64-rescue-live cd. Which I made this AM. That would definitely improve things. Because then you will have compatible versions of all of the tools. Is your system amd64? Yes, a Supermicro X7DAL-E M/B with dual XEON quad core 3.2 ghz processors and 4 Seagate Barracuda drives. 8 gigs of Ram. I need to find out what's there... further: Can I execute the mdadm commands from a su out of a busybox prompt? If you are in a busybox prompt at boot time then you are already root and don't need an explicit 'su'. You should be able to execute root commands. The question is whether the mdadm command is available at that point. The reason for busybox is that it is a self-contained set of small unix commands. 'mdadm' isn't one of those and so probably isn't available. Normally you can edit files and the like. Normally I would mount and chroot to the system. But you don't yet have a system. So that is problematic at that point. Bob This AM when I booted, (I powerdown init 0 each PM to save power hassle from S/O) the machine did not come up with grub-rescue prompt. It booted to the correct grub menu then to Busy Box. I am thinking it goes to BB because it can't find /var and or /usr on the md1/sda5 LVM partition. I checked /proc/mdstat and lo behold there was md1:active with correct partitions and md0: active also correct partitions... I must have been seeing md125 et al from only the sysrescuecd 2.0.0. So here I sit with a root prompt from Busy Box I checked mdadm --examine for all known partitions and mdadm --detail /mdo /md1 and all seems normal and correct. No Errors. I seem to need a way of rerunning grub-install or update-grub to fix this setup. What say you?? I am thinking of trying to start the /etc/grub.d demon. Jack -- 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/20110118081441.6a807...@torrid.volunteerwireless.net
Re: Grub2 reinstall on raid1 system.
On Mon, 17 Jan 2011 20:43:16 -0700 Bob Proulx b...@proulx.com wrote: Jack Schneider wrote: Bob Proulx wrote: mdadm --stop /dev/md125 mdadm --assemble /dev/md0 --update=super-minor /dev/sda1 /dev/sdc1 mdadm --stop /dev/126 mdadm --assemble /dev/md1 --update=super-minor /dev/sda5 /dev/sdc5 Bob, a small glitch. mdadm:/dev/sda1 exists but is not an md array. mdadm --stop was successful, before the above. If mdadm --stop was successful then it must have been an array before that point. So that doesn't make sense. Double check everything. mdadm --examine /dev/sda1 mdadm --examine /dev/sdc1 mdadm --detail /dev/md0 It appears that a --create-like command is needed. Looks like md125 is md0 overwritten somewhere... If you create an array it will destroy the data that is on the array. Unless you want to discard your data you don't want to do that. You want to assemble an array from the components. That is an important distinction. You really want to be able to assemble the array. Do so with one disk only if that is the only way (would need the mdadm forcing options to start an array without all of the components) and then add the other disk back in. But if the array was up a moment before then it should still be okay. So I am suspicious about the problem. Poke around a little more with --examine and --detail first. Something does seem right. Additionally, maybe I'm in the wrong config. Running from a sysrescuecd. I do have a current Debian-AMD64-rescue-live cd. Which I made this AM. That would definitely improve things. Because then you will have compatible versions of all of the tools. Is your system amd64? I need to find out what's there... further: Can I execute the mdadm commands from a su out of a busybox prompt? If you are in a busybox prompt at boot time then you are already root and don't need an explicit 'su'. You should be able to execute root commands. The question is whether the mdadm command is available at that point. The reason for busybox is that it is a self-contained set of small unix commands. 'mdadm' isn't one of those and so probably isn't available. Normally you can edit files and the like. Normally I would mount and chroot to the system. But you don't yet have a system. So that is problematic at that point. Bob Bob, MORE! Both /etc/fstab and /etc/mtab show entries for /dev/md126.. What the ... ? Jack -- 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/20110118084217.0e9ed...@torrid.volunteerwireless.net
Re: Grub2 reinstall on raid1 system.
On Tue, 18 Jan 2011 16:19:11 -0200 Henrique de Moraes Holschuh h...@debian.org wrote: On Tue, 18 Jan 2011, Jack Schneider wrote: Both /etc/fstab and /etc/mtab show entries for /dev/md126.. What the ... ? After you modified thei files in the real filesystem, did you update the initramfs? Hi, Henrique I have not modified any files a yet. I never got to the mdadm --assemble because of the mdadm:/dev/sda1 exists but is not an md array. ERROR! The curious question that exists is why were md125,md126, created when I tried to build the /dev/md2 array. The only difference is the versions of mdadm used 3 years ago and ~10 days ago TIA Jack -- 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/20110118132038.4cad8...@torrid.volunteerwireless.net
Re: Grub2 reinstall on raid1 system.
On Tue, 18 Jan 2011 17:31:29 -0700 Bob Proulx b...@proulx.com wrote: Jack Schneider wrote: It booted to the correct grub menu then to Busy Box. I am thinking it goes to BB because it can't find /var and or /usr on the md1/sda5 LVM partition. Very likely. I checked /proc/mdstat and lo behold there was md1:active with correct partitions and md0: active also correct partitions... That is good news to hear. Becuase it should mean that all of your data is okay on those disks. That is always a comfort to know. So here I sit with a root prompt from Busy Box I checked mdadm --examine for all known partitions and mdadm --detail /mdo /md1 and all seems normal and correct. No Errors. Yeah! :-) Both /etc/fstab and /etc/mtab show entries for /dev/md126.. What the ... ? That does seem strange. Could the tool you used previously have edited that file? You said you were using /dev/md1 as an lvm volume for /var, /home, swap and other. As I read this it means you would only have /dev/md0 for /boot in your /etc/fstab. Right? Something like this from my system: /dev/md0/boot ext2defaults0 2 You /var, /home and swap would use the lvm, right? So from my system I have the following: /dev/mapper/v1-var /var ext3defaults0 2 /dev/mapper/v1-home /home ext3defaults0 2 Those don't mention /dev/md1 (which showed up for you as /dev/md126) at all. They would only show up in the volume group display. If you are seeing /dev/md126 in /etc/fstab then it is conflicting information. You will have to sort out the information conflict. Do you really have LVM in there? Certainly if the /dev/md0 /boot boot line is incorrect then you should correct it. Edit the file and fix it. If your filesystem is mounted read-only at that point you will need to remount it read-write. mount -n -o remount,rw / Bob Hi, Bob Back at it...8-( I think I found a significant glitch.. I appears that mdadm is confused. I think it happened when I created the /dev/md2 array from the new disks. It looks like the metadata 1.2 vs 0.90 configs is the culprit... Here's the output of: mdadm --detail --scan: ARRAY /dev/md0 metadata=0.90 UUID=e45b34d8:50614884:1f1d6a6a:d9c6914c ARRAY /dev/md1 metadata=0.90 UUID=c06c0ea6:5780b170:ea2fd86a:09558bd1 Here's the output of /etc/mdadm/mdadm.conf: # mdadm.conf # # Please refer to mdadm.conf(5) for information about this file. # # by default, scan all partitions (/proc/partitions) for MD superblocks. # alternatively, specify devices to scan, using wildcards if desired. DEVICE partitions # auto-create devices with Debian standard permissions CREATE owner=root group=disk mode=0660 auto=yes # automatically tag new arrays as belonging to the local system HOMEHOST system # instruct the monitoring daemon where to send mail alerts MAILADDR root # definitions of existing MD arrays ARRAY /dev/md/0 metadata=1.2 UUID=f6de5584:d9dbce39:090f16ff:f795e54c name=hetzner:0 ARRAY /dev/md/1 metadata=1.2 UUID=0e065fee:15dea43e:f4ed7183:70d519bd name=hetzner:1 ARRAY /dev/md/2 metadata=1.2 UUID=ce4dd5a8:d8c2fdf4:4612713e:06047473 name=hetzner:2 # This file was auto-generated on Mon, 10 Jan 2011 00:32:59 + # by mkconf 3.1.4-1+8efb9d1 Given that the metadata from 0.90 1.2 cannot be on each md0 and md1 at the same time. Although they are on different places on the disks IIRC. Something needs to change... I am thinking of an mdadm.conf edit. But there maybe an alternative tool or approach... This was obtained using my Debian-live amd64 rescue disk. TIA Jack -- 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/20110121195115.3e62f...@torrid.volunteerwireless.net
Re: Grub2 reinstall on raid1 system.
On Sat, 22 Jan 2011 04:54:32 -0500 Tom H tomh0...@gmail.com wrote: On Fri, Jan 21, 2011 at 8:51 PM, Jack Schneider p...@dp-indexing.com wrote: I think I found a significant glitch.. I appears that mdadm is confused. I think it happened when I created the /dev/md2 array from the new disks. It looks like the metadata 1.2 vs 0.90 configs is the culprit... Here's the output of: mdadm --detail --scan: ARRAY /dev/md0 metadata=0.90 UUID=e45b34d8:50614884:1f1d6a6a:d9c6914c ARRAY /dev/md1 metadata=0.90 UUID=c06c0ea6:5780b170:ea2fd86a:09558bd1 Here's the output of /etc/mdadm/mdadm.conf: DEVICE partitions CREATE owner=root group=disk mode=0660 auto=yes HOMEHOST system MAILADDR root ARRAY /dev/md/0 metadata=1.2 UUID=f6de5584:d9dbce39:090f16ff:f795e54c name=hetzner:0 ARRAY /dev/md/1 metadata=1.2 UUID=0e065fee:15dea43e:f4ed7183:70d519bd name=hetzner:1 ARRAY /dev/md/2 metadata=1.2 UUID=ce4dd5a8:d8c2fdf4:4612713e:06047473 name=hetzner:2 Given that the metadata from 0.90 1.2 cannot be on each md0 and md1 at the same time. Although they are on different places on the disks IIRC. Something needs to change... I am thinking of an mdadm.conf edit. But there maybe an alternative tool or approach... This was obtained using my Debian-live amd64 rescue disk. Check your partitions' metadata with mdadm --examine --scan --config=partitions. Those'll be the settings that you'll need in mdadm.conf. Thanks, Tom A couple of small ?s. I can get the output of the command on the live file system and it appears to make sense. I am running on a debian-live amd64 O/S. The data has 4 arrays and I only have 3, there are two entries for the new empty disks /dev/md/2 and /dev/md127. They don't appear in /proc/mdstat, so they are not running. Do I need to kill them permanently some how? I need, I think, to get the info to the mdadm.conf on the real /dev/sda1 /dev/sdc1 partitions. Mount them on the live system and edit mdadm.conf??? When I reboot, I'll need the right info... chroot?? TIA Jack -- 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/20110122072452.0a4b5...@torrid.volunteerwireless.net
Re: Difficulty installing Debian 6.0.0 on an old computer
On Thu, 10 Feb 2011 00:29:44 + Brian a...@cityscape.co.uk wrote: On Wed 09 Feb 2011 at 18:13:54 -0600, Jason Hsu wrote: Thanks, Brian, I'll try installing Lenny and then upgrading. If I still have trouble with Squeeze, then I'll have to stick with Lenny until I buy a somewhat newer computer that doesn't have problems with the Debian Squeeze CD. As it happens I used PLOP and a usb stick to install Squeeze on one machine. The netinst.iso was put on to the stick using cat netinst.iso /dev/sdX If the Squeeze installer and your machine don't get on it may not help you - but you never know. If you can try burning the ISO on a CD-R media some OLD optical drives can't handle the newer media, also burn at lowest speeds.. FWIW Jack -- 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/20110211164006.36347...@torrid.volunteerwireless.net
Window Borders Disappear
Hi, folks I have lost my Desktop window borders. I am using Debian lenny updated. Problem occurred after an abortedattempt to install Compiz.. I get the following error from theSystempreferenceswindows menu.. Cannot start the preferences application for your window manager.Window manager unknown has not registered a configuration tool.. Any help would be great... J ack
Re: Cannot boot from root lvm volume: lvm2 broken?
On Wed, 26 Mar 2008 20:32:50 +0100 Benjamin Kircher [EMAIL PROTECTED] wrote: Hi there, need some advice over here. Installed Etch from netinstall iso and upgraded to sid, which works flawlessly. All partitions except /boot are in a LVM group (even my root fs is a LVM volume). Then I removed (more precise: purged) 2.6.18-5-486 kernel in favor of 2.6.24-1-686. After running a update-initramfs -u and a shutdown -r now my box fails to boot up. It complains: (nah nah nah, a lot of this not and a lot of that not, neh neh ney) ... /scripts/local-top/lvm2: line 68 tr not found /scripts/local-top/lvm2: line 68 sed not found (I guess, this part of the script tries to activate my volume group) ... /proc/mounts: fopen %s failed: No such file or directory Failed to create lvm type filter Waiting for root file system ... ... which my box never gets. Hereafter it throws me to a very limited shell. Indeed, /proc and /dev are empty ;( Google isn't my friend: A search found no similar messages like this. There are no bugs listed for the lvm2 package which describes this behavior nor are there any recent changes in the /scripts/local-top/lvm2 script. Any clues from you guys on how to proceed and hunting down this issue? Thanks in advance, Benjamin Hi, Did you update grub (if that's what your using)? grub install? or edit at boot? Jack -- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Aptitude Abnormality
Hi, All Minor problem... I thinks 8-) Just noted an error/warning during an install, as follows: database /var/lib/apt/listchanges.db failed to load Install completed OK. My Sys_Info: Debian Lenny Linux Speeduke 2.6.24-1-amd64 #1 SMP Thu Mar 27 16:52:38 UTC 2008 x86_64 GNU/Linux What does it mean? Besides the obvious..-- Is it serious? How do I fix? What's needed? Thanks, Jack -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Aptitude Abnormality
Thanks, for the reply. On Tue, 22 Apr 2008 03:34:05 +0200 (CEST) s. keeling [EMAIL PROTECTED] wrote: Jack Schneider [EMAIL PROTECTED]: Minor problem... I thinks 8-) Just noted an error/warning during an install, as follows: database /var/lib/apt/listchanges.db failed to load Install completed OK. My Sys_Info: Debian Lenny Linux Speeduke 2.6.24-1-amd64 #1 SMP Thu Mar 27 16:52:38 UTC 2008 x86_64 GNU/Linux What does it mean? Besides the obvious..-- It looks like a non-fatal warning from apt-listchanges. Is it serious? What's apt-listchanges do when you install something, or does this happen on every install? Yes,this seems to happen on every install How do I fix? What's needed? Can't help there, sorry. Does /var/lib/apt/listchanges.db exist? [EMAIL PROTECTED]:~$ du -h /var/lib/apt/listchanges.db 12K /var/lib/apt/listchanges.db So the file seems to be there... What next coach? -- Jack -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Window Borders Disappear
On Tue, 2007-11-20 at 10:26 -0500, Michael Pobega wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tue, Nov 20, 2007 at 02:42:09PM +, Jack Schneider wrote: Hi, folks I have lost my Desktop window borders. I am using Debian lenny updated. Problem occurred after an abortedattempt to install Compiz.. I get the following error from theSystempreferenceswindows menu.. Cannot start the preferences application for your window manager.Window manager unknown has not registered a configuration tool.. Any help would be great... J ack Why don't you try aptitude reinstall metacity? That may work. - -- If programmers deserve to be rewarded for creating innovative programs, by the same token they deserve to be punished if they restrict the use of these programs. - Richard Stallman -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFHQvyeg6qL2BGnx4QRAtJ6AKCpsifzfjb0qwef2H+NznSRjDl0OACeJkTY tOqFhYDUm23ZvY4iFkdMHAM= =+Nhg -END PGP SIGNATURE- Thanks, for the reply... I did the # aptitude reinstall metacity thing and regretably no change... It really makes it painfull to have all windows in upper left corner with no size or position control... What could be plan b??? Thanks, again Jack -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Window Borders Disappear
On Tue, 2007-11-20 at 20:59 -0800, Daniel Burrows wrote: On Tue, Nov 20, 2007 at 09:06:59PM -0600, Jack Schneider [EMAIL PROTECTED] was heard to say: On Tue, 2007-11-20 at 10:26 -0500, Michael Pobega wrote: On Tue, Nov 20, 2007 at 02:42:09PM +, Jack Schneider wrote: I have lost my Desktop window borders. I am using Debian lenny updated. Problem occurred after an abortedattempt to install Compiz.. I get the following error from theSystempreferenceswindows menu.. Cannot start the preferences application for your window manager.Window manager unknown has not registered a configuration tool.. Any help would be great... J ack Why don't you try aptitude reinstall metacity? That may work. Thanks, for the reply... I did the # aptitude reinstall metacity thing and regretably no change... It really makes it painfull to have all windows in upper left corner with no size or position control... What could be plan b??? If you can get access to the windows themselves: does running metacity from a terminal help? If that complains that another window manager is running, try metacity --replace. I think you have to save the Gnome session after that if it works, but I don't remember what the Gnome voodoo for saving a session is. Daniel Thanks, Daniel, That helps.. I now have window's with borders on current screen , after running: sudo metacity --replace. I get an error though!! [Window manager warning: Failed to load theme Clearlooks: Failed to find a valid file for theme Clearlooks] and I am not sure this condition will be there at next login Re: Andrei's question.. How did you try to install compiz? Please detail your steps, maybe we can find a way to revert what has been done. Since it's been a couple of day's, this is best that I can recall. I run a NVIDIA Geforce 8600GT video card. So There were some howto's on the (I think) Debian-Compiz wiki. calling for some changes to xorg.conf under etch. I run lenny but the same video driver as I did under etch, NVIDIA 100.14.19 so I added the suggested changes...via $ sudo vim /etc/X11/xorg.conf. I recall a addtion entry to the device' section and a new extensions entry... then I used # aptitude install compiz to load Compiz. It installed with out error... I then logged out and in. and that's where the problem happened... I PANICed ! I was able to use a xterm OK so I replaced the xorg.conf from xorg.conf.bak and # aptitude remove compizOK. That didnt help. Then I asked for help This is the best I can remember...Memory is slipping as I get older...really old...8-( Thanks, to both of you... Jack -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Window Borders Disappear
On Wed, 2007-11-21 at 09:42 -0500, Michael Pobega wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tue, Nov 20, 2007 at 09:06:59PM -0600, Jack Schneider wrote: On Tue, 2007-11-20 at 10:26 -0500, Michael Pobega wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tue, Nov 20, 2007 at 02:42:09PM +, Jack Schneider wrote: Hi, folks I have lost my Desktop window borders. I am using Debian lenny updated. Problem occurred after an abortedattempt to install Compiz.. I get the following error from theSystempreferenceswindows menu.. Cannot start the preferences application for your window manager.Window manager unknown has not registered a configuration tool.. Any help would be great... J ack Why don't you try aptitude reinstall metacity? That may work. aptitude purge metacity aptitude install metacity (If this gives you dependency errors reinstall everything else as well). - Have'nt done this yet,but A little more info... what might everything else entail I'm guessing you mean whatever dependency errors occur... Thanks, Jack -- If programmers deserve to be rewaeverything elserded for creating innovative programs, by the same token they deserve to be punished if they restrict the use of these programs. - Richard Stallman -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFHREPYg6qL2BGnx4QRAo2OAJ9gwixc9HYCiMilJzpZCc6nafQHggCgh+hR +v9JR9ivQJuhWsrphNWSgRw= =L+S7 -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Window Borders Disappear
On Wed, 2007-11-21 at 09:42 -0500, Michael Pobega wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tue, Nov 20, 2007 at 09:06:59PM -0600, Jack Schneider wrote: On Tue, 2007-11-20 at 10:26 -0500, Michael Pobega wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tue, Nov 20, 2007 at 02:42:09PM +, Jack Schneider wrote: Hi, folks I have lost my Desktop window borders. I am using Debian lenny updated. Problem occurred after an abortedattempt to install Compiz.. I get the following error from theSystempreferenceswindows menu.. Cannot start the preferences application for your window manager.Window manager unknown has not registered a configuration tool.. Any help would be great... J ack Why don't you try aptitude reinstall metacity? That may work. aptitude purge metacity aptitude install metacity (If this gives you dependency errors reinstall everything else as well). - -- If programmers deserve to be rewarded for creating innovative programs, by the same token they deserve to be punished if they restrict the use of these programs. - Richard Stallman -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFHREPYg6qL2BGnx4QRAo2OAJ9gwixc9HYCiMilJzpZCc6nafQHggCgh+hR +v9JR9ivQJuhWsrphNWSgRw= =L+S7 -END PGP SIGNATURE- Hi, Michael Tried it, purge reinstall, log out in -- No Change... Only way to get borders back is $ metacity --replacethat works... FYI Jack ps plan C ??? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
NO mail from Debian lists..
Hi, Anyone seeing mail??? Jack -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Corrupted Gnome terminal ( reposted from debian-amd64)
Hi, all I screwed up my Gnome Terminal setup some how... on my workstation desktop. My system: Debian Lenny Kernel: 2.6.22-3-amd64 Video: Nvidia 8600 GT Video Drv. NVIDIA 169.07 My Problems: Gnome terminal has unreadable fonts..TOO small. The terminal will not close, when clicking on X, and cntrl++ will not work. Xterm seems to work. OK /var/log/Xorg.0.log has one failure: (EE) Failed to load module type1 (module does not exist, 0) I created a new user, and the Gnome terminal on that Desktop works normally..OK So it seems I have a hidden file screwed up on my desktop... Anyone have a idea what folder i should replace??? or what/where I should look or go from here??? I have been struggling for several days and come up blank from Archive and Google. Thanks, in advance.. Jack -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Installation upgrade errors--- HELP
Hi, All Does anyone have a recommendation as to: what do I do with this error??? [EMAIL PROTECTED]:/home/jack# apt-get install Reading Package Lists... Done Building Dependency Tree... Done 0 upgraded, 0 newly installed, 0 to remove and 478 not upgraded. 3 not fully installed or removed. Need to get 0B of archives. After unpacking 0B of additional disk space will be used. Setting up cron (3.0pl1-81) ... Adding group crontab (106)... groupadd: unable to lock group file addgroup: `/usr/sbin/groupadd -g 106 crontab' returned error code 10. Aborting. Cleaning up. dpkg: error processing cron (--configure): subprocess post-installation script returned error exit status 1 dpkg: dependency problems prevent configuration of logrotate: logrotate depends on cron (= 3.0pl1-53) | anacron; however: Package cron is not configured yet. Package anacron is not installed. dpkg: error processing logrotate (--configure): dependency problems - leaving unconfigured dpkg: dependency problems prevent configuration of adminmenu: adminmenu depends on logrotate; however: Package logrotate is not configured yet. dpkg: error processing adminmenu (--configure): dependency problems - leaving unconfigured Errors were encountered while processing: cron logrotate adminmenu E: Sub-process /usr/bin/dpkg returned an error code (1) [EMAIL PROTECTED]:/home/jack# Thanks, if you can help! Thanks anyway. Jack -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: xorg update clobbers Nvidia GL
On Sat, 16 Aug 2008 13:57:51 -0500 Ron Johnson [EMAIL PROTECTED] wrote: On 08/16/08 12:57, Patrick Wiseman wrote: Hello: It seems every time xorg is updated it clobbers my Nvidia driver and, all of a sudden, those cool GLX screen savers, not to mention Google Earth (a mission-critical application!) don't work. If I use nvidia-installer to UNinstall the drivers, it tells me '/usr/lib/xorg/modules/extensions/libglx.so is not a symbolic link', whereas, right after installing the nvidia drivers, it IS. So, what I'm wondering is whether there's any way to protect a symbolic link from being overwritten. Ordinarily, if I want to protect a file, I'll make it read- or read-and-execute-only, but a symbolic link is always 'lrwxrwxrwx' and 'chmod 555 link' just changes the permissions on the underlying file. Perhaps that will protect the link from being replaced with a file, but I'm not confident! A hack solution would be simply to rename the underlying file to the link name and make THAT unwritable, but I think that might confuse the nvidia installer. Any suggestions will be welcome. After any xorg update, I go into /usr/lib/xorg/modules/extensions and manually symlink the nvidia libglx.so.XXX.YY.ZZ to libglx.so. Hey, Ron Does yours look like this??? lrwxrwxrwx 1 root root 19 2008-07-13 16:25 libglx.so - libglx.so.173.14.09 Sorry about the highjack!!! Jack -- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
BUSY BOX after boot attempt..
-- Hi, all I created my own problem. I think! I have a dual boot Dell M60 laptop. Running Lenny, linux kernel 2.6.26-1-686. I have/had a small primary (hda3) as /boot. A larger logical (hda2) with / (hda5) and /home (hda6) + Swap (hda7). hda1 is XP. I used GRML 1.1 iso and gparted to resize/move /boot to 5X intial size. because with kernel changes, I had low disk space errors. All seemed to go well. No errors. When I rebooted back to lenny on hdd I get the BusyBox prompt. I get the GRUB window OK. I see what looks like errors as follows, Mount: No such file or directory. (Three times) Target filesystem doesn't have /sbin/init No init found, Try parsing init= bootarg I don't know where to go next... Thanks in advance... Jack -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: BUSY BOX after boot attempt..
On Wed, 10 Sep 2008 01:30:15 +0300 Andrei Popescu [EMAIL PROTECTED] wrote: On Tue,09.Sep.08, 16:00:11, Jack Schneider wrote: -- Hi, all I created my own problem. I think! I have a dual boot Dell M60 laptop. Running Lenny, linux kernel 2.6.26-1-686. I have/had a small primary (hda3) as /boot. A larger logical (hda2) with / (hda5) and /home (hda6) + Swap (hda7). hda1 is XP. I used GRML 1.1 iso and gparted to resize/move /boot to 5X intial size. because with kernel changes, I had low disk space errors. All seemed to go well. No errors. When I rebooted back to lenny on hdd I get the BusyBox prompt. I get the GRUB window OK. I see what looks like errors as follows, Mount: No such file or directory. (Three times) Target filesystem doesn't have /sbin/init No init found, Try parsing init= bootarg I don't know where to go next... I've had cases where changes in partitioning has changed the partition numbers. Boot your GRML and check what the correct numbers are. In case of any doubt use labels. Regards, Andrei -- Thanks, Andrei for the response. Checked out #s and yes they have changed. So I need some further guidance... In case of any doubt use labels. Any pointers to an appropriate howto Question 2 What's the impact on FSTAB settings? Thanks, again. Jack -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: BUSY BOX after boot attempt..
On Thu, 11 Sep 2008 00:52:30 +0300
Andrei Popescu [EMAIL PROTECTED] wrote:
On Wed,10.Sep.08, 14:24:07, Jack Schneider wrote:
Thanks, Andrei for the response. Checked out #s and yes they have
changed.
So I need some further guidance... In case of any doubt use
labels. Any pointers to an appropriate howto Question
2 What's the impact on FSTAB settings?
Thanks, again.
Here's a (very quick) howto:
* use e2label to create labels for all your partition:
This is done by mounting the drive somewhere under grml?
Since I can't boot the OS with the current partition #s.
Seems tricky..8-( since I know less of GRML than lenny...I however
can get to a bash term # window. 8-)
e2label /dev/hdaX root_part
(where 'root_part' is the label for the root partition and /dev/hdaX
is the device name of the root partition. Use whatever naming scheme
you want).
* edit /boot/grub/menu.lst and change the line
/boot is on a separate partition, which I will have labeled. Will I
have a problem mounting /boot under grml?? say with
~# mount /dev/hda3 /mnt ?? cd mnt then edit /boot/grub/menu.lst
# kopt=root=/dev/hda5 ro (other boot options)
to
# kopt=root=LABEL=root_part ro (other boot options)
* also edit the stanza that you will boot and replace
'root=/dev/hda5' with 'root=LABEL=root_part'
* edit /etc/fstab and change all references to the device (/dev/hda5,
...) with LABEL={label}
* reboot
If it doesn't, then what?
* run /usr/sbin/update-grub to regenerate /boot/grub/menu.lst to use
the label everywhere.
Regards,
Andrei
--
The power of Debian-Users is earth-shaking.
Have a great day!
Jack
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Best methods?
Hi, all Just noticed that the results of doing [dpkg --get-selections Packages] gives me a list which includes-- 194 packages marked for deinstall'. What's the best tool to clean this up, and how to do it?? TIA, Jack -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Best methods?
On Thu, 18 Sep 2008 22:44:56 +0200 Sven Joachim [EMAIL PROTECTED] wrote: On 2008-09-18 22:34 +0200, Andrei Popescu wrote: On Thu,18.Sep.08, 15:18:37, Jack Schneider wrote: Hi, all Just noticed that the results of doing [dpkg --get-selections Packages] gives me a list which includes-- 194 packages marked for deinstall'. What's the best tool to clean this up, and how to do it?? Don't ever ask what the best method is, there are just too many of them. Here's the first I can think of: grep -v deinstall file new_file This gives a list without these packages, but I assume that Jack's goal is to get rid of (= purge) the packages themselves. Sven Hi, all Thanks for all the guides. Andrei, deliberately done. I read this list.. Sven has the key.. My / partition is growing beyond 80% 0f 10 Gig, so I thought there may be some junk in there, /home /var /tmp are on separate partitions.. OK This machine is a noob's (me) upgrade from i386 etch to lenny -AMD64 -update over the past year. I'll re-read responses and choose... Thanks.. -- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: anyone installed nvidia drivers on etch recently?
On Fri, 03 Oct 2008 18:21:18 +0100 Adam Hardy [EMAIL PROTECTED] wrote: I'm suffering from repeated crashes in my Eclipse IDE, which is java. Restarting it is slow and losing work is never much fun anyway, but I thought I'd find a solution until now. I have 4 approaches to the problem: - upgrade java (done that, now on the latest release of JDK 1.5, 1.5.0_16) - upgrade Eclipse (worst approach, might require me to do a dev environment re-install) - upgrade Etch to latest packages (done that) - upgrade the nvidia driver (trying and failing). I'm using nv, so I thought I'd try the proprietary nvidia driver. Following any of the methods on http://wiki.debian.org/NvidiaGraphicsDrivers just leads me down the same path to the point where I find nvidia.ko failed to build in the logs. I'm using the stock kernel 2.6.26-bpo.1-686 from apt, and trying to get the nvidia-glx-legacy nvidia-kernel-common nvidia-kernel-legacy-2.6-686 packages from non-free to install, but using the instruction: m-a auto-install nvidia leads to the error nvidia.ko failed build, as I mentioned above. The other methods outlined on the wiki fail similarly. The executable download directly from nvidia.com has the same problem. Is this whole thing with the proprietary driver a bad idea or just something that won't work until I get lenny? Thanks Adam Take a look at this link: -- http://tinyplanet.ca/~lsorense/debian/debian-nvidia-dri-howto.html Thanks to Len Sorenson for keeping me straight...8-) Jack -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: anyone installed nvidia drivers on etch recently?
On Sat, 04 Oct 2008 15:24:16 +0100 Adam Hardy [EMAIL PROTECTED] wrote: Jack Schneider on 04/10/08 03:46, wrote: On Fri, 03 Oct 2008 18:21:18 +0100 Adam Hardy [EMAIL PROTECTED] wrote: I'm using nv, so I thought I'd try the proprietary nvidia driver. Following any of the methods on http://wiki.debian.org/NvidiaGraphicsDrivers just leads me down the same path to the point where I find nvidia.ko failed to build in the logs. I'm using the stock kernel 2.6.26-bpo.1-686 from apt, and trying to get the nvidia-glx-legacy nvidia-kernel-common nvidia-kernel-legacy-2.6-686 packages from non-free to install, but using the instruction: m-a auto-install nvidia leads to the error nvidia.ko failed build, as I mentioned above. Take a look at this link: -- http://tinyplanet.ca/~lsorense/debian/debian-nvidia-dri-howto.html I followed those instructions to the letter with no success. It was good in that it was definitive about whether I should be using legacy or not, however the only other main difference from the wiki article was the m-a command: m-a a-i -i -t -f nvidia-kernel-source which made no difference to the end result of the nvidia.ko build. I think it's something to do with v 2.6.26-bpo.1-686 Is that the kernel version you're running too? Regards Adam Hi. Adam :~$ uname -r 2.6.26-1-amd64 May be the difference... Send Len a query...He's super helpful... [EMAIL PROTECTED] Have a great day... Jack -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: House wireless/wired router: choices? Plus wireless neophyte questions.
On Sat, 4 Oct 2008 08:58:41 +0300 Andrei Popescu [EMAIL PROTECTED] wrote: On Fri,03.Oct.08, 01:46:48, Chris Metzler wrote: [...] One detail not mentioned here was that you should use WPA2 encryption to protect your wireless network. WEP is easy to crack with standard Linux tools. As far as I recall the XP version of the other OS needs at least SP2 (or was that SP3?) to use WPA2. As for choice of wireless routers, I have used a D-Link DI-524 for a while with no problems (using the standard firmware). That box is now at my mom's house and I'm planning on getting the Asus WL-500g Premium, which has a lot of nice features, but is more expensive. Maybe it would be interesting for you to look for a model with integrated DSL modem? Regards, Andrei -- Andrei, Doesn't WPA2 require access to a Radius server..? My Cisco seems to... Jack -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: (nautilus:3241): Unique-DBus-WARNING **: Error while sending message: Did not receive a reply.
On Sat, 1 Aug 2009 13:21:33 -0400 Rick Thomas rbthoma...@pobox.com wrote: On Aug 1, 2009, at 5:28 AM, Leonardo Gaudino wrote: I experience the same problem (only difference is nautilus:3645, whatever it means...). A pop-up message appears while loading the session showing that phrase. The strangest is that everything does work fine. This happens only at the first login: if i terminate the session and login again no errors pop up. Debian testing, kernel 2.6.30-bpo.1-686, gnome 2.26.1 Leonardo Check your ~/.xsession-errors file. I have two machines that are having this problem. On one, I get the same popup you do, but I get it every time I log in. The other one, I don't get the popup, but it shows up in the .xsession-errors file instead. Both of my machines are PowerPC Macs. How about you? And yes, everything seems to be working fine. Very curious! Rick Me Too!!! only different: 8-( This is on my desktop at startup: There was an error starting the GNOME Settings Daemon Some things, such as themes, sounds, or background settings may not work correctly. The last error message was: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. GNOME will still try to restart the Settings Daemon next time you log in. Looks somthing like a dbus like error.. Keep me informed... Nothing else seems broken.. Jack -- -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Virtualbox Lenny Guest - Screen resize and Seamless mode
On Mon, 03 Aug 2009 16:33:32 -0500 Mark Allums m...@allums.com wrote: Chris wrote: On Monday 03 August 2009, go...@dobosevic.com wrote: Chris wrote: I am trying to get Screen resize and Seamless mode working on Lenny guest systems to no avail. I have tried insalling the guest-utils packages, as well as the guest-additions the manual way with m-a. They install fine, but sreen-resize and seamless mode don't work. Does anyone have this working at all? I've tried various xorg.conf files with the video driver and no screen resolutions. I am running virtualbox-ose 2.1.4 from lenny-backports on the host. Thanks, Chris I also have same problem. I have Debian Sid LXDE, Debian Sid XFCE and Debian Sid KDE as a guest. They were first Lenny and screen size was to big so I was edit xorg.conf and it was fine. After upgrade to Sid all of them have to small screen with black frame around (800x600 on 15 laptop, native resolution is 1024x768). Editing xorg.conf doesn't help any more. Bye, Goran Dobosevic Hrvatski: www.dobosevic.com English: www.dobosevic.com/en/ Lets see if anyone has it working! I have some SIDUX guests (09-01, 09-02) that work... I have the same problem. An update to xorg occuring at approximately the same time as an upgrade of VirtualBox has caused VBox to turn off dynamic resizing, and nothing I can think of will bring it back. Editing xorg.conf is futile. Reinstalling the additions does nothing. The screen resolutions allowed are 800x600 or 640x480. It is very frustrating. Mark Allums Hi, folks I'm running VirtualBox 3.0.2 not the Debian -OSE edition, but downloaded from the Sun Site.. Sun has precipitated a good number of changes, Guest Additions work much better... I have resized windows in M$, SuSE, without incident. uname -r 2.6.26-2-amd64 FWIW Jack -- -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Virtualbox Lenny Guest - Screen resize and Seamless mode
On Mon, 03 Aug 2009 21:11:49 -0500 Mark Allums m...@allums.com wrote: Jack Schneider wrote: On Mon, 03 Aug 2009 16:33:32 -0500 Mark Allums m...@allums.com wrote: Chris wrote: On Monday 03 August 2009, go...@dobosevic.com wrote: Chris wrote: I am trying to get Screen resize and Seamless mode working on Lenny guest systems to no avail. I have tried insalling the guest-utils packages, as well as the guest-additions the manual way with m-a. They install fine, but sreen-resize and seamless mode don't work. Does anyone have this working at all? I've tried various xorg.conf files with the video driver and no screen resolutions. I am running virtualbox-ose 2.1.4 from lenny-backports on the host. Thanks, Chris I also have same problem. I have Debian Sid LXDE, Debian Sid XFCE and Debian Sid KDE as a guest. They were first Lenny and screen size was to big so I was edit xorg.conf and it was fine. After upgrade to Sid all of them have to small screen with black frame around (800x600 on 15 laptop, native resolution is 1024x768). Editing xorg.conf doesn't help any more. Bye, Goran Dobosevic Hrvatski: www.dobosevic.com English: www.dobosevic.com/en/ Lets see if anyone has it working! I have some SIDUX guests (09-01, 09-02) that work... I have the same problem. An update to xorg occuring at approximately the same time as an upgrade of VirtualBox has caused VBox to turn off dynamic resizing, and nothing I can think of will bring it back. Editing xorg.conf is futile. Reinstalling the additions does nothing. The screen resolutions allowed are 800x600 or 640x480. It is very frustrating. Mark Allums Hi, folks I'm running VirtualBox 3.0.2 not the Debian -OSE edition, but downloaded from the Sun Site.. Sun has precipitated a good number of changes, Guest Additions work much better... I have resized windows in M$, SuSE, without incident. uname -r 2.6.26-2-amd64 FWIW Jack I am Vista 64 SP2, VBox 3.0.2 (non-free), Debian amd64 guest, Squeeze with a few Sid bits. This includes Sid X.org, GNOME, and GCC 4.3.3, with Debian kernel 2.6.30-1 (which is Sid version of 2.6.30.5). # uname -a Linux patricia 2.6.30-1-amd64 #1 SMP Mon Aug 3 12:28:22 UTC 2009 x86_64 GNU/Linux Mark Allums Mark, sorry I didn't mention it, I run Debian Squeeze as host... Jack -- -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Musings on debian-user list
On Mon, 03 Aug 2009 21:54:56 -0400 Chris Jones cjns1...@gmail.com wrote: On Mon, Aug 03, 2009 at 08:20:58PM EDT, John Hasler wrote: Chris Jones writes: I guess so.. though I'm not sure about the usefulness thereof, save for demo'ing the flexibility of, what's the word.. Window Managers..? Organization. I can have an FVWM desktop with a couple of dozen panes for each of umpteen projects. I can then, for rxample, switch quickly from the environment where I am working on Chrony, with a couple of Emacs instances, a debugger, an xterm running tail -f on a log, etc, to the desktop where I am studing music theory and have Noteedit, Solfege, etc running. Yes John, but why would one need all shapes of xterms with extraordinary dimensions to achieve this..? I mean, most terminal screen-oriented apps assume some form of 4:3 geometry to begin with.. If you need the editor, a shell, a debugger, and a log tail displaying concurrently on the one physical screen to achieve what you are working one faster and more effectively, fine.. but as I hinted above, I suspect that in most circumstances, having all that stuff visible on the same display is often a case of showing off one's environment.. screenshot feed, no more.. Sounds like you're talking IDE.. but correct me if I'm wrong, doesn't text-mode emacs provide all of this, and more - even on a barebones linux console..?? But never mind, what I really was saying is that I'm as much of an idiot as the next guy for wasting huge amounts of time to set up, modify, etc. my computing interface.. and all the same I often feel that better folks than myself do not care too much about such aspects. I mean.. I'm a mediocre hobbyist programmer, trying to make some sense of some C code that clearly shows its age, via vim and gdb.. Now, do I really need, am I really going to keep an eye on, half a dozen five line xterms that tail all my system's logs while I chug along..? In my case the tradeoff at this point is to have whatever I'm working on full screen - with some form of split/windowed display when useful.. and a minimal one-line last (status in gnu/screen parlance..) line of the screen display a bunch of automatically refreshed counters that provide me with a summary of what's going on in my system.. as much as I can grasp in one eyeful. And naturally use different X desktops in order to instantly switch to a different environment as necessary. Thanks, CJ Chris, I've found Compiz-fusion useful to keep multiple things going.. ctrl-alt-- giving a new desktop quickly... YMMV. Jack -- -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: usb floppy, image files
On Thu, 20 Aug 2009 09:08:26 -0400 Hugh Lawson hlaw...@triad.rr.com wrote: Hello Debian Users, I'm looking for a program like 'dd' that can copy image files to a USB floppy drive. I've done some googling without success. Hugh Lawson Did you you look @ clonezilla-live ?? http://www.clonezilla.org/ FWIW, Jack -- -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Which programming Language
On Tue, 10 Feb 2009 12:45:49 -0600 Ron Johnson ron.l.john...@cox.net wrote: On 02/10/2009 12:32 PM, Mark Allums wrote: Ron Johnson wrote: Readability and maintainability of assembly language. Yep. The (CISC) VAX instruction set was designed partly with assembly programmers in mind (and also to map closely to FORTRAN and COBOL instructions), and the (macro, natch) assembler is designed with HLL features. The Motorola 68000 series was allegedly designed partly with C in mind. Patterned after the PDP-11 (), and DEC always liked orthogonal CISC chips. http://en.wikipedia.org/wiki/Motorola_68000#History The MACSS team drew heavily on the influence of minicomputer processor design, such as the PDP-11 and VAX systems, which were similarly microcoded. Hey, Ron Due to Obama's intent to automate medical records, do you think that it may be helpful to get out the old MUMPS(M) docs? Never got it's place in the sun. But still in use at the GOV! Thinks I may have them on DECtape! 8-) Jack -- -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Which programming Language
On Tue, 10 Feb 2009 17:42:15 -0600 Ron Johnson ron.l.john...@cox.net wrote: On 02/10/2009 04:55 PM, Jack Schneider wrote: [snip] Due to Obama's intent to automate medical records, do you think that it I don't think his ultimate purpose is hackable medical records, but that's another story... may be helpful to get out the old MUMPS(M) docs? Never got it's place in the sun. But still in use at the GOV! Thinks I may have them on DECtape! 8-) Found this via Google: http://www.vistasoftware.org/presentations/VSA-What_Is_VistA_080406.pdf Hooray! Now I know of two incompatible systems named VISTA!!! Have a great evening! Jack -- -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: [OT] Friday the 13th
On Wed, 11 Feb 2009 11:29:37 + David Jardine da...@jardine.de wrote: On Wed, Feb 11, 2009 at 05:17:47AM -0600, Dave Sherohman wrote: [...] No, I think the much better idea would be to ditch timezones and put the whole world on UTC. Get rid of DST and 12-hour clocks, too, while you're at it. There is absolutely no real benefit to having the clock say 7am when you wake up and 11pm when you go to sleep instead of (assuming UTC-6) waking up at 1:00 (which, remember, represents the same actual time as is currently called 7am in that timezone), working 3-12, and going to bed at 19:00. And whatever happened to decimalisation? Hi,folks We are probably the only entities in the universe who spend so much energy keeping track of the number of times our planet spins. How bazaar! Jack -- -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: [OT] Friday the 13th
On Wed, 11 Feb 2009 08:06:36 -0600 Ron Johnson ron.l.john...@cox.net wrote: On 02/11/2009 07:47 AM, Jack Schneider wrote: [snip] We are probably the only entities in the universe who spend so much energy keeping track of the number of times our planet spins. How bazaar! How can you make such a comment when you have *no clue* as to what any other entity does? RE: probably Jack -- -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: [OT] Friday the 13th
On Wed, 11 Feb 2009 07:05:10 -0800 Marc Shapiro mshapiro...@yahoo.com wrote: Jack Schneider wrote: We are probably the only entities in the universe who spend so much energy keeping track of the number of times our planet spins. How bazaar! Or, how bizarre. Bazaar goes with 'The Cathedral and the. Sorry to nitpick, but I could resist. Thanks! Never was good at spellin Jack -- -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: [OT] Friday the 13th
On Wed, 11 Feb 2009 09:12:21 -0600
Ron Johnson ron.l.john...@cox.net wrote:
On 02/11/2009 08:32 AM, Jack Schneider wrote:
On Wed, 11 Feb 2009 08:06:36 -0600
Ron Johnson ron.l.john...@cox.net wrote:
On 02/11/2009 07:47 AM, Jack Schneider wrote:
[snip]
We are probably the only entities in the universe who spend so
much energy keeping track of the number of times our planet spins.
How bazaar!
How can you make such a comment when you have *no clue* as to what
any other entity does?
RE: probably
From WordNet (r) 3.0 (2006) [wn]:
probably
adv 1: with considerable certainty; without much doubt; He is
probably out of the country; in all likelihood we are
headed for war [syn: {probably}, {likely}, {in all
likelihood}, {in all probability}, {belike}]
2: easy to believe on the basis of available evidence; he
talked plausibly before the committee; he will probably win
the election [syn: {credibly}, {believably}, {plausibly},
{probably}] [ant: {implausibly}, {improbably}, {incredibly},
{unbelievably}]
Based on these definitions, your statement is a fallacy:
(Logic) An argument, or apparent argument, which professes
to be decisive of the matter at issue, while in reality it
is not; a sophism.
1/6,759,846,988
Jack
--
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: [OT] Friday the 13th
On Sun, 15 Feb 2009 19:28:45 -0800 Marc Shapiro mshapiro...@yahoo.com wrote: Celejar wrote: On Sat, 14 Feb 2009 10:13:15 -0800 Marc Shapiro mshapiro...@yahoo.com wrote: On Wed, Feb 11, 2009 at 03:16:49PM +, Avi Greenbury wrote: Marc Shapiro wrote: Jack Schneider wrote: We are probably the only entities in the universe who spend so much energy keeping track of the number of times our planet spins. How bazaar! Or, how bizarre. Bazaar goes with 'The Cathedral and the. Sorry to nitpick, but I could resist. What's the name of that law that states that any post pointing out someone's mistake will always include a typo of its own? Avi, Are you referring to my mismatched single and double quotes? Or is there something else that I am not seeing? You wrote could resist rather than couldn't resist. Ah! I missed it when I wrote the post, and again, when you commented. We are always our own worst proofreaders. BIZARRE! Jack -- -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: how does GRUB read from /boot on software-RAID partition?
On Tue, 24 Feb 2009 15:21:23 -0500 Barclay, Daniel dan...@fgm.com wrote: Eduardo M KALINOWSKI wrote: Barclay, Daniel wrote: ... Since GRUB hasn't loaded the kernel file yet, GRUB can't be using the kernel and its md driver, and therefore can't be reading the partition _as_a_RAID_ _volume_ (/dev/mdX), right? So is GRUB just reading the partition directly to get to the file system? GRUB does not know anything about RAID, so I assume this is true. That's what I have been thinking, but I just found the message at http://www.mail-archive.com/linux-r...@vger.kernel.org/msg09712.html that says:: ... once grub2 has determined that the intended boot partition is a raid partition, the raid code takes over ... and it scans for all the other members of the raid array and utilizes whichever drives it needs to in order to complete the boot process. ... [I]t doesn't need any member of a raid1 array to be perfect[;] it will attempt a round robin read on all the sectors and only fail if all drives return an error for a given read. Is that _just_ for GRUB2 and or does the current GRUB (0.97) in Lenny also do that? ... is GRUB taking advantage of the fact that the RAID metadata is written at the end of a partition ... ... If so, how reliable is that? Should one put /boot on a plain, non-RAID partition on one disk and somehow (manually or automatically) maintain a backup /boot partition on the second disk, or is it fine to put /boot on a mirrored partition (so maintaining redundancy is automatic) and let GRUB read the partition directly? Again, while I haven't tried, I've seen several reports that this works. ... So why make things more complicated and not automatic? I don't get why you're asking that. I _am_ trying to avoid the complicated and non-automatic solution (trying to check whether the simpler solution is reliable). Daniel Hi, Daniel et al The following is an outline of my setup on a couple of the system disks. Roughly I have two md devices for the host system, md0 md1: j...@host:~$ df -m Filesystem 1M-blocks Used Available Use% Mounted on /dev/md0 9389 7157 1755 81% / tmpfs 4005 1 4005 1% /lib/init/rw udev10 110 2% /dev tmpfs 4005 0 4005 0% /dev/shm /dev/dm-040318 11628 26642 31% /home /dev/dm-419686 15356 3331 83% /home/jack/XP_VDI /dev/dm-630238 7453 21250 26% /home/jack/suse /dev/dm-2 302470 2802 3% /tmp /dev/dm-1 8064 3426 4229 45% /var /dev/hda9090 0 100% /media/cdrom0 The only concern I have is that / is marginally small. It's expandable tho. /boot is just on /mdo. I have run without incident for over a year. Provides sufficient isolation from my bumbling around... 8-) FWIW. Jack . -- -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: how does GRUB read from /boot on software-RAID partition?
On Tue, 24 Feb 2009 17:14:54 -0500 Barclay, Daniel dan...@fgm.com wrote: Jack Schneider wrote: On Tue, 24 Feb 2009 15:21:23 -0500 Barclay, Daniel dan...@fgm.com wrote: Eduardo M KALINOWSKI wrote: Barclay, Daniel wrote: ... ... is GRUB taking advantage of the fact that the RAID metadata is written at the end of a partition ... ... If so, how reliable is that? Should one put /boot on a plain, non-RAID partition on one disk and ...maintain a backup /boot partition on the second disk, or is it fine to put /boot on a mirrored partition (so maintaining redundancy is automatic) and let GRUB read the partition directly? ... why make things more complicated and not automatic? ... I _am_ trying to avoid the complicated and non-automatic solution (trying to check whether the simpler solution is reliable). ... Hi, Daniel et al The following is an outline of my setup on a couple of the system disks. Roughly I have two md devices for the host system, md0 md1: j...@host:~$ df -m Filesystem 1M-blocks Used Available Use% Mounted on /dev/md0 9389 7157 1755 81% / tmpfs 4005 1 4005 1% /lib/init/rw udev10 110 2% /dev tmpfs 4005 0 4005 0% /dev/shm /dev/dm-040318 11628 26642 31% /home /dev/dm-419686 15356 3331 83% /home/jack/XP_VDI /dev/dm-630238 7453 21250 26% /home/jack/suse /dev/dm-2 3024 70 2802 3% /tmp /dev/dm-1 8064 3426 4229 45% /var /dev/hda90 90 0 100% /media/cdrom0 The only concern I have is that / is marginally small. It's expandable tho. /boot is just on /mdo. I have run without incident for over a year. But if you haven't had any disk-failure incidents, do you know whether your setup will reliably work if either disk fails? (Did you mean that you simulated disk failure?) Daniel Hi, Daniel Sorry, no failures to date. My thinking was since I was running testing I didn't want updates/bugs/my ineptitude to trash my data and other OS. This config allows me to change easily... of course I'm a Debian nooby. I can boot from either disk. I pulled a sata cable from one. Jack -- -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Issue with URL and firefox (iceweasel)
On Fri, 17 Oct 2008 09:05:17 +0200 Mathieu Malaterre [EMAIL PROTECTED] wrote: Hi there, If I click on the following URLs: * http://gdcm.svn.sourceforge.net/gdcm/?rev=4628view=rev * http://gdcm.svn.sourceforge.net/gdcm/?rev=4627view=rev I can get a 404 error on the second one, however if I copy/paste them directly in the URL bar, both appears to be working fine. I can reproduce on firefox 3.0 2.0 on debian testing/stable. Could someone please try and report ? thank you, They both work for me... Lenny AMD64 FF 3.0.3 Have a great day! Jack -- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Nvidia, apt-get Synaptic
On Tue, 28 Oct 2008 11:52:43 -0500 MLewis [EMAIL PROTECTED] wrote: I'm new to the list and Debian, but not new to Linux. I have been running RH for 10+ years and recently was very impressed with Debian and decided to make the switch. Congrats to the team that puts Debian together, it looks like a well thought out distribution. Also, thanks much for an update method that doesn't require a six-pack to get through. I'm running Lenny Beta2. Two questions: Nvidia - I have an Nvidia Geforce 6600LE video card in my machine. I understand that it is better to run 'nvidia' or 'nv' drivers than to get the binaries from Nvidia (However no glx mode). I have looked for the nv nvidia drivers on my machine and apparently do not have them: rattler:/etc/postfix$ dpkg -S nv.ko linux-image-2.6.26-1-686: /lib/modules/2.6.26-1-686/kernel/drivers/ata/sata_nv.ko rattler:/etc/postfix$ dpkg -S nvidia.ko dpkg: *nvidia.ko* not found. I've tried dpkg-reconfigure xserver-xorg but that didn't help either. What package do I need to install to get the nv nvidia drivers? Synaptic vs apt-get: Is there a difference in these two packages other than one is a GUI and one is CLI? If so, is one method preferred over the other? Thanks, Mike Hi, Mike Try this link : http://tinyplanet.ca/~lsorense/debian/debian-nvidia-dri-howto.html Len watches this list so you might ask him if you have further questions Jack -- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Broken flashplayer installation.
Hi, all. Debian lenny Linux Speeduke 2.6.26-1-amd64 #1 SMP Thu Oct 9 14:16:53 UTC 2008 x86_64 GNU/Linux -- I get the following errors from Synaptic when trying to reinstall flashplayer-mozilla. RE: E: /var/cache/apt/archives/ia32-libs-libidn11_1.10-0.0_amd64.deb: trying to overwrite `/emul/ia32-linux/usr/lib/libidn.so.11.5.39', which is also in package libidn11-emul E: /var/cache/apt/archives/ia32-libs-libssh2_0.18-0.0_amd64.deb: trying to overwrite `/emul/ia32-linux/usr/lib/libssh2.so.1.0.0', which is also in package libssh2-1-emul E: /var/cache/apt/archives/ia32-libs-libcurl3_7.18.2-0.0_amd64.deb: trying to overwrite `/emul/ia32-linux/usr/lib/libcurl.so.4.1.0', which is also in package libcurl3-emul E: /var/cache/apt/archives/ia32-libs-libnspr4_4.7.1-0.1_amd64.deb: trying to overwrite `/emul/ia32-linux/usr/lib/libplds4.so.0d', which is also in package libnspr4-0d-emul E: /var/cache/apt/archives/ia32-libs-libnss3_3.12.0-0.1_amd64.deb: trying to overwrite `/emul/ia32-linux/usr/lib/libssl3.so.1d', which is also in package libnss3-1d-emul I don't know what the /emul/* stuff is or where it came from... How do I get started fixing this...?? TIA Jack -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: [OT] Broken flashplayer installation.
On Tue, 18 Nov 2008 14:18:55 -0600 Stackpole, Chris [EMAIL PROTECTED] wrote: From: Jack Schneider [mailto:[EMAIL PROTECTED] Sent: Tuesday, November 18, 2008 2:01 PM Subject: Broken flashplayer installation. Hi, all. Debian lenny Linux Speeduke 2.6.26-1-amd64 #1 SMP Thu Oct 9 14:16:53 UTC 2008 x86_64 GNU/Linux -- I get the following errors from Synaptic when trying to reinstall flashplayer-mozilla. RE: E: /var/cache/apt/archives/ia32-libs-libidn11_1.10-0.0_amd64.deb: trying to overwrite `/emul/ia32-linux/usr/lib/libidn.so.11.5.39', which is also in package libidn11-emul E: /var/cache/apt/archives/ia32-libs-libssh2_0.18-0.0_amd64.deb: trying to overwrite `/emul/ia32-linux/usr/lib/libssh2.so.1.0.0', which is also in package libssh2-1-emul E: /var/cache/apt/archives/ia32-libs-libcurl3_7.18.2-0.0_amd64.deb: trying to overwrite `/emul/ia32-linux/usr/lib/libcurl.so.4.1.0', which is also in package libcurl3-emul E: /var/cache/apt/archives/ia32-libs-libnspr4_4.7.1-0.1_amd64.deb: trying to overwrite `/emul/ia32-linux/usr/lib/libplds4.so.0d', which is also in package libnspr4-0d-emul E: /var/cache/apt/archives/ia32-libs-libnss3_3.12.0-0.1_amd64.deb: trying to overwrite `/emul/ia32-linux/usr/lib/libssl3.so.1d', which is also in package libnss3-1d-emul I don't know what the /emul/* stuff is or where it came from... How do I get started fixing this...?? TIA Jack This is probably not the answer you were expecting, so I labeled it Off Topic. Have you looked into the new 64bit version from Adobe? http://labs.adobe.com/technologies/flashplayer10/ I had many problems with getting 32bit flash working right. I ended up getting something usable, but nothing satisfactory. Adobe still claims that the 64bit version is Alpha and it was only released yesterday but I have not had any issues with it yet. I have already seen a noticeable decrease in system resources while getting much better performance. The 32bit wrapper would take minutes to load a youtube video and would crash if I skipped around too much. None of those issues so far with the 64bit version. All of the sites I visit work without problem (YMMV of course). I have 2 64bit Debian Lenny systems with flash. So far 0 problems with the 64bit flash player 10. It is something you might want to consider. Have fun! ~S~ Thanks, Chris I am off to see the (that) wizard... That may help... alot. Jack -- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: [OT] Broken flashplayer installation.
On Tue, 18 Nov 2008 14:18:55 -0600 Stackpole, Chris [EMAIL PROTECTED] wrote: From: Jack Schneider [mailto:[EMAIL PROTECTED] Sent: Tuesday, November 18, 2008 2:01 PM Subject: Broken flashplayer installation. Hi, all. Debian lenny Linux Speeduke 2.6.26-1-amd64 #1 SMP Thu Oct 9 14:16:53 UTC 2008 x86_64 GNU/Linux -- I get the following errors from Synaptic when trying to reinstall flashplayer-mozilla. RE: E: /var/cache/apt/archives/ia32-libs-libidn11_1.10-0.0_amd64.deb: trying to overwrite `/emul/ia32-linux/usr/lib/libidn.so.11.5.39', which is also in package libidn11-emul E: /var/cache/apt/archives/ia32-libs-libssh2_0.18-0.0_amd64.deb: trying to overwrite `/emul/ia32-linux/usr/lib/libssh2.so.1.0.0', which is also in package libssh2-1-emul E: /var/cache/apt/archives/ia32-libs-libcurl3_7.18.2-0.0_amd64.deb: trying to overwrite `/emul/ia32-linux/usr/lib/libcurl.so.4.1.0', which is also in package libcurl3-emul E: /var/cache/apt/archives/ia32-libs-libnspr4_4.7.1-0.1_amd64.deb: trying to overwrite `/emul/ia32-linux/usr/lib/libplds4.so.0d', which is also in package libnspr4-0d-emul E: /var/cache/apt/archives/ia32-libs-libnss3_3.12.0-0.1_amd64.deb: trying to overwrite `/emul/ia32-linux/usr/lib/libssl3.so.1d', which is also in package libnss3-1d-emul I don't know what the /emul/* stuff is or where it came from... How do I get started fixing this...?? TIA Jack This is probably not the answer you were expecting, so I labeled it Off Topic. Have you looked into the new 64bit version from Adobe? http://labs.adobe.com/technologies/flashplayer10/ I had many problems with getting 32bit flash working right. I ended up getting something usable, but nothing satisfactory. Adobe still claims that the 64bit version is Alpha and it was only released yesterday but I have not had any issues with it yet. I have already seen a noticeable decrease in system resources while getting much better performance. The 32bit wrapper would take minutes to load a youtube video and would crash if I skipped around too much. None of those issues so far with the 64bit version. All of the sites I visit work without problem (YMMV of course). I have 2 64bit Debian Lenny systems with flash. So far 0 problems with the 64bit flash player 10. It is something you might want to consider. Have fun! ~S~ Hi, Chris Got the libflashplayer.so.So where exactly do I put it??? FWIW, just spent a few minutes removing the 32bit stuff... Thanks again! Jack -- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: [OT] Broken flashplayer installation.
On Tue, 18 Nov 2008 15:13:18 -0600 Stackpole, Chris [EMAIL PROTECTED] wrote: From: Jack Schneider [mailto:[EMAIL PROTECTED] Sent: Tuesday, November 18, 2008 3:02 PM Subject: Re: [OT] Broken flashplayer installation. On Tue, 18 Nov 2008 14:18:55 -0600 Stackpole, Chris [EMAIL PROTECTED] wrote: From: Jack Schneider [mailto:[EMAIL PROTECTED] Sent: Tuesday, November 18, 2008 2:01 PM Subject: Broken flashplayer installation. Hi, all. Debian lenny Linux Speeduke 2.6.26-1-amd64 #1 SMP Thu Oct 9 14:16:53 UTC 2008 x86_64 GNU/Linux -- I get the following errors from Synaptic when trying to reinstall flashplayer-mozilla. RE: E: /var/cache/apt/archives/ia32-libs-libidn11_1.10-0.0_amd64.deb: trying to overwrite `/emul/ia32-linux/usr/lib/libidn.so.11.5.39', which is also in package libidn11-emul E: /var/cache/apt/archives/ia32-libs-libssh2_0.18-0.0_amd64.deb: trying to overwrite `/emul/ia32-linux/usr/lib/libssh2.so.1.0.0', which is also in package libssh2-1-emul E: /var/cache/apt/archives/ia32-libs-libcurl3_7.18.2-0.0_amd64.deb: trying to overwrite `/emul/ia32-linux/usr/lib/libcurl.so.4.1.0', which is also in package libcurl3-emul E: /var/cache/apt/archives/ia32-libs-libnspr4_4.7.1-0.1_amd64.deb: trying to overwrite `/emul/ia32-linux/usr/lib/libplds4.so.0d', which is also in package libnspr4-0d-emul E: /var/cache/apt/archives/ia32-libs-libnss3_3.12.0-0.1_amd64.deb: trying to overwrite `/emul/ia32-linux/usr/lib/libssl3.so.1d', which is also in package libnss3-1d-emul I don't know what the /emul/* stuff is or where it came from... How do I get started fixing this...?? TIA Jack This is probably not the answer you were expecting, so I labeled it Off Topic. Have you looked into the new 64bit version from Adobe? http://labs.adobe.com/technologies/flashplayer10/ I had many problems with getting 32bit flash working right. I ended up getting something usable, but nothing satisfactory. Adobe still claims that the 64bit version is Alpha and it was only released yesterday but I have not had any issues with it yet. I have already seen a noticeable decrease in system resources while getting much better performance. The 32bit wrapper would take minutes to load a youtube video and would crash if I skipped around too much. None of those issues so far with the 64bit version. All of the sites I visit work without problem (YMMV of course). I have 2 64bit Debian Lenny systems with flash. So far 0 problems with the 64bit flash player 10. It is something you might want to consider. Have fun! ~S~ Hi, Chris Got the libflashplayer.so.So where exactly do I put it??? FWIW, just spent a few minutes removing the 32bit stuff... Thanks again! Jack I just put it in ~/.mozilla/plugins/, restarted iceweasel, and as soon as iceweasel came back up it said it found a new add-on. I verified it by checking Tools-Add-ons and it worked for me from there on out. Have fun! ~S~ Thanks, Chris That did it!! You're the man! Ain't DEBIAN folks wunderfull!! 8-) Jack -- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: 64-bit Flash Player
On Sat, 22 Nov 2008 17:02:01 +0200 Andrei Popescu [EMAIL PROTECTED] wrote: On Sat,22.Nov.08, 07:59:29, John Hasler wrote: Debian-multimedia now has a native 64 bit flashplayer in Experimental. I haven't tried it yet so I don't know how well it works. It needed some hacking to get installed # LANG=C dpkg --configure -a Setting up flashplayer-mozilla (2:10.0.d20.7-0.1) ... update-alternatives: unable to make /usr/lib/mozilla/plugins/flash-mozilla.so.dpkg-tmp a symlink to /etc/alternatives/flash-mozilla.so: No such file or directory dpkg: error processing flashplayer-mozilla (--configure): subprocess post-installation script returned error exit status 2 Errors were encountered while processing: flashplayer-mozilla # ln -s /usr/lib/flashplayer-mozilla/libflashplayer.so /etc/alternatives/flash-mozilla.so think:/etc# LANG=C dpkg --configure -a Setting up flashplayer-mozilla (2:10.0.d20.7-0.1) ... So it installed, but iceweasel didn't see it so I symlinked /usr/lib/libflashplayer.so into ~/.mozilla/plugins I only tested with one youtube video, but no problems. Regards, Andrei -- Hi, folks the following worked for me : Linux Speeduke 2.6.26-1-amd64 #1 SMP Sat Nov 8 18:25:23 UTC 2008 x86_64 GNU/Linux Hi, Chris Got the libflashplayer.so. from adobe. So where exactly do I put it??? FWIW, just spent a few minutes removing the 32bit stuff... Thanks again! Jack I just put it in ~/.mozilla/plugins/, restarted iceweasel, and as soon as iceweasel came back up it said it found a new add-on. I verified it by checking Tools-Add-ons and it worked for me from there on out. Have fun! ~S~ Thanks, Chris That did it!! You're the man! Ain't DEBIAN folks wunderfull!! 8-) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: OT: laptop recomendations
On Thu, 11 Dec 2008 12:08:14 +0100 Sjoerd Hardeman [EMAIL PROTECTED] wrote: Micha Feigin wrote: Hello, Sorry for being a bit off topic but it's time for a new laptop that will run linux solely and I'm looking for recomendation on what has a good build quallity (will travel), descent battery life, although more important is good computing power and a good screen at 15.4 (needs to be workable with the screen) at a price range of around 1500$ rough ballpark. Good service is a must since it's a working laptop. I know that hp and compaq are a big no no (build quality is shaky at best). I also have the worst experience possible with Sony support on just about every continent (haven't managed to run into worse). Lenovo 3000 series also has a bad track run at our uni in terms of build quallity, no experience with the ideapad pad heard that they are not much brighter. Currently the best candidates are the lenovo thinkpad series (either stick with the older and probed t61 or go with the t500 or similar), mac (not sure about the one button issue although the design is nice). Runner up is Dell, although the hardware seems a bit cheap when looking at the drivers (especially the touchpad which tends to be alps which isn't up to par with the synaptic). Toshiba local dealers didn't prove themselves with a friends laptop. Can't find anyone with experience with lg and fujitsu. Will be happy for feedback/experience/hardware trouble/Service experience in case of mulfunciton etc. Thanks I love my Dell XPS. I have a 13.3', but there are versions with larger screens. They can be bought with Ubuntu preinstalled, so you know for sure that Linux works on these systems. Also some Inspirions can be bought with Ubuntu, which saves you a Windows licence. Sjoerd -- Hi, I concur with the DELL idea. I have an Precision M60 3-years old and it's a tank. still using initial battery. I would recommend that you explore the refurbished supply for a more reasonable price. Mine has been dropped, rained on, slipped off the car hood and sat-on with never a hiccup. But of course, YMMV. My .02 Jack -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: OT: laptop recomendations
On Thu, 11 Dec 2008 15:51:47 + Tzafrir Cohen tzaf...@cohens.org.il wrote: On Thu, Dec 11, 2008 at 08:54:41AM -0600, Jack Schneider wrote: -- Hi, I concur with the DELL idea. I have an Precision M60 3-years Is that an answer or a signature? '-- ' on a line of its own is a signature separator. If you really like '--' as a separator line, just don't put the extra space after it. As in: -- Just Carelessness.. 8-) Jack -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Hypervisor on an existing system?
On Tue, 23 Dec 2008 08:12:36 -0600 Boyd Stephen Smith Jr. bs...@volumehost.net wrote: On Monday 22 December 2008, Ross Boylan rossboy...@stanfordalumni.org wrote about 'Re: Hypervisor on an existing system?': All I really wanted was to run MS Windows to watch TV online and maybe play games; I'm thinking maybe qemu is the way to go for that. Some games are not going to be playable under an emulator (kvm, qemu, virtualbox, vmware-workstation) or under a hypervisor (xen, vmware-esx). Anything that uses Direct3D, e.g., needs direct hardware access to the video card, which isn't available under either of those environments right now. I run Vbox-peul edition version 2.1.0. This supports USB devices in guest O/S. also has 3D enabled on my NVIDIA graphics card.. One H--- of a lot faster than native install of MS. FWIW Jack -- -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Nit-query
Hi,all I have just used CLI 'users' command. I get two(2) entries for myself. Re: j...@speeduke:~$ users jack jack Is this normal??? --- -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Nit-query
On Tue, 23 Dec 2008 09:43:50 -0800 Raquel raq...@thericehouse.net wrote: On Tue, 23 Dec 2008 11:17:41 -0600 Jack Schneider p...@dp-indexing.com wrote: Hi,all I have just used CLI 'users' command. I get two(2) entries for myself. Re: j...@speeduke:~$ users jack jack Is this normal??? --- Let's see, I have 9 raquel because I have 6 windows open and 3 terminals, using ssh, to other machines. OK, Thanks folks. I get it!! Jack -- -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Nit-query
On Tue, 23 Dec 2008 18:24:54 + Tzafr irCohen tzaf...@cohens.org.il wrote: On Tue, Dec 23, 2008 at 11:17:41AM -0600, Jack Schneider wrote: Hi,all I have just used CLI 'users' command. I get two(2) entries for myself. Re: j...@speeduke:~$ users jack jack See also: w who finger It also depends on your terminal. Some terminals don't register each new terminal as a login entry in utmp . Hi, Tzafr Is that a/the reason for SYSTEM ADMINISTRATION USERSGROUPS ROOT(password) gives so many user entries??? TIA Jack -- -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Hypervisor on an existing system?
On Mon, 22 Dec 2008 15:45:08 -0600 Ron Johnson ron.l.john...@cox.net wrote: On 12/22/08 14:58, Tzafrir Cohen wrote: On Mon, Dec 22, 2008 at 02:14:06PM -0600, Ron Johnson wrote: I don't know enough about the subject to be able to intelligently Google, so I thought I'd ask first. My system is a fully-kitted out Sid system, and I'd like to experiment with virtual machines. qemu / virtualbox? openvz / vserver? (for userspace utilities only). Probably virtualbox-ose, but I'm open to ideas. Ron, run the Virtual Box_ peul edition. You get a robust USB support and 3D Graphics. Just my $.02 That is free too single users. 'it's come a long way since SUN acquired them. Have a great day! Jack -- -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Debian Live hangs on cd boot.
Hi, All I have a debian live cd which starts to boot. I get the ISOLINUX 3.71 Debian-2008-9-06 Copyright notice. Then it just hangs- cd active. Disk is debian-live-502-amd64-gnome-desktop.iso MD5 sums check out...Cd is on-top in bios boot priority. Others, sysrescucd, Ubuntu, Debian testing net-installer all boot fine. I have tried other RW disks. 'may try CD-R disk if no one has a helping guess... TIA Jack -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Debian Live hangs on cd boot.
On Tue, 12 Jan 2010 13:00:27 -0500 (EST) Stephen Powell zlinux...@wowway.com wrote: On 2010-01-12 at 12:23:49 -0500, Jack Schneider wrote: Hi, All I have a debian live cd which starts to boot. I get the ISOLINUX 3.71 Debian-2008-9-06 Copyright notice. Then it just hangs- cd active. Disk is debian-live-502-amd64-gnome-desktop.iso MD5 sums check out...Cd is on-top in bios boot priority. Others, sysrescucd, Ubuntu, Debian testing net-installer all boot fine. I have tried other RW disks. 'may try CD-R disk if no one has a helping guess... You haven't said what your hardware is, and this is just a wild guess. But I have an old laptop which frequently hangs on cold boot from CD (i.e. boot from power-on). Warm boot from an already running operating system (Ctrl+Alt+Delete) works fine. Obviously, it's possible there's something wrong with the image or with that particular burn of the image. But try warm booting the Debian Live CD after booting something else first. In fact, try warm booting from the hang of the cold boot. That is one possibility. In the case of my laptop, the cold boot from CD problem appears to be a BIOS bug. Stephen: Thanks for the reply. My hardware is a Supermicro X7DAL-E M/B a couple of years old. I burned the image using Brasero from an Ubuntu laptop. I tried your suggestion - Warm Boot - deliberately I probably had done it before, without thinking, chasing this.. THX, Jack -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Segmentation fault query.
Hi, all I need some direction. I am running Debian squeeze-amd64 and have encountered a problem. On shutting down with kernel 2.6.32-trunk-amd64 after the system halt, I get a segmentation fault and hangs. the system stays powered up. Booting with kernel 2.6.30-1 this does not occur and the system shuts down normally. I have a trace output but it's beyond my understanding and not complete as it may be scrolled off screen. How and to whom should this be reported? What other info should I obtain? My syslog and messages seem to not be reporting it. as it has halted. TIA Jack -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Graphics Diag Query
Hi, All Does any one know of a diagnostic tool to pin down a smeared LCD screen? I have an old laptop i386, running lenny, up2date, 2.6.26-2-486 kernel, which I want to take the load as a parallel-port printer host. It runs a Neomagic NM2093 video chip. I have checked the LCD display with lcdtest and all's well. It seems to display B/W terms at full screen, OK. I have googled 'till I get running in circles. I am thinking about removing color from the display, pointers on if/how to do that would be appreciated. TIA jack -- 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/20100222120641.30ac9...@speeduke.volunteerwireless.net
Re: Graphics Diag Query
On Mon, 22 Feb 2010 13:51:09 -0500 (EST) Stephen Powell zlinux...@wowway.com wrote: On Mon, 22 Feb 2010 13:06:41 -0500 (EST), Jack Schneider wrote: Hi, All Does any one know of a diagnostic tool to pin down a smeared LCD screen? I have an old laptop i386, running lenny, up2date, 2.6.26-2-486 kernel, which I want to take the load as a parallel-port printer host. It runs a Neomagic NM2093 video chip. I have checked the LCD display with lcdtest and all's well. It seems to display B/W terms at full screen, OK. I have googled 'till I get running in circles. I am thinking about removing color from the display, pointers on if/how to do that would be appreciated. I am a native speaker of English, but I haven't a clue what you're asking. What exactly do you mean by pin down? What do you mean by smeared? (I assume you *don't* mean that your child smeared his peanut butter and jelly sandwich all over it, but I don't know what you *do* mean.) And if you're only using it as a print server anyway, who cares? Would you be so kind as to explain in less techno-slang terms exactly what the problem is and exactly what you are trying to accomplish. I have an old laptop too, with an LCD screen and a neomagic 2160 chipset. So I'm familiar with the hardware. But I still have no clue what you are talking about. Stephen, thanks for the reply...8-) I want to find out if the color distortions (smears on left side of images) I see on the LCD are due to a faulty LCD or faulty graphics chip. I want to know if there is a diagnostic to help figure that out. I want to place a message/s in the screen (legible) what jobs are pending/finished as appropriate. Thanks, Jack ps sometimes it appears that peanut butter was smeared... red-blue- green-pink-violet peanut butter etc -- 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/20100222134307.3ff6a...@speeduke.volunteerwireless.net
Re: Graphics Diag Query
On Mon, 22 Feb 2010 15:10:18 -0500 (EST) Stephen Powell zlinux...@wowway.com wrote: On Mon, 22 Feb 2010 14:43:07 -0500 (EST), Jack Schneider wrote: Stephen, thanks for the reply...8-) I want to find out if the color distortions (smears on left side of images) I see on the LCD are due to a faulty LCD or faulty graphics chip. I want to know if there is a diagnostic to help figure that out. I want to place a message/s in the screen (legible) what jobs are pending/finished as appropriate. OK, so you're seeing strange distortion of the colors and you want to figure out if it is a hardware problem or a software problem. I see. Well, the only suggestion I have is rather low-tech; and I'm sure you've thought of it already; but I would suggest installing some other graphical operating system, such as Windows 95, DOS/Win 3.1, etc. and see how things look then. If you still see the smear, it's almost certainly a hardware problem. But again, I'm sure you've thought of that. Maybe someone else has a better idea, but that's all I know to suggest. Thanks again, But no way to connect...8-( The boot up screen is perfectly OK in black and white. Just need to turn off colors, I think... Jack -- 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/20100222162907.05b6e...@speeduke.volunteerwireless.net
Re: ACPI problem on linux-image-2.6.32-trunk-amd64 powering off
On Tue, 2 Mar 2010 20:37:28 + campbell mcleay campbell.mcl...@googlemail.com wrote: Hi, I am running 64-bit Debian Squeeze with kernel linux-image-2.6.32-trunk-vserver-amd64, and when I initiate a shutdown to halt/poweroff the system, either within a Gnome session or on the console, it reboots instead of powering off. I can see what looks like a kernel oops error message at the very end of the shutdown process, and then it reboots (it is too quick for me to see the exact error). My suspicion was that ACPI was the issue, so I disabled it at boot with 'acpi=off', and indeed it no longer reboots when I issue shutdown to halt it, but I lose hyperthreading and it won't power off at all. I have used Ubuntu 9.04 and 10.04 (which uses 2.6.32 kernel) to test the hardware as well, and these shut the machine down with no issue. I would use another linux-image package, but there seems to be only one for Squeeze (aside from a vserver image). Any suggestions on a way round this? I don't want to boot with 'acpi=off', as it won't shutdown and hyperthreading won't work. Hardware is dual Xeon x5550 with 6GB ram and SSD hard disk. Cheers, Campbell Hi, See http://bugzilla.kernel.org/show_bug.cgi?id=15005 FWIW Jack -- 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/20100303084016.02308...@speeduke.volunteerwireless.net
Re: Wifi Can't Connect
On Mon, 22 Mar 2010 16:23:23 -0400
Mark herrpoe...@hailmail.net wrote:
I had wifi, now I don't.
I just upgraded my kernel (using aptitude) from 2.6.26-686 to
2.6.32-3-686 and followed that with aptitude full-upgrade, which
removed a number of packages (that I wasn't using anyway) because I
had previously always used apt-get (and I understand the consequences
of this). I also installed kde-minimal (version 4).
I know that the wifi was working for at least one session on the new
kernel. But after a reboot, it stopped being able to connect. Alas, I
do not know what I did in between. I was messing with aptitude
without really knowing the consequences of my actions.
SYMPTOMS
Both when booting up and when trying things like ifup wlan0 and
dhclient wlan0, I get the following response:
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 3
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 6
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 11
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 8
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 12
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 19
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 9
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 9
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 14
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 10
No DHCPOFFERS received.
No working leases in persistent database - sleeping.
When I open KWiFiManager, most of the time it sees my SSID and
alternates between appearing connected -- i.e. green bars, good
signal strength -- but with no Local IP, and an Unavailable Access
Point; -- it stays like that for maybe 10-15 seconds, and then shows
no connection.
CONFIGURATION
Basics: Dell Inspiron E1505, 2GB RAM. Running Lenny. Using
repositories: lenny, testing, lenny-backports, lenny/updates
(security), and debian-volatile.
I have a Verizon (Westell) wireless modem/router. My MacBook Pro is
connected to it wirelessly with no problem. I use WPA authentication.
My /etc/wpa_supplicant.conf file reads (actual values not given here):
network={
ssid=MY_SSID
psk=MY_PSK
}
My /etc/network/interfaces files reads:
# This file describes the network interfaces available on your
system # and how to activate them. For more information, see
interfaces(5).
# The loopback network interface
auto lo
iface lo inet loopback
# The primary network interface -- This section commented-out on
12/31/09, and got wifi working in the first place.
#allow-hotplug eth0
#iface eth0 inet static
# address 192.168.1.24
# netmask 255.255.255.0
# network 192.168.1.0
# broadcast 192.168.1.255
# gateway 192.168.1.1
# # dns-* options are implemented by the resolvconf package,
if installed # dns-nameservers 192.168.1.1
# New DHCP Setup [WORKED UNTIL YESTERDAY]
iface eth0 inet dhcp
allow-hotplug eth0
iface wlan0 inet dhcp
wpa-driver wext
wpa-key-mgmt WPA-PSK
wpa-proto WPA
wpa-ssid MY_SSID
auto wlan0
Trying something I found on the web, I edited
my /etc/dhcp3/dhclient.conf file by uncommenting the timeout line:
#timeout 60;
# NEXT LINE ADDED AS PER
http://forums.debian.net/viewtopic.php?t=21520 timeout 100;
I've installed KNetworkManager, but I don't understand how it works,
and adding my wifi network in the WiFi tab seems to do nothing at all.
I would appreciate any help anyone can offer!
- Mark
Hi, Mark
Have you got wpa-supplicant /installed/loaded ?
You need that for wpa access, I believe...
FWIW
Jack
--
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/2010030305.428c3...@speeduke.volunteerwireless.net
Re: Wifi Can't Connect
On Tue, 23 Mar 2010 00:30:42 -0400
Mark herrpoe...@hailmail.net wrote:
On 3/22/10 11:03 PM, Jack Schneider wrote:
Hi, Mark
Have you got wpa-supplicant /installed/loaded ?
You need that for wpa access, I believe...
FWIW
Jack
Good question, Jack. I had not remembered that there was actually a
wpasupplicant package. I did have it installed. I just upgraded it,
rebooted. No change: still no wifi.
I think in my first post about this I gave a slightly mixed up
account of what happens when I start KWiFiManager. It alternates
every few seconds between Ultimate Signal Strength (full bars) and
Out of Range (no bars). When it has full bars, The Status of
Active Connection box says Connected to network: [MY_SSID]. When
it has no bars, it says Searching for network: any. It persistently
shows Local IP: unavailable. If I click on the Scan for
Networks... button, it sees my SSID (and my neighbor's).
But the odd thing is that, in the Status of Active Connection
box, the Access point address shows a mac address that is the same
as my broadband router's address, except for the last digit: the last
digit of my router's mac address is 5, but KWiFiManager says it's
connecting to an Access point address that ends in B.
When I run KNetworkManager, And click on the Scan button next to
the SSID textbox, it sees no SSIDs at all -- neither in the map nor
the details view.
This is killing me. The computer's networking is handshaking my
router but not getting an IP. Can anyone help me figure this out?
Below is the rest of my original post, for reference.
- - - - - - - - - - - - - - - - - - -
I had wifi, now I don't.
I just upgraded my kernel (using aptitude) from 2.6.26-686 to
2.6.32-3-686 and followed that with aptitude full-upgrade, which
removed a number of packages (that I wasn't using anyway) because I
had previously always used apt-get (and I understand the consequences
of this). I also installed kde-minimal (version 4).
I know that the wifi was working for at least one session on the new
kernel. But after a reboot, it stopped being able to connect. Alas, I
do not know what I did in between. I was messing with aptitude
without really knowing the consequences of my actions.
SYMPTOMS
Both when booting up and when trying things like ifup wlan0 and
dhclient wlan0, I get the following response:
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 3
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 6
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 11
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 8
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 12
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 19
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 9
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 9
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 14
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 10
No DHCPOFFERS received.
No working leases in persistent database - sleeping.
When I open KWiFiManager, most of the time it sees my SSID and
alternates between appearing connected -- i.e. green bars, good
signal strength -- but with no Local IP, and an Unavailable Access
Point; -- it stays like that for maybe 10-15 seconds, and then shows
no connection.
CONFIGURATION
Basics: Dell Inspiron E1505, 2GB RAM. Running Lenny. Using
repositories: lenny, testing, lenny-backports, lenny/updates
(security), and debian-volatile.
I have a Verizon (Westell) wireless modem/router. My MacBook Pro is
connected to it wirelessly with no problem. I use WPA authentication.
My /etc/wpa_supplicant.conf file reads (actual values not given here):
network={
ssid=MY_SSID
psk=MY_PSK
}
My /etc/network/interfaces files reads:
# This file describes the network interfaces available on your
system # and how to activate them. For more information, see
interfaces(5).
# The loopback network interface
auto lo
iface lo inet loopback
# The primary network interface -- This section commented-out on
12/31/09, and got wifi working in the first place.
#allow-hotplug eth0
#iface eth0 inet static
#address 192.168.1.24
#netmask 255.255.255.0
#network 192.168.1.0
#broadcast 192.168.1.255
#gateway 192.168.1.1
## dns-* options are implemented by the resolvconf
package, if installed # dns-nameservers 192.168.1.1
# New DHCP Setup [WORKED UNTIL YESTERDAY]
iface eth0 inet dhcp
allow-hotplug eth0
iface wlan0 inet dhcp
wpa-driver wext
wpa-key-mgmt WPA-PSK
wpa-proto WPA
wpa-ssid MY_SSID
auto wlan0
Trying something I found on the web, I edited
my /etc/dhcp3/dhclient.conf file by uncommenting the timeout line:
#timeout 60
Gnome/X terminal resize
Hi, All Got a minor problem, Desktop and laptop running Debian lenny 2.6.24-1 up to date with updates. Problem: On 'desktop' cannot resize Gnome or X-term windows by dragging borders-- Laptop works fine. Comparing terminal config info to laptop install shows no setup differences. No Errors reported in X-org logs.. Where should I looked further???[don't need use laptop... 8-) ] Thanks in advance.. Jack -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Gnome/X terminal resize
On Mon, 28 Apr 2008 15:58:11 -0500 Ron Johnson [EMAIL PROTECTED] wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 04/28/08 14:55, Jack Schneider wrote: Hi, All Got a minor problem, Desktop and laptop running Debian lenny 2.6.24-1 up to date with updates. Problem: On 'desktop' cannot resize Gnome or X-term windows by dragging borders-- Laptop works fine. Comparing terminal config info to laptop install shows no setup differences. No Errors reported in X-org logs.. Where should I looked further???[don't need use laptop... 8-) ] It sounds like your window manager (metacity) isn't running. - -- Ron Johnson, Jr. Jefferson LA USA We want... a Shrubbery!! -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFIFjpjS9HxQb37XmcRArPeAKDvXBCDTOKyY0MOlF1aRGEDO+cpSQCg5ADT Ymc5HMxenUfxSE3Do6DkJuA= =rM0h -END PGP SIGNATURE- --Thanks, Ron That was it. Now to takeoff from here... Jack -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Blank CDRW wierdness
On Fri, 17 Apr 2009 07:59:17 -0500 John W Foster jfoster81...@gmail.com wrote: On Fri, 2009-04-17 at 14:16 +0300, Aioanei Rares wrote: John W Foster wrote: I have Debian Lenny on a box that I use to burn Data CD's on I have recently noticed that when I burn one and for some reason need to read it on the Debian box, it says I have inserted anothe 'blank' CD. It will no longet read it. I have been using GnomeBaker to do this. I can read them just fine on a Windows XP box. If I want to add data to them from time to time I can not do it. Any ideas? What flavor of Debian are you using? What brand/type of hardware? What kernel? I'm using the recently updated stable. I decided that this must be because the CDRW device is a very old Mitsumi piece. I don't use it often so I do not know exactly when this started. I currently believe this is the result of the kernel moving past obsolete devices. CDRW is at least 14 years old. Thanks! Hi, John I have had a similar dilemma. 'could not read verified CD on old drive- ATAPI type. Had to only write to CD-R media at min write speed. Then all cd-r disks read correctly.. FWIW, Jack -- -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Raid disk delimma
Hi, All Somewhere (about 9/15) in my enthusiasm for Debian, Testing up2date kernel 2.6.30-1-amd64,--updating I said (y) where I should have said (q). My system will not boot correctly. It halts with: fsck died with exit status 8 I have 4 disks, 2 in raid1, ie. 2 in use - 2 unused Disks are setup as /dev/md0 --/root (small-ish) partition and /dev/md1 much bigger containing /tmp /opt /var and several VirtualBox DVI partitions all under lvm2. I get to the Give root password for maintenance etc. place and when I do it will not allow me to find any logs. I can run dmesg which looks normal. Anything that that tries to use /var -locks. etc. fails, so it's unable to find /dev/md1 and contents..it seems to me... df -h finds /md0 but not /md1 I have tried to google/linux and man on mdadm etc. but ... nothing close... I don't know where to go from here... HELP! or directions, Please! TIA Jack -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Raid disk delimma
On Sun, 20 Sep 2009 08:37:51 +0200 martin f krafft madd...@debian.org wrote: also sprach Jack Schneider p...@dp-indexing.com [2009.09.20.0044 +0200]: I get to the Give root password for maintenance etc. place and when I do it will not allow me to find any logs. I can run dmesg which looks normal. Anything that that tries to use /var -locks. etc. fails, so it's unable to find /dev/md1 and contents..it seems to me... df -h finds /md0 but not /md1 Have a look at the output of mdadm -Es and compare that to the ARRAY lines /etc/mdadm/mdadm.conf. Anything different? What do you see when you run mdadm -Asayes vgchange -a ? Hi,Martin Thanks for your reply... A little more info /home is also on a /dev/md1 partition. Re:mdadm -Es and compare that to the ARRAY lines /etc/mdadm/mdadm.conf. Anything different? There is 'no' difference in the array info UUID's match for both md0 md1. I have yet to try the other commands. need to see what they mean...8-) Jack -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Grub update problems
On Mon, 21 Sep 2009 08:54:44 +0300 Andrei Popescu andreimpope...@gmail.com wrote: On Sun,20.Sep.09, 22:34:23, Frank McCormick wrote: [snip grub2 troubles] As far as I understand you fixed your problem by going back to grub1. I also don't see any reference in it to the Ubuntu which I have on hda3. Debian testing is on hda2. For the archives, to boot other OSes on your machine just install os-prober and run update-grub. In unstable os-prober is recommended by grub-common. Regards, Andrei Andrei, thanks, I think. 8-) I am Paranoid this AM. I have two broken machines from this problem... I'm on the last... Here's the output from update-grub: sudo update-grub Generating grub.cfg ... Found Debian background: moreblue-orbit-grub.png Found linux image: /boot/vmlinuz-2.6.30-1-686 Found initrd image: /boot/initrd.img-2.6.30-1-686 Found Microsoft Windows XP Professional on /dev/hda1 done Does that guarantee a safe reboot??? Thanks, Jack -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Raid disk delimma
On Mon, 21 Sep 2009 19:03:45 +0200 martin f krafft madd...@debian.org wrote: Let's keep this on the list... OK with me.. I normally just hit reply in Claws 3.5. You may get 2 if I use reply-all.. also sprach Jack Schneider p...@dp-indexing.com [2009.09.21.1857 +0200]: Results from : mdadm -Asayes Just returns a prompt: # vgchange -a (gives argument needed message) vgchange -a y :gives 7 logical volume(s) in volume group Speeduke now active 'first seems to complete without error and the second (with my change) seems to indicate that all volume groups are found...hmmm! I'll take a shot into the dark: does it work if you add rootdelay=30 to the linux kernel boot line? E.g. kernel /boot/vmlinuz ro root=/dev/md0 rootdelay=30 This will incur a 30 second delay during boot. If that makes it work, you can experiment with lowering this value, but you will need to have some sort of sleep in there like that, because apparently your controllers need more time to make the disks available, and they do not properly convey to the kernel when they're ready. Cheers, You mean in the grub boot edit function? At boot-up ? Where I put it, /boot/grub/menu.lst It didn't help... Same fault. Sorry about that.. It was not a problem until the 2.6.30 update I did about 9/14- 9/15 time frame... the problem came up after the next boot. I had to shut down for a storm... I don't trust UPS's for protection..8-( TIA, Jack -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Odd behavusr
On Mon, 12 Oct 2009 09:21:12 +0200 steef debian.li...@home.nl wrote: Wayne Topa wrote: Hi List I have noticed some odd behavior with aptitude when doing safe-upgrades for the past month or so. On 5 or 6 occasions a number of files are downloaded more then once. Below is an example on my current upgrade Get:95 http://mirrors.kernel.org unstable/main xulrunner-1.9.1 1.9.1.3-3 [8389kB] Get:96 http://mirrors.kernel.org unstable/main xulrunner-1.9.1 1.9.1.3-3 [8389kB] So far this is the only time it has happened in this run. Has anyone else seen this? IT does not happen every time I upgrade but when it does, it sure runs my up my download close to my limit. Especially when its happen with the linux-source and openoffice files. THIA Wayne nope, steef Ay-yup! I see it all the time... Thought it might be my ISP... but now that you brought it up... my aptitude update is most frequently the issue.. Jack -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Raid help needed !
Hi, All For over two years, I have used /md0 as / and /md1 under lvm2 with 7 partitions on this amd64 system. I have migrated from etch to squeeze without undue problems. BUT, now I cannot boot either kernel 2.6.30-1 or 2.6.30-2 with grub2, it fails by not finding or identifying my swap partition. It is one of the seven partitions on /md1. I can boot 2.6.26-2 without error. I have looked at list archives and googled but nothing helped. Since I have had minimal problems to this point, I am not fluent in mirroring commands. My reading of mdadm lvm manpages doesn't seem to address swap issues. Can someone point me in the right direction??? TIA, Jack -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Raid help needed !
On Tue, 13 Oct 2009 23:03:11 -0400 Justin eqi...@gmail.com wrote: On Tue, Oct 13, 2009 at 10:16 PM, Jack Schneider p...@dp-indexing.com wrote: Hi, All For over two years, I have used /md0 as / and /md1 under lvm2 with 7 partitions on this amd64 system. I have migrated from etch to squeeze without undue problems. BUT, now I cannot boot either kernel 2.6.30-1 or 2.6.30-2 with grub2, it fails by not finding or identifying my swap partition. It is one of the seven partitions on /md1. I can boot 2.6.26-2 without error. I have looked at list archives and googled but nothing helped. Since I have had minimal problems to this point, I am not fluent in mirroring commands. My reading of mdadm lvm manpages doesn't seem to address swap issues. Can someone point me in the right direction??? TIA, Jack -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org What are you raiding and what time? How are we doing loot? Hi, Justin What: Cumulative smarts of Debian Users When: Almost any time, when you're ready Loot: Stored in 75 year old grey matter If you want to help http://pastebin.com/m7cc9da3d TIA Jack -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Raid help needed !
On Wed, 14 Oct 2009 15:19:56 +1100 Alex Samad a...@samad.com.au wrote: On Tue, Oct 13, 2009 at 09:16:47PM -0500, Jack Schneider wrote: Hi, All For over two years, I have used /md0 as / and /md1 under lvm2 with 7 partitions on this amd64 system. I have migrated from etch to squeeze without undue problems. BUT, now I cannot boot either kernel 2.6.30-1 or 2.6.30-2 with grub2, it fails by not finding or identifying my swap partition. It is one of the seven partitions on /md1. I can boot 2.6.26-2 without error. I have looked at list archives and googled but nothing helped. Since I have had minimal problems to this point, I am not fluent in mirroring commands. My reading of mdadm lvm manpages doesn't seem to address swap issues. Can someone point me in the right direction??? what is the error you are getting ? what happens when you type mount -a or swapon -a TIA, Jack Hi, Alex Error: The superblock could not be read or does not describe a correct ext2 file system..fsck died with exit status 8 # mount -a gives : wrong fs type, bad option, bad superblock on dev/mapper/Speeduke-_swap,missing codepage or helper program, or other error (plus some others that says it's not reading/recognizing /md1 ) # swapon -a gives: swapon: /dev/mapper/Speeduke-_tmp: read swap header failed: Invalid argument #swapon /dev/mapper/Speeduke-_swap (executes with out error) Note: see http://pastebin.com/m7cc9da3d for a view of what I've got in this system.. Thanks for your reply... Jack -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Raid help needed !
On Thu, 15 Oct 2009 03:31:36 +0200 Tom H tomh0...@gmail.com wrote: On Wed, Oct 14, 2009 at 1:48 PM, Jack Schneider p...@dp-indexing.com wrote: On Wed, 14 Oct 2009 15:19:56 +1100 Alex Samad a...@samad.com.au wrote: On Tue, Oct 13, 2009 at 09:16:47PM -0500, Jack Schneider wrote: For over two years, I have used /md0 as / and /md1 under lvm2 with 7 partitions on this amd64 system. I have migrated from etch to squeeze without undue problems. BUT, now I cannot boot either kernel 2.6.30-1 or 2.6.30-2 with grub2, it fails by not finding or identifying my swap partition. It is one of the seven partitions on /md1. I can boot 2.6.26-2 without error. I have looked at list archives and googled but nothing helped. Since I have had minimal problems to this point, I am not fluent in mirroring commands. My reading of mdadm lvm manpages doesn't seem to address swap issues. Can someone point me in the right direction??? what is the error you are getting ? what happens when you type mount -a or swapon -a Error: The superblock could not be read or does not describe a correct ext2 file system..fsck died with exit status 8 # mount -a gives : wrong fs type, bad option, bad superblock on dev/mapper/Speeduke-_swap,missing codepage or helper program, or other error (plus some others that says it's not reading/recognizing /md1 ) # swapon -a gives: swapon: /dev/mapper/Speeduke-_tmp: read swap header failed: Invalid argument #swapon /dev/mapper/Speeduke-_swap (executes with out error) Note: see http://pastebin.com/m7cc9da3d for a view of what I've got in this system.. I am confused... Before suggesting anything... (1) All the output in pastebin is when booted into 2.6.26-2, I assume that the above mount and swapon are also when booted into 2.6.26-2. Hi, Tom Thanks for the reply. (1) No, Those are the responses I get when trying to boot into 2.6.30-X and get to the type root password for maintenance. (2) When you say that you cannot boot into 2.6.30-1 or 2.6.30-2 because of your swap partition, are you not booting at all into these kernels or are you booting but swap is not mounting? (2) When I try to boot into a 2.6.30-X kernel I get the repair promt. as in (1) what it complains about is fsck.ext3: Bad magic number etc... (3) When you say that you have migrated from etch to squeeze without undue problems, what do you actually mean? (3) I built this machine to run Debian as host for VirtualBox. Started with etch then etch 1/2, lenny(testing), now squeeze(testing) using aptitude dist-upgrades. I had some expected Nvidia driver and gnome desktop glitches and some NetworkManager instability. I never got Compiz working right... I have much cruft in /root (/md0) it's over 8 gigs of disk space and /var-/home-/tmp are on (/md1)... (4i) Please post your grub.cfg. Here's the link. http://pastebin.com/m243acd1 (4ii) Please post fstab and, while booted into the kernel with the mount and swapon output above, the following sequence: swapoff -a mount -a swapon -s swapoff -a swapon -s I'll send (4ii) when I figure out how to get it 8-( TIA, Jack -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re:Raid help needed !
On Thu, 15 Oct 2009 09:03:26 -0500 Jack Schneider p...@dp-indexing.com wrote: On Thu, 15 Oct 2009 03:31:36 +0200 Tom H tomh0...@gmail.com wrote: On Wed, Oct 14, 2009 at 1:48 PM, Jack Schneider p...@dp-indexing.com wrote: On Wed, 14 Oct 2009 15:19:56 +1100 Alex Samad a...@samad.com.au wrote: On Tue, Oct 13, 2009 at 09:16:47PM -0500, Jack Schneider wrote: For over two years, I have used /md0 as / and /md1 under lvm2 with 7 partitions on this amd64 system. I have migrated from etch to squeeze without undue problems. BUT, now I cannot boot either kernel 2.6.30-1 or 2.6.30-2 with grub2, it fails by not finding or identifying my swap partition. It is one of the seven partitions on /md1. I can boot 2.6.26-2 without error. I have looked at list archives and googled but nothing helped. Since I have had minimal problems to this point, I am not fluent in mirroring commands. My reading of mdadm lvm manpages doesn't seem to address swap issues. Can someone point me in the right direction??? what is the error you are getting ? what happens when you type mount -a or swapon -a Error: The superblock could not be read or does not describe a correct ext2 file system..fsck died with exit status 8 # mount -a gives : wrong fs type, bad option, bad superblock on dev/mapper/Speeduke-_swap,missing codepage or helper program, or other error (plus some others that says it's not reading/recognizing /md1 ) # swapon -a gives: swapon: /dev/mapper/Speeduke-_tmp: read swap header failed: Invalid argument #swapon /dev/mapper/Speeduke-_swap (executes with out error) Note: see http://pastebin.com/m7cc9da3d for a view of what I've got in this system.. I am confused... Before suggesting anything... (1) All the output in pastebin is when booted into 2.6.26-2, I assume that the above mount and swapon are also when booted into 2.6.26-2. Hi, Tom Thanks for the reply. (1) No, Those are the responses I get when trying to boot into 2.6.30-X and get to the type root password for maintenance. (2) When you say that you cannot boot into 2.6.30-1 or 2.6.30-2 because of your swap partition, are you not booting at all into these kernels or are you booting but swap is not mounting? (2) When I try to boot into a 2.6.30-X kernel I get the repair promt. as in (1) what it complains about is fsck.ext3: Bad magic number etc... (3) When you say that you have migrated from etch to squeeze without undue problems, what do you actually mean? (3) I built this machine to run Debian as host for VirtualBox. Started with etch then etch 1/2, lenny(testing), now squeeze(testing) using aptitude dist-upgrades. I had some expected Nvidia driver and gnome desktop glitches and some NetworkManager instability. I never got Compiz working right... I have much cruft in /root (/md0) it's over 8 gigs of disk space and /var-/home-/tmp are on (/md1)... (4i) Please post your grub.cfg. Here's the link. http://pastebin.com/m243acd1 (4ii) Please post fstab and, while booted into the kernel with the mount and swapon output above, the following sequence: swapoff -a mount -a swapon -s swapoff -a swapon -s I'll send (4ii) when I figure out how to get it 8-( TIA, Jack Hi, Tom I've attached the FSTAB to the bottom of my prior pastebin post: http://pastebin.com/m50e45f6a swapoff -a gives Speeduke prompt mount -agives [ 982.179.186] VFS: Can't find ext3 filesystem on dev dm-0, mount: wrong fs type,bad option,bad superblock on /dev/mapper/Speeduke-_swap, missing codepage etc... mount: mount point /home/jack/XP_VDI does not exist (+ more similar) swapon -s gives Filename Type Size Used Priority (no other data) swapoff -a gives Speeduke prompt swapon -s gives (same as previous swapon -s) 'Hope that helps!! Jack -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: initramfs-tools does not add dm-mod.ko to initrd for kernels 2.6.30-2-686 and kernels 2.6.30-2-686-bigmem
On Thu, 15 Oct 2009 00:56:20 -0400 Mitchell Laks ml...@post.harvard.edu wrote: On 00:05 Thu 15 Oct , Mitchell Laks wrote: How can I work around this and what to do? My old kernel 2.6.26 works fine How to force initrd to load the dm-mod and other device-mapper kernel modules? I have added dm_mod dm_log dm_snapshot dm_mirror to /etc/initramfs-tools/modules file and then did dpkg-reconfigure linux-image-2.6.30-2-686-bigmen and it regenerated the initrd.img file but then when I selected this kernel in grub2 it still could not find the /dev/mapper/debian-root device. I was dumped by grub2 into Busybox (initramfs) and when I ran (initramfs) cat /proc/modules sure enough these modules were now in the kernel. However when I did ls /dev/mapper all I see is /dev/mapper/control and I cannot find the /dev/mapper/debian-root directory which exists when I boot into the vmlinuz-2.6.26-2-686 kernel. So why is grub2 failing to boot in the 2.6.30-2-686 kernel? Mitchell Hi, Mitchell FWIW I have exactly the same problem... Whew !!! I didn't cause this messI hope!!! Thanks more that you know... BTW I haven't fix mine yet... But getting some help. Jack Jack -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Raid help needed !
Hi, Tim what is the error you are getting ? what happens when you type mount -a or swapon -a Error: The superblock could not be read or does not describe a correct ext2 file system..fsck died with exit status 8 # mount -a gives : wrong fs type, bad option, bad superblock on dev/mapper/Speeduke-_swap,missing codepage or helper program, or other error (plus some others that says it's not reading/recognizing /md1 ) # swapon -a gives: swapon: /dev/mapper/Speeduke-_tmp: read swap header failed: Invalid argument #swapon /dev/mapper/Speeduke-_swap (executes with out error) Note: see http://pastebin.com/m7cc9da3d for a view of what I've got in this system.. I am going to be at work for a while so I will not have a chance to look at this closely for a few more hours. Sorry about that. 8-) (1) All the output in pastebin is when booted into 2.6.26-2, I assume that the above mount and swapon are also when booted into 2.6.26-2. (1) No, Those are the responses I get when trying to boot into 2.6.30-X and get to the type root password for maintenance. The first two lines of your pastebin are: j...@speeduke:~$ uname -a Linux Speeduke 2.6.26-2-amd64 #1 SMP Sun Jun 21 04:47:08 UTC 2009 x86_64 GNU/Linux so I am surprised. The paste bin was generated using the only kernel that works right now! 2.6.30-X and the like, will not run at all usefully... Sorry, that the best this old man can do. 8-) (2) When you say that you cannot boot into 2.6.30-1 or 2.6.30-2 because of your swap partition, are you not booting at all into these kernels or are you booting but swap is not mounting? (2) When I try to boot into a 2.6.30-X kernel I get the repair prompt. as in (1) what it complains about is fsck.ext3: Bad magic number etc... OK. Thanks. (3) When you say that you have migrated from etch to squeeze without undue problems, what do you actually mean? (3) I built this machine to run Debian as host for VirtualBox. Started with etch then etch 1/2, lenny(testing), now squeeze(testing) using aptitude dist-upgrades. I had some expected Nvidia driver and gnome desktop glitches and some NetworkManager instability. I never got Compiz working right... I have much cruft in /root (/md0) it's over 8 gigs of disk space and /var-/home-/tmp are on (/md1)... OK, more or less. Did I answer your question?? (4i) Please post your grub.cfg. http://pastebin.com/m243acd1 Your grub.cfg looks OK at first glance. I would have thought that you would have needed an insmod lvm but I am still teaching myself about grub2 so my assumption must be wrong. Can't address this Grub2 just worked as advertised, for me.. (4ii) Please post fstab and, while booted into the kernel with the mount and swapon output above, the following sequence: swapoff -a mount -a swapon -s swapoff -a swapon -s I'll send (4ii) when I figure out how to get it 8-( Sorry. I emailed you late and should probably have been in bed rather than going through emails at 3am - and missed a line (a swapon -a) as a penultimate step. Please email the output of: swapoff -a swapon -a swapon -s Thanks and sorry... swapoff -a gives Speeduke prompt mount -agives [ 982.179.186] VFS: Can't find ext3 filesystem on dev dm-0, mount: wrong fs type,bad option,bad superblock on /dev/mapper/Speeduke-_swap, missing codepage etc... mount: mount point /home/jack/XP_VDI does not exist (+ more similar) swapon -s gives Filename Type Size Used Priority (no other data) swapoff -a gives Speeduke prompt swapon -s gives (same as previous swapon -s) It is difficult to reconcile mount point /home/jack/XP_VDI does not exist with the output of df -h pastebin. Are any of your /dev/dm-x mounted? Please add the output of mount after the swapon -s above. Thanks. There is another email from earlier today about initramfs and success with 2.6.26 and problems with 2.6.30. The other OP's symptoms are different but I do not believe coincidences. Yes, 'Saw that. Whew!!! I guess!! I will have to sync this mail to the laptop and reboot this machine... I'll add the above later... Thanks,more than you know! Jack -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Raid help needed !
On Thu, 15 Oct 2009 10:23:59 -0500 Jack Schneider p...@dp-indexing.com wrote: On Thu, 15 Oct 2009 09:03:26 -0500 Jack Schneider p...@dp-indexing.com wrote: On Thu, 15 Oct 2009 03:31:36 +0200 Tom H tomh0...@gmail.com wrote: On Wed, Oct 14, 2009 at 1:48 PM, Jack Schneider p...@dp-indexing.com wrote: On Wed, 14 Oct 2009 15:19:56 +1100 Alex Samad a...@samad.com.au wrote: On Tue, Oct 13, 2009 at 09:16:47PM -0500, Jack Schneider wrote: For over two years, I have used /md0 as / and /md1 under lvm2 with 7 partitions on this amd64 system. I have migrated from etch to squeeze without undue problems. BUT, now I cannot boot either kernel 2.6.30-1 or 2.6.30-2 with grub2, it fails by not finding or identifying my swap partition. It is one of the seven partitions on /md1. I can boot 2.6.26-2 without error. I have looked at list archives and googled but nothing helped. Since I have had minimal problems to this point, I am not fluent in mirroring commands. My reading of mdadm lvm manpages doesn't seem to address swap issues. Can someone point me in the right direction??? what is the error you are getting ? what happens when you type mount -a or swapon -a Error: The superblock could not be read or does not describe a correct ext2 file system..fsck died with exit status 8 # mount -a gives : wrong fs type, bad option, bad superblock on dev/mapper/Speeduke-_swap,missing codepage or helper program, or other error (plus some others that says it's not reading/recognizing /md1 ) # swapon -a gives: swapon: /dev/mapper/Speeduke-_tmp: read swap header failed: Invalid argument #swapon /dev/mapper/Speeduke-_swap (executes with out error) Note: see http://pastebin.com/m7cc9da3d for a view of what I've got in this system.. I am confused... Before suggesting anything... (1) All the output in pastebin is when booted into 2.6.26-2, I assume that the above mount and swapon are also when booted into 2.6.26-2. Hi, Tom Thanks for the reply. (1) No, Those are the responses I get when trying to boot into 2.6.30-X and get to the type root password for maintenance. (2) When you say that you cannot boot into 2.6.30-1 or 2.6.30-2 because of your swap partition, are you not booting at all into these kernels or are you booting but swap is not mounting? (2) When I try to boot into a 2.6.30-X kernel I get the repair promt. as in (1) what it complains about is fsck.ext3: Bad magic number etc... (3) When you say that you have migrated from etch to squeeze without undue problems, what do you actually mean? (3) I built this machine to run Debian as host for VirtualBox. Started with etch then etch 1/2, lenny(testing), now squeeze(testing) using aptitude dist-upgrades. I had some expected Nvidia driver and gnome desktop glitches and some NetworkManager instability. I never got Compiz working right... I have much cruft in /root (/md0) it's over 8 gigs of disk space and /var-/home-/tmp are on (/md1)... (4i) Please post your grub.cfg. Here's the link. http://pastebin.com/m243acd1 (4ii) Please post fstab and, while booted into the kernel with the mount and swapon output above, the following sequence: swapoff -a mount -a swapon -s swapoff -a swapon -s I'll send (4ii) when I figure out how to get it 8-( TIA, Jack Hi, Tom I've attached the FSTAB to the bottom of my prior pastebin post: http://pastebin.com/m50e45f6a swapoff -a gives Speeduke prompt mount -agives [ 982.179.186] VFS: Can't find ext3 filesystem on dev dm-0, mount: wrong fs type,bad option,bad superblock on /dev/mapper/Speeduke-_swap, missing codepage etc... mount: mount point /home/jack/XP_VDI does not exist (+ more similar) swapon -s gives Filename Type Size Used Priority (no other data) swapoff -a gives Speeduke prompt swapon -s gives (same as previous swapon -s) 'Hope that helps!! Jack Hi, Tom Response after the swapon -s to the mount cmd is /dev/md0 and a bunch of the transient fs stuff.. tmpfs, proc, etc. No /dev/md1!! Which appears to be the same as Mitchell Laks problem. Thanks, Jack -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: initramfs-tools does not add dm-mod.ko to initrd for kernels 2.6.30-2-686 and kernels 2.6.30-2-686-bigmem
On Thu, 15 Oct 2009 20:42:00 -0400 Mitchell Laks ml...@post.harvard.edu wrote: On 15:47 Thu 15 Oct , Jack Schneider wrote: Hi, Mitchell FWIW I have exactly the same problem... Whew !!! I didn't cause this messI hope!!! Thanks more that you know... BTW I haven't fix mine yet... But getting some help. Jack I have identified the problem. dist-upgrade was the problem: 1. lvm2 requires dmsetup 2. devicekit-disks conflicts with dmsetup 3. gnome-control-center and other gnome crap need devicekit-disks 4. so lvm2 and dmsetup get kicked out to rc status 5. then you can't boot with your kernel if / is on lvm2 Hi, Mitchell Just some nits. I really am happy you found the glitch. I just wanted to let you know that my raid1 system is a bit different. My /boot /root partitions are on /md0 (not under LVM2). I have 7 partitions under /md1, but /home /var /tmp are 3 of those partitions. 'Don't know if that affects your analysis, which is undoubtedly correct, but may require some extension.. If you are going to file a bug report, you may suggest that more complexity may/can exist. I was going to reinstall as a cruft clean-up exercise. Not Now!! Until this gets fixed... Thanks, for your effort.. Keep me informed please... Jack :) so apt-get install dmsetup lvm2 will kick out lots of gnome stuff but i use stumpwm anyway :) I will start a new thread to publicize this information. Mitchell -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: installing mdadm breaks udev (and *lots* of other stuff!) in squeeze
On Sat, 24 Oct 2009 22:55:04 +1100 Alex Samad a...@samad.com.au wrote: On Sat, Oct 24, 2009 at 02:48:32AM -0400, Rick Thomas wrote: Whooo boy! When I decided to raid my home directories, I never expected this! Anybody have any suggestions for getting udev and mdadm to coexist? Rick a recent release of udev conflicted against the at the time current version of mdadm, I found it through out quit a lot of my packges as well some suggested to use the one from sid [snip] Hi,All see bug #550434 et al FIW Jack -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
