chroot: failed to run command ‘/bin/bash’: No such file or directory

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP








up vote
1
down vote

favorite












To fix grub, I tried following codes:



sudo mount /dev/sd6 /mnt 
sudo mount --bind /dev /mnt/dev 
sudo mount --bind /dev/pts /mnt/dev/pts
sudo mount --bind /proc /mnt/proc
sudo mount --bind /sys /mnt/sys


While trying:



sudo chroot /mnt


it shows "chroot: failed to run command ‘/bin/bash’: No such file or directory" error.



Please help me fix this problem.



Thanks in advance.



The output for sudo lsblk -o name,mountpoint,label,size,fstype,uuid | egrep -v ^loop&&sudo fdisk -l is:



NAME MOUNTPOINT LABEL SIZE FSTYPE UUID
sda 931.5G 
├─sda1 ESP 500M vfat 92E7-0D79
├─sda2 128M 
├─sda3 253.5G ntfs B6B65DCCB65D8DAD
├─sda4 WINRETOOLS 450M ntfs 38F87730F876EB8E
├─sda5 [SWAP] 15.3G swap 2a3bc8d1-c30e-4475-b23e-075969c6ec10
├─sda6 190.8G ext4 05298325-c1ee-4f08-8d7c-ea39d13a6958
└─sda7 428.8G ext4 2637ce7a-0e9b-407b-9b1e-021cf3bc536a
sdb /cdrom Ubuntu 16.04 LTS amd64 7.6G iso9660 2016-04-20-22-29-52-00
├─sdb1 Ubuntu 16.04 LTS amd64 1.4G iso9660 2016-04-20-22-29-52-00
└─sdb2 Ubuntu 16.04 LTS amd64 2.3M vfat B1F5-0A13
sr0 1024M 
Disk /dev/ram0: 64 MiB, 67108864 bytes, 131072 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram1: 64 MiB, 67108864 bytes, 131072 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram2: 64 MiB, 67108864 bytes, 131072 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram3: 64 MiB, 67108864 bytes, 131072 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram4: 64 MiB, 67108864 bytes, 131072 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram5: 64 MiB, 67108864 bytes, 131072 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram6: 64 MiB, 67108864 bytes, 131072 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram7: 64 MiB, 67108864 bytes, 131072 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram8: 64 MiB, 67108864 bytes, 131072 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram9: 64 MiB, 67108864 bytes, 131072 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram10: 64 MiB, 67108864 bytes, 131072 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram11: 64 MiB, 67108864 bytes, 131072 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram12: 64 MiB, 67108864 bytes, 131072 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram13: 64 MiB, 67108864 bytes, 131072 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram14: 64 MiB, 67108864 bytes, 131072 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram15: 64 MiB, 67108864 bytes, 131072 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/loop0: 1.3 GiB, 1433468928 bytes, 2799744 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/sda: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: 111A7812-C4EA-440D-AD62-0FE5922BA109

Device Start End Sectors Size Type
/dev/sda1 2048 1026047 1024000 500M EFI System
/dev/sda2 1026048 1288191 262144 128M Microsoft reserved
/dev/sda3 1288192 532901887 531613696 253.5G Microsoft basic data
/dev/sda4 1952602112 1953523711 921600 450M Windows recovery environment
/dev/sda5 621402112 653402111 32000000 15.3G Linux swap
/dev/sda6 653402112 1053403135 400001024 190.8G Linux filesystem
/dev/sda7 1053403136 1952602111 899198976 428.8G Linux filesystem

Partition table entries are not in disk order.




Disk /dev/sdb: 7.6 GiB, 8178892800 bytes, 15974400 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x0e0e8e70

Device Boot Start End Sectors Size Id Type
/dev/sdb1 * 0 2902111 2902112 1.4G 0 Empty
/dev/sdb2 2888004 2892739 4736 2.3M ef EFI (FAT-12/16/32)



grub2 bash mount chroot




share|improve this question


















  • 2




    Did you literally run sudo mount /dev/sd6 /mnt? That is unlikely to work. Furthermore, is it the correct / partition?
    – vidarlo
    Apr 22 at 12:49






  • 3




    Will you edit your question and add the output of this command: sudo lsblk -o name,mountpoint,label,size,fstype,uuid | egrep -v ^loop&&sudo fdisk -l
    – L. D. James
    Apr 22 at 12:51










  • @L.D.James I edited my question, please check it.
    – Mahesh
    Apr 23 at 1:44










  • What architecture are the chroot and the Ubuntu you're running for setting up the chroot?
    – muru
    Apr 23 at 1:53






  • 1




    You appear to have two Linux partitions. The largest is /dev/sda7. There's a chance that your /dev/sda6 might not be complete if it doesn't have a /bin folder. Try the commands you already performed and test /dev/sda7 as an alternative. I thought the output would show a name of your partitions and one might say something like Ubuntu OS and a different one might say DATA.
    – L. D. James
    Apr 23 at 1:56















up vote
1
down vote

favorite












To fix grub, I tried following codes:



sudo mount /dev/sd6 /mnt 
sudo mount --bind /dev /mnt/dev 
sudo mount --bind /dev/pts /mnt/dev/pts
sudo mount --bind /proc /mnt/proc
sudo mount --bind /sys /mnt/sys


While trying:



sudo chroot /mnt


it shows "chroot: failed to run command ‘/bin/bash’: No such file or directory" error.



Please help me fix this problem.



Thanks in advance.



The output for sudo lsblk -o name,mountpoint,label,size,fstype,uuid | egrep -v ^loop&&sudo fdisk -l is:



NAME MOUNTPOINT LABEL SIZE FSTYPE UUID
sda 931.5G 
├─sda1 ESP 500M vfat 92E7-0D79
├─sda2 128M 
├─sda3 253.5G ntfs B6B65DCCB65D8DAD
├─sda4 WINRETOOLS 450M ntfs 38F87730F876EB8E
├─sda5 [SWAP] 15.3G swap 2a3bc8d1-c30e-4475-b23e-075969c6ec10
├─sda6 190.8G ext4 05298325-c1ee-4f08-8d7c-ea39d13a6958
└─sda7 428.8G ext4 2637ce7a-0e9b-407b-9b1e-021cf3bc536a
sdb /cdrom Ubuntu 16.04 LTS amd64 7.6G iso9660 2016-04-20-22-29-52-00
├─sdb1 Ubuntu 16.04 LTS amd64 1.4G iso9660 2016-04-20-22-29-52-00
└─sdb2 Ubuntu 16.04 LTS amd64 2.3M vfat B1F5-0A13
sr0 1024M 
Disk /dev/ram0: 64 MiB, 67108864 bytes, 131072 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram1: 64 MiB, 67108864 bytes, 131072 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram2: 64 MiB, 67108864 bytes, 131072 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram3: 64 MiB, 67108864 bytes, 131072 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram4: 64 MiB, 67108864 bytes, 131072 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram5: 64 MiB, 67108864 bytes, 131072 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram6: 64 MiB, 67108864 bytes, 131072 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram7: 64 MiB, 67108864 bytes, 131072 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram8: 64 MiB, 67108864 bytes, 131072 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram9: 64 MiB, 67108864 bytes, 131072 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram10: 64 MiB, 67108864 bytes, 131072 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram11: 64 MiB, 67108864 bytes, 131072 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram12: 64 MiB, 67108864 bytes, 131072 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram13: 64 MiB, 67108864 bytes, 131072 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram14: 64 MiB, 67108864 bytes, 131072 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram15: 64 MiB, 67108864 bytes, 131072 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/loop0: 1.3 GiB, 1433468928 bytes, 2799744 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/sda: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: 111A7812-C4EA-440D-AD62-0FE5922BA109

Device Start End Sectors Size Type
/dev/sda1 2048 1026047 1024000 500M EFI System
/dev/sda2 1026048 1288191 262144 128M Microsoft reserved
/dev/sda3 1288192 532901887 531613696 253.5G Microsoft basic data
/dev/sda4 1952602112 1953523711 921600 450M Windows recovery environment
/dev/sda5 621402112 653402111 32000000 15.3G Linux swap
/dev/sda6 653402112 1053403135 400001024 190.8G Linux filesystem
/dev/sda7 1053403136 1952602111 899198976 428.8G Linux filesystem

Partition table entries are not in disk order.




Disk /dev/sdb: 7.6 GiB, 8178892800 bytes, 15974400 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x0e0e8e70

Device Boot Start End Sectors Size Id Type
/dev/sdb1 * 0 2902111 2902112 1.4G 0 Empty
/dev/sdb2 2888004 2892739 4736 2.3M ef EFI (FAT-12/16/32)



grub2 bash mount chroot




share|improve this question


















  • 2




    Did you literally run sudo mount /dev/sd6 /mnt? That is unlikely to work. Furthermore, is it the correct / partition?
    – vidarlo
    Apr 22 at 12:49






  • 3




    Will you edit your question and add the output of this command: sudo lsblk -o name,mountpoint,label,size,fstype,uuid | egrep -v ^loop&&sudo fdisk -l
    – L. D. James
    Apr 22 at 12:51










  • @L.D.James I edited my question, please check it.
    – Mahesh
    Apr 23 at 1:44










  • What architecture are the chroot and the Ubuntu you're running for setting up the chroot?
    – muru
    Apr 23 at 1:53






  • 1




    You appear to have two Linux partitions. The largest is /dev/sda7. There's a chance that your /dev/sda6 might not be complete if it doesn't have a /bin folder. Try the commands you already performed and test /dev/sda7 as an alternative. I thought the output would show a name of your partitions and one might say something like Ubuntu OS and a different one might say DATA.
    – L. D. James
    Apr 23 at 1:56













up vote
1
down vote

favorite









up vote
1
down vote

favorite











To fix grub, I tried following codes:



sudo mount /dev/sd6 /mnt 
sudo mount --bind /dev /mnt/dev 
sudo mount --bind /dev/pts /mnt/dev/pts
sudo mount --bind /proc /mnt/proc
sudo mount --bind /sys /mnt/sys


While trying:



sudo chroot /mnt


it shows "chroot: failed to run command ‘/bin/bash’: No such file or directory" error.



Please help me fix this problem.



Thanks in advance.



The output for sudo lsblk -o name,mountpoint,label,size,fstype,uuid | egrep -v ^loop&&sudo fdisk -l is:



NAME MOUNTPOINT LABEL SIZE FSTYPE UUID
sda 931.5G 
├─sda1 ESP 500M vfat 92E7-0D79
├─sda2 128M 
├─sda3 253.5G ntfs B6B65DCCB65D8DAD
├─sda4 WINRETOOLS 450M ntfs 38F87730F876EB8E
├─sda5 [SWAP] 15.3G swap 2a3bc8d1-c30e-4475-b23e-075969c6ec10
├─sda6 190.8G ext4 05298325-c1ee-4f08-8d7c-ea39d13a6958
└─sda7 428.8G ext4 2637ce7a-0e9b-407b-9b1e-021cf3bc536a
sdb /cdrom Ubuntu 16.04 LTS amd64 7.6G iso9660 2016-04-20-22-29-52-00
├─sdb1 Ubuntu 16.04 LTS amd64 1.4G iso9660 2016-04-20-22-29-52-00
└─sdb2 Ubuntu 16.04 LTS amd64 2.3M vfat B1F5-0A13
sr0 1024M 
Disk /dev/ram0: 64 MiB, 67108864 bytes, 131072 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram1: 64 MiB, 67108864 bytes, 131072 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram2: 64 MiB, 67108864 bytes, 131072 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram3: 64 MiB, 67108864 bytes, 131072 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram4: 64 MiB, 67108864 bytes, 131072 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram5: 64 MiB, 67108864 bytes, 131072 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram6: 64 MiB, 67108864 bytes, 131072 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram7: 64 MiB, 67108864 bytes, 131072 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram8: 64 MiB, 67108864 bytes, 131072 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram9: 64 MiB, 67108864 bytes, 131072 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram10: 64 MiB, 67108864 bytes, 131072 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram11: 64 MiB, 67108864 bytes, 131072 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram12: 64 MiB, 67108864 bytes, 131072 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram13: 64 MiB, 67108864 bytes, 131072 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram14: 64 MiB, 67108864 bytes, 131072 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram15: 64 MiB, 67108864 bytes, 131072 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/loop0: 1.3 GiB, 1433468928 bytes, 2799744 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/sda: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: 111A7812-C4EA-440D-AD62-0FE5922BA109

Device Start End Sectors Size Type
/dev/sda1 2048 1026047 1024000 500M EFI System
/dev/sda2 1026048 1288191 262144 128M Microsoft reserved
/dev/sda3 1288192 532901887 531613696 253.5G Microsoft basic data
/dev/sda4 1952602112 1953523711 921600 450M Windows recovery environment
/dev/sda5 621402112 653402111 32000000 15.3G Linux swap
/dev/sda6 653402112 1053403135 400001024 190.8G Linux filesystem
/dev/sda7 1053403136 1952602111 899198976 428.8G Linux filesystem

Partition table entries are not in disk order.




Disk /dev/sdb: 7.6 GiB, 8178892800 bytes, 15974400 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x0e0e8e70

Device Boot Start End Sectors Size Id Type
/dev/sdb1 * 0 2902111 2902112 1.4G 0 Empty
/dev/sdb2 2888004 2892739 4736 2.3M ef EFI (FAT-12/16/32)



grub2 bash mount chroot




share|improve this question














To fix grub, I tried following codes:



sudo mount /dev/sd6 /mnt 
sudo mount --bind /dev /mnt/dev 
sudo mount --bind /dev/pts /mnt/dev/pts
sudo mount --bind /proc /mnt/proc
sudo mount --bind /sys /mnt/sys


While trying:



sudo chroot /mnt


it shows "chroot: failed to run command ‘/bin/bash’: No such file or directory" error.



Please help me fix this problem.



Thanks in advance.



The output for sudo lsblk -o name,mountpoint,label,size,fstype,uuid | egrep -v ^loop&&sudo fdisk -l is:



NAME MOUNTPOINT LABEL SIZE FSTYPE UUID
sda 931.5G 
├─sda1 ESP 500M vfat 92E7-0D79
├─sda2 128M 
├─sda3 253.5G ntfs B6B65DCCB65D8DAD
├─sda4 WINRETOOLS 450M ntfs 38F87730F876EB8E
├─sda5 [SWAP] 15.3G swap 2a3bc8d1-c30e-4475-b23e-075969c6ec10
├─sda6 190.8G ext4 05298325-c1ee-4f08-8d7c-ea39d13a6958
└─sda7 428.8G ext4 2637ce7a-0e9b-407b-9b1e-021cf3bc536a
sdb /cdrom Ubuntu 16.04 LTS amd64 7.6G iso9660 2016-04-20-22-29-52-00
├─sdb1 Ubuntu 16.04 LTS amd64 1.4G iso9660 2016-04-20-22-29-52-00
└─sdb2 Ubuntu 16.04 LTS amd64 2.3M vfat B1F5-0A13
sr0 1024M 
Disk /dev/ram0: 64 MiB, 67108864 bytes, 131072 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram1: 64 MiB, 67108864 bytes, 131072 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram2: 64 MiB, 67108864 bytes, 131072 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram3: 64 MiB, 67108864 bytes, 131072 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram4: 64 MiB, 67108864 bytes, 131072 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram5: 64 MiB, 67108864 bytes, 131072 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram6: 64 MiB, 67108864 bytes, 131072 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram7: 64 MiB, 67108864 bytes, 131072 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram8: 64 MiB, 67108864 bytes, 131072 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram9: 64 MiB, 67108864 bytes, 131072 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram10: 64 MiB, 67108864 bytes, 131072 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram11: 64 MiB, 67108864 bytes, 131072 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram12: 64 MiB, 67108864 bytes, 131072 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram13: 64 MiB, 67108864 bytes, 131072 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram14: 64 MiB, 67108864 bytes, 131072 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram15: 64 MiB, 67108864 bytes, 131072 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/loop0: 1.3 GiB, 1433468928 bytes, 2799744 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/sda: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: 111A7812-C4EA-440D-AD62-0FE5922BA109

Device Start End Sectors Size Type
/dev/sda1 2048 1026047 1024000 500M EFI System
/dev/sda2 1026048 1288191 262144 128M Microsoft reserved
/dev/sda3 1288192 532901887 531613696 253.5G Microsoft basic data
/dev/sda4 1952602112 1953523711 921600 450M Windows recovery environment
/dev/sda5 621402112 653402111 32000000 15.3G Linux swap
/dev/sda6 653402112 1053403135 400001024 190.8G Linux filesystem
/dev/sda7 1053403136 1952602111 899198976 428.8G Linux filesystem

Partition table entries are not in disk order.




Disk /dev/sdb: 7.6 GiB, 8178892800 bytes, 15974400 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x0e0e8e70

Device Boot Start End Sectors Size Id Type
/dev/sdb1 * 0 2902111 2902112 1.4G 0 Empty
/dev/sdb2 2888004 2892739 4736 2.3M ef EFI (FAT-12/16/32)




grub2 bash mount chroot





share|improve this question













share|improve this question




share|improve this question








edited Apr 23 at 1:52









muru

129k19272462




129k19272462










asked Apr 22 at 12:42









Mahesh

62




62







  • 2




    Did you literally run sudo mount /dev/sd6 /mnt? That is unlikely to work. Furthermore, is it the correct / partition?
    – vidarlo
    Apr 22 at 12:49






  • 3




    Will you edit your question and add the output of this command: sudo lsblk -o name,mountpoint,label,size,fstype,uuid | egrep -v ^loop&&sudo fdisk -l
    – L. D. James
    Apr 22 at 12:51










  • @L.D.James I edited my question, please check it.
    – Mahesh
    Apr 23 at 1:44










  • What architecture are the chroot and the Ubuntu you're running for setting up the chroot?
    – muru
    Apr 23 at 1:53






  • 1




    You appear to have two Linux partitions. The largest is /dev/sda7. There's a chance that your /dev/sda6 might not be complete if it doesn't have a /bin folder. Try the commands you already performed and test /dev/sda7 as an alternative. I thought the output would show a name of your partitions and one might say something like Ubuntu OS and a different one might say DATA.
    – L. D. James
    Apr 23 at 1:56













  • 2




    Did you literally run sudo mount /dev/sd6 /mnt? That is unlikely to work. Furthermore, is it the correct / partition?
    – vidarlo
    Apr 22 at 12:49






  • 3




    Will you edit your question and add the output of this command: sudo lsblk -o name,mountpoint,label,size,fstype,uuid | egrep -v ^loop&&sudo fdisk -l
    – L. D. James
    Apr 22 at 12:51










  • @L.D.James I edited my question, please check it.
    – Mahesh
    Apr 23 at 1:44










  • What architecture are the chroot and the Ubuntu you're running for setting up the chroot?
    – muru
    Apr 23 at 1:53






  • 1




    You appear to have two Linux partitions. The largest is /dev/sda7. There's a chance that your /dev/sda6 might not be complete if it doesn't have a /bin folder. Try the commands you already performed and test /dev/sda7 as an alternative. I thought the output would show a name of your partitions and one might say something like Ubuntu OS and a different one might say DATA.
    – L. D. James
    Apr 23 at 1:56








2




2




Did you literally run sudo mount /dev/sd6 /mnt? That is unlikely to work. Furthermore, is it the correct / partition?
– vidarlo
Apr 22 at 12:49




Did you literally run sudo mount /dev/sd6 /mnt? That is unlikely to work. Furthermore, is it the correct / partition?
– vidarlo
Apr 22 at 12:49




3




3




Will you edit your question and add the output of this command: sudo lsblk -o name,mountpoint,label,size,fstype,uuid | egrep -v ^loop&&sudo fdisk -l
– L. D. James
Apr 22 at 12:51




Will you edit your question and add the output of this command: sudo lsblk -o name,mountpoint,label,size,fstype,uuid | egrep -v ^loop&&sudo fdisk -l
– L. D. James
Apr 22 at 12:51












@L.D.James I edited my question, please check it.
– Mahesh
Apr 23 at 1:44




@L.D.James I edited my question, please check it.
– Mahesh
Apr 23 at 1:44












What architecture are the chroot and the Ubuntu you're running for setting up the chroot?
– muru
Apr 23 at 1:53




What architecture are the chroot and the Ubuntu you're running for setting up the chroot?
– muru
Apr 23 at 1:53




1




1




You appear to have two Linux partitions. The largest is /dev/sda7. There's a chance that your /dev/sda6 might not be complete if it doesn't have a /bin folder. Try the commands you already performed and test /dev/sda7 as an alternative. I thought the output would show a name of your partitions and one might say something like Ubuntu OS and a different one might say DATA.
– L. D. James
Apr 23 at 1:56





You appear to have two Linux partitions. The largest is /dev/sda7. There's a chance that your /dev/sda6 might not be complete if it doesn't have a /bin folder. Try the commands you already performed and test /dev/sda7 as an alternative. I thought the output would show a name of your partitions and one might say something like Ubuntu OS and a different one might say DATA.
– L. D. James
Apr 23 at 1:56
















active

oldest

votes











Your Answer







StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "89"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);

else
createEditor();

);

function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
convertImagesToLinks: true,
noModals: false,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);



);













 

draft saved


draft discarded


















StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1027190%2fchroot-failed-to-run-command-bin-bash-no-such-file-or-directory%23new-answer', 'question_page');

);

Post as a guest






















active

oldest

votes













active

oldest

votes









active

oldest

votes






active

oldest

votes















 

draft saved


draft discarded















































 


draft saved


draft discarded














StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1027190%2fchroot-failed-to-run-command-bin-bash-no-such-file-or-directory%23new-answer', 'question_page');

);

Post as a guest
































































-

Popular posts from this blog

How do so many people here on Academia.SE, and in general, afford lavish higher education programs?

Image
Clash Royale CLAN TAG #URR8PPP up vote 45 down vote favorite 7 I graduated last year with a BS in Computer Science. I do not come from a particularly wealthy family, (very low middle class), and was only able to afford my education via school loans/scholarships and working low-wage jobs, with no support from my family or anyone else. I realize some scholarship/loan programs extend into grad school. But I don't think those cover all costs. Now I'm lucky enough to have a decent-paying salary in industry, along with benefits and living on my own, and I'm thinking one day (sooner rather than later) I'd like to try my hand at research or continue my degree, but these things cost money, in addition to my regular living expenses. I read posts here often about academic people being in positions of choosing between these crazy research grad programs, some in Japan, or Ireland (while they currently live in the U.S./U.K.) then moving around between countries/universit...
Read more

Trouble downloading packages list due to a “Hash sum mismatch” error

Image
Clash Royale CLAN TAG #URR8PPP .everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty margin-bottom:0; up vote 331 down vote favorite 117 When I check for updates, I get a "Failed To Download Repository Information" error. This is what comes up under details: W: Failed to fetch gzip:/var/lib/apt/lists/partial/us.archive.ubuntu.com_ubuntu_dists_natty_main_source_Sources Hash Sum mismatch, E: Some index files failed to download. They have been ignored, or old ones used instead. apt share | improve this question edited Nov 12 '14 at 23:37 Braiam 49.5k 19 130 210 asked May 9 '11 at 20:55 Rob 5,300 10 26 40 add a comment  |  up vote 331 down vote favorite 117 When I check for updates, I get a "Failed To Download Repository Information" error. This is what comes up under details: W: Failed to fetch gzip:/var/lib/apt/lists/partial/us.archive.ubuntu.com_ubuntu_dists_nat...
Read more

How do I move numbers in filenames, in a batch renaming operation?

Image
Clash Royale CLAN TAG #URR8PPP up vote 10 down vote favorite 1 I have been trying to figure out how to rename files for the past few hours. I have 2000 files that are like this: file.1.pdb file.2.pdb file.3.pdb I would like to rename these files to something like: file.pdb.1 file.pdb.2 file.pdb.3 command-line batch-rename share | improve this question edited Mar 29 at 21:36 Eliah Kagan 79.6k 20 222 359 asked Mar 29 at 15:33 user812758 51 3 Didn't you mean bash ? – avazula Mar 29 at 15:38 4 @avazula No please read this article : en.wikipedia.org/wiki/Batch_renaming – Ali Razmdideh Mar 29 at 15:47 @PerlDuck yes ;) – Ali Razmdideh Mar 29 at 15:52 6 Possible duplicate of How to easily rename files using command line? – wjandrea Mar 29 at 16:09 2 Hey close voters...
Read more