"Nil" <rednoise9@rednoise9.invalid> wrote
|I was proceeding to add a second hard disk to my Win 10 computer.
|I
| hooked up a spare HD and booted up, intending to reformat the
| "new" disk and move some data to it. I realized too late that the
| spare disk I hooked up was a previous Windows 7 boot disk that I
| had decommissioned. The computer proceeded to boot up to Win7. I
| shut down immediately and unplugged the Win7 disk, but now it
| won't boot up into Win10.
Not sure, but it sounds like you might just need to boot
to something like a partition manager and reset the active
partition. Simply booting into Win7 shouldn't have damaged
anything.
In general I never do anything except with a tool. (I use
BootIt.) Windows has become increasingly worse about doing
what you want it to do in terms of booting, partitions, etc.
Nil wrote on 2/20/2023 5:25 PM:
I was proceeding to add a second hard disk to my Win 10 computer.
I hooked up a spare HD and booted up, intending to reformat the
"new" disk and move some data to it. I realized too late that the
spare disk I hooked up was a previous Windows 7 boot disk that I
had decommissioned. The computer proceeded to boot up to Win7. I
shut down immediately and unplugged the Win7 disk, but now it
won't boot up into Win10. I can get it to the blue Repair screen
where I can do a Windows Reset, boot to Safe Mode (haven't tried
that yet, but I don't expect it to work), etc. I CAN get to a
command prompt where I can see everything on the C drive. I can
get to a Repair thing where it appears to do a CHKDSK-type check,
but that doesn't help, of course.
Any suggestions how I can get this thing back on its feet? Will a
"Windows Reset" work (not quite sure what this does - it claims
to not disturb my data files, so maybe it just reinstalls Windows
only?) Am I correct in assuming that restoring from a Restore
Point is not likely to help?
Win10
Do you recall if your old boot disk was GPT formatted.
Do you recall if the Win7 disk is MBR
Access your UEFI or BIOS and determine which disk is enabled as
the primary boot device. Don't make any changes, just look.
Exit UEFI or BIOS
Disconnect the Win7 disk
Access the UEFI or BIOS and ensure the Win10 disk is the boot
device.
- if not, make it the first booting device.
Exit the UEFI or BIOS and see if the device boots to Windows 10
Report the results.
I was proceeding to add a second hard disk to my Win 10 computer. I
hooked up a spare HD and booted up, intending to reformat the "new"
disk and move some data to it. I realized too late that the spare disk
I hooked up was a previous Windows 7 boot disk that I had
decommissioned. The computer proceeded to boot up to Win7. I shut down immediately and unplugged the Win7 disk, but now it won't boot up into
Win10. I can get it to the blue Repair screen where I can do a Windows
Reset, boot to Safe Mode (haven't tried that yet, but I don't expect it
to work), etc. I CAN get to a command prompt where I can see everything
on the C drive. I can get to a Repair thing where it appears to do a CHKDSK-type check, but that doesn't help, of course.
Any suggestions how I can get this thing back on its feet? Will a
"Windows Reset" work (not quite sure what this does - it claims to not disturb my data files, so maybe it just reinstalls Windows only?) Am I correct in assuming that restoring from a Restore Point is not likely
to help?
"Nil" <rednoise9@rednoise9.invalid> wrote
|I was proceeding to add a second hard disk to my Win 10 computer.
|I
| hooked up a spare HD and booted up, intending to reformat the
| "new" disk and move some data to it. I realized too late that the
| spare disk I hooked up was a previous Windows 7 boot disk that I
| had decommissioned. The computer proceeded to boot up to Win7. I
| shut down immediately and unplugged the Win7 disk, but now it
| won't boot up into Win10.
Not sure, but it sounds like you might just need to boot
to something like a partition manager and reset the active
partition. Simply booting into Win7 shouldn't have damaged
anything.
In general I never do anything except with a tool. (I use
BootIt.) Windows has become increasingly worse about doing
what you want it to do in terms of booting, partitions, etc.
On 20 Feb 2023, =?UTF-8?B?Li4ud8Khw7HCp8KxwqTDsSA=?=
<winstonmvp@gmail.com> wrote in alt.comp.os.windows-10:
Nil wrote on 2/20/2023 5:25 PM:
I was proceeding to add a second hard disk to my Win 10 computer.
I hooked up a spare HD and booted up, intending to reformat the
"new" disk and move some data to it. I realized too late that the
spare disk I hooked up was a previous Windows 7 boot disk that I
had decommissioned. The computer proceeded to boot up to Win7. I
shut down immediately and unplugged the Win7 disk, but now it
won't boot up into Win10. I can get it to the blue Repair screen
where I can do a Windows Reset, boot to Safe Mode (haven't tried
that yet, but I don't expect it to work), etc. I CAN get to a
command prompt where I can see everything on the C drive. I can
get to a Repair thing where it appears to do a CHKDSK-type check,
but that doesn't help, of course.
Any suggestions how I can get this thing back on its feet? Will a
"Windows Reset" work (not quite sure what this does - it claims
to not disturb my data files, so maybe it just reinstalls Windows
only?) Am I correct in assuming that restoring from a Restore
Point is not likely to help?
I got the disk back. I tried several things, not sure what was the
magic trick that got it going. In the process I did some of what you suggest...
Win10
Do you recall if your old boot disk was GPT formatted.
Do you recall if the Win7 disk is MBR
The Win10 disk is GPT. I think the Win7 disk is MBR but not sure.
Access your UEFI or BIOS and determine which disk is enabled as
the primary boot device. Don't make any changes, just look.
Exit UEFI or BIOS
Disconnect the Win7 disk
Access the UEFI or BIOS and ensure the Win10 disk is the boot
device.
- if not, make it the first booting device.
I had already disconnected the Win7 disk, but I went into UEFI. At
first it didn't seem to detect the HD at all, but after a couple of power-downs it did, and I set it to be the first boot device, with the
CD drive as second.
Exit the UEFI or BIOS and see if the device boots to Windows 10
It did not boot to Win10 at this point. I got into a command prompt and executed some DISKPART commands I found on the net, which was
nervewracking because I don't really understand what they do. That may
have helped me mark a correct partition as Active.
Next restart it still didn't boot to windows, but when I went to UEFI a
third boot option is now there that I don't recall seeing before,
"Windows Boot Manager". I set IT to be the first boot device and now I
can boot up to Windows 10 seemingly like I did before.
Report the results.
The new Boot Manager bothers me - I feel like it wasn't there before -
but it functions the way it should, so I'll consider that later, unless
you have some thoughts about it.
Thank you.
drwxr-xr-x 0 0 0 5-Feb-2022 15:33 .drwxr-xr-x 0 0 0 5-Feb-2022 15:33 ..
On 20 Feb 2023, =?UTF-8?B?Li4ud8Khw7HCp8KxwqTDsSA=?=
<winstonmvp@gmail.com> wrote in alt.comp.os.windows-10:
Nil wrote on 2/20/2023 5:25 PM:
I was proceeding to add a second hard disk to my Win 10 computer.
I hooked up a spare HD and booted up, intending to reformat the
"new" disk and move some data to it. I realized too late that the
spare disk I hooked up was a previous Windows 7 boot disk that I
had decommissioned. The computer proceeded to boot up to Win7. I
shut down immediately and unplugged the Win7 disk, but now it
won't boot up into Win10. I can get it to the blue Repair screen
where I can do a Windows Reset, boot to Safe Mode (haven't tried
that yet, but I don't expect it to work), etc. I CAN get to a
command prompt where I can see everything on the C drive. I can
get to a Repair thing where it appears to do a CHKDSK-type check,
but that doesn't help, of course.
Any suggestions how I can get this thing back on its feet? Will a
"Windows Reset" work (not quite sure what this does - it claims
to not disturb my data files, so maybe it just reinstalls Windows
only?) Am I correct in assuming that restoring from a Restore
Point is not likely to help?
I got the disk back. I tried several things, not sure what was the
magic trick that got it going. In the process I did some of what you suggest...
Win10
Do you recall if your old boot disk was GPT formatted.
Do you recall if the Win7 disk is MBR
The Win10 disk is GPT. I think the Win7 disk is MBR but not sure.
Access your UEFI or BIOS and determine which disk is enabled as
the primary boot device. Don't make any changes, just look.
Exit UEFI or BIOS
Disconnect the Win7 disk
Access the UEFI or BIOS and ensure the Win10 disk is the boot
device.
- if not, make it the first booting device.
I had already disconnected the Win7 disk, but I went into UEFI. At
first it didn't seem to detect the HD at all, but after a couple of power-downs it did, and I set it to be the first boot device, with the
CD drive as second.
Exit the UEFI or BIOS and see if the device boots to Windows 10
It did not boot to Win10 at this point. I got into a command prompt and executed some DISKPART commands I found on the net, which was
nervewracking because I don't really understand what they do. That may
have helped me mark a correct partition as Active.
Next restart it still didn't boot to windows, but when I went to UEFI a
third boot option is now there that I don't recall seeing before,
"Windows Boot Manager". I set IT to be the first boot device and now I
can boot up to Windows 10 seemingly like I did before.
Report the results.
The new Boot Manager bothers me - I feel like it wasn't there before -
but it functions the way it should, so I'll consider that later, unless
you have some thoughts about it.
Thank you.
On 20 Feb 2023, =?UTF-8?B?Li4ud8Khw7HCp8KxwqTDsSA=?=
<winstonmvp@gmail.com> wrote in alt.comp.os.windows-10:
Nil wrote on 2/20/2023 5:25 PM:
I was proceeding to add a second hard disk to my Win 10 computer.
I hooked up a spare HD and booted up, intending to reformat the
"new" disk and move some data to it. I realized too late that the
spare disk I hooked up was a previous Windows 7 boot disk that I
had decommissioned. The computer proceeded to boot up to Win7. I
shut down immediately and unplugged the Win7 disk, but now it
won't boot up into Win10. I can get it to the blue Repair screen
where I can do a Windows Reset, boot to Safe Mode (haven't tried
that yet, but I don't expect it to work), etc. I CAN get to a
command prompt where I can see everything on the C drive. I can
get to a Repair thing where it appears to do a CHKDSK-type check,
but that doesn't help, of course.
Any suggestions how I can get this thing back on its feet? Will a
"Windows Reset" work (not quite sure what this does - it claims
to not disturb my data files, so maybe it just reinstalls Windows
only?) Am I correct in assuming that restoring from a Restore
Point is not likely to help?
I got the disk back. I tried several things, not sure what was the
magic trick that got it going. In the process I did some of what you suggest...
Win10
Do you recall if your old boot disk was GPT formatted.
Do you recall if the Win7 disk is MBR
The Win10 disk is GPT. I think the Win7 disk is MBR but not sure.
Access your UEFI or BIOS and determine which disk is enabled as
the primary boot device. Don't make any changes, just look.
Exit UEFI or BIOS
Disconnect the Win7 disk
Access the UEFI or BIOS and ensure the Win10 disk is the boot
device.
- if not, make it the first booting device.
I had already disconnected the Win7 disk, but I went into UEFI. At
first it didn't seem to detect the HD at all, but after a couple of power-downs it did, and I set it to be the first boot device, with the
CD drive as second.
Exit the UEFI or BIOS and see if the device boots to Windows 10
It did not boot to Win10 at this point. I got into a command prompt and executed some DISKPART commands I found on the net, which was
nervewracking because I don't really understand what they do. That may
have helped me mark a correct partition as Active.
Next restart it still didn't boot to windows, but when I went to UEFI a
third boot option is now there that I don't recall seeing before,
"Windows Boot Manager". I set IT to be the first boot device and now I
can boot up to Windows 10 seemingly like I did before.
Report the results.
The new Boot Manager bothers me - I feel like it wasn't there before -
but it functions the way it should, so I'll consider that later, unless
you have some thoughts about it.
Thank you.
I was proceeding to add a second hard disk to my Win 10 computer. I
hooked up a spare HD and booted up, intending to reformat the "new"
disk and move some data to it. I realized too late that the spare disk
I hooked up was a previous Windows 7 boot disk that I had
decommissioned. The computer proceeded to boot up to Win7. I shut down immediately and unplugged the Win7 disk, but now it won't boot up into
Win10. I can get it to the blue Repair screen where I can do a Windows
Reset, boot to Safe Mode (haven't tried that yet, but I don't expect it
to work), etc. I CAN get to a command prompt where I can see everything
on the C drive. I can get to a Repair thing where it appears to do a CHKDSK-type check, but that doesn't help, of course.
On 21/2/2023 8:25 am, Nil wrote:
I was proceeding to add a second hard disk to my Win 10 computer.
I hooked up a spare HD and booted up, intending to reformat the
"new" disk and move some data to it. I realized too late that the
spare disk I hooked up was a previous Windows 7 boot disk that I
had decommissioned. The computer proceeded to boot up to Win7. I
shut down immediately and unplugged the Win7 disk, but now it
won't boot up into Win10. I can get it to the blue Repair screen
where I can do a Windows Reset, boot to Safe Mode (haven't tried
that yet, but I don't expect it to work), etc. I CAN get to a
command prompt where I can see everything on the C drive. I can
get to a Repair thing where it appears to do a CHKDSK-type check,
but that doesn't help, of course.
I don't remember Win 7 being able to boot from a USB...
Last resort: get a 3rd spare/new hard disk to reinstall Win 10
after unplugging the old Win 10 drive?!
Nil wrote on 2/20/2023 5:59 PM:
On 20 Feb 2023, =?UTF-8?B?Li4ud8Khw7HCp8KxwqTDsSA=?=The Windows Boot Manager on UEFI is normal.
<winstonmvp@gmail.com> wrote in alt.comp.os.windows-10:
Nil wrote on 2/20/2023 5:25 PM:
I was proceeding to add a second hard disk to my Win 10
computer. I hooked up a spare HD and booted up, intending to
reformat the "new" disk and move some data to it. I realized
too late that the spare disk I hooked up was a previous Windows
7 boot disk that I had decommissioned. The computer proceeded
to boot up to Win7. I shut down immediately and unplugged the
Win7 disk, but now it won't boot up into Win10. I can get it to
the blue Repair screen where I can do a Windows Reset, boot to
Safe Mode (haven't tried that yet, but I don't expect it to
work), etc. I CAN get to a command prompt where I can see
everything on the C drive. I can get to a Repair thing where it
appears to do a CHKDSK-type check, but that doesn't help, of
course.
Any suggestions how I can get this thing back on its feet? Will
a "Windows Reset" work (not quite sure what this does - it
claims to not disturb my data files, so maybe it just
reinstalls Windows only?) Am I correct in assuming that
restoring from a Restore Point is not likely to help?
I got the disk back. I tried several things, not sure what was
the magic trick that got it going. In the process I did some of
what you suggest...
Win10
Do you recall if your old boot disk was GPT formatted.
Do you recall if the Win7 disk is MBR
The Win10 disk is GPT. I think the Win7 disk is MBR but not sure.
Access your UEFI or BIOS and determine which disk is enabled as
the primary boot device. Don't make any changes, just look.
Exit UEFI or BIOS
Disconnect the Win7 disk
Access the UEFI or BIOS and ensure the Win10 disk is the boot
device.
- if not, make it the first booting device.
I had already disconnected the Win7 disk, but I went into UEFI.
At first it didn't seem to detect the HD at all, but after a
couple of power-downs it did, and I set it to be the first boot
device, with the CD drive as second.
Exit the UEFI or BIOS and see if the device boots to Windows 10
It did not boot to Win10 at this point. I got into a command
prompt and executed some DISKPART commands I found on the net,
which was nervewracking because I don't really understand what
they do. That may have helped me mark a correct partition as
Active.
Next restart it still didn't boot to windows, but when I went to
UEFI a third boot option is now there that I don't recall seeing
before, "Windows Boot Manager". I set IT to be the first boot
device and now I can boot up to Windows 10 seemingly like I did
before.
Report the results.
The new Boot Manager bothers me - I feel like it wasn't there
before - but it functions the way it should, so I'll consider
that later, unless you have some thoughts about it.
Thank you.
- i.e. it's the correct choice
What happened?
Connecting the Win7 disk with a bootable System partition
realigned the
available devices in the UEFI negating the pre-Win7 connected disk
condition that booted using the System partition on the Win10
disk.
- Your two disks have two possibilities
Both GPT or the Win10 GPT and Win7 MBR
There's a possibility that your UEFI has multiple configurations
for the type of connected devices that allows you to select the
type of devices that you want to boot.
UEFI only
UEFI and Legacy
Legacy only
MBR is Legacy.If the Win7 device is MBR and connected and ordered as priority
for
present bootable devices then any setting that uses Legacy when
the Win7 MBR disk has priority will use that MBR Win7 disk to
boot.
If the Win7 device is GPT but ordered as a priority over the
Win10 disk
that priority will use the GPT Win7 disk
- in both cases it uses the wrong device(disk) instead of Win10's
disk and the UEFI setting - Windows Boot Manager
(on some Win7 devices using MBR, the System and the Windows
partition may be the same rather separate partitions on the disk.
You can probably still connect that Windows 7 disk and wipe it and
use for data or other non-booting means.
- Shutdown the device
- Connect it
- Access the UEFI(ensure you know how to prevent it being bypassed
and booting)
- Verify that the correct Win10 disk is first in the device boot
order and Windows Boot Manager is selected. If necessary save
these settings. - Look in the UEFI for Boot options noted
above(UEFI, UEFI&Legacy, Legacy) - if present, ensure that UEFI or
UEFI and Legacy are selected - the former is prefered since its
highly likely that the Win7 disk is MBR - Reverify that the Win10
disk and Windows Boot Manager are still selected - Save the UEFI
setting, Exit the UEFI and boot the device
(optionally you may be able in some UEFI settings to exit the
UEFI by
selecting the Boot device(the Windows Boot Manager) to directly
boot the Win10 disk while exiting the UEFI.
- If successful, navigate to Disk Management and do what you
wanted to
do with that Win7 disk - select the volume(the disk), wipe the
entire disk to bare metal unallocated space, format as GPT, assign
a drive letter(if not pre-populated), close Disk Management, then
use File Explorer to do what you want - create folder, copy
folders, copy files, etc.
Once done, you can go back to the UEFI settings, the Win7 device
will not be present as a possible booting device - no longer
having a System parition(alone or on the same partition as Windows
7).
Good luck.
On 21 Feb 2023, =?UTF-8?B?Li4ud8Khw7HCp8KxwqTDsSA=?=
<winstonmvp@gmail.com> wrote in alt.comp.os.windows-10:
Nil wrote on 2/20/2023 5:59 PM:
On 20 Feb 2023, =?UTF-8?B?Li4ud8Khw7HCp8KxwqTDsSA=?=The Windows Boot Manager on UEFI is normal.
<winstonmvp@gmail.com> wrote in alt.comp.os.windows-10:
Nil wrote on 2/20/2023 5:25 PM:
I was proceeding to add a second hard disk to my Win 10
computer. I hooked up a spare HD and booted up, intending to
reformat the "new" disk and move some data to it. I realized
too late that the spare disk I hooked up was a previous Windows
7 boot disk that I had decommissioned. The computer proceeded
to boot up to Win7. I shut down immediately and unplugged the
Win7 disk, but now it won't boot up into Win10. I can get it to
the blue Repair screen where I can do a Windows Reset, boot to
Safe Mode (haven't tried that yet, but I don't expect it to
work), etc. I CAN get to a command prompt where I can see
everything on the C drive. I can get to a Repair thing where it
appears to do a CHKDSK-type check, but that doesn't help, of
course.
Any suggestions how I can get this thing back on its feet? Will
a "Windows Reset" work (not quite sure what this does - it
claims to not disturb my data files, so maybe it just
reinstalls Windows only?) Am I correct in assuming that
restoring from a Restore Point is not likely to help?
I got the disk back. I tried several things, not sure what was
the magic trick that got it going. In the process I did some of
what you suggest...
Win10
Do you recall if your old boot disk was GPT formatted.
Do you recall if the Win7 disk is MBR
The Win10 disk is GPT. I think the Win7 disk is MBR but not sure.
Access your UEFI or BIOS and determine which disk is enabled as
the primary boot device. Don't make any changes, just look.
Exit UEFI or BIOS
Disconnect the Win7 disk
Access the UEFI or BIOS and ensure the Win10 disk is the boot
device.
- if not, make it the first booting device.
I had already disconnected the Win7 disk, but I went into UEFI.
At first it didn't seem to detect the HD at all, but after a
couple of power-downs it did, and I set it to be the first boot
device, with the CD drive as second.
Exit the UEFI or BIOS and see if the device boots to Windows 10
It did not boot to Win10 at this point. I got into a command
prompt and executed some DISKPART commands I found on the net,
which was nervewracking because I don't really understand what
they do. That may have helped me mark a correct partition as
Active.
Next restart it still didn't boot to windows, but when I went to
UEFI a third boot option is now there that I don't recall seeing
before, "Windows Boot Manager". I set IT to be the first boot
device and now I can boot up to Windows 10 seemingly like I did
before.
Report the results.
The new Boot Manager bothers me - I feel like it wasn't there
before - but it functions the way it should, so I'll consider
that later, unless you have some thoughts about it.
Thank you.
- i.e. it's the correct choice
What happened?
Connecting the Win7 disk with a bootable System partition
realigned the
available devices in the UEFI negating the pre-Win7 connected disk
condition that booted using the System partition on the Win10
disk.
- Your two disks have two possibilities
Both GPT or the Win10 GPT and Win7 MBR
There's a possibility that your UEFI has multiple configurations
for the type of connected devices that allows you to select the
type of devices that you want to boot.
UEFI only
UEFI and Legacy
Legacy only
=> MBR is Legacy.
If the Win7 device is MBR and connected and ordered as priority
for
present bootable devices then any setting that uses Legacy when
the Win7 MBR disk has priority will use that MBR Win7 disk to
boot.
If the Win7 device is GPT but ordered as a priority over the
Win10 disk
that priority will use the GPT Win7 disk
- in both cases it uses the wrong device(disk) instead of Win10's
disk and the UEFI setting - Windows Boot Manager
(on some Win7 devices using MBR, the System and the Windows
partition may be the same rather separate partitions on the disk.
You can probably still connect that Windows 7 disk and wipe it and
use for data or other non-booting means.
- Shutdown the device
- Connect it
- Access the UEFI(ensure you know how to prevent it being bypassed
and booting)
- Verify that the correct Win10 disk is first in the device boot
order and Windows Boot Manager is selected. If necessary save
these settings. - Look in the UEFI for Boot options noted
above(UEFI, UEFI&Legacy, Legacy) - if present, ensure that UEFI or
UEFI and Legacy are selected - the former is prefered since its
highly likely that the Win7 disk is MBR - Reverify that the Win10
disk and Windows Boot Manager are still selected - Save the UEFI
setting, Exit the UEFI and boot the device
(optionally you may be able in some UEFI settings to exit the
UEFI by
selecting the Boot device(the Windows Boot Manager) to directly
boot the Win10 disk while exiting the UEFI.
- If successful, navigate to Disk Management and do what you
wanted to
do with that Win7 disk - select the volume(the disk), wipe the
entire disk to bare metal unallocated space, format as GPT, assign
a drive letter(if not pre-populated), close Disk Management, then
use File Explorer to do what you want - create folder, copy
folders, copy files, etc.
Once done, you can go back to the UEFI settings, the Win7 device
will not be present as a possible booting device - no longer
having a System parition(alone or on the same partition as Windows
7).
Good luck.
Thank you! So, I guess I panicked, and by removing the Win7 disk I left
the system without a viable boot disk. I should have left it in there, interrupted the boot to Windows, gone to UEFT to chosen the Win10 disk
as the first boot device. I still could, I guess, but I don't need to
any more.
My original goal was to blow away the old Win7 disk to be used as a 2nd storage disk. I was trying to save some effort by doing it all with the
SATA connectors on the motherboard while I have the case open. I also
have a USB hard disk dock that I can use, which will be safer, or at
least not as prone to carelessness on my part.
Thanks, again.
Thank you! So, I guess I panicked, and by removing the Win7 disk I left
the system without a viable boot disk. I should have left it in there, interrupted the boot to Windows, gone to UEFT to chosen the Win10 disk
as the first boot device. I still could, I guess, but I don't need to
any more.
My original goal was to blow away the old Win7 disk to be used as a 2nd storage disk. I was trying to save some effort by doing it all with the
SATA connectors on the motherboard while I have the case open. I also
have a USB hard disk dock that I can use, which will be safer, or at
least not as prone to carelessness on my part.
Thanks, again.
Fortunately I didn't have to resort to that. Reinstalling Windows 10
would be a very last resort, though I was considering it. My computer
is so highly tuned for my use that it would be a major PITA to have
reinstall everything.
My computer
is so highly tuned for my use that it would be a major PITA to have
reinstall everything.
| Sysop: | Keyop |
|---|---|
| Location: | Huddersfield, West Yorkshire, UK |
| Users: | 297 |
| Nodes: | 16 (2 / 14) |
| Uptime: | 04:42:51 |
| Calls: | 6,666 |
| Files: | 12,213 |
| Messages: | 5,335,886 |
