[opensuse-factory] Tumbleweed on SSD stopped booting
I have this *Let's see about ssd's* install on partition 3 of a 250gb tester (GPT table). It stopped booting (possibly after an update). Some start job is not completing. see attached. The SSD is in a new iStar rack http://trixtar.org/3/tinkerings/quietcool/quietcool.html ..second rack image near bottom I've noticed that as opposed to the other magnetic drives showing blue lights the light for this SSD is ALWAYS pinkish, as if it were always writing. TIA
Am 27.11.2016 um 04:42 schrieb k-16@trixtar.org:
I have this *Let's see about ssd's* install on partition 3 of a 250gb tester (GPT table). It stopped booting (possibly after an update). Some start job is not completing. see attached.
how many disks are in this machine? -- Stefan Seyfried "For a successful technology, reality must take precedence over public relations, for nature cannot be fooled." -- Richard Feynman -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Sun, 27 Nov 2016 11:30:04 +0100
Stefan Seyfried
Am 27.11.2016 um 04:42 schrieb k-16@trixtar.org:
I have this *Let's see about ssd's* install on partition 3 of a 250gb tester (GPT table). It stopped booting (possibly after an update). Some start job is not completing. see attached.
how many disks are in this machine?
#1 2tb normal battlestar wd #2 250gb samsung ssd #3 unbootable 2 tb backup wd #4 unbootable 2 tb backup wd (green POS on death row) #5 unbootable 500 gb oldie wd if I wanna boot the ssd, i pull #1 if I wanna boot the primary i pull the ssd #3 is always plugged-in the others i plug/pull according to anticipated need {I don't do raid & I use only dev-id} slot #5 is really unusable, it serves as a shelf mostly because bios setup assigns #5 & #6 to IDE so as to protect DVD boots. I haven't yet looked into working around this for lack of real need to. I'm still learning, I think if i leave #1 and #2 withj the ssd in then the ssd will boot, don't know why the ssd would preferentially show up a the boot disk I love this kind of storage, no internal fixed drives!
-- Stefan Seyfried
"For a successful technology, reality must take precedence over public relations, for nature cannot be fooled." -- Richard Feynman -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Am 27.11.2016 um 14:53 schrieb k-16@trixtar.org:
On Sun, 27 Nov 2016 11:30:04 +0100 Stefan Seyfried
wrote: how many disks are in this machine?
#1 2tb normal battlestar wd #2 250gb samsung ssd #3 unbootable 2 tb backup wd #4 unbootable 2 tb backup wd (green POS on death row) #5 unbootable 500 gb oldie wd
if I wanna boot the ssd, i pull #1
if I wanna boot the primary i pull the ssd
#3 is always plugged-in
the others i plug/pull according to anticipated need {I don't do raid & I use only dev-id}
Well, the photo you showed looks like you use devname (/dev/sda3) in fstab. It shows sde,f,g,h which looks like 8 drives, or that the persistent naming rules for some reason have decided your drives have to be freshly named. Try booting by-uuid or by-label, and it might work better / more reliable. -- Stefan Seyfried "For a successful technology, reality must take precedence over public relations, for nature cannot be fooled." -- Richard Feynman -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
#1 2tb normal battlestar wd #2 250gb samsung ssd #3 unbootable 2 tb backup wd #4 unbootable 2 tb backup wd (green POS on death row) #5 unbootable 500 gb oldie wd
if I wanna boot the ssd, i pull #1
if I wanna boot the primary i pull the ssd
#3 is always plugged-in
this was WROOOOONG
the others i plug/pull according to anticipated need {I don't do raid & I use only dev-id}
Well, the photo you showed looks like you use devname (/dev/sda3) in fstab.
To ask the question is to answer it. Did I say I was experimenting with SSD? When I installed it there was no other drive plugged-in, so it showed up as partition-3 on /dev/sda. But then I forgot that if booting the ssd then the other drives could be plugged-in only after booting. It's the same story as when the first SATA's hit the street, if only one PATA was also plugged in then it had to become /dev/sde. I don't se why it has to be this way but it doesn't really matter because soon there may be no magnetic drives left at all just like there are no PATAs left today.
Try booting by-uuid or by-label, and it might work better / more reliable.
That's a non-starter for me, it may be more reliable in some ways but it's too many headaches for me as I use dd blatantly, all the time, to copy partitions :-) If dd ever becomes extinct I'll can computing ALTOGETHER! -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 2016-11-27 23:34, k-16@trixtar.org wrote:
Well, the photo you showed looks like you use devname (/dev/sda3) in fstab.
To ask the question is to answer it. Did I say I was experimenting with SSD? When I installed it there was no other drive plugged-in, so it showed up as partition-3 on /dev/sda. But then I forgot that if booting the ssd then the other drives could be plugged-in only after booting. It's the same story as when the first SATA's hit the street, if only one PATA was also plugged in then it had to become /dev/sde.
I don't se why it has to be this way but it doesn't really matter because soon there may be no magnetic drives left at all just like there are no PATAs left today.
This is absurd. You have to forget about using names such as /dev/sda3. That is causing you problems. Just use proper access, then forget about having to connect or disconnect this or that disk.
Try booting by-uuid or by-label, and it might work better / more reliable.
That's a non-starter for me, it may be more reliable in some ways but it's too many headaches for me as I use dd blatantly, all the time, to copy partitions :-)
If dd ever becomes extinct I'll can computing ALTOGETHER!
Just learn how to use things properly. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
On Monday 2016-11-28 00:18, Anton Aylward wrote:
On 11/27/2016 05:51 PM, Carlos E. R. wrote:
Just learn how to use things properly.
Quit right.
Just in case you were wondering how to get off the stage in style ;-) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
k-16@trixtar.org composed on 2016-11-27 17:34 (UTC-0500):
Stefan Seyfried composed on 2016-11-27 18:05 (UTC+0100):
Try booting by-uuid or by-label, and it might work better / more reliable.
That's a non-starter for me, it may be more reliable in some ways but it's too many headaches for me as I use dd blatantly, all the time, to copy partitions :-)
No headaches here, where cloning is routine. It's a simple enough matter to update UUIDs and LABELs after cloning operations. I both boot and mount FOSS filesystems by LABEL as a matter of course, which is mentally much easier than by UUID or by ID. The labels make it simple enough to keep track of what's what when partition count is the normal-for-around-here count of upwards of a dozen, even as many as 63 on one disk. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
That's a non-starter for me, it may be more reliable in some ways but it's too many headaches for me as I use dd blatantly, all the time, to copy partitions :-)
No headaches here, where cloning is routine. It's a simple enough matter to update UUIDs
That approach is not excluded in the future, I just have too many other things going on to get involved in anything new
Team OS/2 **
Wellllll, I'll be! I remember packing Lilo and warp BootMangler onto several disks for a Christmas show once, one would boot the other in a neverending chain using different colors ..it was pretty :-))) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 11/27/2016 05:34 PM, k-16@trixtar.org wrote:
Try booting by-uuid or by-label, and it might work better / more reliable. That's a non-starter for me, it may be more reliable in some ways but it's too many headaches for me as I use dd blatantly, all the time, to copy partitions :-)
That /shouldn't/ be a problem. Or rather it wouldn't be a problem for me, if I used DD to copy. Sometimes I use rsync. that's very useful when I'm face with my ~/MyPhotographs/ByYear and want to move part of the tree, say 2015, to a new partition. I can also use it with 'find' to do more specific filtering. I mention this as moving part of partition, splitting a partition, freeing up space, archiving, is more common for me, and I suspect a number of other people. that simply shuffling partitions. When I do need to copy a partition as a while, well I use LVM, remember :-) That has the ability to move a 'partition', or as LVM terms it, a Logical Volume (LV). Simply take a snapshot and copy that. heck, the snapshot only need to be as big as space used on the primary, so you can use this technique to shrink or grow a 'partition'! If you’re using the same size partitions you could use dd, or even xfs_copy if you’re using XFS. However if what you are doing is a "move", that is a copy/delete-the-original, migrating to a new physical drive, the 'pvmove' command can do that all in one go. But in the absence of LVM, simply using DD to copy, yes it copies the whole image, and with it the UUID and label information But so what? You can simply - and immediately, before you forget - relabel the new partition and set a new uuid The 'swaplabel' command can be used for this, do them both with one command: swaplabel -L NEWLABEL -U $(uuidgen) /dev/sdXXXnnn There are probably other ways, after all this is Linux and Larry's Dictum usually applies" "There's more than one way to do that". -- /"\ \ / ASCII Ribbon Campaign X Against HTML Mail / \ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
participants (6)
-
Anton Aylward
-
Carlos E. R.
-
Felix Miata
-
Jan Engelhardt
-
k-16@trixtar.org
-
Stefan Seyfried