Re: [ilugd] (hardware/slightly OT) New SATA disk giving BIOS errors
you should try changing the disk mode to _ata_ if it is set to _ahci_. This option is somewhere in the BIOS settings. ___ Ilugd mailing list Ilugd@lists.linux-delhi.org http://frodo.hserus.net/mailman/listinfo/ilugd
Re: [ilugd] (hardware/slightly OT) New SATA disk giving BIOS errors
A. Mani said on Thu, Nov 24, 2011 at 08:49:01AM +0530,: > Some mainboard component has failed or it is a built-in bug for the > type of chipset you have. Yes, I suspect I will upgrade the BIOS and see. > > change bios. > > Remove all other sata drives and test. No use - see the other mail. > use ahci 1. How? "ahci=yes" or somesuch on the kernel? 2. But I am talking of BIOS? > speed? The mobo supports 3 GBPS transfer rate on the SATA port. Not sure about the disk - now I need to pull itout to read the label. Will do it later. Now, this has me thinking. Thanks for the hint, will check if this can cause such issues. Or, in otherwords, will using a 6GBPS capable drive on a 3gbps only mobo cause problems? Aren't these thingies supposed to be backward compatible? Or should I look for some jumber settings on the disk? (errrm... cannot find any - this is a SATA disk nothing looking like jumber connectors on it). -- Mahesh T. Pai || The next best thing to knowing something is to know where to find it. --Samuel Johnson ___ Ilugd mailing list Ilugd@lists.linux-delhi.org http://frodo.hserus.net/mailman/listinfo/ilugd
Re: [ilugd] (hardware/slightly OT) New SATA disk giving BIOS errors
Ashish SHUKLA said on Thu, Nov 24, 2011 at 08:46:15AM +0530,: > Are you sure your RTC (real-time clock) battery is not discharged ? Maybe try > replacing the battery. This certainly is not a battery / RTC problem, because things work perfectly with the new drive disconnected. > I used to experience these issues (has nothing to do with RTC) some years > ago, > mostly due to crappy SMPS, bad power/data cable which got fixed after I > replaced its SMPS. Again, everything on the system is same - except a new drive and its cable. Did try changing the cable; no avail. Did try with the other SATA dirk disconnected, again no avail. > And what's that error message you get from BIOS ? How do I find out - except with the POST card you mentioned? > > 2. Is there a problem with the new disk? > > Very less likely. Thanks, it is a relief to hear that. Anyway, the system was powered off few minutes after I posted the question, and powered on just now; and with the new HDD disconnected, things work just fine. Since ifup scripts automatically run ntpdate sync, the system time is all right just now. And syslog says time was offset by a mere -0.3odd seconds. I hate to tinker with the bios; and chipset is z not supported by flashrom. :-( That by itself does not seem to be a problem, since the BIOS seems to support reading from ISO9660 filesystems for upgrading the BIOS. There goes my weekend!!! (120KM commuting and a 15hour work schedule is not very conducive for flashing the BIOS). . -- Mahesh T. Pai || L'homme est libre au moment qu'il veut l'etre. * Man is free at the instant he wants to be. ___ Ilugd mailing list Ilugd@lists.linux-delhi.org http://frodo.hserus.net/mailman/listinfo/ilugd
Re: [ilugd] (hardware/slightly OT) New SATA disk giving BIOS errors
On Thu, Nov 24, 2011 at 7:48 AM, Mahesh T. Pai wrote: > > Hi all. > > I know this is not related to Linux or FOSS. But the box runs Debian, > and am hoping that people here would have some experience dealing with > things like this. > > I got a new 500 GB SATA HDD, Seagate make. Output of smartctl says > something about compliance with version of 8 of ATA standards. (the > disk is not connected right now). There are many SATA versions http://www.t13.org/Standards/Default.aspx?DocumentType=3 > > When the new disk is connected, the BIOS either shows a blank screen > or throws up an error message, and asks me to set CMOS time, which > falls back to 2002. Especially When I power on after a gap of 20 > minutes or more. M28N Some mainboard component has failed or it is a built-in bug for the type of chipset you have. change bios. Remove all other sata drives and test. use ahci speed? Best A. Mani -- A. Mani CU, ASL, CLC, AMS, CMS http://www.logicamani.co.cc ___ Ilugd mailing list Ilugd@lists.linux-delhi.org http://frodo.hserus.net/mailman/listinfo/ilugd
Re: [ilugd] (hardware/slightly OT) New SATA disk giving BIOS errors
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Mahesh T Pai writes: > Hi all. /nick all Hi Mahesh, > I know this is not related to Linux or FOSS. But the box runs Debian, > and am hoping that people here would have some experience dealing with > things like this. > I got a new 500 GB SATA HDD, Seagate make. Output of smartctl says > something about compliance with version of 8 of ATA standards. (the > disk is not connected right now). > When the new disk is connected, the BIOS either shows a blank screen > or throws up an error message, and asks me to set CMOS time, which > falls back to 2002. Especially When I power on after a gap of 20 > minutes or more. Are you sure your RTC (real-time clock) battery is not discharged ? Maybe try replacing the battery. I used to experience these issues (has nothing to do with RTC) some years ago, mostly due to crappy SMPS, bad power/data cable which got fixed after I replaced its SMPS. And what's that error message you get from BIOS ? > There are no error messages in any of the logs; if I get past the BIOS > barrier, I can use the disk, I partitioned and created ext4 FS too. > The BIOS is of 2002 vintage, going by the copyright notice in the BIOS > menu. But the system is hardly 3 years old; it is an Asus M2N 68 AM > plus mother board. The other disk too is a SATA one, only 80 Gigs, > and is about 6 years or more old (reused the old disk in the new > system). The DVD r/w drive is IDE. So are there total of 3 drives (including the DVD writer) connected in your box ? > Questions:- > 1. Is this a problem with the MoBo / BIOS? Probably. > 2. Is there a problem with the new disk? Very less likely. > 3. How safe is it to tell the BIOS to ignore boot up errors (there is >an option somewhere in the BIOS to "halt on errord" - currently enabled) > 4. How to identify the error BIOS is getting? For extended troubleshooting, you can get a POST card[1] (or Debug card), a PCI card which displays progress made by BIOS by emitting various codes as it progresses to the I/O port which POST cards hooks itself to, and used to sell for INR 100-150 few years ago. You'll need your motherboard manual (or a copy of Upgrading and Repairing PCs[2]), which contains a table to interpret the codes. > Anything else I can do here? Maybe start with replacing RTC battery, if you've not already done that. References: [1] http://en.wikipedia.org/wiki/POST_card [2] http://www.quepublishing.com/imprint/series_detail.aspx?st=87406 HTH - -- Ashish SHUKLA “You don't have to distrust the government to want to use cryptography.” (Phil Zimmermann) -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.17 (FreeBSD) iQIcBAEBCgAGBQJOzbcFAAoJEMdGz6nnT6Sw+OUP/2B6ah6v0PqWgRmPL7Oo6ZFa iLPvU0CtF+spFPJUhBTkNNFNZRIN6O8WWWTkvK7/mCL4px36iBSHHV/16l0YkRB7 nwSK5Xq3EbCV0v5QoSnkPSZgydBuiveocq4PnRFAsMNJC5ckmb1nUlTwmARBD1D0 3GauJq5mBHWvgE1E1rFZC8KFkUoArizY7X6pTjlI9OMfSqSOBqLAhs61jnFkdYJ8 wYnaoPp+zZ1R93QLweN5/S93NqdsgIY8H9t7ZNSNhmoCa2vuWhBe8XfGXYQwN+V8 hmbAmY4ixrphFyCWzxLZapp/UJ/qeoErtoFo8Az9qnv0H37lBklG2bx++5jikcH8 DTu7iVG98GEOMtOxJSd60e58d2bvX6BZwO9r51CjkqLpX2UUdG/klxGRPxKyzkCf 6o3zfSN6VCreGC9ePkM+ZjU9U9VktUuEivF+wdhnAIowSH4Pq4L/oCd1PbDZ8dZb 1i0zsaGzrMVrjShTVg11TM9LInocpivfimiEb928WYC5WXOh8y86K8tAFnhCnz3V hFwvBuBIiRAcSf8zl7vZ64iCkJ71SlkMkgOEMGiHzakV4F0v3qe3LGeZq7mJ4+/j LMEPmRF9qfCblzKYQHuc1hPFVGkJj40rHwuIM8Gt+sGKEVswJkoMdeM50/+X4r5H eIRu4bkgwCBG0ykYnFfV =iPsQ -END PGP SIGNATURE- ___ Ilugd mailing list Ilugd@lists.linux-delhi.org http://frodo.hserus.net/mailman/listinfo/ilugd
[ilugd] (hardware/slightly OT) New SATA disk giving BIOS errors
Hi all. I know this is not related to Linux or FOSS. But the box runs Debian, and am hoping that people here would have some experience dealing with things like this. I got a new 500 GB SATA HDD, Seagate make. Output of smartctl says something about compliance with version of 8 of ATA standards. (the disk is not connected right now). When the new disk is connected, the BIOS either shows a blank screen or throws up an error message, and asks me to set CMOS time, which falls back to 2002. Especially When I power on after a gap of 20 minutes or more. There are no error messages in any of the logs; if I get past the BIOS barrier, I can use the disk, I partitioned and created ext4 FS too. The BIOS is of 2002 vintage, going by the copyright notice in the BIOS menu. But the system is hardly 3 years old; it is an Asus M2N 68 AM plus mother board. The other disk too is a SATA one, only 80 Gigs, and is about 6 years or more old (reused the old disk in the new system). The DVD r/w drive is IDE. Questions:- 1. Is this a problem with the MoBo / BIOS? 2. Is there a problem with the new disk? 3. How safe is it to tell the BIOS to ignore boot up errors (there is an option somewhere in the BIOS to "halt on errord" - currently enabled) 4. How to identify the error BIOS is getting? Anything else I can do here? -- Mahesh T. Pai || Free Software - it is free as in FREEDOM ___ Ilugd mailing list Ilugd@lists.linux-delhi.org http://frodo.hserus.net/mailman/listinfo/ilugd
