[arch-general] New install second drive issue
Morning folks I have just done a complete new install on a new drive , That is all working now fine . My problem comes when trying to include another drive on the system , it just refuses to boot fully , I get a message unable to mount sda2 now sda2 mounts , /dev/sda2 on / type xfs (rw,relatime,attr2,inode64,noquota) when just the one drive is in the system but as soon as i connect it refuses to to boot fully and drops out to an emergency shell that is locked up solid i. I have set the working drive in the bios this is an older motherboard with an AMD Phenome quad core CPU . $ lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:0 0 1.8T 0 disk ├─sda1 8:1 0 300M 0 part /boot ├─sda2 8:2 0 40G 0 part / ├─sda3 8:3 0 4G 0 part [SWAP] └─sda4 8:4 0 1.8T 0 part /home sr0 11:0 1 1024M 0 rom the drive order in the bios is set correctly not that it makes much difference these days . I am stuck right now i need to be able to include the old drive to recover data from it . Any ideas folks .. Pete .
On September 16, 2019 10:45:18 AM GMT+02:00, pete via arch-general <arch-general@archlinux.org> wrote:
Morning folks
I have just done a complete new install on a new drive , That is all working now fine .
My problem comes when trying to include another drive on the system , it just refuses to boot fully , I get a message unable to mount sda2 now sda2 mounts , /dev/sda2 on / type xfs (rw,relatime,attr2,inode64,noquota)
when just the one drive is in the system but as soon as i connect it refuses to to boot fully and drops out to an emergency shell that is locked up solid i.
I have set the working drive in the bios this is an older motherboard with an AMD Phenome quad core CPU .
$ lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:0 0 1.8T 0 disk ├─sda1 8:1 0 300M 0 part /boot ├─sda2 8:2 0 40G 0 part / ├─sda3 8:3 0 4G 0 part [SWAP] └─sda4 8:4 0 1.8T 0 part /home sr0 11:0 1 1024M 0 rom
the drive order in the bios is set correctly not that it makes much difference these days .
I am stuck right now i need to be able to include the old drive to recover data from it .
Any ideas folks ..
Pete .
Hi Pete, Can you add your fstab? I would hazard a guess and claim that if you use device names in fstab (sdXY) that your newly plugged in drive takes that name and isn't a valid rootfs. Preferably, you would use UUIDs in fstab. Regards, Khorne
On Mon, 16 Sep 2019 11:18:59 +0200 Khorne via arch-general <arch-general@archlinux.org> wrote:
On September 16, 2019 10:45:18 AM GMT+02:00, pete via arch-general <arch-general@archlinux.org> wrote:
Morning folks
I have just done a complete new install on a new drive , That is all working now fine .
My problem comes when trying to include another drive on the system , it just refuses to boot fully , I get a message unable to mount sda2 now sda2 mounts , /dev/sda2 on / type xfs (rw,relatime,attr2,inode64,noquota)
when just the one drive is in the system but as soon as i connect it refuses to to boot fully and drops out to an emergency shell that is locked up solid i.
I have set the working drive in the bios this is an older motherboard with an AMD Phenome quad core CPU .
$ lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:0 0 1.8T 0 disk ├─sda1 8:1 0 300M 0 part /boot ├─sda2 8:2 0 40G 0 part / ├─sda3 8:3 0 4G 0 part [SWAP] └─sda4 8:4 0 1.8T 0 part /home sr0 11:0 1 1024M 0 rom
the drive order in the bios is set correctly not that it makes much difference these days .
I am stuck right now i need to be able to include the old drive to recover data from it .
Any ideas folks ..
Pete .
Hi Pete,
Can you add your fstab? I would hazard a guess and claim that if you use device names in fstab (sdXY) that your newly plugged in drive takes that name and isn't a valid rootfs.
Preferably, you would use UUIDs in fstab.
Regards, Khorne
hi Fstab .. # /dev/sda2 UUID=318fa89a-22b9-4bdd-92a1-1e9b3f070cb3 / xfs rw,relatime,attr2,inode64,noquota 0 1 # /dev/sda1 UUID=78aca2f9-6dbd-4e21-9f4d-dae59b8c1a4f /boot ext2 rw,relatime 0 2 # /dev/sda4 UUID=b17ea3f0-c632-46b1-9c78-4f1aeb8773c7 /home xfs rw,relatime,attr2,inode64,noquota 0 2 # /dev/sda3 UUID=a755fa7c-93ff-4ccb-bcd6-47560bd54cee none swap defaults 0 0 Hope that helps . Thanks Pete .
Hi Ralph . No this was a total clean install the uuids were what was automatically generated . I cant make heads or tails of it right now . Last time i had anything like this was way back in the days of MFM and RLL drives . Pete On Mon, 16 Sep 2019, 11:55 pete, <pg.nikolic1@gmail.com> wrote:
On Mon, 16 Sep 2019 11:18:59 +0200 Khorne via arch-general <arch-general@archlinux.org> wrote:
On September 16, 2019 10:45:18 AM GMT+02:00, pete via arch-general <arch-general@archlinux.org> wrote:
Morning folks
I have just done a complete new install on a new drive , That is all working now fine .
My problem comes when trying to include another drive on the system , it just refuses to boot fully , I get a message unable to mount sda2 now sda2 mounts , /dev/sda2 on / type xfs (rw,relatime,attr2,inode64,noquota)
when just the one drive is in the system but as soon as i connect it refuses to to boot fully and drops out to an emergency shell that is locked up solid i.
I have set the working drive in the bios this is an older motherboard with an AMD Phenome quad core CPU .
$ lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:0 0 1.8T 0 disk ├─sda1 8:1 0 300M 0 part /boot ├─sda2 8:2 0 40G 0 part / ├─sda3 8:3 0 4G 0 part [SWAP] └─sda4 8:4 0 1.8T 0 part /home sr0 11:0 1 1024M 0 rom
the drive order in the bios is set correctly not that it makes much difference these days .
I am stuck right now i need to be able to include the old drive to recover data from it .
Any ideas folks ..
Pete .
Hi Pete,
Can you add your fstab? I would hazard a guess and claim that if you use device names in fstab (sdXY) that your newly plugged in drive takes that name and isn't a valid rootfs.
Preferably, you would use UUIDs in fstab.
Regards, Khorne
hi Fstab ..
# /dev/sda2 UUID=318fa89a-22b9-4bdd-92a1-1e9b3f070cb3 / xfs rw,relatime,attr2,inode64,noquota 0 1
# /dev/sda1 UUID=78aca2f9-6dbd-4e21-9f4d-dae59b8c1a4f /boot ext2 rw,relatime 0 2
# /dev/sda4 UUID=b17ea3f0-c632-46b1-9c78-4f1aeb8773c7 /home xfs rw,relatime,attr2,inode64,noquota 0 2
# /dev/sda3 UUID=a755fa7c-93ff-4ccb-bcd6-47560bd54cee none swap defaults 0 0
Hope that helps .
Thanks Pete .
On Monday, 16 September 2019 12:55:29 CEST pete via arch-general wrote:
On Mon, 16 Sep 2019 11:18:59 +0200
Khorne via arch-general <arch-general@archlinux.org> wrote:
On September 16, 2019 10:45:18 AM GMT+02:00, pete via arch-general
<arch-general@archlinux.org> wrote:
Morning folks
I have just done a complete new install on a new drive , That is all working now fine .
My problem comes when trying to include another drive on the system , it just refuses to boot fully , I get a message unable to mount sda2 [...] hi Fstab ..
# /dev/sda2 UUID=318fa89a-22b9-4bdd-92a1-1e9b3f070cb3 / xfs rw,relatime,attr2,inode64,noquota 0 1
# /dev/sda1 UUID=78aca2f9-6dbd-4e21-9f4d-dae59b8c1a4f /boot ext2 rw,relatime 0 2
# /dev/sda4 UUID=b17ea3f0-c632-46b1-9c78-4f1aeb8773c7 /home xfs rw,relatime,attr2,inode64,noquota 0 2
# /dev/sda3 UUID=a755fa7c-93ff-4ccb-bcd6-47560bd54cee none swap defaults 0 0
Perhaps there is an entry, or a missing entry, in grubs configuration file. Have you tried to use /dev/sda2 instead of the UUID in /etc/fstab? Do you know if the other drive does work? I have seen an SSD that had failed and when installed into another machine to see just if it might work, the computer wouldn't boot at all.
What tool is being used to boot (grub, refind, etc)? Should we assume this is UEFI? And if so, what are UEFI Bios settings possibly relevant (like a boot manager setting for example which "can" choose disks oher than your preference).
Hi Pete,
I am stuck right now i need to be able to include the old drive to recover data from it.
When you installed on the new drive, did you attempt to reuse UUIDs, labels, etc., from the old drive? -- Cheers, Ralph.
Op ma 16 sep. 2019 10:45 schreef pete via arch-general < arch-general@archlinux.org>:
Morning folks
I have just done a complete new install on a new drive , That is all working now fine .
My problem comes when trying to include another drive on the system , it just refuses to boot fully , I get a message unable to mount sda2 now sda2 mounts , /dev/sda2 on / type xfs (rw,relatime,attr2,inode64,noquota)
Hmm, sda2 should be on disk1, but xfs uses UUID's also (I think). Could it be an UUID conflict? Can you attach that 2nd drive another way, like in an USB enclosure or even another PC? Mvg, Guus
On Mon, 16 Sep 2019 19:11:48 +0200 Guus Snijders via arch-general <arch-general@archlinux.org> wrote:
Op ma 16 sep. 2019 10:45 schreef pete via arch-general < arch-general@archlinux.org>:
Morning folks
I have just done a complete new install on a new drive , That is all working now fine .
My problem comes when trying to include another drive on the system , it just refuses to boot fully , I get a message unable to mount sda2 now sda2 mounts , /dev/sda2 on / type xfs (rw,relatime,attr2,inode64,noquota)
Hmm, sda2 should be on disk1, but xfs uses UUID's also (I think). Could it be an UUID conflict?
Can you attach that 2nd drive another way, like in an USB enclosure or even another PC?
Mvg, Guus
Hi Folks Well just to fill in a few bit .. I use syslinux to boot the machine no Windows no UEFI the system is too old for that . BUT any how i have solved the problem and its the one i did not want to find 3 of the 4 sata ports on the mother board are shot 1 works fine port 4 port 3 throws up errors ports 2 and 1 just cause the boot problem so i will be need to replace the mother board shame because the CPU is fin AMD Phenom II quad core so need a replacement board to suit . Thanks for all the help anyways folks Pete . now not an appy bunny ho humm
participants (7)
-
Genes Lists
-
Guus Snijders
-
Khorne
-
lee＠yun.yagibdah.de
-
pete
-
Pete Nikolic
-
Ralph Corderoy