Help Mounting A CD-R/DVD-R, Then Using Dd To Write To Them.

I can't seem to mount a CD-R or DVD-R, doesn't matter if it is blank or not.
However, when I use a program such as Brasero, I am able to write to them. I cannot use dd to write to them.

This is the output of trying to mount/unmount.
Code:
root@delarocha-> mount /dev/sr0 /media/cd
mount: /dev/sr0 is write-protected, mounting read-only
mount: wrong fs type, bad option, bad superblock on /dev/sr0,
       missing codepage or helper program, or other error
       In some cases useful info is found in syslog - try
       dmesg | tail or so.

root@delarocha-> umount /dev/sr0
umount: /dev/sr0: not mounted
root@delarocha-> umount /media/cd
umount: /media/cd: not mounted
root@delarocha-> umount /media/cdrom
umount: /media/cdrom: not mounted

dmesg | tail
Code:
root@delarocha-> dmesg | tail
[ 1536.299777] sr 1:0:0:0: [sr0]  
[ 1536.299804] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[ 1536.299809] sr 1:0:0:0: [sr0]  
[ 1536.299814] Sense Key : Illegal Request [current] 
[ 1536.299820] sr 1:0:0:0: [sr0]  
[ 1536.299824] Add. Sense: Logical block address out of range
[ 1536.299829] sr 1:0:0:0: [sr0] CDB: 
[ 1536.299832] Read(10): 28 00 00 00 00 00 00 00 01 00
[ 1536.299846] end_request: I/O error, dev sr0, sector 0
[ 1536.299915] EXT4-fs (sr0): unable to read superblock

I don't think it can be anything wrong with the disk, since it is a untouched disk.
Note: The results of everything(apart from dmesg I would assume), are the same for a CD-R and DVD-R

This is what I get while trying to dd a .iso and .mp4, respectively.

Code:
web@delarocha-> dd if=/dev/sr0 of=~/Downloads/xubuntu-14.04.1-desktop-amd64.iso
0+0 records in
0+0 records out
0 bytes (0 B) copied, 0.000377316 s, 0.0 kB/s

Code:
web@delarocha-> dd if=/dev/sr0 of=~/Videos/The\ Hobbit/The\ Hobbit\ The\ Desolation\ of\ Smaug.mp4
0+0 records in
0+0 records out
0 bytes (0 B) copied, 0.000377179 s, 0.0 kB/s

uname -a
Code:
Linux delarocha 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt2-1 (2014-12-08) x86_64 GNU/Linux

When I used lsblk when I close the disk tray, it shows it mounted.
Code:
sr0                     11:0    1     2K  0 rom

But after I use the dd command to write the .iso, it disappears.

Here is my /etc/fstab
Code:
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point>   <type>  <options>       <dump>  <pass>
/dev/mapper/delarocha-root /               ext4    errors=remount-ro 0       1
# /boot was on /dev/sda1 during installation
UUID=5bbedec0-6e3d-4185-91e0-292a72585908 /boot           ext2    defaults        0       2
/dev/mapper/delarocha-swap_1 none            swap    sw              0       0
/dev/sr0        /media/cdrom0   udf,iso9660 user,noauto     0       0
/dev/sdb1       /media/usb0     auto    rw,user,noauto  0       0

I have also tried replacing /dev/sr0 in the above commands with /media/cdrom0.


Similar Content



Recovering After Windows 7 Install: Rescue Cannot Mount Root

I have a dual boot laptop with debian stable & Windows 7.

The HD partitions a
sda1: NTFS for W7
sda2: FAT32 (currently unused)
sda3: linux /boot
sda4: linux ext4, which is LVM with encryption

I've re-installed W7 and now need to recover the MBR & grub menu.

I've booted with the netinst usb in rescue mode, but it fails to mount the root partition /sda4:
"An error occured while mounting the device you entered for your root file system (/dev/sda4) on /target"

and /var/syslog shows:
Code:
rescue-mode: selected root device '/dev/sda4'
umount: cant umount /target: Invalid argument
isofs_fill_super: bread failed, dev=sda4, iso_blknum=16, block=32
EXT2-fs (sda4): error: unable to readsuperblock
EXT3-fs (sda4): error: unable to readsuperblock
rescue: mount: mounting /dev/sda4 on /target failed: Invalid argument

So it seems like something is wrong with the mount command?

Would appreciate suggestions how to solve this.

Thanks

Problem With NFS Sharing Between Two Raspberry Pis

I have two raspberrys, one running OSMC and another running raspbian. The first one has two 1TB hard drives plugged in through a powered usb hub. I want to access to the osmc hard drives from the one running raspbian. They are both in the same local network, the osmc one has the ip 192.168.1.24 and the raspbian one has 192.168.1.28. Both are static ips.

These are the hard drives::
Code:
osmc@osmc:~$ ls /media/ -la
total 36
drwxr-xr-x  4 root root  4096 Mar 31 18:28 .
drwxr-xr-x 23 root root  4096 Mar 15 13:35 ..
drwx------  1 osmc osmc  8192 Mar 30 21:54 ELEMENTS
-rw-r--r--  1 root root   232 Mar  6 13:34 README
drwx------  1 osmc osmc 16384 Mar 30 15:22 TOURO

ELEMENTS and TOURO, two ntfs hard drives that work just fine.

I tried sharing the first one through nfs with the following config (i copied the parameters from a tutorial):
Code:
osmc@osmc:~$ cat /etc/exports
# /etc/exports: the access control list for filesystems which may be exported
#               to NFS clients.  See exports(5).
#
# Example for NFSv2 and NFSv3:
# /srv/homes       hostname1(rw,sync,no_subtree_check) hostname2(ro,sync,no_subtree_check)
#
# Example for NFSv4:
# /srv/nfs4        gss/krb5i(rw,sync,fsid=0,crossmnt,no_subtree_check)
# /srv/nfs4/homes  gss/krb5i(rw,sync,no_subtree_check)
#
/media/ELEMENTS/Pelis/ 192.168.1.0/24(rw,subtree_check,insecure,no_root_squash)
/media/TOURO/Series/ 192.168.1.0/24(rw,subtree_check,insecure,no_root_squash)

and from the pi running raspbian I have confirmed that I can see the drives being shared:
Code:
 /media $ showmount -e 192.168.1.24
Export list for 192.168.1.24:
/media/TOURO/Series/   192.168.1.0/24
/media/ELEMENTS/Pelis/ 192.168.1.0/24

Now, when I try to mount them, all works fine, but when I ls the folders nothing cames back. This is my fstab:
Code:
1cat /etc/fstab
proc            /proc           proc    defaults          0       0
/dev/mmcblk0p1  /boot           vfat    defaults          0       2
/dev/mmcblk0p2  /               ext4    defaults,noatime  0       1
# a swapfile is not a swap partition, so no using swapon|off from here on, use  dphys-swapfile swap[on|off]  for that
UUID=fdff96e6-816c-d001-e05f-96e6816cd001 /media/hdd/ auto defaults,user 0 0 #external hdd

192.168.1.24:/media/ELEMENTS/Pelis /media/pelis nfs rsize=8192,wsize=8192,timeo=14,intr
192.168.1.24:/media/TOURO/Series /media/series nfs rsize=8192,wsize=8192,timeo=14,intr

Code:
apoc@raspbian ~ $ ls /media/pelis/
apoc@raspbian ~ $

The superweird thing is that they are mounted, as they show up if I run "df -h"

Code:
 df -h
S.ficheros                         Tamaño Usados  Disp Uso% Montado en
rootfs                               7,2G   2,6G  4,4G  37% /
/dev/root                            7,2G   2,6G  4,4G  37% /
devtmpfs                             484M      0  484M   0% /dev
tmpfs                                 98M   380K   98M   1% /run
tmpfs                                5,0M      0  5,0M   0% /run/lock
tmpfs                                195M      0  195M   0% /run/shm
/dev/mmcblk0p1                        56M    15M   42M  26% /boot
/dev/sda1                            219G   4,7G  202G   3% /media/hdd
192.168.1.24:/media/ELEMENTS/Pelis   932G   742G  191G  80% /media/pelis
192.168.1.24:/media/TOURO/Series     932G   813G  120G  88% /media/series

Code:
ls /media/ -la
total 808
drwxr-xr-x  5 root root   4096 abr  2 18:36 .
drwxr-xr-x 22 root root   4096 mar 25 16:14 ..
drwxr-xr-x  5 apoc apoc   4096 abr  2 13:12 hdd
drwx------  1 apoc pi   786432 mar 30 22:03 pelis
drwx------  1 apoc pi    28672 mar 29 16:09 series

Note that the group for the two folders is "pi", but if I umount the drives it becomes "apoc" (my nick and my personal group).
Code:
ls /media/ -la
total 20
drwxr-xr-x  5 root root 4096 abr  2 18:36 .
drwxr-xr-x 22 root root 4096 mar 25 16:14 ..
drwxr-xr-x  5 apoc apoc 4096 abr  2 13:12 hdd
drwxr-xr-x  2 apoc apoc 4096 abr  2 18:36 pelis
drwxr-xr-x  2 apoc apoc 4096 abr  2 18:36 series

Both users ("osmc" in the osmc pi and "apoc" in the raspbian one) have the same uid: 1000.

What am i doing wrong?

Problems With Mounting Drive At Boot

Hi,

I have problems mounting my second drive at boot automatically.
(sorry i am a noob)

When i use the mount command, it works fine.
Code:
mount -t ext3 /dev/sdb2 /mnt/HD/HD_b2

But when i try to add one if the following lines to /etc/fstab
It will not mount the drive at boot or with Code:
mount -a

, also fstab is empty afer reboot (normal??)

Code:
/dev/sdb2 /mnt/HD/HD_b2 ext3 defaults,errors=remount-ro 0 1

Code:
UUID=553afede-fa45-4cdc-9972-c0a9aa899509 /mnt/HD/HD_b2 ext3 errors=remount-ro 0 1

Code:
/dev/sdb2 /mnt/HD/HD_b2 ext3 rw 0 0

Code:
/dev/sdb2 /mnt/HD/HD_b2 ext3 defaults 0 1

output blkid:

Code:
/dev/sda1: UUID="e67e5c15-7b8b-9389-c311-e5d4c61326f9" TYPE="linux_raid_member"
/dev/sda2: UUID="09e0e365-0aa6-4214-b571-2bc6b027fd9f" TYPE="ext3"
/dev/sda4: UUID="64038414-136c-4939-bd14-9871a20290bd" TYPE="ext3"
/dev/sdb1: UUID="e67e5c15-7b8b-9389-c311-e5d4c61326f9" TYPE="linux_raid_member"
/dev/sdb2: UUID="553afede-fa45-4cdc-9972-c0a9aa899509" TYPE="ext3"
/dev/sdb4: UUID="bf594be6-ffb6-469d-a3a8-246be66a4d90" TYPE="ext2"

/etc/mtab:

Code:
rootfs / rootfs rw 0 0
/dev/root / ext2 rw,relatime,errors=continue 0 0
sysfs /sys sysfs rw,relatime 0 0
proc /proc proc rw,relatime 0 0
squash /usr/local/tmp ramfs rw,relatime,size=38m 0 0
/dev/loop0 /usr/local/modules squashfs ro,relatime 0 0
/dev/mtdblock5 /usr/local/config jffs2 rw,relatime 0 0
/dev/sda4 /mnt/HD_a4 ext3 rw,relatime,errors=continue,data=writeback 0 0
/dev/sdb4 /mnt/HD_b4 ext2 rw,relatime,errors=continue 0 0
none /proc/bus/usb usbfs rw,relatime 0 0
/dev/sda2 /mnt/HD/HD_a2 ext3 rw,relatime,errors=continue,user_xattr,data=writeb$
/dev/sdb2 /mnt/HD/HD_b2 ext3 rw,relatime,errors=continue,user_xattr,data=writeb$
/dev/sda2 /mnt/HD/HD_a2/squeeze/mnt/HD/HD_a2 ext3 rw,relatime,errors=continue,u$
/dev/root /mnt/HD/HD_a2/squeeze/mnt/root ext2 rw,relatime,errors=continue 0 0
/dev/root /mnt/HD/HD_a2/squeeze/dev ext2 rw,relatime,errors=continue 0 0
sysfs /mnt/HD/HD_a2/squeeze/sys sysfs rw,relatime 0 0
proc /mnt/HD/HD_a2/squeeze/proc proc rw,relatime 0 0

When mount command is used Code:
mount -t ext3 /dev/sdb2 /mnt/HD/HD_b2

The following line is added to mstab -->
Code:
/dev/sdb2 /mnt/HD/HD_b2 ext3 rw 0 0

I diont know what i am doing wrong, mount for HD_a2 works fine (other disk, worked at default), i hav e NAS DNS-325 where i installed Debian on. I used this tutorial to install debian.

The strange thing is, i had to reinstall my NAS, and befor it worked fine after i had installed debian 2 years ago, i just dont remeber how i fixed this.

Mounting A USB For Vbox

I am installing VirtualBox on Centos per http://www.digitesters.com/centos-in...adless-system/, and I don't understand the very end. Seems like Line 5 is not needed as it is already done on Line 4, right?

Code:
# mkdir /data/virtual_machines/vbox/vbusbfs
# chown vboxuser.vboxusers /data/virtual_machines/vbox/vbusbfs
# chmod 775 /data/virtual_machines/vbox/vbusbfs
# echo "none /data/virtual_machines/vbox/vbusbfs usbfs rw,devgid=$(awk -F : '/vboxusers/ {print $3}' /etc/group),devmode=664 0 0" >> /etc/fstab
# echo "none /data/virtual_machines/vbox/vbusbfs usbfs rw,devgid=$(awk -F : '/vboxusers/ {print $3}' /etc/group),devmode=664 0 0" >> /etc/fstab
# mount -a

I executed the above script (except didn't execute Line 5, and my user:group is vbox:vbox and not vboxuser.vboxusers, and the folder is at /home/vbox and not /data/virtual_machines/vbox), and the following was added to /etc/fstab. Please explain what Line 4 did and what the below line in my fstab file means.
Code:
none /home/vbox/vbusbfs usbfs rw,devgid=496
504,devmode=664 0 0

I then executed mount -a, and got the following response. The part about /var/www/main/ayb_resources and /var/www/main/ayb_cache does not exist is probably some old stuff which I can get rid of, but I am particularly interested in "mount point 0 does not exist" as it seems to be related to the above.

Code:
[root@devserver vbox]# mount -a
mount: special device /var/www/main/ayb_resources does not exist
mount: special device /var/www/main/ayb_cache does not exist
mount: mount point 0 does not exist
[root@devserver vbox]#

My total fstab file is as follows:

Code:
[root@devserver vbox]# cat /etc/fstab
#
# /etc/fstab
# Created by anaconda on Sat Apr 19 05:57:56 2014
#
# Accessible filesystems, by reference, are maintained under '/dev/disk'
# See man pages fstab(5), findfs(8), mount(8) and/or blkid(8) for more info
#
/dev/mapper/VolGroup-lv_root /                       ext4    defaults        1 1
UUID=xxx-xxx-xxx-xxx-xxx /boot                   ext4    defaults        1 2
/dev/mapper/VolGroup-lv_home  /home                  ext4    defaults        1 2
/dev/mapper/VolGroup-lv_mysql /var/lib/mysql         ext3    barrier=0       1 2
/dev/mapper/VolGroup-lv_swap swap                    swap    defaults        0 0
tmpfs                   /dev/shm                tmpfs   defaults        0 0
devpts                  /dev/pts                devpts  gid=5,mode=620  0 0
sysfs                   /sys                    sysfs   defaults        0 0
proc                    /proc                   proc    defaults        0 0
/home/public/lib /var/www/main_lib/ayb_application/lib none bind
/var/www/main/html /var/www/main_lib/html none bind
/var/www/main/ayb_resources /var/www/main_lib/ayb_resources none bind
/var/www/main/ayb_cache /var/www/main_lib/ayb_cache none bind
none /home/vbox/vbusbfs usbfs rw,devgid=496
504,devmode=664 0 0
[root@devserver vbox]# mount -a
mount: special device /var/www/main/ayb_resources does not exist
mount: special device /var/www/main/ayb_cache does not exist
mount: mount point 0 does not exist
[root@devserver vbox]#

Extended Partition Error On Boot

Did you find any way to get out with this error ? I've got the same with an extended partition...
Code:
# fdisk /dev/sda

Welcome to fdisk (util-linux 2.25.2).
Changes will remain in memory only, until you decide to write them.
Be careful before using the write command.

Command (m for help): p
Disk /dev/sda: 55,9 GiB, 60022480896 bytes, 117231408 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: 0x00015c35

Device     Boot    Start       End  Sectors  Size Id Type
/dev/sda1  *        2048  19531775 19529728  9,3G 83 Linux
/dev/sda2       19533822 117229567 97695746 46,6G  5 Extended
/dev/sda5       19533824  23558143  4024320  1,9G 82 Linux swap / Solaris
/dev/sda6       23560192 117229567 93669376 44,7G 83 Linux

Code:
# dmesg|less
[   84.343741] EXT4-fs (sda2): unable to read superblock
[   84.348074] EXT4-fs (sda2): unable to read superblock
[   84.352391] EXT4-fs (sda2): unable to read superblock
[   84.357159] XFS (sda2): Invalid superblock magic number
[   84.373676] FAT-fs (sda2): utf8 is not a recommended IO charset for FAT filesystems, filesystem will be case sensitive!
[   84.373891] FAT-fs (sda2): bogus logical sector size 65535
[   84.373897] FAT-fs (sda2): Can't find a valid FAT filesystem
[   84.378220] FAT-fs (sda2): utf8 is not a recommended IO charset for FAT filesystems, filesystem will be case sensitive!
[   84.378444] FAT-fs (sda2): bogus logical sector size 65535
[   84.378449] FAT-fs (sda2): Can't find a valid FAT filesystem
[   84.386262] ntfs: (device sda2): is_boot_sector_ntfs(): Invalid boot sector checksum.
[   84.386270] ntfs: (device sda2): read_ntfs_boot_sector(): Primary boot sector is invalid.
[   84.386275] ntfs: (device sda2): read_ntfs_boot_sector(): Mount option errors=recover not used. Aborting without trying to recover.
[   84.386279] ntfs: (device sda2): ntfs_fill_super(): Not an NTFS volume.
[   84.390737] MINIX-fs: unable to read superblock
[   84.395176] attempt to access beyond end of device
[   84.395185] sda2: rw=16, want=3, limit=2
[   84.395191] hfsplus: unable to find HFS+ superblock
[   84.404204] qnx4: no qnx4 filesystem (no root dir).
[   84.408959] You didn't specify the type of your ufs filesystem

mount -t ufs -o ufstype=sun|sunx86|44bsd|ufs2|5xbsd|old|hp|nextstep|nextstep-cd|openstep ...

>>>WARNING<<< Wrong ufstype may corrupt your filesystem, default is ufstype=old
[   84.417367] hfs: can't find a HFS filesystem on dev sda2

Write Permissions To External Drive

I have an external disk but I can only write to it using sudo, not as my normal user.

The commands I've issued a
Code:
sudo mkdir /media/USBSSD
sudo mount -t auto /dev/sda1 /media/USBSSD
sudo chmod 777 /media/USBSSD
sudo mkdir /media/USBSSD/share

How can I set it up so that other users can write to it?

Trying To Dd A Server With LVM To Another Ext HD, Then To Another Server

I have Linux enterprise server 11 sp3 with 3 250 GB WD blue drives in a raid 5 configuration.

Server “A” (external drive not plugged in):
Code:
Disk /dev/sda: 499.0 GB, 499021512704 bytes
255 heads, 63 sectors/track, 60669 cylinders, total 974651392 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 identifier: 0x00059fd2

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1   *        2048     1028095      513024   83  Linux
/dev/sda2         1028096    21993471    10482688   82  Linux swap / Solaris
/dev/sda3        21993472   974651391   476328960   8e  Linux LVM

Disk /dev/mapper/VG_SYSTEM-ROOT: 487.8 GB, 487755612160 bytes
255 heads, 63 sectors/track, 59299 cylinders, total 952647680 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 identifier: 0x00000000

Disk /dev/mapper/VG_SYSTEM-ROOT doesn't contain a valid partition table

I am trying to clone this machine to another server, both servers are Dell Poweredge 1900, with 3 – 250 WD drives (the only difference is the ‘B’ server has WD Cavier drives), pretty much identical machines, same processor and ram. I have a 2TB ext hard drive that I am using to store the output of DD. I have booted from the CD to a rescue system, then mounted my 2TB ext and did the following:
Code:
    # dd if=/dev/sda conv=sync,noerror bs=64k | gzip –c | split –a3 –b 2G –verbose - /mnt/exthd/

This gives me the following files on my external hard drive:
Code:
    
-rwxr-xr-x 1 root root 2147483648 Jan 10 21:00 aaa
-rwxr-xr-x 1 root root 2147483648 Jan 10 21:31 aab
-rwxr-xr-x 1 root root 2147483648 Jan 10 21:53 aac
-rwxr-xr-x 1 root root 2147483648 Jan 10 22:05 aad
-rwxr-xr-x 1 root root 2147483648 Jan 10 22:10 aae
-rwxr-xr-x 1 root root 2147483648 Jan 10 22:17 aaf
-rwxr-xr-x 1 root root 2147483648 Jan 10 22:24 aag
-rwxr-xr-x 1 root root 2147483648 Jan 10 22:31 aah
-rwxr-xr-x 1 root root 2147483648 Jan 10 22:37 aai
-rwxr-xr-x 1 root root 2147483648 Jan 10 22:43 aaj
-rwxr-xr-x 1 root root 2147483648 Jan 10 22:50 aak
-rwxr-xr-x 1 root root 2147483648 Jan 10 22:56 aal
-rwxr-xr-x 1 root root 2147483648 Jan 10 23:02 aam
-rwxr-xr-x 1 root root 2147483648 Jan 10 23:06 aan
-rwxr-xr-x 1 root root 2147483648 Jan 10 23:12 aao
-rwxr-xr-x 1 root root 2147483648 Jan 10 23:32 aap
-rwxr-xr-x 1 root root  324998512 Jan 10 23:35 aaq

Now, I boot to the rescue system on server ‘B’ with the external drive plugged in, and run fdisk:
Code:
Disk /dev/sda: 498.8 GB, 498753077248 bytes
255 heads, 63 sectors/track, 60636 cylinders, total 974127104 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 identifier: 0x00059fd2

   Device Boot      Start         End      Blocks   Id  System

Disk /dev/sdb: 2000.4 GB, 2000398933504 bytes
255 heads, 63 sectors/track, 243201 cylinders, total 3907029167 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 identifier: 0x00015a3d

   Device Boot      Start         End      Blocks   Id  System
/dev/sdb1            2048  3907028991  1953513472    c  W95 FAT32 (LBA)

Notice sda is only 498.8GB where on server ’A’, it was 499.0. when I try to restore my files from the DD, I get an out of space error. To restore, I use the following:
Code:
    # cat /mnt/exthd/aa* | gunzip –c | dd of=/dev/sda
    
dd: writing to ‘/dev/sda’:  No space left on device
974127105+0 records in
974127104+0 records out
498753077248 bytes (499 GB) copied, 37067.3 s, 13.5MB/s

My guess, is that although the drives are the same capacity (3 – 250GB in RAID 5 array), the number of cylinders is different because it is a different model, and that is where it is running out of space, although I wouldn’t think it would.

Please correct me if I am wrong as I am a newbie, but if I do “# dd if=/dev/sda” that will take all the partitions with it? Such as sda1, sda2, sda3 correct?

UEFI Vs Debian - Cannot Boot Into Grub After Installation

The installation of the latest stable on my Lenovo G505s went just fine in UEFI mode but when the installation finished I never reach grub during the bootup process. I put Refind media onto a usb stick and boot into my computer using it after that I tried to follow this guide https://wiki.debian.org/GrubEFIReinstall but I'm having some trouble.

When I start the computer with the "Refind media" it gives me 3 options where the first is

"Boot EFI\debian\grubx64.efi from 510 Mib Fat Volume" If I choose this option it takes me to grub via eufi(?) and then I can get into my computer as usual.

How can I make my computer understand that it should recognize and boot from EFI\debian\grubx64.efi, 510 Mib Fat Volume?

I found https://wiki.debian.org/EFIStub and since my
/boot/efi/EFI/debian looks like; grubx64.efi initrd.img-3.16.0-4-amd64 vmlinuz-3.16.0-4-amd64
I tried the following
Code:
# efibootmgr -c -g -L "Debian (EFI stub)" -l '\EFI\debian\grubx64.efi' -u 'root=UUID=$UUID ro quiet rootfstype=ext4 add_efi_memmap initrd=\\EFI\\debian\\initrd.img-3.16.0-4-amd-64'
efibootmgr: Could not set variable Boot0005: No such file or directory
efibootmgr: Could not prepare boot variable: No such file or directory

Code:
    [ -d /sys/firmware/efi ] && echo "EFI boot on HDD" || echo "Legacy boot on HDD"
    EFI boot on HDD


     apt-get install --reinstall grub-efi

went just fine and I have /dev/sda1 mounted on /boot/efi
but when I try grub-install I get

Code:
grub-install /dev/sda
Installing for x86_64-efi platform.
efibootmgr: Could not set variable Boot0005: No such file or directory
efibootmgr: Could not prepare boot variable: No such file or directory
Installation finished. No error reported.

What is going wrong here?

Code:
    update-grub
    Generating grub configuration file ...
    Found background image: .background_cache.png
    Found linux image: /boot/vmlinuz-3.16.0-4-amd64
    Found initrd image: /boot/initrd.img-3.16.0-4-amd64
    Adding boot menu entry for EFI firmware configuration
    done

Code:
file /boot/efi/EFI/debian/grubx64.efi
/boot/efi/EFI/debian/grubx64.efi: PE32+ executable (EFI application) x86-64 (stripped to external PDB), for MS Windows

but efibootmgr --verbose | grep debian gives me nothing. If I run efibootmgr without grep I get:

Code:
    efibootmgr --verbose
    BootCurrent: 0002
    Timeout: 0 seconds
    BootOrder: 2001,0003,0004,0001,0000,2002,2003
    Boot0000* USB HDD     : SanDisk U3 Cruzer Micro    BIOS(2,500,00)..................3.......1...5........................................
    Boot0001* USB ODD     : SanDisk U3 Cruzer Micro    BIOS(3,500,00)..................;.......9...=........................................
    Boot0002* EFI USB Device   ACPI(a0341d0,0)PCI(10,0)USB(2,0)0311050000HD(1,800,2d5f,55fc859c-5227-4cd5-bd64-a4fd678ba8b6)RC
    Boot0003* SATA HDD    : ST1000LM014-1EJ164                         BIOS(2,0,00).......................................................................
    Boot0004* SATA ODD    : MATSHITADVD-RAM UJ8C2                      BIOS(3,0,00).......................................................................
    Boot2001* EFI USB Device   RC
    Boot2002* EFI DVD/CDROM   RC
    Boot2003* EFI Network   RC

Here is some additonial information which might be relevant.

Code:
    # df -h
    Filesystem                 Size  Used Avail Use% Mounted on
    /dev/dm-1                  9.1G  2.5G  6.2G  29% /
    udev                        10M     0   10M   0% /dev
    tmpfs                      1.4G  9.1M  1.4G   1% /run
    tmpfs                      3.5G   68K  3.5G   1% /dev/shm
    tmpfs                      5.0M  4.0K  5.0M   1% /run/lock
    tmpfs                      3.5G     0  3.5G   0% /sys/fs/cgroup
    /dev/sda2                  237M   35M  190M  16% /boot
    /dev/sda1                  511M  132K  511M   1% /boot/efi
    /dev/mapper/ludo--vg-home  893G  103M  848G   1% /home
    tmpfs                      713M  4.0K  713M   1% /run/user/117
    tmpfs                      713M  8.0K  713M   1% /run/user/1000

Code:
fdisk -l

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: 0080BBEA-1B46-4EAE-9471-CC523BFCAD44

Device       Start        End    Sectors   Size Type
/dev/sda1     2048    1050623    1048576   512M EFI System
/dev/sda2  1050624    1550335     499712   244M Linux filesystem
/dev/sda3  1550336 1953523711 1951973376 930.8G Linux filesystem

GPT PMBR size mismatch (13695 != 2009726) will be corrected by w(rite).

Disk /dev/sdb: 981.3 MiB, 1028980224 bytes, 2009727 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: gpt
Disk identifier: E4A93BB9-2F9C-4487-B090-91B620879E4C

Device     Start   End Sectors  Size Type
/dev/sdb1   2048 13662   11615  5.7M EFI System

Disk /dev/mapper/sda3_crypt: 930.8 GiB, 999408271360 bytes, 1951969280 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/mapper/ludo--vg-root: 9.3 GiB, 9999220736 bytes, 19529728 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/mapper/ludo--vg-swap_1: 14.4 GiB, 15439233024 bytes, 30154752 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/mapper/ludo--vg-home: 907.1 GiB, 973967720448 bytes, 1902280704 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

Virtual CentOS 6.4 Server Expand Disk For Splunk Instance

As I'm sure there are other posts for this, I'm terrified to mess with disks in Linux as I'm very green. I've looked at one other post which suggests to run the following so I'm going to do the same. The drive provisioned originally had 400 gb, but currently has 500 gb allocated in vmware. Thanks so much in advance!

Code:
fdisk -l
pvs
vgs
lvs
df -h


Code:
[root@uspk10splunk ~]# fdisk -l

Disk /dev/sda: 8589 MB, 8589934592 bytes
64 heads, 32 sectors/track, 8192 cylinders
Units = cylinders of 2048 * 512 = 1048576 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x000c255c

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1   *           2         501      512000   83  Linux
Partition 1 does not end on cylinder boundary.
/dev/sda2             502        8192     7875584   8e  Linux LVM
Partition 2 does not end on cylinder boundary.

Disk /dev/sdb: 536.9 GB, 536870912000 bytes
255 heads, 63 sectors/track, 65270 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x69437664

   Device Boot      Start         End      Blocks   Id  System
/dev/sdb1               1       52216   419424988+  8e  Linux LVM

Disk /dev/mapper/vg_uspk10vsp03-lv_root: 3833 MB, 3833593856 bytes
255 heads, 63 sectors/track, 466 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000


Disk /dev/mapper/vg_uspk10vsp03-lv_swap: 4227 MB, 4227858432 bytes
255 heads, 63 sectors/track, 514 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000


Disk /dev/mapper/vg_opt-lv_opt: 429.5 GB, 429488340992 bytes
255 heads, 63 sectors/track, 52215 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000

Code:
[root@uspk10splunk ~]# pvs
  PV         VG             Fmt  Attr PSize   PFree
  /dev/sda2  vg_uspk10vsp03 lvm2 a--    7.51g    0
  /dev/sdb1  vg_opt         lvm2 a--  399.99g    0

Code:
[root@uspk10splunk ~]# vgs
  VG             #PV #LV #SN Attr   VSize   VFree
  vg_opt           1   1   0 wz--n- 399.99g    0
  vg_uspk10vsp03   1   2   0 wz--n-   7.51g    0

Code:
[root@uspk10splunk ~]# lvs
  LV      VG             Attr      LSize   Pool Origin Data%  Move Log Cpy%Sync                     Convert
  lv_opt  vg_opt         -wi-ao--- 399.99g                                                          
  lv_root vg_uspk10vsp03 -wi-ao---   3.57g                                                          
  lv_swap vg_uspk10vsp03 -wi-ao---   3.94g

Code:
[root@uspk10splunk ~]# df -h
Filesystem            Size  Used Avail Use% Mounted on
/dev/mapper/vg_uspk10vsp03-lv_root
                      3.6G  1.5G  1.9G  45% /
tmpfs                 1.9G     0  1.9G   0% /dev/shm
/dev/mapper/vg_opt-lv_opt
                      394G  374G  422M 100% /opt
/dev/sda1             485M   32M  428M   7% /boot

Eth0:no IPv6 Routers Present

When I try to open my filesystem I get the following error message:

Unable to mount 496GB filesystem error mounting:mount:wrong fs type, bad option,bad superblock on /dev/sdb2, missing codepage or helper program, or other error. In some cases useful info is found in syslog - try dmesg | tail or so. What does all this mean? Everything had worked so far until now. I'm using Debian V 7.8.0

Thanks for any help I can get

Gary