Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
hi, dos is a windows thing from what i understand so dos commands wont work on gnu/linux.
you would go to the terminal. where you can type commands (there is probably a gui to get similar info but copying/pasting output is more precise to get diagnostic info).
i dont use ubuntu but maybe search in the menu for something called terminal (mite be called gnome-terminal ?).
copy-paste the commands (for instance its /fdisk -l not fdisk -1 (and there is a space between cat and /)).
colorpurple provided a link to a script that makes it easier for people to provide this type of info for this specific purpose.
drivemap -s (hd0) ${root}
chainloader +1
}
set timeout_style=menu
if[ "${timeout}" =0]; then
set timeout=10
fi
### END /etc/grub.d/30_os-prober ###
### BEGIN /etc/grub.d/30_uefi-firmware ###
### END /etc/grub.d30_uefi-firmware ###
### BEGIN /etc/grub.d/40_custom ###
# This file provides an easy way to add custom menu entries. Simply type the
# menu entries you want to add after this comment. Be careful not to change
# the 'exec tail' line above.
### END /etc/grub.d/40_custom ###
### BEGIN /etc/grub.d41_custom ###
if [ -f $prefix/custom.cfg ]; then
source $prefix/custom.cfg;
fi
### END /etc/grub.d/41_custom ###
edward@edward-RE473AA-ABA-SR2020NX-NA681:**$
^ seems incomplete.
i dont have much experience with windows so hopefully i'm not off base.
anyways from the partial fdisk output above it seems like you have both operating systems as different partitions on the 2nd physical harddrive (gnu/linux refers to this as /dev/sdb). and the first physical harddrive contains only random data (/dev/sda). did windows work before like this ?
windows has a habit of only wanting drive c: to be the first partition on the 1st harddrive (then d: would be first optical drive (cd-rom ?); e: would be 2nd optical if it exist (dvd/cd-r); then first partition on the 2nd harddrive would be f:, then the remaining partitions on the 1st drive; then remaining partitions on 2nd drive). -- i memorized this because i got hosed once.
the linux enumerating scheme is much simpler. in your case the linux partition is /dev/sdb5 and the windows partition would be /dev/sdb2 (i think windows cant see this as drive c: and windows needs drive c: in order to operate).
maybe you can try to change drivemap -s (hd0) ${root} to drivemap -s (hd1) ${root} in /boot/grub/grub.cfg.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.