Re: jessie won't install/boot on a Dell Poweredge R815
I'd like to thank everyone for helping out.
Here is an update on installing jessie on R815s.
I succeeded in installing on three of my four R815s. But I am holding off on
the last because it is my file server and there are still issues. Please read
on. I don't believe that the problem is solved and there may be a bug lurking
that can lead to data loss.
Here is what I did.
1. Before the install, while still running wheezy, I upgraded the BIOS.
R815_BIOS_JF8YH_LN_3.2.2.BIN
This seemed to alleviate the problem of the jessie installer failing to
find the ISO. More on this later.
2. Before the install, while still running wheezy, I reduced the number of
components of md0 from 6 to 4. This was in response to Steve' suggestion.
mdadm /dev/md0 --fail /dev/sdf1
mdadm /dev/md0 --fail /dev/sde1
mdadm /dev/md0 --remove /dev/sdf1
mdadm /dev/md0 --remove /dev/sde1
3. I did a fresh USB install of jessie. More on this later.
4. When it asked about which devices to install grub, I answered "manual" and
then typed /dev/sdb. More on this later.
5. After the fresh install, I rebooted, and in grub, I added rootdelay=20.
This was in response to Don's suggestion.
6. After the reboot, I ran my standard post-install script. Among other
things, this installs numerous packages, makes a small number of mods to
/etc, and does a dpkg-reconfigure grub-pc. When it did that, I specified
only the 4 drives with active components of md0 and added rootdelay=20.
7. I rebooted. More on this later.
Now for the issues.
A. Even after the BIOS upgrade, when it no longer fails to find the ISO,
during the installer phase where it searches for an ISO, I notice
nondetermininstic behavior. Sometimes it searchs sdb{1,2,3}, sdc{1,2,3},
sdd{1,2,3}, sde{1,2,3}, sdf{1,2,3}, sdg{1,2,3}, sd{a,b,c,d,e,f,g} and
eventually finds an ISO (sda is the USB dongle). Sometimes it finds the
ISO right away without any searching. This doesn't cause problems but I
believe that it is symptomatic of other problems.
B. I'm not sure that reducing the number of components of md0 to 4 and/or
adding rootdelay=20 really solved the problem. I think it just reduced the
likelihood of occurrence. On one of the machines (arivu), during the
reboot in step (7), at an early phase of the boot, the machine first
reported that it found all 4 components of md0 and all 6 components of md1.
Then at a later phase it reported that there were errors on 3 of the 4
components. After the machine came up, md0 had only one component. Three
of the four components were in failed (F) state. I did mdadm --remove to
them and then mdadm --add to them. This doesn't happen all of the time. But
it happens some of the time.
qobi@upplysingaoflun>all-n-3g dmesg --level=err
upplysingaoflun:
verstand:
arivu:
[ 28.012558] mpt2sas0: fault_state(0x265d)!
[ 29.231355] end_request: I/O error, dev sdb, sector 2056
[ 29.231600] end_request: I/O error, dev sdc, sector 2056
[ 29.231773] end_request: I/O error, dev sde, sector 2056
[ 29.232020] end_request: I/O error, dev sda, sector 2056
perisikan:
[ 13.035132] mpt2sas0: fault_state(0x265d)!
[ 28.600099] mpt2sas0: fault_state(0x265d)!
qobi@upplysingaoflun>
qobi@upplysingaoflun>all-n-3g "dmesg --level=warn|fgrep -i error|fgrep -v
ACPI"
upplysingaoflun:
verstand:
arivu:
[ 29.231430] md: super_written gets error=-5, uptodate=0
[ 29.231670] md: super_written gets error=-5, uptodate=0
[ 29.231869] md: super_written gets error=-5, uptodate=0
[ 29.232117] md: super_written gets error=-5, uptodate=0
perisikan:
qobi@upplysingaoflun>
(These are my four R815s. upplysingaflun is the file server that has not
been updated. The other three have.) Note that one machine reports no
"mpt2sas0: fault_state(0x265d)" errors, one machine reports one, and one
machine reports two. Note that the machine that dropped three components
of md0 during boot reported I/O errors on all 4 disks with the 4
components of md0. I don't believe that there really are faulty disks.
Whenever I observe any of the behavior reported in this email, it is
almost always associated with dmesg reporting the same error on the same
sector 2056 (sometimes 2058 or 2062). Given the dozens of attempted
reinstalls and reboots, at this point, I have seen this on almost all, if
not all, of the six disks on each of the four machines. I don't believe
that 24 disks all have the same bad sectors.
C. In step (3), sometimes, but not always, during the install, I get a screen
that says that some partition failed. If offers a menu of two options. I
select "retry". Sometimes, but not always, this causes md0 to drop
components in the installer, which I fix by going to ctrl-alt-f2
Re: jessie won't install/boot on a Dell Poweredge R815
On Mon, 2016-06-27 at 08:07 -0400, Jeffrey Mark Siskind wrote: [...] > Whenever I observe any of the behavior reported in this email, it is > almost always associated with dmesg reporting the same error on the same > sector 2056 (sometimes 2058 or 2062). Given the dozens of attempted > reinstalls and reboots, at this point, I have seen this on almost all, if > not all, of the six disks on each of the four machines. I don't believe > that 24 disks all have the same bad sectors. The first partition probably starts at an offset of 1MB, which is 2048 sectors. So these errors are presumably occurring while reading a filesystem label near the start of that partition, which is pretty much the first thing that will happen after the array is assembled. [...] > D. In step (4), there appears to be nondeterminism in the serial numbers of > the disks that get reported in the menu of options of where to install > grub. Sometimes, the disks get reported as ata-*, sometimes as scsi-*. > Note that all of my disks are SATA so the ones reported as scsi-* are > clearly in error. If I do fresh installs multiple times on the same > machine, each time it reports different serial numbers for the disks. Linux uses an ATA/SCSI translation layer (libata), so that each ATA drive is also seen as a SCSI drive and has two such identifiers. The non-determinism in which identifiers are shown might be a bug in the installer, or it might be caused by failure of ID commands to the drives. [...] > Note that there is a lot of nondeterministic behavior (all cases above where I > say "sometimes"). In all cases, I do exactly the same thing over and over to > the same machine and get different behavior. This is an unfortunate effect of doing multiple things in parallel, which is really the only way to make them go fast. I think most of the problems you're still having must be caused by a bug in the RAID driver, mpt2sas (or its firmware, if that's not embedded in the BIOS). Ben. -- Ben Hutchings Humour is the best antidote to reality. signature.asc Description: This is a digitally signed message part
Problems with Apper / automatic upgrading of my Debian 7.11 system
Background: Since I upgraded to Debian 7.11 (wheezy) maybe 6 months to a year ago (maybe longer), I've made it a habit to upgrade any software for which Apper notifies me that an upgrade is available. Something like two weeks ago, I upgraded the Linux kernel when notified. Before the upgrade completed, I got the following popup: Package failed to install - Apper One of the selected packages failed to install correctly. More information is available in the detailed report. And, upon clicking on Details, I got the following: subprocess installed post-installation script returned error exit status 1 But, the upgrade seemed to complete successfully, eventually giving me the message (~"Your system is up to date, verified hours and minutes ago"). Aside: I did not reboot after that upgrade nor any time since then. After that, the next several upgrades proceeded in the same fashion--that is, I saw the warning that one of the selected packages failed to install properly, but it then seemed to complete and said my system was up to date. Since then (maybe the last 2 or so upgrades, in the last 2 or 3 days) the upgrades do not complete successfully--the apper screen just "hangs"--I do not get the message that the upgrade completed successfully, even if I let the apper screen sit there for half an hour. Today I got a notification to update default-jre, default-jre-headless, and java common and: * it gave me a list of other software that had to be updated: libsctp1, openjdk-7-jre, and openjdk-7-jre-headless, and I accepted that (clicked Continue) * it asked me for authentication, which I gave it * it downloaded the packages * it started preparing and installing the packages The popup "Package Failed to install - Apper" appeared-- this time I noticed that it appeared during an attempt to install "linux-image-3.2.0-4-amd64 Linux 3.2 for 64-bit PCs". I don't know (didn't notice) if during the other problem installs it attempted to install the linux image. (Aside: I assume that a new linux-image is only activated after a reboot? OTOH, when I run uname -a I get: "Linux s19 3.2.0-4-amd64 #1 SMP Debian 3.2.78-1 x86_64 GNU/Linux" which seems to indicate I am using the latest Linux kernel (??).) Anyway, it seemed that today's update did complete successfully--after today's upgrade I did get the message: Your system is up to date Verified 3 hours and 26 minutes ago So: 1. Should I be worried? 2. Should I reboot? 3. Was there something wrong with that kernel upgrade that I should expect to be fixed, and wait to install that fix before rebooting? 4. Can anyone explain what is going on? 5. Any other advice? Thanks! Randy Kramer
bigs problems wifi connexion
Hello, since the last update to Debian, the 8.5, I have big problems with my wifi connection. The connection constantly cutting and sometimes asks me the login password to restart. I think this is the ath9k package that is the problem, but I do not find a solution on the forums. Today I can work on my PC so the cuts are frequent. Here's my setup: HP Pavilion AMD A6-5200 APU with Radeon HD graphics Debian 8.5 Linux AMD64-3.16.0-4 KDE SC 4.14.2 wireless card: AR9485 Wireless Network Adapter (AR9485 / HB125 802.11bgn Wi-Fi Adapter) I sincerely hope that you will respond to my message and you will have a solution that can help me. Truly, Jocelyn Boulogne-sur-mer France
Re: jessie won't install/boot on a Dell Poweredge R815
The non-determinism in which identifiers are shown might be a bug in the installer, or it might be caused by failure of ID commands to the drives. I think most of the problems you're still having must be caused by a bug in the RAID driver, mpt2sas (or its firmware, if that's not embedded in the BIOS). Thanks. Please let me know how I can report the potential bug(s) and what I can do to help track them down. Jeff (http://engineering.purdue.edu/~qobi)
Re: Problems with Apper / automatic upgrading of my Debian 7.11 system
Thanks for the reply, but I want to clarify a little more (oh, and the other questions still stand...): * I assume that I only have to reboot if I / when I'm ready to have that new kernel be activated--otherwise the system will continue to use the old kernel--presumably with no problems. * Or, do you think my problems with upgrading / Apper are because I didn't activate the new kernel? * But, that wouldn't explain the problem with they first problematic upgrade, which was the kernel... Thanks for any clarification you can add... On Monday, June 27, 2016 10:27:24 AM somebody who didn't want to reply on list wrote: > If the kernel was updated, you MUST reboot. And that's the only case > where it is mandatory. On Monday, June 27, 2016 10:18:10 AM rhkra...@gmail.com wrote: > Background: > > Since I upgraded to Debian 7.11 (wheezy) maybe 6 months to a year ago > (maybe longer), I've made it a habit to upgrade any software for which > Apper notifies me that an upgrade is available. > > Something like two weeks ago, I upgraded the Linux kernel when notified. > > Before the upgrade completed, I got the following popup: > > > Package failed to install - Apper > > One of the selected packages failed to install correctly. > More information is available in the detailed report. > > > And, upon clicking on Details, I got the following: > > > subprocess installed post-installation script returned error exit status 1 > > > But, the upgrade seemed to complete successfully, eventually giving me the > message (~"Your system is up to date, verified hours and minutes > ago"). > > Aside: I did not reboot after that upgrade nor any time since then. > > After that, the next several upgrades proceeded in the same fashion--that > is, I saw the warning that one of the selected packages failed to install > properly, but it then seemed to complete and said my system was up to > date. > > Since then (maybe the last 2 or so upgrades, in the last 2 or 3 days) the > upgrades do not complete successfully--the apper screen just "hangs"--I do > not get the message that the upgrade completed successfully, even if I let > the apper screen sit there for half an hour. > > Today I got a notification to update default-jre, default-jre-headless, and > java common and: > >* it gave me a list of other software that had to be updated: libsctp1, > openjdk-7-jre, and openjdk-7-jre-headless, and I accepted that (clicked > Continue) >* it asked me for authentication, which I gave it >* it downloaded the packages >* it started preparing and installing the packages > > The popup "Package Failed to install - Apper" appeared-- this time I > noticed that it appeared during an attempt to install > "linux-image-3.2.0-4-amd64 Linux 3.2 for 64-bit PCs". > > I don't know (didn't notice) if during the other problem installs it > attempted to install the linux image. > > (Aside: I assume that a new linux-image is only activated after a reboot? > OTOH, when I run uname -a I get: "Linux s19 3.2.0-4-amd64 #1 SMP Debian > 3.2.78-1 x86_64 GNU/Linux" which seems to indicate I am using the latest > Linux kernel (??).) > > Anyway, it seemed that today's update did complete successfully--after > today's upgrade I did get the message: > > > Your system is up to date > Verified 3 hours and 26 minutes ago > > > So: >1. Should I be worried? >2. Should I reboot? >3. Was there something wrong with that kernel upgrade that I should > expect to be fixed, and wait to install that fix before rebooting? >4. Can anyone explain what is going on? >5. Any other advice? > > Thanks! > Randy Kramer
Re: bigs problems wifi connexion
Dnia 2016-06-27, pon o godzinie 17:10 +0200, Jocelyn Lebegue pisze: > Hello, > > since the last update to Debian, the 8.5, I have big problems with my > wifi connection. > > The connection constantly cutting and sometimes asks me the login > password to restart. > I think this is the ath9k package that is the problem, but I do not find > a solution on the forums. > Today I can work on my PC so the cuts are frequent. > > Here's my setup: > HP Pavilion > AMD A6-5200 APU with Radeon HD graphics > Debian 8.5 > Linux AMD64-3.16.0-4 > KDE SC 4.14.2 > wireless card: AR9485 Wireless Network Adapter (AR9485 / HB125 802.11bgn > Wi-Fi Adapter) > > I sincerely hope that you will respond to my message and you will have a > solution that can help me. > > Truly, > > Jocelyn > Boulogne-sur-mer > France > Im rarely using wifi, but try use frag/rts: # iwconfig wlan0 frag 256 # iwconfig wlan0 rts 256 Do experiments with those settings. If wont help, give us result of iwconfig (with no parameters), iwlist wlan0 scan and portion of logs on reconnects/disconnection.
Re: Problems with Apper / automatic upgrading of my Debian 7.11 system
Don't reboot until you know that the bootloader got installed correctly. Ideally have a boot CD ready in case it goes wrong.
Re: Problems with Apper / automatic upgrading of my Debian 7.11 system
That sounds like good advice, thanks! But, has anyone else had similar problems recently with "automatic" upgrades in apper (see my original post), or can anyone explain (or theorize) on what is going on? On Monday, June 27, 2016 01:48:41 PM Johann Klammer wrote: > Don't reboot until you know that the bootloader got installed correctly. > Ideally have a boot CD ready in case it goes wrong.
Re: jessie won't install/boot on a Dell Poweredge R815
I had big issues with mptsas and 3.16 in jessie, so I am still using 3.2.0-4-rt-amd64 Will jessie run with 3.2.0-4-rt-amd64? If so, where do I get it and how do I install it on a fresh jessie install that wasn't dist-upgraded from wheezy? Jeff (http://engineering.purdue.edu/~qobi)
HNI Email List
Hi, I am Amanda, Would you be interested in acquiring an email list of "HNI Email List" from USA? We have data for Cruise Travelers Email List, Pool Owners Email List, RV Owners Email List, and many more. Choose the best one that meets your need. We provide you with current and active contact on every list. Take advantage of that, let your marketing efforts be fruitful. Each record in the list Contact Name( First, Middle, Last Name), Direct Mailing Address ( Address, City, State, Zip Code), List Type, Source, IP Address, and Email Address. All the contacts are opt-in verified, 100% permission based and can be used for unlimited multi-channel marketing. Please let me know your thoughts towards HNI Email List. Best Regards, Amanda Clark --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus
Re: KVM: writethrough / writeback - data integrity
Chris, This wholly depends on what kind of application and/or database you're hosting on your production server; and, it also depends on what kind of back-end infrastructure (SAN? Virtualized Lx? VMware, Xen, otherwise?) -- Write-through, write-back and mixed-mode options have implications that will affect the performance, redundancy, availability and time-to-recover of your production applications. Are you using any database software? In example, production DB filesystems can have different mount options and attributes as listed in /etc/fstab and based on production requirements. Can you share more information about your specific environment? Best, -- Visidon, LLC - http://www.visidon.com/ - supp...@visidon.com Expert cloud, open source software, and Linux consulting services On Mon, 27 Jun 2016, Chris wrote: All, should one use writethrough or writeback caching mode on a production server? I've read on the Internet that writethrough was more secure. With writeback there could be data loss in case of power failure? On the other hand, writeback is Ubuntu's default mode. Is a Debian Jessie VirtIO guest capable of handling "flush disk caches" correctly? I don't know the low-level details. Furthermore, does it matter that the raw-partition respectively raw-image is on a hardware RAID 5? Thank you in advance. - Chris https://www.ibm.com/support/knowledgecenter/linuxonibm/liaat/liaatbpkvmguestcache.htm says: writethrough: mode is the default caching mode. With caching set to writethrough mode, the host page cache is enabled, but the disk write cache is disabled for the guest. Consequently, this caching mode ensures data integrity even if the applications and storage stack in the guest do not transfer data to permanent storage properly (either through fsync operations or file system barriers). writeback: writeback With caching set to writeback mode, both the host page cache and the disk write cache are enabled for the guest. Because of this, the I/O performance for applications running in the guest is good, but the data is not protected in a power failure. As a result, this caching mode is recommended only for temporary data where potential data loss is not a concern.
Interesting audio problem
Hello, I'm not running debian, rather Gentoo, but this happens with any distro and sound card (so far), so I figured this is as good a place as any to start (though linuxquestions is a close second). My sound card is currently (according to lspci), an ATI/ATI SBx00 Azalia (Intel HDA), though I used another ATI card on another MB before the MB broke (the MB was a lemon). Both cards are built into the MB. The said problem also happens independent of the audio playing app. The problem is this, if I plug an audio jack for my headphone into the jack the whole way then I get a lot less volume on the channels. I don't think it's a decrease in the bass, though it might be. Now, if I pull the headphone jack out, just a bit, it plays everything fine. This is a little odd, and I might just dismiss it as a random quirk of my machine, but now it has happened to my laptops headphone jack too. Also, I've recorded some audio from an old cassette tape onto my computer (cassette tape players are getting hard to find), and some of the said audio I somehow got to require that the headphone jack be fully plugged in to play correctly. [scratches head] I with I knew how I did this, it's really odd. So, my questions are: 1: What causes this? 2: How might I rerecord the audio files so they play right on a computer without this problem without using the now broken tape deck? Thanks, David
Re: Interesting audio problem
David Niklas wrote: > Hello, Hi David, > I'm not running debian, rather Gentoo, but this happens with any distro > and sound card (so far), so I figured this is as good a place as any to > start (though linuxquestions is a close second). > > My sound card is currently (according to lspci), an ATI/ATI SBx00 Azalia > (Intel HDA), though I used another ATI card on another MB before the MB > broke (the MB was a lemon). Both cards are built into the MB. > > The said problem also happens independent of the audio playing app. > > The problem is this, if I plug an audio jack for my headphone into the > jack the whole way then I get a lot less volume on the channels. I don't > think it's a decrease in the bass, though it might be. > > Now, if I pull the headphone jack out, just a bit, it plays everything > fine. > > This is a little odd, and I might just dismiss it as a random quirk of > my machine, but now it has happened to my laptops headphone jack too. Did you try with different cables/jacks? What type of jack is it - perhaps you soldiered yourself, or perhaps some special headphones - just asking? In my opinion it might be either hardware - jack is shortening, or some odd setting somewhere, but if latter it wouldn't be same on different board. Anyway for the case it is not the jack itself we would need some additional info. In debian cat /proc/asound/cards cat /proc/asound/card*/codec* cat /var/lib/alsa/asound.state Please attach or upload somewhere. Another option would be a setting to turn off speaker when you plugin headphones. > > Also, I've recorded some audio from an old cassette tape onto my computer > (cassette tape players are getting hard to find), and some of the said > audio I somehow got to require that the headphone jack be fully plugged in > to play correctly. [scratches head] I with I knew how I did this, it's > really odd. > There is no connection between these two. What means correctly? > So, my questions are: > 1: What causes this? > 2: How might I rerecord the audio files so they play right on a computer > without this problem without using the now broken tape deck? It's just like normal recorder - set up input output level and record. If your mixer or pulseaudio are not set up properly you could have issues with the volume. I would check both. There are also cases where the settings for specific audio chips are broken or misaligned - it might also need attention. Just post the specs of your audio card and setup and there will be perhaps someone with the same who could compare and share regards
