Harddrives renaming themselves?

[Eadwine Rose]

*facepalm* Why didn't I think of that??



(I want a like button.. heh)

[Eadwine Rose]

Happened again. Last thing to try is putting the Plextor on slave with the jumpers (currently on CS, and becomes master during the boot).

[richb]

I just ran into this for the first time. I just got a USB 3.0 stick. I have always used USB 2.0 in USB 2.0 ports. When I booted the USB 3.0 stick in a USB 3.0 port, what was sda, the internal hard drive, became sdb and the stick was sda.

It would seem to be a timing problem. Is it possible the stick beat the hd when booting?

[anticapitalista]

I just ran into this for the first time. I just got a USB 3.0 stick. I have always used USB 2.0 in USB 2.0 ports. When I booted the USB 3.0 stick in a USB 3.0 port, what was sda, the internal hard drive, became sdb and the stick was sda.

It would seem to be a timing problem. Is it possible the stick beat the hd when booting?

Yes and it is all pretty random now how devices are labelled ie sda or sdc

[Eadwine Rose]

Rich: Could very well be!


I am getting this about 20-25% of the time still with my system. Still need to change that jumper on plextor to slave though. Other stuff is keeping me occupied at the moment


Anti: you mean there is a newer kernel and such now that will avoid such problems as I have here in the future?

[richb]

I just ran into this for the first time. I just got a USB 3.0 stick. I have always used USB 2.0 in USB 2.0 ports. When I booted the USB 3.0 stick in a USB 3.0 port, what was sda, the internal hard drive, became sdb and the stick was sda.

It would seem to be a timing problem. Is it possible the stick beat the hd when booting?

Yes and it is all pretty random now how devices are labelled ie sda or sdc

Then unexplained.

[anticapitalista]

Anti: you mean there is a newer kernel and such now that will avoid such problems as I have here in the future?

No, the opposite :)

[anticapitalista]

I just ran into this for the first time. I just got a USB 3.0 stick. I have always used USB 2.0 in USB 2.0 ports. When I booted the USB 3.0 stick in a USB 3.0 port, what was sda, the internal hard drive, became sdb and the stick was sda.

It would seem to be a timing problem. Is it possible the stick beat the hd when booting?

Yes and it is all pretty random now how devices are labelled ie sda or sdc

Then unexplained.

Newer kernels set the device name (sda/sdc etc) on a first come first served basis. This means that your usb stick might be shown as sda on one box, but sdc on another or even possibly sda on first boot and sdc on second boot. It is a race.
BitJam posted somewhere about this.

[richb]

Yes and it is all pretty random now how devices are labelled ie sda or sdc
Then unexplained.

Newer kernels set the device name (sda/sdc etc) on a first come first served basis. This means that your usb stick might be shown as sda on one box, but sdc on another or even possibly sda on first boot and sdc on second boot. It is a race.
BitJam posted somewhere about this.

That was what I meant, in-artfully stated.

[Eadwine Rose]

Cool.. we can expect more of these situations then with newbies coming in asking why their dvd players aren't recognized.

Something to keep in the back of the mind then when something unexplained like this comes along: ask for that drive naming command.