... Yeah, I already looked at the man page for fsck. Nothing on error codes that I saw. I even tried Gparted from my live boot. It said it fixed stuff, but when I went into terminal to check, still got the "bad magic number in super-block" error.

Well, I've been planning on going dual boot from 2 drives, but I'm waiting for a warmer day so I can blow the dust out of the case. It hasn't been done for a few months, since it got colder. One things fer sure, when I do this I will be giving the root partition more space on the M.2 drive, since it is 1TB. ;)

I think I'm just gonna brave the cold and do that after posting this. :)

Good luck and hope not too cold!


Running dual boot with Windows is always 'difficult' due to Windows ignoring all other OSes and monopolizing the partition table and the first one or two partitions...

To lose the 'magic number' at the start of a partition suggests that something has overwritten that area...

Easiest by far for going dual boot with Windows is to give Windows it's own disk to fully monopolize and install your other OSes onto another disk(s). Then use a boot loader from that other disk or the BIOS boot selection to boot accordingly.


Good luck!

Cheers,
Martin

---

See new freedom: Mageia Linux
Take a look for yourself: Linux Format
The Future is what We all make IT (GPLv3)

To lose the 'magic number' at the start of a partition suggests that something has overwritten that area...

or the drive is physically hosed or the master table is no longer pointing at the start of the partition.

Greetings,

Thanks Rob, Martin and Gary! :) I decided to brave the cold and took the PC out to the porch and blew the dust out.

I installed my old M.2 drive, with Winders, and got the PC running again. I installed Linux Mint on the 1TB M.2 all by it's little ol' lonesome. Got BOINC running by copying my backup BOINC directory over to my /home directory. Checked the permissions, they were set correctly. BOINC created another host with the same name when I started it. I merged the 2 and everything is hunky dory.

I just checked and can now boot into Winders on the 250GB M.2 drive.

I don't have a Grub menu. I was under the impression that one would be installed. The PC defaults to Mint. I'll need to use F8 to get to the drive menu and select Winders from there. Would I need to run "update-grub" so it will locate Winders perhaps?

Have a great day! :)

Siran

---

CAPT Siran d'Vel'nahr - L L & P _\\//
Winders 11 OS? "What a piece of junk!" - L. Skywalker
"Logic is the cement of our civilization with which we ascend from chaos using reason as our guide." - T'Plana-hath

Not necessarily if you haven't mounted the Windows drive in Linux Mint. If you must have a grub menu with the choice for Windows and Linux then you can mount the Windows drive and then do a:

sudo os-prober

Followed up by a:

sudo update-grub

https://askubuntu.com/questions/197868/grub-does-not-detect-windows

---

Seti@Home classic workunits:20,676 CPU time:74,226 hours

A proud member of the OFA (Old Farts Association)

But you're better off using the BIOS boot menu than having a grub menu as grub corruption can be a headache.

Cheers.

Not necessarily if you haven't mounted the Windows drive in Linux Mint. If you must have a grub menu with the choice for Windows and Linux then you can mount the Windows drive and then do a:

sudo os-prober

Followed up by a:

sudo update-grub

https://askubuntu.com/questions/197868/grub-does-not-detect-windows

Hi Keith,

Thanks for this. I don't HAVE to have a Grub menu. I'm just thinking it might be more efficient to have one in case I forget to hit F8 for the boot menu when I want to go play WoW. I believe I'll do the Grub thingy anyway. :)

Got BT running with all hosts listed in it. Was so much easier this time around. :)

Have a great day! :)

Siran

---

CAPT Siran d'Vel'nahr - L L & P _\\//
Winders 11 OS? "What a piece of junk!" - L. Skywalker
"Logic is the cement of our civilization with which we ascend from chaos using reason as our guide." - T'Plana-hath

But you're better off using the BIOS boot menu than having a grub menu as grub corruption can be a headache.

Cheers.

Hi Wiggo,

Thanks. I edited my last post with what I got in terminal when trying to do it. :(

Have a great day! :)

Siran

---

CAPT Siran d'Vel'nahr - L L & P _\\//
Winders 11 OS? "What a piece of junk!" - L. Skywalker
"Logic is the cement of our civilization with which we ascend from chaos using reason as our guide." - T'Plana-hath

But you're better off using the BIOS boot menu than having a grub menu as grub corruption can be a headache.

Cheers.

Yes, I agree with Wiggo's sentiments. If you don't HAVE to have a grub menu, it can be a pain to correct it. I think using the BIOS is simple enough. If you miss the F8 time, then a CTRL-ALT-DEL resets the clock to try again.

It can be quite time consuming to hand edit the grub menu. If you must have a grub menu, then I find the grub-customizer utility very handy for making changes in priority or menu layout very easy.

---

Seti@Home classic workunits:20,676 CPU time:74,226 hours

A proud member of the OFA (Old Farts Association)

But you're better off using the BIOS boot menu than having a grub menu as grub corruption can be a headache.

Cheers.

Yes, I agree with Wiggo's sentiments. If you don't HAVE to have a grub menu, it can be a pain to correct it. I think using the BIOS is simple enough. If you miss the F8 time, then a CTRL-ALT-DEL resets the clock to try again.

It can be quite time consuming to hand edit the grub menu. If you must have a grub menu, then I find the grub-customizer utility very handy for making changes in priority or menu layout very easy.

Hi Keith,

Yeah, I gave up on Grub. I'll just go with as it is right now and just F8 it. ;)

Gotta work on Remmina again. I don't remember how I set it up with my hosts the last time. Seems there is something missing. I'll Internet it tomorrow. :)

Have a great day! :)

Siran

---

CAPT Siran d'Vel'nahr - L L & P _\\//
Winders 11 OS? "What a piece of junk!" - L. Skywalker
"Logic is the cement of our civilization with which we ascend from chaos using reason as our guide." - T'Plana-hath

Wiggo's tip is a boon. Only problem I had was on booting up sometimes, disappeared to the kitchen for a cuppa & on returning was looking at Mint. Easy to fix , just enter bios & change disk priorities. :-)

Wiggo's tip is a boon. Only problem I had was on booting up sometimes, disappeared to the kitchen for a cuppa & on returning was looking at Mint. Easy to fix , just enter bios & change disk priorities. :-)

Hi Sirius,

I use Linux Mint exclusively for everything I used to do in Winders 10, except for playing World of Warcraft. So, I prefer to have the PC default to Linux and F8 to get to Winders. :)

Have a great day! :)

Siran

---

CAPT Siran d'Vel'nahr - L L & P _\\//
Winders 11 OS? "What a piece of junk!" - L. Skywalker
"Logic is the cement of our civilization with which we ascend from chaos using reason as our guide." - T'Plana-hath

Greetings,

I'm not sure why this is different this time than the last, but...

When I dual booted Linux and Windows on the same drive, I had no problem with time. Now that I dual boot with Linux and Windows on their own drives, I had a problem where Windows was not keeping proper time. It was about 6 hours off.

I searched the Internet and found that Linux uses UTC time to keep time where Windows uses the RTC. To fix this you can change Linux to use the RTC or change Windows to use UTC. The best way that I read about was to change Linux to use the RTC and have Windows maintain the RTC with its time sync. I will not be going into how to change Windows since it requires a hack to the Registry.

Here's how to modify Linux, in my case, Linux Mint. Open a terminal and enter the following:

timedatectl set-local-rtc 1 --adjust-system-clock

To be sure the change took affect enter the following:

timedatectl

The readout will have a line reading “RTC in local TZ: yes”. This is my whole readout:

rick@Minty-Winders:~$ timedatectl
                      Local time: Sun 2020-02-23 15:32:34 CST
                  Universal time: Sun 2020-02-23 21:32:34 UTC
                        RTC time: Sun 2020-02-23 15:32:33
                       Time zone: America/Chicago (CST, -0600)
       System clock synchronized: no
systemd-timesyncd.service active: yes
                 RTC in local TZ: yes

Warning: The system is configured to read the RTC time in the local time zone.
         This mode can not be fully supported. It will create various problems
         with time zone changes and daylight saving time adjustments. The RTC
         time is never updated, it relies on external facilities to maintain it.
         If at all possible, use RTC in UTC by calling
         'timedatectl set-local-rtc 0'.
rick@Minty-Winders:~$

Notice the warning. You will need to boot into Windows to get the RTC updated for time changes such as Daylight Saving Time or going to different time zones.

This mode is probably better supported than the UTC option in Windows.

Have a great day! :)

Siran

---

CAPT Siran d'Vel'nahr - L L & P _\\//
Winders 11 OS? "What a piece of junk!" - L. Skywalker
"Logic is the cement of our civilization with which we ascend from chaos using reason as our guide." - T'Plana-hath

Greetings,

I'm not sure why this is different this time than the last, but...

When I dual booted Linux and Windows on the same drive, I had no problem with time. Now that I dual boot with Linux and Windows on their own drives, I had a problem where Windows was not keeping proper time. It was about 6 hours off.

I searched the Internet and found that Linux uses UTC time to keep time where Windows uses the RTC. To fix this you can change Linux to use the RTC or change Windows to use UTC. The best way that I read about was to change Linux to use the RTC and have Windows maintain the RTC with its time sync. I will not be going into how to change Windows since it requires a hack to the Registry.

Here's how to modify Linux, in my case, Linux Mint. Open a terminal and enter the following:

timedatectl set-local-rtc 1 --adjust-system-clock

To be sure the change took affect enter the following:

timedatectl

The readout will have a line reading “RTC in local TZ: yes”. This is my whole readout:

rick@Minty-Winders:~$ timedatectl
                      Local time: Sun 2020-02-23 15:32:34 CST
                  Universal time: Sun 2020-02-23 21:32:34 UTC
                        RTC time: Sun 2020-02-23 15:32:33
                       Time zone: America/Chicago (CST, -0600)
       System clock synchronized: no
systemd-timesyncd.service active: yes
                 RTC in local TZ: yes

Warning: The system is configured to read the RTC time in the local time zone.
         This mode can not be fully supported. It will create various problems
         with time zone changes and daylight saving time adjustments. The RTC
         time is never updated, it relies on external facilities to maintain it.
         If at all possible, use RTC in UTC by calling
         'timedatectl set-local-rtc 0'.
rick@Minty-Winders:~$

Notice the warning. You will need to boot into Windows to get the RTC updated for time changes such as Daylight Saving Time or going to different time zones.

This mode is probably better supported than the UTC option in Windows.

Have a great day! :)

Siran

[MSG: 2011071:]

[Repeat of Msg:]

Siran,

Set RealTimeIsUniversal=1 in Windows.

Remember to Set BIOS Clock to UTC First. THEN go to Step 2 in the Instructions at the Link, above, and IF your Windows is 64-Bit USE "QWORD" for the "RealTimeIsUniversal=1" Registry Hack.

I do this for my Hackintosh, otherwise Windows Clock is ALWAYS wrong when logging back into Windows after being in MacOS. The "RealTimeIsUniversal=1" Hack saved me from MUCH ANGUISH on the Windows side of things.


TL

[EDIT:]

The Instructions state this is for Win 10, BUT, this ALSO works in Win 7.


TL

---

TimeLord04
Have TARDIS, will travel...
Come along K-9!
Join Calm Chaos

-[ snip ]-

[MSG: 2011071:]

[Repeat of Msg:]

Siran,

Set RealTimeIsUniversal=1 in Windows.

Remember to Set BIOS Clock to UTC First. THEN go to Step 2 in the Instructions at the Link, above, and IF your Windows is 64-Bit USE "QWORD" for the "RealTimeIsUniversal=1" Registry Hack.

I do this for my Hackintosh, otherwise Windows Clock is ALWAYS wrong when logging back into Windows after being in MacOS. The "RealTimeIsUniversal=1" Hack saved me from MUCH ANGUISH on the Windows side of things.


TL

[EDIT:]

The Instructions state this is for Win 10, BUT, this ALSO works in Win 7.


TL

Hi TL,

Since I only use Winders for ONE thing, to play World of Warcraft, and since I never liked the idea of registry hacks to "fix stuff", I opted to change my Linux instead. I'm ok with Winders taking care of the RTC. I boot into it early morning to do some stuff in WoW so the RTC will be taken care of then. :)

Have a great day! :)

Siran

---

CAPT Siran d'Vel'nahr - L L & P _\\//
Winders 11 OS? "What a piece of junk!" - L. Skywalker
"Logic is the cement of our civilization with which we ascend from chaos using reason as our guide." - T'Plana-hath

Hi TL,

Since I only use Winders for ONE thing, to play World of Warcraft, and since I never liked the idea of registry hacks to "fix stuff", I opted to change my Linux instead. I'm ok with Winders taking care of the RTC. I boot into it early morning to do some stuff in WoW so the RTC will be taken care of then. :)

Have a great day! :)

Siran

Well with the Registry Hack in Windows, Daylight Savings Time works for me in both Operating Systems.
That is, Daylight Savings is controlled by the Primary Active OS, (for me MacOS), and when Booting
to the Secondary OS, (for me, Win 7 Pro SP-1 x64), Windows just has the right time... No adjustments
needed.

Funny thing, though, is that on Daedalus, (Mac Pro 5,1), under BootCamp - Windows 7;
even though Windows is on a Separate Drive, (like Hackintosh-Andromeda), I DID NOT
need to employ RealTimeIsUniversal=1 on Daedalus.... (Weird things between Real
Macs and Hackintosh with Dual Boot.)


TL

---

TimeLord04
Have TARDIS, will travel...
Come along K-9!
Join Calm Chaos

-[ snip ]-

Well with the Registry Hack in Windows, Daylight Savings Time works for me in both Operating Systems.
That is, Daylight Savings is controlled by the Primary Active OS, (for me MacOS), and when Booting
to the Secondary OS, (for me, Win 7 Pro SP-1 x64), Windows just has the right time... No adjustments
needed.

Funny thing, though, is that on Daedalus, (Mac Pro 5,1), under BootCamp - Windows 7;
even though Windows is on a Separate Drive, (like Hackintosh-Andromeda), I DID NOT
need to employ RealTimeIsUniversal=1 on Daedalus.... (Weird things between Real
Macs and Hackintosh with Dual Boot.)


TL

Hi TL,

No offence, but my original post was not intended to start an argument on the merits of doing this one way or another. My purpose was to give brief instructions on how to do this in Linux, which happens to be the easiest way to go, not Mac or anything else, hence the title of this thread. If someone wants to know how to do it with Winders, they could either go to the Internet themselves or ask here and I would provide a link. 99% of what I do on my PC is done in Linux, so I saw no need to give the Winders instructions too.

Have a great day! :)

Siran

---

CAPT Siran d'Vel'nahr - L L & P _\\//
Winders 11 OS? "What a piece of junk!" - L. Skywalker
"Logic is the cement of our civilization with which we ascend from chaos using reason as our guide." - T'Plana-hath

Since I mostly use Linux on my dual system, I thought it was best to let Linux control time settings and disable Windows time update. Following the instructions from this page it was quite simple...

http://ubuntuhandbook.org/index.php/2016/05/time-differences-ubuntu-1604-windows-10/

Since I mostly use Linux on my dual system, I thought it was best to let Linux control time settings and disable Windows time update. Following the instructions from this page it was quite simple...

http://ubuntuhandbook.org/index.php/2016/05/time-differences-ubuntu-1604-windows-10/

Hi John,

I used the instructions on this website which is basically the same as what you used except yours uses a command in terminal to hack the Registry while mine goes into the registry to do the hack. There are a couple statements on the instructions I used that made up my mind to let Winders take care of the RTC.

However, this mode is probably better supported than the UTC option in Windows. If you dual-boot with Windows, Windows will handle daylight savings time for you.

What I get is that RTC is better supported in Linux than UTC is in Winders.

I can actually understand why you did it your way. I just have always hated doing Registry hacks in Winders and the above quoted statements made up my mind to do it differently. There really is no right or wrong way, it's just per a users preference. :)

Have a great day! :)

Siran

---

CAPT Siran d'Vel'nahr - L L & P _\\//
Winders 11 OS? "What a piece of junk!" - L. Skywalker
"Logic is the cement of our civilization with which we ascend from chaos using reason as our guide." - T'Plana-hath

Regardless of what machine or what OS, my personal experience has been that to avoid confusion, best is to:

Set the RTC ('Real Time Clock') value to UTC (or GMT...) for all your OSes.


What that means is that instead of trying to set 'whatever local time' into the RTC...

There is never any confusion as to whether or not daylight savings time shifts or time zone time shifts need to be applied... Very simply, the OS must unambiguously ALWAYS apply the time shifts! Much safer.

And that is a lot less confusing, especially if your machine is shut down and then rebooted across a daylight savings change-over.

And very much less confusing for systems that travel across time zones!...


Happy cool crunchin',
Martin

---

See new freedom: Mageia Linux
Take a look for yourself: Linux Format
The Future is what We all make IT (GPLv3)

Greetings,

Thank goodness for GParted!!!! :)

I noticed when I was rebooting to go into Winders 10 to do some WoW, that one of the line entries had a FAILED in the [ ] brackets. I just thought ok something didn't shut down correctly or something like that. After I was done in WoW I went to reboot back into Linux Mint. The boot failed. It said I needed to use "fsck" to fix a disk. I tried and I tried and I tried to no avail so I whipped out my Winders 10 laptop and started doing some Internet searching. I found all kinds of stuff about "fsck" and variants thereof. Nothing worked.

I then thought of GParted so I booted into my live USB flash drive and did more searching on the laptop. I found one website about fixing a disk with GParted. But! Another program called "testdisk" was needed. Ok, that wasn't gonna work for me either. I had GParted running and decided to run through the menus to see what I could find. On one (cannot remember which one) I saw an item called "Check". Ok, lets try that so I selected each partition and ran "Check" and everything went just fine, at least I hoped. ;)

I started a reboot and pulled my USB flash drive and hit F8 for the boot menu. I selected the Ubuntu menu item and lo and behold it was fixed and booted into Linux Mint no problem. Woohoo! :)

Have a great day! :)

Siran

---

CAPT Siran d'Vel'nahr - L L & P _\\//
Winders 11 OS? "What a piece of junk!" - L. Skywalker
"Logic is the cement of our civilization with which we ascend from chaos using reason as our guide." - T'Plana-hath