MX Linux Forum

A brief how-to > http://www.youtube.com/watch?v=qdY2Jwd2rbQ
A more complex one... long and 2 parts > http://www.youtube.com/watch?v=wtC8RhYHAAI

lucky9 is right

"Post # 331955
Post Re: Harddrives renaming themselves?
The Master/Slave setting is, or at least can be, extremely important. Depends on the Hardware and Software (Firmware on the optical drive) and the kernel that's being used (and the way it's built).
Cable Select (CS) is probably (mostly) the safest setting. However, even CS can cause problems. CS at one time was worse. You had to have the Master and Slave settings correct given what the BIOS was set at (given the particular setup and kernel).
Dive in there girl. We're all here to help,"

I often heard that for the boot drive, usually sda1 you want that as a master , then the CDROM/DVDROM is slave. The slow device should not be a the master.
Therefore it is better if the motherboard has two pata connectors to have the sda1 as master in ide1 and the CDROM as master on ide2. Linux can be particular about correct drives, where Windows will usually work even wrongly wired and set. So the old wisdom was for linux, better to correctly use the master and slave. But, In all my experience cable select works correctly .

If you are going to move jumpers, you need to get the correct setting diagram. It is often on the drive, but when installed it may be hard to see. If you know the model of your drives you can find it with Google. To move them usually a light and tweezers or needle nose pliers are needed. Obviously move the jumpers when the system is powered off.

So much easier with SATA these days !

This is all confusing me way too much with all the namings, sorry guys. Too much info coming at me at once.

I am back from diving in the system! Man did that case get heavier over the years?


One thing: "Obviously move the jumpers when the system is powered off."
I do know I am NOT so stupid to move jumpers with the power on. I have dealt with hardware before multiple times, not just my system but also that friends' as he has a sight problem. I know what to do and what not to do when I dive into a case. Sorry, but that remark did come across a little insulting; I may not remember things, that is an issue in itself, but I am not stupid.


In any case, I opened the case, and then another issue that I did not have back in Sept 2010 crept up on me again.. bleh: I cannot get the power and flat cable out of the drive anymore to remove it to get to the jumper, and I cannot get to the jumper nor the schematic without taking cables out, unfortunately. I'd rather take the drive out of the bay to check its jumper settings schematic as I have no idea what the exact type is anymore, and I am not doing the guessing game with these things.


So.. I have to wait for my friend to help me out with both the info posted before and he can draw his conclusions on it, and also because my hands are not cooperating anymore to be able to do this.

So.. in the mean time I have to leave the disk in the drive.

Ah well.. at least this way I can test THAT solution longer hehe.




Edit: Wednesday afternoon we are going to tackle this one will try both slave and CS, slave first though. I will read him the posts above, so he knows what the issue is that you guys are talking about with the kernel and its preference and such and he can act accordingly with the cables and stuff. Wait and see

I have a large size case so, if necessary, I could pull out the drive while it was still connected to the motherboard and power connector. I forget how it is for smaller cases.
Tweezers make it much easier, especially if the Connectors are still in place. Small needle-nose pliers are easier to use. More leverage.
I print out the Jumper Settings from the manufacturer's website. (I have at least one HDD that doesn't have Jumper Settings printed on the case. I can't remember having an Optical Drive that had no Jumper Settings. (But I used to buy one every year, or every big increase in speed/functionality.)

Yeah.. not so with my case.. those cables are TOUGH to get through. And I don't print out the schematic because simply I don't NEED to change jumpers, never had the need to do so before this now


Anyway. I cannot get to it like this and unless someone has some new hands.. ah well.

Wednesday is the day that I can test stuff.

Eadwine - I have the same motherboard but my dvd drive is connected via SATA (in IDE mode). I have not had a problem with drive renaming, but I have had a few problems on booting and these seem always to be related to drive/dvd identification. I have tried various adjustments in the BIOS to no effect.

When it's next convenient, could you look in your BIOS setup and let me know the Asus BIOS version (mine is 1601). Also in Main>SATA Configuration for the settings (I have Ports 1-4 AHCI & Ports 5-6 IDE). Finally, your Boot Device Priority ( mine is CDROM, IDE: Corsair SSD, Removable Device).

I don't use the PATA port - by the time I built this machine I had heard of enough problems mixing PATA & SATA that I bought a new SATA DVDE writer.

Phil

This I can do

Gaer Boy wrote:When it's next convenient, could you look in your BIOS setup and let me know the Asus BIOS version (mine is 1601).

I find two version numbers, one in the bottom of the screen, says v02.61, and one in main-system info: version 2005

Also in Main>SATA Configuration for the settings (I have Ports 1-4 AHCI & Ports 5-6 IDE).

All IDE

Finally, your Boot Device Priority ( mine is CDROM, IDE: Corsair SSD, Removable Device).

1: cdrom: pm-plextor d
2: sata: 3M-WDC WD5000
3: Removable Dev.

I don't use the PATA port - by the time I built this machine I had heard of enough problems mixing PATA & SATA that I bought a new SATA DVDE writer.

The old burner cost me plenty, I wasn't going to buy a new one just yet.

Again I will say: this was never an issue, until now.

I think the 2.62 version is the base AMI BIOS version that Asus used. They tweak it for the motherboard and add their version number - top right of the BIOS screen. As far as I can see, they started with v1015 in 2010 and it was rapidly updated in 2010 to v1601 and then a few updates in 2011 & 2012. Typically, Asus are no more forthcoming that Microsoft when it comes to updates - except for a major one to correct RAID setups, most of the others say "Improve system stability".

Anyway, I wouldn't suggest a BIOS update - as far as I'm concerned, it's a last resort when something won't work. Your other settings seem OK. If you still get problems, you might try moving the cdrom down the Boot Priority list - if you need to boot from CD/DVD you can hit F8 early in the boot.

My occasional boot hangs sometimes produce split messages re disks on screen. The next time I get one, I'll transcribe the sequence - that could be weeks or months from now.

Anyway, I wouldn't suggest a BIOS update - as far as I'm concerned, it's a last resort when something won't work.

Indeed, it is not something I am even willing to do It may open a whole other can of worms that cannot be closed, so not going there anyway hehe

Your other settings seem OK. If you still get problems, you might try moving the cdrom down the Boot Priority list - if you need to boot from CD/DVD you can hit F8 early in the boot.

F8? Oh? I didn't know about that one, thanks.

Could it help to move it down the list, set the WD as the first one, that way it won't even look at the plextor upon boot, might sort it too? *shrug* Just throwing something up if I need to boot a livecd I can always change it back after all.

That's my thought. I don't know that it would have effect, but it can't hurt to try.