Clean (re)install - Can't find partition on second drive
Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then 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.
Clean (re)install - Can't find partition on second drive
Erk!
I've (half) successfully installed debian (wheezy) on my media/file server, i.e it's on and half configured.
Problem is I seem to have lost my data disc*.
The system has a small (160Gb) harddisc for boot/OS/and stuff, and another pair of 2TB discs on a raid card.
I've definitely installed Wheezy on the right disc, but it's not seeing the other disc at all (only dev/sdb which is some removable flash card reader). It's there in the BIOS/boot menu, but that's it.
How do I remind/tell debian that there's data on the array, and then get it mounted and accessible?
*yes I did do a backup
Last edited by CrowbarHero; 03-31-2018 at 04:45 PM.
Reason: misleading info removed
when restarting from the bios (after checking a few settings) I occasionally get a FSCK error 2 (no such file or directory) screen, with some kinda busybox prompt. attempting to exit from this results in a crash requiring a hard reset.
on looking up this error it seems it might be related to INITRAMFS, which when I try to initramfs-update -u presents "possible missing firmware" errors.
I can boot into the raid card bios and the array is recognised there, but not in the main motherboard bios (I can't remember if it should be or not).
Am I missing some drivers? or is it a config problem at a lower level (i.e. during boot up).
I'm sure putting this lot together before wasn't this difficult!
Started it up this morning and it can't get beyond this initramfs thing. Most annoying. so no fdisk -l output for breakfast.
On reflection I think I might have gotten something wrong during the installation, as I adopted all the default settings, whereas in hindsight I think there was something regarding boot devices and the grub loader which might have needed more considered attention.
I will try re-installation, as I've not really installed much (/anything)
right, reinstall seemed to have worked, no errors on boot (I've left the bios alone this time). I took a few screenshots (old-school) during the install process of critical points so I've got a memory of what I've done.
This time I've used LVM rather than the default setting (no LVM) - it seems to have detected the raid array as it offered to format/install on it (no thanks!) so paraphrasing from the setup it's given me the following:
Code:
LVM VG Rosco-vg, LV root - 158.7GB Linux device-mapper (linear)
#1 158.7GB f ext4 /
LVM VG Rosco-vg, LV swap - 1.1GB Linux device-mapper (linear)
#1 1.1GB f swap swap
SCSI1 (0,0,0) (sda) - 2.0TB ATA MARVELL Raid V0
#1 primary 2.0TB ext3
SCSI9 (0,0,0) (sdb) - 160.0GB ATA SAMSUNG HD161GJ
#1 primary 254.8MB f ext2 /boot
#5 logical 159.8GB k lvm
SCSI12 (0,0,0) (sdd) - 31.5GB Kingston DataTraveler 2.0
The Samsung is the onboard boot/system drive, the Marvell is the SATA board/raid array and the Kingston Data traveler is the USB I install from.. Simples?
It asked if I wanted to put the GRUB boot loader on the master boot record, so I said yes as there's no other OS going on this. So it put it on /dev/sdb (the Samsung HD)
I reckon I've got this right now.
For the record, here's the fdisk -l output as root:
Code:
Disk /dev/sda: 1.8 TiB, 2000315023360 bytes, 3906865280 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: 0x00000000
Device Boot Start End Sectors Size Id Type
/dev/sda1 63 3906865279 3906865217 1.8T 83 Linux
Disk /dev/sdb: 149.1 GiB, 160041885696 bytes, 312581808 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: 0x41c75fdb
Device Boot Start End Sectors Size Id Type
/dev/sdb1 * 2048 499711 497664 243M 83 Linux
/dev/sdb2 501758 312580095 312078338 148.8G 5 Extended
/dev/sdb5 501760 312580095 312078336 148.8G 8e Linux LVM
Disk /dev/mapper/Rosco--vg-root: 147.8 GiB, 158716657664 bytes, 309993472 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/mapper/Rosco--vg-swap_1: 1016 MiB, 1065353216 bytes, 2080768 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
Now to get it mounted, and hope I've not wiped it in the process (no big deal, it's just going to take an age to restore the backup), but first the kids need their rice-krispies..
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
