Scheduled Maintenance: We are aware of an issue with Google, AOL, and Yahoo services as email providers which are blocking new registrations. We are trying to fix the issue and we have several internal and external support tickets in process to resolve the issue. Please see: viewtopic.php?t=158230
Need help leaving Windows - New Debian install errors
-
- Posts: 8
- Joined: 2020-04-29 21:00
Need help leaving Windows - New Debian install errors
Hi there,
I'm trying to leave windows behind, but I am having issues getting Debian 10 (debian-live-10.3.0-amd64-kde+nonfree) to work with multiple startup errors (listed at the bottom of this post) and the solutions I've tried to date have not worked and I'm running out of ideas. Here are some details...
a) I have 2 x SSD Hard Drives one of which still has Windows 7 installed and the other is a brand new one for Debian 10
b) I'm able to install Debian 10 (debian-live-10.3.0-amd64-kde+nonfree) with no issues off a USB stick that I put the Debian 10 ISO onto using Etcher. I did check the SHA256 of the ISO when I downloaded it to confirm a good download. That said I don't know how to check the bootable USB that Etcher created, but perhaps I need to check this too ?
c) After installing Debian 10, when I start the PC I get the error message as listed at the bottom of this post
To try and resolve this I have to date tried...
1) Re-installing Debian 10 (multiple times)
2) Installing Linux Mint 19.3 MATE as a test to see if the errors were specific to Debian 10 but Linux Mint 19.3 MATE had similar error messages too
3) I've run tests to check the RAM and SSD health and all showed ok
4) Did lots of research about the older Linux related issues with some Samsung SSD's (as I was using a Samsung 860 EVO) and even tried turning off NCQ (which did not help). That said from what I understand these issues have all been resolved already with the latest versions of Linux
5) I purchased a new SSD from a different brand (Crucial) in case in case my SSD was faulty and/or in case the Samsung SSD issue may not have been 100% resolved
6) I purchased new SATA cables in case these were faulty
Frustratingly none of the above have helped, but I really REALLY want to finally make the move to Linux from Windows, and more specifically to Debian as its reputation for stability really appeals to me.
My PC is an older PC from 2011 which has had the Hard Drives and Graphics Cards upgraded in the last couple of years. Heres some specs...
Motherboard = ASUS P6X58D Premium
Processor = Intel(R) Core(TM) i7 CPU x980 @ 3.33GHz
BIOS version/date = American Megatrends Inc. 1501, 10/5/2011 (the most recent one on their website)
SMBIOS Version = 2.5
Graphics Card = Radeon RX 580
SSD (for the Debian 10 install) = A brand new Samsung EVO 860 1TB (what I first tried using), and currently a Crucial MX500 1TB in replacement of the Samsung
RAM = 20GB
System Type = x64
Any advise, help or guidance would be much appreciated !
ERROR MESSAGES that display during Start-Up (post Grub)....
[ 36.254863] ata8.00: exxception Emask 0x0 SAct 0x1000014 SErr 0x0 action 0x6 frozen
[ 36.254922] ata8.00: failed command: READ FPDMA QUEUED
[ 36.254963] ata8.00: cmd 60/02:10:fe:b7:f0/00:00:71:00:00/40 tag 2 ncq dma 1024 in
[ 36.254963] res 40/00:01:00:00:00/00:00:00:00:00/00 EMask 0x4 (timeout)
[ 36.255020] ata8.00: status: { DRDY }
[ 36.254034] ata8.00: failed command: READ FPDMA QUEUED
[ 36.254954] ata8.00: cmd 60/08:20:f0:67:70/00:00:74:00:00/40 tag 4 ncq dma 4096 in
[ 36.254954] res 40/00:00:00:00:00/00:00:00:00:00/00 EMask 0x4 (timeout)
[ 36.255101] ata8.00: status: { DRDY }
[ 36.255115] ata8.00: failed command: READ FPDMA QUEUED
[ 36.255135] ata8.00: cmd 60/08:c0:f0:af:f0/00:00:71:00:00/40 tag 24 ncq dma 4096 in
[ 36.255135] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 36.255181] ata8.00: status: { DRDY }
[ 36.733649] print_req_error: I/O error, dev sda, sector 1911601150
[ 36.733721] print_req_error: I/O error, dev sda, sector 1953523696
[ 36.733772] print_req_error: I/O error, dev sda, sector 1911599088
Gave up waiting for root file system device. Common problems:
- Boot args (cat /proc/cmdline)
- Check rootdelay= (did the system wait long enough?)
- Missing modules (cat /proc/modules; is /dev)
ALERT! /dev/sdb1 does not exist. Dropping to a shell!
BusgBox u1.30.1 (Debian 1:1.30.1-4) built-in shell (ash)
Enter 'help' for a list of built-in commands.
(initramfs)
I'm trying to leave windows behind, but I am having issues getting Debian 10 (debian-live-10.3.0-amd64-kde+nonfree) to work with multiple startup errors (listed at the bottom of this post) and the solutions I've tried to date have not worked and I'm running out of ideas. Here are some details...
a) I have 2 x SSD Hard Drives one of which still has Windows 7 installed and the other is a brand new one for Debian 10
b) I'm able to install Debian 10 (debian-live-10.3.0-amd64-kde+nonfree) with no issues off a USB stick that I put the Debian 10 ISO onto using Etcher. I did check the SHA256 of the ISO when I downloaded it to confirm a good download. That said I don't know how to check the bootable USB that Etcher created, but perhaps I need to check this too ?
c) After installing Debian 10, when I start the PC I get the error message as listed at the bottom of this post
To try and resolve this I have to date tried...
1) Re-installing Debian 10 (multiple times)
2) Installing Linux Mint 19.3 MATE as a test to see if the errors were specific to Debian 10 but Linux Mint 19.3 MATE had similar error messages too
3) I've run tests to check the RAM and SSD health and all showed ok
4) Did lots of research about the older Linux related issues with some Samsung SSD's (as I was using a Samsung 860 EVO) and even tried turning off NCQ (which did not help). That said from what I understand these issues have all been resolved already with the latest versions of Linux
5) I purchased a new SSD from a different brand (Crucial) in case in case my SSD was faulty and/or in case the Samsung SSD issue may not have been 100% resolved
6) I purchased new SATA cables in case these were faulty
Frustratingly none of the above have helped, but I really REALLY want to finally make the move to Linux from Windows, and more specifically to Debian as its reputation for stability really appeals to me.
My PC is an older PC from 2011 which has had the Hard Drives and Graphics Cards upgraded in the last couple of years. Heres some specs...
Motherboard = ASUS P6X58D Premium
Processor = Intel(R) Core(TM) i7 CPU x980 @ 3.33GHz
BIOS version/date = American Megatrends Inc. 1501, 10/5/2011 (the most recent one on their website)
SMBIOS Version = 2.5
Graphics Card = Radeon RX 580
SSD (for the Debian 10 install) = A brand new Samsung EVO 860 1TB (what I first tried using), and currently a Crucial MX500 1TB in replacement of the Samsung
RAM = 20GB
System Type = x64
Any advise, help or guidance would be much appreciated !
ERROR MESSAGES that display during Start-Up (post Grub)....
[ 36.254863] ata8.00: exxception Emask 0x0 SAct 0x1000014 SErr 0x0 action 0x6 frozen
[ 36.254922] ata8.00: failed command: READ FPDMA QUEUED
[ 36.254963] ata8.00: cmd 60/02:10:fe:b7:f0/00:00:71:00:00/40 tag 2 ncq dma 1024 in
[ 36.254963] res 40/00:01:00:00:00/00:00:00:00:00/00 EMask 0x4 (timeout)
[ 36.255020] ata8.00: status: { DRDY }
[ 36.254034] ata8.00: failed command: READ FPDMA QUEUED
[ 36.254954] ata8.00: cmd 60/08:20:f0:67:70/00:00:74:00:00/40 tag 4 ncq dma 4096 in
[ 36.254954] res 40/00:00:00:00:00/00:00:00:00:00/00 EMask 0x4 (timeout)
[ 36.255101] ata8.00: status: { DRDY }
[ 36.255115] ata8.00: failed command: READ FPDMA QUEUED
[ 36.255135] ata8.00: cmd 60/08:c0:f0:af:f0/00:00:71:00:00/40 tag 24 ncq dma 4096 in
[ 36.255135] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 36.255181] ata8.00: status: { DRDY }
[ 36.733649] print_req_error: I/O error, dev sda, sector 1911601150
[ 36.733721] print_req_error: I/O error, dev sda, sector 1953523696
[ 36.733772] print_req_error: I/O error, dev sda, sector 1911599088
Gave up waiting for root file system device. Common problems:
- Boot args (cat /proc/cmdline)
- Check rootdelay= (did the system wait long enough?)
- Missing modules (cat /proc/modules; is /dev)
ALERT! /dev/sdb1 does not exist. Dropping to a shell!
BusgBox u1.30.1 (Debian 1:1.30.1-4) built-in shell (ash)
Enter 'help' for a list of built-in commands.
(initramfs)
Last edited by haremkeeper on 2020-04-29 22:55, edited 12 times in total.
- sunrat
- Administrator
- Posts: 6460
- Joined: 2006-08-29 09:12
- Location: Melbourne, Australia
- Has thanked: 116 times
- Been thanked: 472 times
Re: Need help leaving Windows - New Debian install errors
Should be no issue with the EVO 860. I do recommend you download and use an installer which includes non-free firmware as that can be a stumbling block.
https://cdimage.debian.org/cdimage/unof ... -firmware/
Images can be uploaded to an image sharing site and linked here. Make it small though.
Edit - you posted error messages while I was typing. Not sure about them myself. Try install with the second SSD disconnected if you haven't done that already, and remove the USB drive you installed from before restarting.
Debian can be difficult to learn as a first foray into Linux.
https://cdimage.debian.org/cdimage/unof ... -firmware/
Images can be uploaded to an image sharing site and linked here. Make it small though.
Edit - you posted error messages while I was typing. Not sure about them myself. Try install with the second SSD disconnected if you haven't done that already, and remove the USB drive you installed from before restarting.
Debian can be difficult to learn as a first foray into Linux.
“ computer users can be divided into 2 categories:
Those who have lost data
...and those who have not lost data YET ” Remember to BACKUP!
Those who have lost data
...and those who have not lost data YET ” Remember to BACKUP!
-
- Posts: 677
- Joined: 2018-05-10 19:34
- Location: Some where out west
- Been thanked: 1 time
Re: Need help leaving Windows - New Debian install errors
Maybe it was your typing, this does not look right:
Using code boxes:
Something is wrong,... there is no it should be :
(one 1 , not l-L)
==========
also , I have found using a optical drive, and CD or DVD is much more reliable, if that is a option for you.
I use a portable USB optical drive on Laptops that do not have one.
"deu" should be "dev" and I am seeing sdl as in L lower case,...?Gave up waiting for root file system device. Common problems:
- Boot args (cat /proc/cmdline)
- Check rootdelay. (did the system wait long enough?)
- Missing modules (cat /proc/modules; is /deu)
ALERT! /deu/sdbl does not exist. Dropping to a shell!
Using code boxes:
Code: Select all
Gave up waiting for root file system device. Common problems:
- Boot args (cat /proc/cmdline)
- Check rootdelay. (did the system wait long enough?)
- Missing modules (cat /proc/modules; is /deu)
ALERT! /deu/sdbl does not exist. Dropping to a shell!
Code: Select all
/deu/sdbl
Code: Select all
/dev/sdb1
==========
also , I have found using a optical drive, and CD or DVD is much more reliable, if that is a option for you.
I use a portable USB optical drive on Laptops that do not have one.
Please Read What we expect you have already Done
Search Engines know a lot, and
"If God had wanted computers to work all the time, He wouldn't have invented RESET buttons"
and
Just say NO to help vampires!
Search Engines know a lot, and
"If God had wanted computers to work all the time, He wouldn't have invented RESET buttons"
and
Just say NO to help vampires!
-
- Posts: 8
- Joined: 2020-04-29 21:00
Re: Need help leaving Windows - New Debian install errors
Re
Re the Error messages, my appologies I manually typed the error messages due to not being able to upload photo and made a few typos. Have re-checked and should be 99% correct now...
ERROR MESSAGES that display during Start-Up (post Grub)....
[ 36.254863] ata8.00: exxception Emask 0x0 SAct 0x1000014 SErr 0x0 action 0x6 frozen
[ 36.254922] ata8.00: failed command: READ FPDMA QUEUED
[ 36.254963] ata8.00: cmd 60/02:10:fe:b7:f0/00:00:71:00:00/40 tag 2 ncq dma 1024 in
[ 36.254963] res 40/00:01:00:00:00/00:00:00:00:00/00 EMask 0x4 (timeout)
[ 36.255020] ata8.00: status: { DRDY }
[ 36.254034] ata8.00: failed command: READ FPDMA QUEUED
[ 36.254954] ata8.00: cmd 60/08:20:f0:67:70/00:00:74:00:00/40 tag 4 ncq dma 4096 in
[ 36.254954] res 40/00:00:00:00:00/00:00:00:00:00/00 EMask 0x4 (timeout)
[ 36.255101] ata8.00: status: { DRDY }
[ 36.255115] ata8.00: failed command: READ FPDMA QUEUED
[ 36.255135] ata8.00: cmd 60/08:c0:f0:af:f0/00:00:71:00:00/40 tag 24 ncq dma 4096 in
[ 36.255135] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 36.255181] ata8.00: status: { DRDY }
[ 36.733649] print_req_error: I/O error, dev sda, sector 1911601150
[ 36.733721] print_req_error: I/O error, dev sda, sector 1953523696
[ 36.733772] print_req_error: I/O error, dev sda, sector 1911599088
Gave up waiting for root file system device. Common problems:
- Boot args (cat /proc/cmdline)
- Check rootdelay= (did the system wait long enough?)
- Missing modules (cat /proc/modules; is /dev)
ALERT! /dev/sdb1 does not exist. Dropping to a shell!
BusgBox u1.30.1 (Debian 1:1.30.1-4) built-in shell (ash)
Enter 'help' for a list of built-in commands.
(initramfs)
unfortunately not i.e. I have an optical drive, but have no CD/DVD's for burning (and can't buy them either due to the current lockdown)also , I have found using a optical drive, and CD or DVD is much more reliable, if that is a option for you.
Re the Error messages, my appologies I manually typed the error messages due to not being able to upload photo and made a few typos. Have re-checked and should be 99% correct now...
ERROR MESSAGES that display during Start-Up (post Grub)....
[ 36.254863] ata8.00: exxception Emask 0x0 SAct 0x1000014 SErr 0x0 action 0x6 frozen
[ 36.254922] ata8.00: failed command: READ FPDMA QUEUED
[ 36.254963] ata8.00: cmd 60/02:10:fe:b7:f0/00:00:71:00:00/40 tag 2 ncq dma 1024 in
[ 36.254963] res 40/00:01:00:00:00/00:00:00:00:00/00 EMask 0x4 (timeout)
[ 36.255020] ata8.00: status: { DRDY }
[ 36.254034] ata8.00: failed command: READ FPDMA QUEUED
[ 36.254954] ata8.00: cmd 60/08:20:f0:67:70/00:00:74:00:00/40 tag 4 ncq dma 4096 in
[ 36.254954] res 40/00:00:00:00:00/00:00:00:00:00/00 EMask 0x4 (timeout)
[ 36.255101] ata8.00: status: { DRDY }
[ 36.255115] ata8.00: failed command: READ FPDMA QUEUED
[ 36.255135] ata8.00: cmd 60/08:c0:f0:af:f0/00:00:71:00:00/40 tag 24 ncq dma 4096 in
[ 36.255135] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 36.255181] ata8.00: status: { DRDY }
[ 36.733649] print_req_error: I/O error, dev sda, sector 1911601150
[ 36.733721] print_req_error: I/O error, dev sda, sector 1953523696
[ 36.733772] print_req_error: I/O error, dev sda, sector 1911599088
Gave up waiting for root file system device. Common problems:
- Boot args (cat /proc/cmdline)
- Check rootdelay= (did the system wait long enough?)
- Missing modules (cat /proc/modules; is /dev)
ALERT! /dev/sdb1 does not exist. Dropping to a shell!
BusgBox u1.30.1 (Debian 1:1.30.1-4) built-in shell (ash)
Enter 'help' for a list of built-in commands.
(initramfs)
cuckooflew wrote:Maybe it was your typing, this does not look right:"deu" should be "dev" and I am seeing sdl as in L lower case,...?Gave up waiting for root file system device. Common problems:
- Boot args (cat /proc/cmdline)
- Check rootdelay. (did the system wait long enough?)
- Missing modules (cat /proc/modules; is /deu)
ALERT! /deu/sdbl does not exist. Dropping to a shell!
Using code boxes:Something is wrong,... there is noCode: Select all
Gave up waiting for root file system device. Common problems: - Boot args (cat /proc/cmdline) - Check rootdelay. (did the system wait long enough?) - Missing modules (cat /proc/modules; is /deu) ALERT! /deu/sdbl does not exist. Dropping to a shell!
it should be :Code: Select all
/deu/sdbl
(one 1 , not l-L)Code: Select all
/dev/sdb1
==========
also , I have found using a optical drive, and CD or DVD is much more reliable, if that is a option for you.
I use a portable USB optical drive on Laptops that do not have one.
-
- Posts: 8
- Joined: 2020-04-29 21:00
Re: Need help leaving Windows - New Debian install errors
thanks for the recommendations. I used this ISO... "debian-live-10.3.0-amd64-kde+nonfree" and did follow your last piece of advise Re disconnection the 2nd SSD (the one I use for Windows) during the install and removed the USB before re-starting
sunrat wrote:Should be no issue with the EVO 860. I do recommend you download and use an installer which includes non-free firmware as that can be a stumbling block.
https://cdimage.debian.org/cdimage/unof ... -firmware/
Images can be uploaded to an image sharing site and linked here. Make it small though.
Edit - you posted error messages while I was typing. Not sure about them myself. Try install with the second SSD disconnected if you haven't done that already, and remove the USB drive you installed from before restarting.
Debian can be difficult to learn as a first foray into Linux.
-
- Posts: 677
- Joined: 2018-05-10 19:34
- Location: Some where out west
- Been thanked: 1 time
Re: Need help leaving Windows - New Debian install errors
Ahh, oh no,...I forget about that....... And , ok on the typos, that is kind of what I figured.(and can't buy them either due to the current lockdown)
=====
So, did this work ?
----during the install and removed the USB before re-starting
Please Read What we expect you have already Done
Search Engines know a lot, and
"If God had wanted computers to work all the time, He wouldn't have invented RESET buttons"
and
Just say NO to help vampires!
Search Engines know a lot, and
"If God had wanted computers to work all the time, He wouldn't have invented RESET buttons"
and
Just say NO to help vampires!
-
- Posts: 8
- Joined: 2020-04-29 21:00
Re: Need help leaving Windows - New Debian install errors
I can confirm that I did remove the USB before re-starting, but still got the errors
cuckooflew wrote:Ahh, oh no,...I forget about that....... And , ok on the typos, that is kind of what I figured.(and can't buy them either due to the current lockdown)
=====
So, did this work ?----during the install and removed the USB before re-starting
Re: Need help leaving Windows - New Debian install errors
Hi,
After the prompt, in BusyBox what does this show?
cat /proc/cmdline
By the way, you can boot Windows from the grub menu?
After the prompt, in BusyBox what does this show?
cat /proc/cmdline
By the way, you can boot Windows from the grub menu?
DebianStable
Code: Select all
$ vrms
No non-free or contrib packages installed on debian! rms would be proud.
-
- Posts: 8
- Joined: 2020-04-29 21:00
Re: Need help leaving Windows - New Debian install errors
Re the Grub menu, currently to boot windows I need to change the boot order in Bios (a temporary arrangement). That said I do know how to add windows to the Grub menu, however, I'm wish to get Debian operational before making changes to the Grub menu.
From "BusyBox" it shows the following then nothing...
BusgBox u1.30.1 (Debian 1:1.30.1-4) built-in shell (ash)
Enter 'help' for a list of built-in commands.
(initramfs) _
From "BusyBox" it shows the following then nothing...
BusgBox u1.30.1 (Debian 1:1.30.1-4) built-in shell (ash)
Enter 'help' for a list of built-in commands.
(initramfs) _
kedaha wrote:Hi,
After the prompt, in BusyBox what does this show?
cat /proc/cmdline
By the way, you can boot Windows from the grub menu?
- dilberts_left_nut
- Administrator
- Posts: 5346
- Joined: 2009-10-05 07:54
- Location: enzed
- Has thanked: 13 times
- Been thanked: 66 times
Re: Need help leaving Windows - New Debian install errors
Those are definitely hardware error messages.
Can you move the drive to a different sata port and see if it follows to "ataX" ?
The "sdb1 does not exist" message looks like a misconfigured boot partition designation, maybe due to the USB (at sda) not being present on next boot. I recall that issue a long from time ago.
Can you move the drive to a different sata port and see if it follows to "ataX" ?
The "sdb1 does not exist" message looks like a misconfigured boot partition designation, maybe due to the USB (at sda) not being present on next boot. I recall that issue a long from time ago.
AdrianTM wrote:There's no hacker in my grandma...
-
- Posts: 8
- Joined: 2020-04-29 21:00
Re: Need help leaving Windows - New Debian install errors
Thanks for the idea.
I firstly (in error) changed just the sata power cable (i.e. the 22pin one) used for the SSD and this for some reason resulted in significantly MORE error messages as per this photo (vs those listed in my original post)...
https://drive.google.com/file/d/1WDSZDe ... sp=sharing
I then realized my mistake and changed the sata (data) cable plug used on the motherboard and this resulted in significantly LESS error messages as per this photo...
https://drive.google.com/file/d/1eIMLY0 ... sp=sharing
In both scenarios that's as far as the boot went and after waiting a good amount of time, I had to shut down the PC.
The reduction in the number of error messages when trying a different sata port as per your suggestion seems to have taken a step in the right direction. At the same time I have no idea what to try next to resolve the remaining error messages ? Any ideas ???
NOTE - strangely I can run the other SSD (that has Windows 7 on it) on any of the sata ports with zero issues
I firstly (in error) changed just the sata power cable (i.e. the 22pin one) used for the SSD and this for some reason resulted in significantly MORE error messages as per this photo (vs those listed in my original post)...
https://drive.google.com/file/d/1WDSZDe ... sp=sharing
I then realized my mistake and changed the sata (data) cable plug used on the motherboard and this resulted in significantly LESS error messages as per this photo...
https://drive.google.com/file/d/1eIMLY0 ... sp=sharing
In both scenarios that's as far as the boot went and after waiting a good amount of time, I had to shut down the PC.
The reduction in the number of error messages when trying a different sata port as per your suggestion seems to have taken a step in the right direction. At the same time I have no idea what to try next to resolve the remaining error messages ? Any ideas ???
NOTE - strangely I can run the other SSD (that has Windows 7 on it) on any of the sata ports with zero issues
dilberts_left_nut wrote:Those are definitely hardware error messages.
Can you move the drive to a different sata port and see if it follows to "ataX" ?
The "sdb1 does not exist" message looks like a misconfigured boot partition designation, maybe due to the USB (at sda) not being present on next boot. I recall that issue a long from time ago.
Re: Need help leaving Windows - New Debian install errors
I think you may be making heavy work of this.
My advice (unless you have already tried it) would be:
Leave the Windows SSD drive enabled in the BIOS as the first drive to be booted.
Since there have been reported issues with the 860 EVO SSD—see for example here—I would use the other Crucial SSD MX500 1TB for Debian.
Rather than the unofficial image, which hasn't worked, I would personally use an official network install iso image and deal with any other firmware issues afterwards.
At the end of the installation when you get to the screen
[!] Install the GRUB boot loader on a hard disk
you will presumably see
And it ought to boot and Windows7 as well.
My advice (unless you have already tried it) would be:
Leave the Windows SSD drive enabled in the BIOS as the first drive to be booted.
Since there have been reported issues with the 860 EVO SSD—see for example here—I would use the other Crucial SSD MX500 1TB for Debian.
Rather than the unofficial image, which hasn't worked, I would personally use an official network install iso image and deal with any other firmware issues afterwards.
At the end of the installation when you get to the screen
[!] Install the GRUB boot loader on a hard disk
you will presumably see
Select the first option, namely /dev/sdaDevice for boot loader installation on:
Enter device manually
/dev/sda (the Windows SSD)
/dev/sdb (your new Crucial SSD)
And it ought to boot and Windows7 as well.
DebianStable
Code: Select all
$ vrms
No non-free or contrib packages installed on debian! rms would be proud.
- sunrat
- Administrator
- Posts: 6460
- Joined: 2006-08-29 09:12
- Location: Melbourne, Australia
- Has thanked: 116 times
- Been thanked: 472 times
Re: Need help leaving Windows - New Debian install errors
I doubt the "unofficial" side of things would affect anything; it's just the official image plus firmware. There have been reports of the live installer failing where subsequent attempts with a full install image or netinstall (I'd still use the unofficial one) have succeeded. Netinstall may be a bit harder to use for someone with no Linux experience in that it requires internet connection; although it's easy if you can connect an ethernet cable rather than hoping and praying wifi will work.kedaha wrote:Rather than the unofficial image, which hasn't worked, I would personally use an official network install iso image and deal with any other firmware issues afterwards.
As alluded to before, the probable issue here is GRUB installing to the wrong drive, perhaps back on the USB drive.
“ computer users can be divided into 2 categories:
Those who have lost data
...and those who have not lost data YET ” Remember to BACKUP!
Those who have lost data
...and those who have not lost data YET ” Remember to BACKUP!
Re: Need help leaving Windows - New Debian install errors
I have little doubt that unofficial images are OK for their purpose, which is to try Debian and to facilitate installation but they can be built by anyone whereas official CD/DVD releases are signed so you can verify they're authentic and any bugs found can be reported to the Debian Bug Tracking System.sunrat wrote: I doubt the "unofficial" side of things would affect anything; it's just the official image plus firmware. There have been reports of the live installer failing where subsequent attempts with a full install image or netinstall (I'd still use the unofficial one) have succeeded.
Speaking for myself, my early progress in becoming a Debian user was, among other things, thanks to problematic drivers requiring firmware. If someone just wants to get a system up and running then I think I might, albeit grudgingly, recommend the easier unofficial way too.sunrat wrote:Netinstall may be a bit harder to use for someone with no Linux experience in that it requires internet connection; although it's easy if you can connect an ethernet cable rather than hoping and praying wifi will work.
Absolutely.sunrat wrote:As alluded to before, the probable issue here is GRUB installing to the wrong drive, perhaps back on the USB drive.
DebianStable
Code: Select all
$ vrms
No non-free or contrib packages installed on debian! rms would be proud.
Re: Need help leaving Windows - New Debian install errors
I have little doubt that unofficial images are OK for their purpose, which is to try Debian and to facilitate installation but they can be built by anyone whereas official CD/DVD releases are signed so you can verify they're authentic and any bugs found can be reported to the Debian Bug Tracking System.sunrat wrote: I doubt the "unofficial" side of things would affect anything; it's just the official image plus firmware. There have been reports of the live installer failing where subsequent attempts with a full install image or netinstall (I'd still use the unofficial one) have succeeded.
Speaking for myself, my early progress in becoming a Debian user was, among other things, thanks to problematic drivers requiring firmware. If someone just wants to get a system up and running then I think I might, albeit grudgingly, recommend the easier unofficial way too.sunrat wrote:Netinstall may be a bit harder to use for someone with no Linux experience in that it requires internet connection; although it's easy if you can connect an ethernet cable rather than hoping and praying wifi will work.
Absolutely.sunrat wrote:As alluded to before, the probable issue here is GRUB installing to the wrong drive, perhaps back on the USB drive.
DebianStable
Code: Select all
$ vrms
No non-free or contrib packages installed on debian! rms would be proud.
Re: Need help leaving Windows - New Debian install errors
I have little doubt that unofficial images are OK for their purpose, which is to try Debian and to facilitate installation but they can be built by anyone whereas official CD/DVD releases are signed so you can verify they're authentic and any bugs found can be reported to the Debian Bug Tracking System.sunrat wrote: I doubt the "unofficial" side of things would affect anything; it's just the official image plus firmware. There have been reports of the live installer failing where subsequent attempts with a full install image or netinstall (I'd still use the unofficial one) have succeeded.
Speaking for myself, my early progress in becoming a Debian user was, among other things, thanks to problematic drivers requiring firmware. If someone just wants to get a system up and running then I think I might, albeit grudgingly, recommend the easier unofficial way too.sunrat wrote:Netinstall may be a bit harder to use for someone with no Linux experience in that it requires internet connection; although it's easy if you can connect an ethernet cable rather than hoping and praying wifi will work.
Absolutely.sunrat wrote:As alluded to before, the probable issue here is GRUB installing to the wrong drive, perhaps back on the USB drive.
DebianStable
Code: Select all
$ vrms
No non-free or contrib packages installed on debian! rms would be proud.
Re: Need help leaving Windows - New Debian install errors
I have little doubt that unofficial images are OK for their purpose, which is to try Debian and to facilitate installation but they can be built by anyone whereas official CD/DVD releases are signed so you can verify they're authentic and any bugs found can be reported to the Debian Bug Tracking System.sunrat wrote: I doubt the "unofficial" side of things would affect anything; it's just the official image plus firmware. There have been reports of the live installer failing where subsequent attempts with a full install image or netinstall (I'd still use the unofficial one) have succeeded.
Speaking for myself, my early progress in becoming a Debian user was, among other things, thanks to problematic drivers requiring firmware. If a someone just wants to get a stable desktop system up and running then I think I might, albeit grudgingly, recommend the easier way too.sunrat wrote:Netinstall may be a bit harder to use for someone with no Linux experience in that it requires internet connection; although it's easy if you can connect an ethernet cable rather than hoping and praying wifi will work.
Very likely.sunrat wrote:As alluded to before, the probable issue here is GRUB installing to the wrong drive, perhaps back on the USB drive.
DebianStable
Code: Select all
$ vrms
No non-free or contrib packages installed on debian! rms would be proud.
Re: Need help leaving Windows - New Debian install errors
I have little doubt that unofficial images are OK for their purpose, which is to try Debian and to facilitate installation but they can be built by anyone whereas official CD/DVD releases are signed so you can verify they're authentic and any bugs found can be reported to the Debian Bug Tracking System.sunrat wrote: I doubt the "unofficial" side of things would affect anything; it's just the official image plus firmware. There have been reports of the live installer failing where subsequent attempts with a full install image or netinstall (I'd still use the unofficial one) have succeeded.
Speaking for myself, my early progress in becoming a Debian user was, among other things, thanks to problematic drivers requiring firmware. If a someone just wants to get a stable desktop system up and running then I think I might, albeit grudgingly, recommend the easier way too.sunrat wrote:Netinstall may be a bit harder to use for someone with no Linux experience in that it requires internet connection; although it's easy if you can connect an ethernet cable rather than hoping and praying wifi will work.
Very likely.sunrat wrote:As alluded to before, the probable issue here is GRUB installing to the wrong drive, perhaps back on the USB drive.
DebianStable
Code: Select all
$ vrms
No non-free or contrib packages installed on debian! rms would be proud.
Re: Need help leaving Windows - New Debian install errors
The advantage of official CD/DVD releases is they're signed so you can verify they're authentic and report any bugs to the Debian Bug Tracking System which isn't the case for unofficial images.sunrat wrote:I doubt the "unofficial" side of things would affect anything; it's just the official image plus firmware. There have been reports of the live installer failing where subsequent attempts with a full install image or netinstall (I'd still use the unofficial one) have succeeded.
Speaking for myself, my early progress in becoming a Debian user was, among other things, thanks to problematic drivers requiring firmware. If a someone just wants to get a stable desktop system up and running then I think I might, albeit grudgingly, recommend the easier way too.sunrat wrote:Netinstall may be a bit harder to use for someone with no Linux experience in that it requires internet connection; although it's easy if you can connect an ethernet cable rather than hoping and praying wifi will work.
Yes, I think so; the installation media chosen has nothing to do with this issue. It could also likely be solved by a bit of busybox tinkering.sunrat wrote:As alluded to before, the probable issue here is GRUB installing to the wrong drive, perhaps back on the USB drive.
I must say I am a bit confused about which disk the error messages refer to since Debian was installed to /dev/sdb1 which we are told does not exist.Gave up waiting for root file system device. Common problems:
- Boot args (cat /proc/cmdline)
- Check rootdelay= (did the system wait long enough?)
- Missing modules (cat /proc/modules; is /dev)
ALERT! /dev/sdb1 does not exist. Dropping to a shell!
DebianStable
Code: Select all
$ vrms
No non-free or contrib packages installed on debian! rms would be proud.
-
- Posts: 8
- Joined: 2020-04-29 21:00
Re: Need help leaving Windows - New Debian install errors
Thanks for the suggestions. As an update I can advise that I have now additionally tried;
1) multiple different methods of installation (live, graphical etc) using the new
2) have used different ISO's (official/unofficial)
3) in all cases GRUB was definitely installed onto the correct SSD (I always disconnect the windows SSD before re-installing debian on the 2nd SSD)
In all cases, I would still get error messages during the boot (after GRUB) and mostly the boot would stop at the error messages and go no further.
With no other ideas of what to try to get Debian10 working, I installed Lint Mint 19.3 MATE and for a day or so everything seemed to work fine (no error messages on boot) making me initially think that the issue must be specific to Debian. However after limited use of Linux Mint the taskbar crashed. On re-starting things would again seem fine, but inevitably after a few hours the taskbar would crash again.
Here what I find MOST CONFUSING... What happens with Debian10 and/or Linx Mint installed lead me to think that even though I've already changed the SSD and Sata Cables, that there must be some other Hardware issue with my PC. At the same time my Windows 7 install (on another SSD) consistently works fine with no crashes whatsoever regardless of which sata port I plug it into i.e. the Windows 7 install seems to be completely uneffected by whatever it is that is affecting Debian 10 and Linut Mint 19.3
I really don't want to return to using Windows 7 as my daily driver, but have completely run out of ideas. Is there some other Hardware issue I should investigate ? Is there something else I could try ?
I really really want to make Linux my daily driver, thus any additional suggestions/recommendation would be much appreciated ! ))
Thanks
1) multiple different methods of installation (live, graphical etc) using the new
2) have used different ISO's (official/unofficial)
3) in all cases GRUB was definitely installed onto the correct SSD (I always disconnect the windows SSD before re-installing debian on the 2nd SSD)
In all cases, I would still get error messages during the boot (after GRUB) and mostly the boot would stop at the error messages and go no further.
With no other ideas of what to try to get Debian10 working, I installed Lint Mint 19.3 MATE and for a day or so everything seemed to work fine (no error messages on boot) making me initially think that the issue must be specific to Debian. However after limited use of Linux Mint the taskbar crashed. On re-starting things would again seem fine, but inevitably after a few hours the taskbar would crash again.
Here what I find MOST CONFUSING... What happens with Debian10 and/or Linx Mint installed lead me to think that even though I've already changed the SSD and Sata Cables, that there must be some other Hardware issue with my PC. At the same time my Windows 7 install (on another SSD) consistently works fine with no crashes whatsoever regardless of which sata port I plug it into i.e. the Windows 7 install seems to be completely uneffected by whatever it is that is affecting Debian 10 and Linut Mint 19.3
I really don't want to return to using Windows 7 as my daily driver, but have completely run out of ideas. Is there some other Hardware issue I should investigate ? Is there something else I could try ?
I really really want to make Linux my daily driver, thus any additional suggestions/recommendation would be much appreciated ! ))
Thanks