#qa | Logs for 2020-02-23

« return
[02:39:27] <Bytram> janrinok: Well, what do you know? Tried the clone SSD in old lappy. Got through BIOS. Saw Starting Windows logo, a few seconds (5-10 or so) and the win logo disappeared as if it were about to boot up... but only a black screen displayed. Waited a minute. Tried another power off and then and another power up. Saw same as before. Hard drive light was blinking *very* briefly about every second. The Caps Lock key was working (saw the light
[02:39:27] <Bytram> indicator come on/go off).
[02:41:56] <chromas> Is that farther than you got with it in the other lap?
[02:42:58] <Bytram> Powered off, yanked the cloned windows SSD. Removed battery & power cord. Reinstalled orig windows SSD. reconnected everything, hit power switch. Complained date/time needed to be set. Set date/time in BIOS, and while I was there, took a picture of every screen in the BIOS for future reference, if ever needed.
[02:44:47] <Bytram> Clicked the "Exit" button in lower right hand corner. Took close to two minutes to get through BIOS (normally is only a couple/few seconds), but eventually it completed, commenced to loading Windows... and it all came back as normal.
[02:46:45] <Bytram> chromas: Please... if you see me documenting something here, I would appreciate waiting until I am done, or ping me in another channel. I *do* appreciate your assistance and know that you are trying to help, but these are my my "instructions" to refer back to in the future.
[02:47:13] <Bytram> To answer your question...
[02:48:42] <Bytram> On the new lappy, it would get to displaying the Windows logo for about 5 seconds... and then do a restart as if it had been powered down (so back through loading BIOS) and then into the loading Windows screen... repeat. repeat. repeat.
[02:49:03] <Bytram> Main difference is
[02:50:07] <Bytram> on the old lappy with the clone SSD, it would get to the WIndows logo, go to a black screen.. and just sit there. New lappy would get stuck in a "boot loop".
[02:52:09] <Bytram> I am really strongly suspecting that the clone IS NOT an exact duplicate of the original disk, and would like nothing better than to start over right from the beginning. Format the drive, (cause right now the clone SSD has the same "drive ID" as the original SSD.
[02:52:27] <Bytram> Excellent question!
[02:52:57] <Bytram> Any other questions?
[02:54:21] * chromas scrolls way back
[02:55:25] <chromas> Did you get ubuntu to install?
[02:55:54] <chromas> And if so, does it boot if you put the SSD it's installed to into the new Windows-to-be lap?
[02:56:07] <Bytram> Yes, that went just fine. New lappy has Ubuntu 18.04.4 installed on its internal SSD
[02:57:10] <Bytram> Grr! Excellent question! I *just* got the old lappy rebooted back into windows... would rather hold off on that unless you are following a hunch.
[02:57:42] <chromas> Just wondering if that particular lap has a hardware issue
[02:58:13] <Bytram> I have absolutely no reason to imagine why Ubuntu SSD should fail to boot on old lappy.
[02:58:41] <Bytram> Okay... I see where you are going.
[02:58:45] <chromas> oh, I mean the other new one. That's the one you're trying to boot the cloned Windows SSD on, right?
[02:59:22] <chromas> Although I'm not sure which one you cloned the SSDs from. Thought maybe the cloning box could have an issue
[02:59:38] <Bytram> But, if the new *did* have a hardware issue... it already *can* boot the Ubuntu SSD. What would we learn if the Ubuntu SSD also booted on old lappy.
[02:59:53] <Bytram> Quick synopsis.
[03:01:33] <Bytram> ugh fat fingrs...
[03:01:43] <Bytram> About a year ago or so
[03:02:39] <Bytram> Cloned the old lappy's 500GB spiny disk to 1 TB using Samsug's utility they provided.
[03:03:19] <Bytram> The Windows SSD has been running fine ever since
[03:03:55] <Bytram> a couple/three days ago (I'm tired, do not remember exactly)
[03:04:26] <Bytram> tried to clone the win SSD from the old lappy onto another SSD to use in the new lappy.
[03:04:46] <Bytram> Booted sysrescuecd on old lappy
[03:05:29] <Bytram> tried to use ddrescue. All was fine *except* I could not seem to get it to accept writing its mapfile to a USB stick.
[03:05:36] <Bytram> got frustrated with that.
[03:05:52] <Bytram> decided to back off and use plain old dd
[03:06:33] <Bytram> no joy at first... from the error messages, I gathered the new drive needed some kind of initialization.
[03:06:40] <Bytram> Launched gparted.
[03:06:57] <Bytram> Looked around.
[03:07:24] <Bytram> Never used it before, so this was a bit... challenging and nerve-wracking
[03:08:10] <Bytram> Tried to set up a primary partition, but got some kind of error message which suggested to me i was missing a boot record or somesuch.
[03:08:55] <Bytram> From the error message, I deduced I needed to setup a DOS boot area of some kind.
[03:09:19] <Bytram> Clicked the obvious buttons and it seemed to work.
[03:09:40] <Bytram> then closed gparted and returned to command prompt.
[03:10:03] <Bytram> Next up was to use dd
[03:10:30] <Bytram> dd if=/dv/sda of=dev/sdb bs=1GiB status=progress
[03:10:42] <Bytram> (If memory serves)
[03:11:18] <Bytram> the SSD I was cloning to was in an external USB drive enclosure/.
[03:11:35] <Bytram> Old lappy's ports top out at USB 2.0
[03:12:18] <Bytram> So, just a bit over 9 hours later, the copy completed and I was returned to the command line.
[03:12:35] <Bytram> Saw no error msg displayed.
[03:13:13] <Bytram> But, when I tried to boot the clone win SSD, in the new lappy, got stuck in a boot loop.
[03:13:44] <Bytram> and now I believe we are caught up to the current time.
[03:14:05] <Bytram> Is that clear? Have any questions?
[03:16:40] <chromas> I think so. Do you still have Samsung's clone utility?
[03:18:07] <Bytram> I expect so... the reason I did not use it originally was that it was designed to clone spinny disk... doubted it would know what to do with as SSD as the source drive.
[03:26:35] <chromas> Do you have a log of the error messages from when you used dd?
[03:26:46] <chromas> (of course he does :) )
[03:26:50] <Bytram> possibly...
[03:27:39] <chromas> I'm wondering because dd shouldn't even know about your partitions (and will overwrite that part of the disk anyhow)
[03:27:43] <Bytram> I was really tired at that point, was seeing so many things that were not going to plan, so I pretty much resigned myself to muddling throught.
[03:31:38] * Bytram is still looking through all the pics he took
[03:32:27] <chromas> A neat thing you can do is open another terminal and run dmesg -wT
[03:32:59] <Bytram> NOTE TO SELF ^^^ =)
[03:33:20] <chromas> dmesg will watch the kernel messages. -w is for watch (like tail) and T gives formatted time. It'll let you know when you plug stuff in and whatnot. Should tell you the driver it's using
[03:34:20] <Bytram> Oh, forgot this part. After probs with ddrescue, I gave clonezilla a try. No Joy.
[03:34:52] <Bytram> Very Nice! Thanks for that!
[03:39:59] <Bytram> clonezlla: Do you want to clone the boot loader (executable code area, the first 446 bytes) to sdc ?
[03:42:36] <Bytram> "Failed to find this Partition in this system: /dev/sdc1
[03:45:38] <Bytram> Still no joy looking for error message.
[03:46:36] <Bytram> Almost fell asleep in my chair. I've been at this off-and-on for about 12 hours today.
[03:47:57] * Bytram yawns
[03:47:57] * MrPlow flips a Skittle into Bytram's gaping mouth
[03:48:22] <Bytram> That does it... by brain is full.
[03:48:32] <Bytram> catch ya all tomorrow
[03:48:38] <Bytram> laters
[07:08:02] <janrinok> I've read your notes, but don't be too despondent
[07:10:10] <janrinok> You have got a good disk copy - but I think that the MBR (Main Boot Record) is not good for both machines. There are several ways we can correct this. And it would be better to solve all the problems - accompanied by you copious notes - before you copy the updated win drive otherwise we might make a mistake while trying to solve each problem.
[07:10:57] <janrinok> Ensure that you BIOS settings are the same on each machine - if one is using BIOS boot and the other UEFI then the MBR simply will not work.
[07:12:58] <janrinok> We can see if your rescuecd has a Repair Boot option - it probably has because it is a major use of a disk repair CD. You can probably check this yourself but I will be back on here later to help.
[07:13:56] <janrinok> If the rescuecd doesn't work, we can use an Ubuntu CD to repair the boot record which should get us far enough to boot the computer.
[07:15:17] <janrinok> The final stage will be to find which drivers need replacing and this could be tricky because if one of the drivers is for the wifi we will have to download drivers on one machine and then transfer them to the new lappy until we get the wifi working.
[07:17:01] <janrinok> However, get plenty of rest, take your time and please read exactly what I write. If you want to make notes at the same time just tell me and I can wait until you are ready to do the next task.
[07:18:11] <janrinok> I always assume that you are doing the task that I have written but you have other calls on your time and you need to do things that I am unaware of - so you have to control the pace that we do things.
[07:18:56] <janrinok> I can always do something on second computer while you undertake a long task or even if you just want to take a break.
[07:19:03] <janrinok> CU laters!
[07:20:39] <janrinok> We ARE making progress!
[14:06:08] <janrinok> Bytram, ping
[14:09:46] <Bytram> pong
[14:09:56] <janrinok> how's things ?
[14:10:08] <Bytram> I have read your 'reply'... thanks!
[14:10:13] <Bytram> Well-ish
[14:10:20] <janrinok> hope you have recovered from that epic effort yesterday!
[14:10:59] <janrinok> you decide what and how much we do today
[14:11:03] <Bytram> lappy is as I described, but something has come up that will keep me away for about 3-4 hours.
[14:11:25] <Bytram> 4hrs from now would be ~6pm for u?
[14:12:41] <janrinok> I start cooking at 5 and it is ten past 3 now
[14:12:42] * Bytram misses the old days when I could read raw sectors off a disk drive.
[14:13:00] <Bytram> Ok, 5hr difference
[14:13:02] <Bytram> hmm
[14:13:05] <Bytram> ~time x
[14:13:06] <exec> location not found - UTC timestamp: Sunday, 23 February 2020, 2:13 pm
[14:13:15] <janrinok> the MBR is sound, just incorrect for one of the 2 machines I think
[14:13:33] <janrinok> I'm on CET
[14:14:12] <janrinok> search for either St Brieuc or Lannion in tz settings
[14:14:27] <Bytram> I do have pics of every single BIOS screen in old lappy (OL), but have not yes looked through New Lappy's (NL) BIOS config
[14:14:41] <Bytram> 1 hr ahead of UTC?
[14:14:59] <janrinok> if you fancy a change we can just set up 18.04 on your new lappy
[14:15:21] <Bytram> Ummm, that is already done.
[14:15:24] <janrinok> yes, 1 hr ahead
[14:15:27] <Bytram> k
[14:15:56] <janrinok> on the new lappy you can try a new desktop or two and find one that works for you
[14:16:24] <janrinok> with Windows you get what you are given, on Linux there are more that half a dozen available
[14:16:30] <janrinok> more than*
[14:16:52] <Bytram> SSD #1: Original Win Install, works on OL; SSD #2: Ubuntu 18.04.4 (works on new lappy); SSD #3: Clone of 1: Does not work on either OL or NL
[14:17:21] <janrinok> which is why I think it is a MBR problem
[14:17:29] <Bytram> I do not recall if I tried to boot Ubuntu SSD on OL
[14:18:05] <janrinok> I would imagine that it would work but you might need to correct screen geometry or something
[14:18:27] <Bytram> ATM, I think the next step is for me to go through the NL's BIOS and check/set its settingss.
[14:18:29] <janrinok> it is always a useful thing to know, so worth a try
[14:18:54] <janrinok> your decision, just let me know how/if I can help
[14:20:10] <janrinok> are you sure that your rescuecd is Arch linux, or is it ArchiveLinux - they are different. I can download it here and search for a Repair MBR option
[14:20:11] <Bytram> Understood on booting U. on OL. Would be about a half-hour project... rebooting win and getting Browser tabs refreshed is... time consuming.
[14:21:08] <Bytram> Not sure. Recall seeing "Arch" a bunch. Did not know about "ArchiveLinux"; just Arch from hearing it mentioned by TMB and others.
[14:21:28] <janrinok> I've got celtic music playing in my headset and a cup of tea in my hand - I can sit here happily all afternoon.
[14:21:38] <Bytram> I'm sure their website would state what it is built on.
[14:22:02] <janrinok> just give a URL and I will download it
[14:22:34] <Bytram> Would so love to keep chugging away at this, but I have about 40 minutes or so to meet up with some friends.
[14:22:59] <janrinok> np - have a rest today. It is Sunday, when all is said and done
[14:22:59] <Bytram> =g systemrescuecd
[14:23:00] <systemd> http://www.system-rescue-cd.org - SystemRescueCd - System Rescue Cd Homepage
[14:23:10] <Bytram> ^^^ that one.
[14:23:12] <Bytram> =)
[14:23:21] <Bytram> nodnod
[14:23:58] <Bytram> barring any surprises, I'll likely be back in about 3 hours or so.
[14:24:39] <janrinok> that works for me, S will be in bed around then and I have a hour or two spare before my next evening tasks
[14:24:45] <Bytram> time to get cleaned up... thanks for the support, patience, and encouragement!
[14:24:56] <Bytram> Yes, and {{{S}}}
[14:24:58] <janrinok> np - I wish I could be there to help more!
[14:25:36] <Bytram> I look at it as a learning opportunity; I'll remember this better from *doing* it than from reading it in some docs.
[14:25:46] <Bytram> ok gtg
[14:26:12] <Bytram> laters
[14:26:24] <janrinok> laters - and downloading now
[14:27:04] <Bytram> BTW, I can *see* the #qa logs on my cell, and if really need be, can use the web chat on my cell, as well.
[14:27:11] <Bytram> o/w I'll see you later!
[14:27:23] <janrinok> ciao
[16:02:55] -!- Bytram_ [Bytram_!~a6b6f8e1@672-690-089-018.mobile.uscc.com] has joined #qa
[16:06:07] <Bytram_> janrinok: ping... i can get on wifi for next hour or so, but chat does not work on it. pls send urls u can think of for me to d/l. =)
[16:07:12] <Bytram_> i will check back in at half past the hour.
[16:11:37] -!- Bytram_ has quit [Ping timeout: 244 seconds]
[16:25:16] -!- Bytram_ [Bytram_!~a6b6f8e1@672-690-089-018.mobile.uscc.com] has joined #qa
[16:29:42] -!- Bytram_ has quit [Ping timeout: 244 seconds]
[16:53:02] -!- Bytram_ [Bytram_!~a6b6f8e1@672-690-089-018.mobile.uscc.com] has joined #qa
[16:53:24] <Bytram_> out of time. =( nvm.
[16:57:36] -!- Bytram_ has quit [Ping timeout: 244 seconds]
[17:43:03] <janrinok> sry - from 1700 to 1900 is cooking, eating and cleaning up the mess that I have just made....
[17:46:40] <janrinok> download urls for what purpose - to fix the MBR you can use 1. systemrescuecd and 2. Ubuntu live disk. If you are looking at installing a different desktop I would suggest you simply use your ubuntu drive to download the necessary packages. Linux doesn't usually need to to download software from other sources. But for Pale Moon see https://software.opensuse.org
[17:47:01] <janrinok> and select the instructions for Ubuntu 18.04.
[19:14:56] -!- Bytram_Unew [Bytram_Unew!~a6b6f9d2@112-646-089-063.mobile.uscc.com] has joined #qa
[19:19:46] <Bytram_Unew> well, that did not quite work out as planned! Rebooted new lappy takng special care to sync settings with what was on old lappy... As I went along, I noticed a couple setting in the new lappy that it made sense to change in the old one's BIOS. Now the old lappy will not boot Orginal Windows SSD. Black screen and slowly blinking drive activty (~ 1 x /second)... Just like what I saw trying to boot the cloned windows SSD on the new lappy
[19:20:49] <Bytram_Unew> work, bt I neglected to write down exactly what I changed in the old lappy BIOS. But all s not lost! Yesterday I took pictures of all of the BIOS settings in the old lappy!
[19:22:22] <Bytram_Unew> So, I need to step throught the origina BIOS settings pictures and the n take note of what changed... that will likely, also, cure the problem with my being unable to boot the cloned Windows SSD on the new lappy.
[19:23:48] <Bytram_Unew> I.e., Identify the deltas made, 'revert' new lappy BIOS to what *was* on old lappy, and (if I do not miss my guess), we should be golden.
[19:24:04] * Bytram_Unew crosses his fimgers...
[19:24:35] <Bytram_Unew> but first goes in search of sustenance. Back in a bit.
[19:28:15] <janrinok> ... at least you made notes/images of the original settings - you can see know why I asked you to check them. It only takes one to be 'wrong' and the system will not boot
[19:28:54] <janrinok> You might not realise it but you could just have taken a big step forward in identifying the problem with the boot failure on the new lappy
[19:30:26] <Bytram_Unew> yes, that is what I meant in my last couple lines...
[19:30:46] <Bytram_Unew> I maynot know exactly which one(s) are reponsible...
[19:31:34] <Bytram_Unew> but i *have* found a subset of BIOS settings that **seem** to replicate the problem.
[19:32:41] <janrinok> well it shouldn't take us too long to track it down. Reset half of them that you changed and see if it cures the problem. If it does it was one of those you changed, otherwise it is in the other half. Find the correct one continuing your binary search
[19:32:49] <Bytram_Unew> First step will be to walk through the old lappy's BIOS and write down what settings changed, and from what and what to.
[19:32:58] <janrinok> agreed
[19:33:38] <Bytram_Unew> then, unless a heuristic reveals itself, single changes, will eventually get things going again. (I hope!)
[19:34:03] <janrinok> then we sit and think, and work out which ones make sense on the new lappy
[19:34:22] <Bytram_Unew> On 2nd thought... confirm that changing ALLthe setinig back 8does* allow for successful booting.
[19:35:04] <Bytram_Unew> 'Zactly... could well be among the ones I had to change to get the old one to boot again..
[19:35:05] <janrinok> OK, then you have to start unsetting them again to identify which one reproduces the fault i.e. which setting is wrong
[19:35:36] <janrinok> then identify if there is an equivalent setting on the new lappy
[19:35:40] <Bytram_Unew> Because, as I went, I tried to change new lappy's bios settings to match the old lappy's except in a select few places.
[19:35:45] <janrinok> sounds like you have a plan!
[19:35:54] <Bytram_Unew> So far, I do...
[19:36:08] <Bytram_Unew> tht's the off the top of my head.
[19:36:29] <janrinok> get the new lappy to boot with ubuntu - that way you are not looking at bad settings and a bad MBR at the same time.
[19:37:08] <janrinok> then start looking for differences between the sets of 'correct' settings
[19:37:40] <Bytram_Unew> Oh! FYI, I am using the web link to IRC on the site front page in a firefox tab on my new lappy running Ubuntu booted from SSD atm.
[19:38:18] <janrinok> I won't even try to get my mind round that one at this time of the evening
[19:38:32] <Bytram_Unew> New lappy *IS* bootecd with *new* BIOS settings on new lappy.
[19:39:19] <Bytram_Unew> On SN main page, there is a linnk to "IRC" -- brings up web-based access to get me here
[19:39:22] <janrinok> with Ubuntu or Windows?
[19:39:28] <Bytram_Unew> Ubuntu
[19:39:43] <janrinok> have you tried the windows disk again yet?
[19:40:06] <Bytram_Unew> IOW, Ubuntu successfully booted on new lappy with bold the old and the new BIOS settings
[19:40:17] <Bytram_Unew> nope
[19:40:46] <Bytram_Unew> would prefer to get old lappy able to boot windows again.
[19:41:06] <janrinok> I wonder if Windows is using BIOS or UEFI and the other lappy is using the other setting?
[19:41:09] <Bytram_Unew> I do NOT have a great surplus of machines I can get online with.
[19:41:22] <janrinok> lol understood brb 5
[19:41:33] <Bytram_Unew> Both are (and were) BIS, first things I checked
[19:41:46] <Bytram_Unew> s/BIS/BIOS/
[19:41:47] <exec> <Bytram_Unew> Both are (and were) BIOS, first things I checked
[19:42:16] <Bytram_Unew> lemme try again
[19:42:59] <Bytram_Unew> first thing I checked on both lappys. each one already was set to BIOS. I left them both that way.
[19:45:31] <Bytram_Unew> Hmmm!
[19:48:50] <Bytram_Unew> I have the ubuntu 18.04.something live 'CD'... I have a USB drive and I am currently booted up on Ubuntu 18.04.1 on this lappy.
[19:49:23] <janrinok> which is 'this' lappy?
[19:50:09] <Bytram_Unew> I happen to have another new lappy, just like *this* one... I could boot it up with the DVD, if necessary. Do you know *if* there is an easy way to make a bootable Ubuntu USB stick?
[19:50:16] <Bytram_Unew> and if so, how to do it?
[19:51:05] <Bytram_Unew> The one I am using right now is what I have been referring toas "the new lappy"
[19:51:07] <janrinok> there is - but I would have to do a quick Google and I only have about 10 minutes left. It is not something that I do often
[19:51:34] <chromas> As long as it's a hyrbid iso you can just dd it onto an usb drive
[19:52:18] <Bytram_Unew> As separate from the original 'old" lappy on which I started (the Latitude E6400).. the new ones are all Latitude E6410s
[19:52:27] <janrinok> yeah, a live disk should just work.... (Although I have said similar before and then been left scratching my head as to why it didn't!
[19:52:32] <Bytram_Unew> Hmm?
[19:52:39] * Bytram_Unew ponders for amoment
[19:53:37] <janrinok> just dd your live disk to a thumb drive - bearing in mind it will overwrite everything on the thumb drive, not just the 4Gb or whatever it is
[19:53:40] <Bytram_Unew> Oh, if it helps at all, I chose a nick when I came on through the web interface which I hoped identified which lappie I was coming in on
[19:53:55] <Bytram_Unew> understood.
[19:53:57] <janrinok> I thought that was a typo - lol
[19:54:34] <Bytram_Unew> Prolly best I not waste a 64 GB stick for this... let me scrounge arond for somethign smaller.
[19:57:02] <Bytram_Unew> Well! *that* stick was not even recognozed as a drive by Ubuntu
[19:57:15] <janrinok> is it formatted?
[19:57:34] <janrinok> did you check lsblk?
[19:57:53] <Bytram_Unew> yes, is what I am doing. lsblk
[19:58:19] <janrinok> start gparted and see if that can see it
[19:58:33] <Bytram_Unew> Oh, the small one... I expect it was. I think I used it in the past.
[19:59:06] <Bytram_Unew> gparted not installed
[19:59:18] <janrinok> standard! sudo apt install g
[19:59:27] <Bytram_Unew> <pre>Command &apos;gparted&apos; not found, but can be installed with: sudo apt install gparted </pre>
[19:59:27] <janrinok> sudo apt install gparted
[19:59:34] <Bytram_Unew> yep
[20:00:02] <janrinok> the first attempt was a typo!
[20:00:41] <Bytram_Unew> installed.
[20:01:04] <janrinok> start it up - any method you know...
[20:02:02] <janrinok> quickest is in a terminal which you have just used - 'sudo gparted'
[20:03:33] <Bytram_Unew> only shows the Ubvuntu SSD
[20:03:45] <Bytram_Unew> neither of the UsB sticks
[20:04:18] <janrinok> have you clicked on the top-right where it tells you the drive? using the up/down arrows
[20:04:49] <Bytram_Unew> but lsblk *does* show the first one I tried... is now: sdd1
[20:04:56] <Bytram_Unew> oh
[20:05:26] <janrinok> you should have at least /dev/sda but you have to check for others. You can only work on one drive at a time...
[20:05:29] <Bytram_Unew> same... not show presumaly smaller drive
[20:06:05] <janrinok> menu top left GParted / Refresh
[20:06:26] <Bytram_Unew> Anything I have on that SSD came from somewhere else (old win lappy0
[20:07:02] <Bytram_Unew> refresh: no change
[20:07:08] <janrinok> I don't understand.... what ssd? I thought we were working with thumb drives
[20:07:28] <Bytram_Unew> this lappy is booted off an ssd
[20:07:36] <Bytram_Unew> oh, tht one
[20:07:39] <janrinok> yes that is /dev/sda
[20:08:21] <Bytram_Unew> just meaning I cannot imagine any info on the USB stick tht *can* be seen that does not exiat elsewhere... i can nuke it.
[20:08:33] <janrinok> I'm running over time at the moment. You want to dd your 18.04.1 DVD onto a thumb drive
[20:09:07] <janrinok> but if you can't see it you can't do anything to it.
[20:09:22] <Bytram_Unew> got it.
[20:09:49] <Bytram_Unew> was thew quESTION I was just aout to ask.
[20:09:50] <janrinok> OK make a note of its /dev/sdx
[20:09:58] <Bytram_Unew> thanks SO much!!!!!!!!!!!!
[20:10:04] <Bytram_Unew> k
[20:10:29] <janrinok> make sure you DO NOT access your /dev/sda at all.
[20:10:57] <janrinok> reading from it will not work on the thumb drive, and writing to it will give you a bad day
[20:11:35] <Bytram_Unew> heh. "bad day". No doubt!
[20:12:43] <janrinok> try a block size of 32MB or even 64MB, but don't go too daft with it ;)
[20:14:05] <Bytram_Unew> ahh, got it.
[20:15:56] <janrinok> sry - I could have typed that out for you
[20:16:10] <Bytram_Unew> np, I knew wht u meant ith that one
[20:16:37] <Bytram_Unew> trying to be sure I have gotten right 'path' for dvd ...
[20:17:02] <Bytram_Unew> ls -ltr /dev
[20:17:12] <janrinok> nope
[20:17:17] <Bytram_Unew> shows 4 things all with -> sr0
[20:18:07] <janrinok> type ls /dev/sr*
[20:18:13] <Bytram_Unew> dvdrw -> sr0 and dvd -> sro and cdrw -> sr0 and cdro -> sr0
[20:18:22] <Bytram_Unew> ls /dev/sr
[20:18:27] <Bytram_Unew> oops~!
[20:18:29] <janrinok> it is sr0
[20:18:49] <janrinok> and others are aliases
[20:19:41] <Bytram_Unew> Great! that is what I thought it was (or a hard link?0
[20:19:43] <Bytram_Unew> anyway
[20:20:28] <janrinok> dd if=/dev/sr0 of=/dev/sdd bs=32M
[20:20:38] <Bytram_Unew> dd if=/dev/sr0 of=/dev/sdd1 bs=16 GB status=progress
[20:20:51] <janrinok> no - not sdd1 that is a partition
[20:20:59] <janrinok> just /dev/sdd
[20:21:01] <Bytram_Unew> kewel
[20:21:09] <Bytram_Unew> dd if=/dev/sr0 of=/dev/sdd bs=16 GB status=progress
[20:21:38] <janrinok> no bs=32M
[20:22:23] <janrinok> you only see the progress at the end of a block - you will only get the progress when 4Gb has been transferred
[20:23:13] <janrinok> I suspect the hw will handle it, but you will not know how quickly it is going
[20:23:14] <Bytram_Unew> huh.
[20:23:18] <Bytram_Unew> martyb@E6410-001:~$ dd if=/dev/sr0 of=/dev/sdd bs=16 GB status=progress dd: unrecognized operand ‘GB’ Try 'dd --help' for more information. martyb@E6410-001:~$ dd if=/dev/sr0 of=/dev/sdd bs=16GB status=progress dd: failed to open '/dev/sdd': Permission denied martyb@E6410-001:~$
[20:23:39] <Bytram_Unew> oh, I need sudo!
[20:23:41] <janrinok> yep, you need to be sudo - just put sudo in front of all of that
[20:23:53] <chromas> You have a space between 16 and GB
[20:24:06] <Bytram_Unew> sudo dd if=/dev/sr0 of=/dev/sdd bs=16GB status=progress
[20:24:15] <Bytram_Unew> yeah fixed tht, too.
[20:24:19] <janrinok> and do not us bs=16G
[20:24:28] <Bytram_Unew> ok...
[20:24:32] <Bytram_Unew> oh!
[20:24:40] <Bytram_Unew> 32M !1
[20:24:52] <janrinok> bs=32M because you will only see a progress update at the end of each block - i.e. every 16GB!
[20:24:53] <Bytram_Unew> sudo dd if=/dev/sr0 of=/dev/sdd bs=32M status=progress
[20:25:09] <janrinok> good
[20:25:45] <janrinok> let me know if the magic smoke escapes.... ;)
[20:26:09] <Bytram_Unew> asked for pwd, and then immediaely after i entered it, heard the dvd spin up. =)
[20:26:26] <janrinok> well, it didn't explode,, so that is a plus
[20:26:27] <Bytram_Unew> .
[20:26:47] <Bytram_Unew> I have enough to keep me busy for a while, thanks SO mch!!
[20:27:20] <janrinok> np - I'm going to clean my teeth and I will check back after that - then it is my beddybyes
[20:27:43] <Bytram_Unew> oh, quick quesion... do i need to unmount usb sticks in some way, or does ubunbtu let me just yank it out?
[20:27:47] <Bytram_Unew> k
[20:29:07] <janrinok> you should umount the, - note the lack of 'n' in that command
[20:29:16] <janrinok> umount them*
[20:29:25] <Bytram_Unew> yes, am aware, but appreciate the reminder!
[20:29:40] <janrinok> so 'sudo umount /dev/sdd
[20:29:40] <Bytram_Unew> obliged!
[20:29:49] <Bytram_Unew> got it. tx!
[20:30:01] <Bytram_Unew> 709 MB cpied so far
[20:30:14] <Bytram_Unew> gonna be a few more minutes
[20:30:36] <janrinok> I will tell you some short cuts tomorrow so that you don't have to keep going through the sudo route, and we can install some additional useful software (ssh etc) so that your 2 lappies can talk to each other
[20:30:41] <Bytram_Unew> janrinok: Have a great night... give S a squeeze, for me. K?
[20:30:54] <Bytram_Unew> .
[20:31:00] <Bytram_Unew> =) =) =)
[20:31:02] <Bytram_Unew> .
[20:31:02] <janrinok> S is prolly already asleep - and I don't plan on being much behind here!
[20:31:07] <janrinok> her*
[20:31:28] <Bytram_Unew> TTFN!
[20:31:34] <janrinok> gtg laters
[20:31:41] <Bytram_Unew> ciao!
[22:54:37] -!- Bytram_Unew has quit [Ping timeout: 244 seconds]