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.
Not entirely new to Linux but this is likely a newbie question for most of you other gurus out there. I have a 3TB USB drive for which I had used gparted and changed it to GPT and then had formated it ext4. I had gone through the work of finding out how to properly align it however the command that I used slips my mind right now. I know that I did properly align it when I used gparted. That being said, I used blkid to find the UUID of the volume and added a line to /etc/fstab to mount it on startup. Everything was working great. I had an issue that I had to reboot the machine for and I got a failure with fsck trying to check that volume (I had put a 2 in the 6th field of the fstab which I probably should have put a 0) so I got the system booted by appending fastboot to the grub line so it wouldn't try to check the volume. I edited /etc/fstab and changed the 2 to a 0 and now the system boots.
All that to say that when the system boots it will not mount the volume. /dev/sda1 does not exist in the /dev directory and looking at dmesg I'm seeing sda: unknown partition table.
More details on your boot and other pertinent information can be obtained by running the bootinfoscript downloaded from the site below and posting the results.txt file. http://sourceforge.net/projects/bootinfoscript/
hexdump: /dev/sda1: No such file or directory
hexdump: stdin: Bad file descriptor.
hexdump: /dev/sda1: No such file or directory
hexdump: /dev/sda1: Bad file descriptor
One or more specified logical volume(s) not found.
One or more specified logical volume(s) not found.
One or more specified logical volume(s) not found.
hexdump: /dev/mapper/vg_backup-lv_root': No such file or directory
hexdump: stdin: Bad file descriptor.
hexdump: /dev/mapper/vg_backup-lv_root': No such file or directory
hexdump: /dev/mapper/vg_backup-lv_root': Bad file descriptor
One or more specified logical volume(s) not found.
One or more specified logical volume(s) not found.
One or more specified logical volume(s) not found.
hexdump: /dev/mapper/vg_backup-lv_home': No such file or directory
hexdump: stdin: Bad file descriptor.
hexdump: /dev/mapper/vg_backup-lv_home': No such file or directory
hexdump: /dev/mapper/vg_backup-lv_home': Bad file descriptor
One or more specified logical volume(s) not found.
One or more specified logical volume(s) not found.
One or more specified logical volume(s) not found.
hexdump: /dev/mapper/vg_backup-lv_swap': No such file or directory
hexdump: stdin: Bad file descriptor.
hexdump: /dev/mapper/vg_backup-lv_swap': No such file or directory
hexdump: /dev/mapper/vg_backup-lv_swap': Bad file descriptor
mdadm: No arrays found in config file or automatically
---------- Post added 10-20-14 at 01:25 PM ----------
Bootinfo Script Results:
Boot Info Script 0.61 [1 April 2012]
============================= Boot Info Summary: ===============================
=> No boot loader is installed in the MBR of /dev/sda.
hexdump: /dev/sda1: No such file or directory
hexdump: stdin: Bad file descriptor.
hexdump: /dev/sda1: No such file or directory
hexdump: /dev/sda1: Bad file descriptor
One or more specified logical volume(s) not found.
One or more specified logical volume(s) not found.
One or more specified logical volume(s) not found.
hexdump: /dev/mapper/vg_backup-lv_root': No such file or directory
hexdump: stdin: Bad file descriptor.
hexdump: /dev/mapper/vg_backup-lv_root': No such file or directory
hexdump: /dev/mapper/vg_backup-lv_root': Bad file descriptor
One or more specified logical volume(s) not found.
One or more specified logical volume(s) not found.
One or more specified logical volume(s) not found.
hexdump: /dev/mapper/vg_backup-lv_home': No such file or directory
hexdump: stdin: Bad file descriptor.
hexdump: /dev/mapper/vg_backup-lv_home': No such file or directory
hexdump: /dev/mapper/vg_backup-lv_home': Bad file descriptor
One or more specified logical volume(s) not found.
One or more specified logical volume(s) not found.
One or more specified logical volume(s) not found.
hexdump: /dev/mapper/vg_backup-lv_swap': No such file or directory
hexdump: stdin: Bad file descriptor.
hexdump: /dev/mapper/vg_backup-lv_swap': No such file or directory
hexdump: /dev/mapper/vg_backup-lv_swap': Bad file descriptor
mdadm: No arrays found in config file or automatically
I'm surprised that sda1 id "unknown filesystem" as that should be a separate boot partition. My understanding is that if you are using GPT with a UEFI system, you need a separate EFI partition and if you are using it without EFI, you need Grub in the MBR and a separate BIOS boot partition. I don't use UEFI boot and am not familiar with LVM so hopefully someone else will come along.
Not booting from it. This is a HP proliant server with a smart array (cciss) with an internal array. The sda1 is the removable USB drive which is gpt partition table and formated with ext4 fs. Problem is I can't access it now for whatever reason and I'm not sure why.
Not entirely new to Linux but this is likely a newbie question for most of you other gurus out there. I have a 3TB USB drive for which I had used gparted and changed it to GPT and then had formated it ext4. I had gone through the work of finding out how to properly align it however the command that I used slips my mind right now. I know that I did properly align it when I used gparted. That being said, I used blkid to find the UUID of the volume and added a line to /etc/fstab to mount it on startup. Everything was working great. I had an issue that I had to reboot the machine for and I got a failure with fsck trying to check that volume (I had put a 2 in the 6th field of the fstab which I probably should have put a 0) so I got the system booted by appending fastboot to the grub line so it wouldn't try to check the volume. I edited /etc/fstab and changed the 2 to a 0 and now the system boots.
All that to say that when the system boots it will not mount the volume. /dev/sda1 does not exist in the /dev directory and looking at dmesg I'm seeing sda: unknown partition table.
The only thing that I changed was the last 0 in the 6th field position on the last line... it was 2 instead of 0 in which it makes fsck check the filesystem upon boot. The error that it gave is it couldn't locate the filesystem with that UUID so fsck failed and hence halted the boot process.
Since that UUID doesn't exist that line will do nothing.
I think this problem is more circling around the issue that the drive is GPT and the partition is > 2TB.
[root@backup ~]# parted /dev/sda
Warning: Device /dev/sda has a logical sector size of 4096. Not all parts of GNU Parted support this at the moment, and the working code is HIGHLY EXPERIMENTAL.
I get this message when going into Parted. When trying to print the partition table I get:
(parted) p
Error: /dev/sda: unrecognised disk label
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.