Harddrives renaming themselves?

[Eadwine Rose]

Guess what.. hehe, here we are:

/etc/fstab

Code: Select all

# Pluggable devices are handled by uDev, they are not in fstab
UUID=db1aed9a-aa14-4458-a611-ddf5d06a7aa6 / auto defaults,noatime 1 1
UUID=399beb91-0a62-43e1-bd92-496305879ac6 swap swap sw,pri=1 0 0
proc /proc proc defaults 0 0
devpts /dev/pts devpts mode=0622 0 0
UUID=375a7b9d-8ef3-4d99-b0a8-7b8b28fd3d74 /home auto defaults,noatime 1 2

wrongboot.txt

wrong70-persistent-cd.rules.txt

Now going to insert a dvd with data in the plextor... aha nope it doesn't get seen:

Code: Select all

root@eadwinemx14beta2:/home/eadwine# cat /proc/sys/dev/cdrom/info
CD-ROM information, Id: cdrom.c 3.20 2003/12/17

drive name:		sr0
drive speed:		40
drive # of slots:	1
Can close tray:		1
Can open tray:		1
Can lock tray:		1
Can change speed:	1
Can select disk:	0
Can read multisession:	1
Can read MCN:		1
Reports media changed:	1
Can play audio:		1
Can write CD-R:		0
Can write CD-RW:	0
Can read DVD:		1
Can write DVD-R:	0
Can write DVD-RAM:	0
Can read MRW:		1
Can write MRW:		1
Can write RAM:		1

Sees only the reader, the Sony, I cannot access the dvd in the drive. Open and close and that is it for the plextor.

Inserting the sd card and as expected that becomes sdd now

wrongbootwithsd.txt

Hope this all helps!

[Eadwine Rose]

I have an idea.. no clue if it works of course.

I am going to leave the dvd with data on it in the Plextor drive. I did that earlier when I rebooted from this wrong one back into a correct boot, who knows maybe upon booting the system will see the dvd and notice it is something not resembling a harddrive *shrug*

Worth a test in any case, and it won't interfere with other things that I am doing

[BitJam]

I hope this will help.

It helps in the sense that it confirms it is quite broken and won't be fixable by writing a udev rule. I'm glad I asked for the redundant information because sda does not even show up in the lsblk output.

One thing I noticed is that the scsi adapter numbers move around between the working and the broken boots:

Code: Select all

Device    Good        Bad
------    ----        ---
Plextor   4:0.0.0     0:0.0.0
Sony      4:0.1.0     0:0.1.0
WD        0:0.0.0     2:0.0.0
LaCie     6:0.0.0     6:0.0.0

The first number is the adapter number which the kernel assigns to adapter card. Then it is channel number, id number, and lun number. The udev rules file seems to assume that these number do not change between boots. In fact your 70-persistent-cd.rules file seems to have been configured in what I list as the bad configuration above. So that file may not be doing anything useful because the symlinks are being created even when the rules don't match.

I don't know if the change in adapter number is related to the problem or not. If you want to find out if they are related then you can run "sudo lshw -C disk" after good boots and bad. The four numbers are listed in the "bus info" field. The LaCie enclosure with the Hitachi drive inside does not have a "product" field but you can deduce which one it is from the logical name and the size. But even if you were to gather this information, I don't know what to do with it.

I am almost out of ideas. I like your idea if leaving a dvd in the drive. My final idea would be to compare the output of "lsmod" when the names are correct and when they are not. Maybe a different module is getting loaded or used and that is causing the problem. I don't think this is very likely but if it is associated with the problem then the solution could be simple by either forcing a module to load or by blacklisting it.

[Eadwine Rose]

The sda4 did show up in Thunar I believe, just couldn't do anything with it. I will cross check next time as I am now in a correct boot again.

Here are two correct boot files of sudo lshw -C disk and lsmod

lsmod.txt

lshw.txt

sdc is present as the canon card is inserted because I took some pics again.

I will do the same commands and list what I get upon a wrong boot.


Mind just for those wondering what the heck I do with all the inserting of that camera card
I modify puzzles for a hobby amongst other things and share the pictures of the progress with fellow puzzlers Here is a picture of something currently in progress

megaball2.jpg

Anyways, that is that. I'll get back to you when I obtain more info on a wrong boot

Any other commands that I can do in this proper boot and the wrong boot for you guys to compare?

[JBoman]

The unrecognized sr0 makes me wonder if the problem I just had recently is related... see here..> http://www.forum.mepiscommunity.org/vie ... 85&t=35587

[kmathern]

...If you are unhappy with this change, just wait until you see what they are doing to eth0. ...

Offtopic: What are they doing to eth0?

[lucky9]

I admit that I'm hanging also.

[BitJam]

It's called Consistent Network Device Naming. There are a number fiery of threads about this over on the Gentoo forums. I think what rankled many people was the fact that this is enabled by default even though the vast majority of people have just one network card and therefore have no need for eth0 to be renamed. Other people were upset because the so-called consistent names would change after reboot or even while running. Changes like this in udev have caused a lot of system breakage over the past few years. This one could hose a system you trying to administer remotely. There was a breakout of people thinking other people are stupid which can be highly contagious. One result is that enthusiasm for systemd has been greatly dampened in some quarters. If you want to talk more about this, we should start a new thread.

[JBoman]

It's called Consistent Network Device Naming. There are a number fiery of threads about this over on the Gentoo forums. I think what rankled many people was the fact that this is enabled by default even though the vast majority of people have just one network card and therefore have no need for eth0 to be renamed. Other people were upset because the so-called consistent names would change after reboot or even while running. Changes like this in udev have caused a lot of system breakage over the past few years. This one could hose a system you trying to administer remotely. There was a breakout of people thinking other people are stupid which can be highly contagious. One result is that enthusiasm for systemd has been greatly dampened in some quarters. If you want to talk more about this, we should start a new thread.

Thought that was Fedora specific... is it not?

[Eadwine Rose]

Just letting you guys know I am still keeping an eye on this. Leaving the dvd disk in the drive still.

I haven't done that many reboots lately, but there has been no occurrence either. You'll see now that I have posted this that tomorrow morning when I boot the system the wrong boot happens