LinuxQuestions.org
Visit Jeremy's Blog.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Hardware
User Name
Password
Linux - Hardware This forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?

Notices


Reply
  Search this Thread
Old 06-13-2021, 12:02 PM   #1
HannemanThrashKing
Member
 
Registered: Oct 2017
Location: Canada
Distribution: Ubuntu MATE
Posts: 35

Rep: Reputation: Disabled
Exclamation Hard drive Ubuntu can see but that my system doesn't see at boot anymore


Well I can't explain this, and this is rather annoying, it's an emptied 1TB drive, that is 5 years old, it's not about to die per diagnostics...which I can do once I boot in a live session, that drive was to install Ubuntu Mate on, but right now I got no space on any other drives, well I have an old 200gb WD drive that will just not die but it is only regular old SATA, not SATA 6gb/s like this one....which doesn't show up at boot where my ASUS mobo will not list it in the drives anymore all of a sudden, after a forced power-down of a live session by a power failure (I have a voltage protection power bar, a good one, and all is saying that my PSU is in top shape still (it's 4 years old).

How can Ubuntu see it and the system not? Which is bad, when I hit Delete to enter the mobo's bios or UEFI or whatever, it's not a "BIOS" I think, it's a fancy looking, mouse-using GUI that I get. I have to go in there so that my memory works at the speed it should. Anyways, in the list of drives, last time before I booted back, boot priority and such, it's not seen either.

I installed testdisk, which has always been quite the saviour when it came to hard drive issues, and all of a sudden, that whole drive I had partitioned as a Primary partition in ext4, testdisk tells me it not seen as wheter P or L, it's got a star next to it, so it lost it's Primary Partition tag I put on it with gParted. I know it doesn't have an MBR, but it should be listed in the drives at boot like all the others shouldn't it? I mean it also lists my Pioneer BD-R. It's always been seen as sdb but now it's sdd, because Ubuntu sees it!

I never saw such a crazy problem with a hard drive before, but I had testdisk write-in the information that it is a Primary partition and now I can't use the drive anymore because testdisk says I need to reboot it and I can't mount it no more, but it still sees it, I'll see what happens when I boot back.

I'll give you a peak of a terminal command to list all of my drives...internal and external :

Code:
sudo lshw -C disk
  *-disk                    
       description: SCSI Disk
       product: EZAZ-00GGJB0
       vendor: WDC WD20
       physical id: 0.0.0
       bus info: scsi@8:0.0.0
       logical name: /dev/sdf
       version: 0106
       serial: 00000000000000000000
       size: 1863GiB (2TB)
       capabilities: gpt-1.00 partitioned partitioned:gpt
       configuration: ansiversion=6 guid=b53648e4-c450-4e79-b448-f7fe152f8f9f logicalsectorsize=512 sectorsize=512
  *-disk
       description: SCSI Disk
       product: DataTraveler 3.0
       vendor: Kingston
       physical id: 0.0.0
       bus info: scsi@7:0.0.0
       logical name: /dev/sdc
       version: PMAP
       serial: EE03D85155E9
       size: 115GiB (124GB)
       capabilities: removable
       configuration: ansiversion=6 logicalsectorsize=512 sectorsize=512
     *-medium
          physical id: 0
          logical name: /dev/sdc
          size: 115GiB (124GB)
          capabilities: partitioned partitioned:dos
          configuration: signature=f844846e
  *-disk
       description: SCSI Disk
       product: Expansion
       vendor: Seagate
       physical id: 0.0.0
       bus info: scsi@6:0.0.0
       logical name: /dev/sdb
       version: 0708
       serial: NA8K6MSK
       size: 1863GiB (2TB)
       capabilities: partitioned partitioned:dos
       configuration: ansiversion=6 logicalsectorsize=512 sectorsize=512 signature=628822a0
  *-cdrom
       description: DVD-RAM writer
       product: BD-RW   BDR-209M
       vendor: PIONEER
       physical id: 0
       bus info: scsi@1:0.0.0
       logical name: /dev/cdrom
       logical name: /dev/cdrw
       logical name: /dev/dvd
       logical name: /dev/dvdrw
       logical name: /dev/sr0
       version: 1.50
       capabilities: removable audio cd-r cd-rw dvd dvd-r dvd-ram
       configuration: ansiversion=5 status=nodisc
  *-disk:0
       description: ATA Disk
       product: WDC WD2000JD-22H
       vendor: Western Digital
       physical id: 1
       bus info: scsi@3:0.0.0
       logical name: /dev/sda
       version: 2D08
       serial: WD-WCAL81786689
       size: 186GiB (200GB)
       capabilities: partitioned partitioned:dos
       configuration: ansiversion=5 logicalsectorsize=512 sectorsize=512 signature=00095704
  *-disk:1
       description: ATA Disk
       product: ST1000DM003-1CH1
       physical id: 2
       bus info: scsi@4:0.0.0
       logical name: /dev/sdd
       version: CC47
       serial: W1D45DY8
       size: 931GiB (1TB)
       capabilities: partitioned partitioned:dos
       configuration: ansiversion=5 logicalsectorsize=512 sectorsize=4096 signature=d88eb14d
  *-disk:2
       description: ATA Disk
       product: WDC WD10EFRX-68J
       vendor: Western Digital
       physical id: 3
       bus info: scsi@5:0.0.0
       logical name: /dev/sde
       version: 1A01
       serial: WD-WCC1U0505191
       size: 931GiB (1TB)
       capabilities: partitioned partitioned:dos
       configuration: ansiversion=5 logicalsectorsize=512 sectorsize=4096 signature=000ee848
  *-disk
       description: SCSI Disk
       product: Expansion
       vendor: Seagate
       physical id: 0.0.0
       bus info: scsi@9:0.0.0
       logical name: /dev/sdg
       version: 1805
       serial: NA87MBQP
       size: 931GiB (1TB)
       capabilities: partitioned partitioned:dos
       configuration: ansiversion=6 logicalsectorsize=512 sectorsize=4096 signature=000b3352
It's this one : ST1000DM003-1CH1. Disks info tells me things about pre-fail in some cases, but it does with almost anything older than a year, the undying 200gb drive could be used, but, I already don't have SSD's (internally) as you can see, so I'm not gonna be slowing things down by not using a 6gb/s drive like that Seagate drive, the eternal 200gb WD from 2005 is fine for storage, I've seen 2 hard drives die after that one, they don't make em like they used to when there was more than 2 good companies making hdds and there was no quality levels/colour levels.

Anyways, if I don't see it at reboot in the drive list on the first screen where memory,keyboards, mouses, hubs, external drives and internal drives are listed and where I can press Delete to get into the gui....you tell me what it is BIOS or UEFI, the motherboard is this model :

ASUSTeK model: M5A97 LE R2.0 v: Rev 1.xx
serial: <superuser/root required> UEFI: American Megatrends v: 2701
date: 03/24/2016

Which is the last firmware update version (03/24/2016), I bought it in 2017 so I only had to apply it once easily back when I still dual-booted (when win7 wasn't dead).

The only thing bothering me is that Disks sees 78 bad blocks which is more than all other drives, where it's 20 tops on the old 200gb WD and none on the others.

I will update this post after I had a reboot, but now that I have a live session going on the 256gb usb key and everything is setup as I like it, I usually just use it this way (except for last week when I was ready to finally install it permanently, ubuntu mate 20.04 that is, the kernel the usb key loads must be getting old). But if anybody has an idea of how in the **** my motherboard itself claims the Seagate internal drive isn't there anymore but Ubuntu not only sees it, but can mount it, have files copied to it etc, even though there were no longer any flags on it, I'd like to know. Also, seems like lba flag should be checked right? Otherwise I'm stumped here, but I wanted to use it to install 20.04 and be done with always-overdue-to-crash live sessions or the annoying power failures we've been experiencing so often around here since the last few years, that often "brownout", as in, it comes back right when it cuts but then fails again which is bad when I forget to turn off the PSU even with a voltage variation protection power bar, I hear.

Sorry if the post is a bit long, I don't want details to be missed and getting questions about things I didn't ask about so I provided everything I could here.

Have a good day everyone! Stay safe from the bug, everyone imagines it's practically gone during the summer, but that's when I got it last year, wasn't too bad, just going on and on...like this post, lol.
 
Old 06-13-2021, 02:14 PM   #2
colorpurple21859
LQ Veteran
 
Registered: Jan 2008
Location: florida panhandle
Distribution: Slackware Debian, Fedora, others
Posts: 7,765

Rep: Reputation: 1677Reputation: 1677Reputation: 1677Reputation: 1677Reputation: 1677Reputation: 1677Reputation: 1677Reputation: 1677Reputation: 1677Reputation: 1677Reputation: 1677
Post the output of
Code:
sudo parted -l
Edit: Fixed the missing space

Last edited by colorpurple21859; 06-13-2021 at 06:43 PM.
 
Old 06-13-2021, 02:41 PM   #3
!!!
Member
 
Registered: Jan 2017
Location: Fremont, CA, USA
Distribution: Trying any&ALL on old/minimal
Posts: 997

Rep: Reputation: 383Reputation: 383Reputation: 383Reputation: 383
A space before the -l, of course.

Might this be relevant?
https://www.asus.com/us/support/FAQ/1044083/
(Cannot find the hard disk drive)

Last edited by !!!; 06-13-2021 at 02:43 PM.
 
Old 06-13-2021, 11:52 PM   #4
computersavvy
Senior Member
 
Registered: Aug 2016
Posts: 3,345

Rep: Reputation: 1486Reputation: 1486Reputation: 1486Reputation: 1486Reputation: 1486Reputation: 1486Reputation: 1486Reputation: 1486Reputation: 1486Reputation: 1486
You are saying that Ubuntu can see the drive but your UEFI bios cannot. That really makes sense because the OS is able to configure and make bare devices available, while the bios cannot make the drive available unless it has an OS installed (you cannot put it into the boot list, nor select it to boot from).

Anyway, the earlier request for the output of "sudo fdisk -l" will tell the whole story about that.
 
Old 06-14-2021, 10:19 AM   #5
HannemanThrashKing
Member
 
Registered: Oct 2017
Location: Canada
Distribution: Ubuntu MATE
Posts: 35

Original Poster
Rep: Reputation: Disabled
I just woke up and will do this command in a bit, but I have to put emphasis that on the black and white boot screen, the mobo always lists all of the drives connected to it, bootable or not, it even lists a drive shared on LAN on my other computers (which are less powerful than this one, it is my main desktop). That is before entering the UEFI. It always has done so and in the UEFI, I could put first in the list of bootable drives a drive that has nothing but data and no OS, and if I disabled all other drives from boot sequence, well, I'd get a black screen telling me there's no bootable drive. I'm afraid that my mobo (the weakest link in all of this, I got it because I don't need wifi and it has a lot of usb 2.0 ports, even has 6 others that are not accessible in the back for a total of 18, I bought a floppy bay with 4 2.0 usb to take advantage of that, unfortunate it only had 2 usb 3.0 ports, so I bought an external hub with on/off switches for those external seagate SSD drives, because they couldn't be turned off otherwise, for a total of 6.

My CPU is in excellent shape, the large cooling tower over it is much better than the stock fan that came with it (AMDFX-8350 Black Edition octocore overclocked slightly from 4ghz to 4.2ghz). Thankfully the hub for the externals, plus the dock for mechanical HDD's (which is seen as an internal drive by the system/linux, and I can hot swap and all, if I had another drive I could buy right now I would not worry and just install Ubuntu Mate on a drive and stick in the dock, but money is tight until my next pay, I miss being paid weekly I can tell that) have their own power source so I'm giving the PSU a break from all those add-ons.

I'll do what I have to do in meatspace then give you the results of that fdisk command, for those who think it will help. I'm more worried with the motherboard not listing the drive at boot, like it does with all drives, bootable or not. It's happened before with this particular Seagate 1Tb 6gb/s internal HDD, but I just pressed reset and it was back in the list, I must put emphasis that this is the boot screen, where it lists everything connected to the mobo pretty much, if it's not seen there, it doesn't show up in the UEFI BIOS. I know there's another screen in the UEFI other than the boot sequence menu regarding hard drives, but it's been so long I had to play around in there that I forgot, but I doubt it can be seen by it if it's not listed in the Internal Drives list on the "welcome" screen.

Take this into consideration, I'll give the output of this comment in a few hours, I'm watching my recorded Isles game (I know they won, but still, I didn't see it) in my bed right now and this is the first day of paid vacation out of 5 paid off weeks, I'm taking it easy right now

Last edited by HannemanThrashKing; 06-15-2021 at 08:06 AM.
 
Old 06-15-2021, 08:21 AM   #6
HannemanThrashKing
Member
 
Registered: Oct 2017
Location: Canada
Distribution: Ubuntu MATE
Posts: 35

Original Poster
Rep: Reputation: Disabled
Here you go :

Quote:
sudo parted -l
Model: ATA WDC WD2000JD-22H (scsi)
Disk /dev/sda: 200GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags:

Number Start End Size Type File system Flags
1 1049kB 184GB 184GB primary ext4 boot
2 184GB 200GB 15.6GB extended
5 184GB 200GB 15.6GB logical linux-swap(v1)


Model: Seagate Expansion (scsi)
Disk /dev/sdb: 2000GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags:

Number Start End Size Type File system Flags
1 32.8kB 2000GB 2000GB primary ntfs


Model: Kingston DataTraveler 3.0 (scsi)
Disk /dev/sdc: 124GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags:

Number Start End Size Type File system Flags
1 1049kB 124GB 124GB primary fat32 boot


Model: ATA ST1000DM003-1CH1 (scsi)
Disk /dev/sdd: 1000GB
Sector size (logical/physical): 512B/4096B
Partition Table: msdos
Disk Flags:

Number Start End Size Type File system Flags
1 1049kB 1000GB 1000GB primary ext4


Model: ATA WDC WD10EFRX-68J (scsi)
Disk /dev/sde: 1000GB
Sector size (logical/physical): 512B/4096B
Partition Table: msdos
Disk Flags:

Number Start End Size Type File system Flags
1 1049kB 211GB 211GB primary ntfs
2 211GB 433GB 223GB primary ext4
3 433GB 1000GB 567GB primary ntfs


Model: WDC WD20 EZAZ-00GGJB0 (scsi)
Disk /dev/sdf: 2000GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags:

Number Start End Size File system Name Flags
1 1049kB 2000GB 2000GB ntfs msftdata


Model: Seagate Expansion (scsi)
Disk /dev/sdg: 1000GB
Sector size (logical/physical): 512B/4096B
Partition Table: msdos
Disk Flags:

Number Start End Size Type File system Flags
1 1049kB 1000GB 1000GB primary ntfs
I see only the mechanical HDD in the hot-swap dock is formatted to GPT and the others msdos...I never knew what the difference was later on, but it never made a difference. I only remember formatting it that way because it was the newest thing, I kinda have a knowledge gap from when UEFI/EFI and GPT showed up, at the time I had a great PC that was built to be relevant for 10 years, the mobo died after 8. Now I know more, the desktop on which I have win10 on is in RAID mode with 2 hard drives showing only as one drive and not double capacity, never messed around with RAID much since way back when I learned what it was, you required identical drives for it to work and I never got around to this until I built that other one for my s/o.

I haven't rebooted yet, I really hate rebooting when I'm running from a usb stick a live session. BTW this might indicate that there is an OS installed on sda, the undying 200GB WD I keep in it for amusement purposes mostly, I don't put anything I don't want to lose on it, but I bet I could, they don't make em as sturdy as they used to...but it's Linux Mint 17.3 on it, way past its time, I don't even remember the password I used for it, just so you know I'm aware of that, I never really even mount that drive, I should just buy a new one and replace it, but the 2 6gb/s sata ports are taken, although that Seagate 1tb drive that's giving me trouble might just have to be removed if it's getting undetected like this and seemingly nothing can be done about it....I'll see what happens on the next reboot and see what Testdisk's partition modification from nothing (it wasn't nothing to start with, with is troubling) to Primary will have done anything.

Hope this is useful, but it just gives the same kind of info in a different manner, looks like, oh and it lists partitions..:shrug:
 
Old 06-15-2021, 10:38 AM   #7
colorpurple21859
LQ Veteran
 
Registered: Jan 2008
Location: florida panhandle
Distribution: Slackware Debian, Fedora, others
Posts: 7,765

Rep: Reputation: 1677Reputation: 1677Reputation: 1677Reputation: 1677Reputation: 1677Reputation: 1677Reputation: 1677Reputation: 1677Reputation: 1677Reputation: 1677Reputation: 1677
For a uefi system to see a gpt drive as bootable, needs an efi fat32 partition flagged as esp with an uefi bootloader installed to the efi partition. You can't mix legacy booting with efi booting with grub bootloader. A gpt drive can be setup to boot in legacy mode with a linux bootloader, but I don't think it can be done with windows bootloader.

Last edited by colorpurple21859; 06-15-2021 at 10:42 AM.
 
Old 06-17-2021, 02:32 PM   #8
HannemanThrashKing
Member
 
Registered: Oct 2017
Location: Canada
Distribution: Ubuntu MATE
Posts: 35

Original Poster
Rep: Reputation: Disabled
The "windows bootloader" is overriden by the old install of Linux Mint 17.3. The partition it's on has been entirely stripped of Windows content, you can't boot it. It doesn't matter. What matters is that the 1TB internal Seagate is no longer listed in the disk list at boot, which lists all of them, a section with the externals and a section with the internals on the first black and white screen with the memory and all that. I was wondering about gpt because I knew it was the newest thing when I bought my latest hard drive, the 2TB WD that's detected as USB but internal, that's because it's in a hdd dock, I formatted it this way because I think it's better to have them this way if you can these days?

Like I said, it lists all the drives at boot, before the grub screen, which I never see anyways since I boot on the grub menu of my usb stick with 20.04 on it. Now it's not seen there, and it lists all connected drives, whether they are bootable or not. After that power failure a few days before I posted here, it was still showing. That's the drive I was procrastinating on installing 20.04 permanently on it so I can have the kernel updates and get on with a setup that doesn't have to be reconfigured everytime the system shuts down for some reason. But now it isn't seen by the motherboard, which is bad. But it's seen by Ubuntu Mate (!). So maybe it isn't a lost cause. I am worried of the 80 or so bad blocks reported by Disks on it. But if it was something weird like it losing its Primary flag, which I corrected with Testdisk....I'll see at reboot.

If there's nothing else relevant that can be discussed until then, so be it, I'll give an update next time I feel masochistic and reboot...I just hope it isn't dead yet, it's not that old at all, but if it messes up again, I'm taking it out and putting it in another desktop to see what happens and if it's still not see by motherboard software, it's no good to try and install an OS on it, I'll be getting some cheap 1TB drive at 6gb/s 7200, there's always some model sold for dirt cheap on newegg. But I'd rather not, I can tell you that, especially with all the work it took to archive what was on that drive before I cleaned it up to make it an "OS only" drive to finally install 20.04 on it.

I'll read a little bit about gpt, even if its not directly relevant to the discussion. I know it's the preferred formatting method these days, but I never really had to know why and didn't format my drives when they are all 3/4 full, moving data around wasn't easy, the trusty usb dock (it could be eSATA too, but I haven't tried it, apparently usb 3.0 is faster) drive is still only half full, but I refuse to interchange it with the problematic Seagate, this 2TB WD is for data only and there's plenty on it, more than the mere 1TB Seagate can even bear.

Anybody with an idea, other than unplug and plug back the power and sata cables...it's already not very necessary in these days to do that, more so back with IDE and the grey licorice, so I won't bother with that.

Have a good evening everyone!
 
Old 06-17-2021, 04:23 PM   #9
michaelk
Moderator
 
Registered: Aug 2002
Posts: 26,511

Rep: Reputation: 6223Reputation: 6223Reputation: 6223Reputation: 6223Reputation: 6223Reputation: 6223Reputation: 6223Reputation: 6223Reputation: 6223Reputation: 6223Reputation: 6223
My experience with UEFI is a bit limited but here is my SWAG.

The EFI boot manager saves it settings in NVRAM and for some reason whether or not it was due to a power interruption, surge or something else the drive was removed from the table or whatever. You should be able to fix it using efibootmgr but I am not familiar enough to post the exact steps.

https://wiki.archlinux.org/title/Uni...ware_Interface

linux sees the drive because it does its own hardware probe during the boot process independent of the UEFI.
 
Old 06-17-2021, 06:59 PM   #10
HannemanThrashKing
Member
 
Registered: Oct 2017
Location: Canada
Distribution: Ubuntu MATE
Posts: 35

Original Poster
Rep: Reputation: Disabled
Thanks, that's a step forward

I'll see what happens when I reboot with Testdisk's change to the drive, adding the P flag for Primary, which apparently was gone. If that fails, I'll look into this and give you feedback.

Have a nice evening/day.
 
Old 06-18-2021, 03:01 PM   #11
computersavvy
Senior Member
 
Registered: Aug 2016
Posts: 3,345

Rep: Reputation: 1486Reputation: 1486Reputation: 1486Reputation: 1486Reputation: 1486Reputation: 1486Reputation: 1486Reputation: 1486Reputation: 1486Reputation: 1486
Just one more comment about uefi and disk partitioning.

A drive that has the 'old' msdos partitioning (which has existed since at least the 70s) that uses MBR booting cannot be used for uefi booting. If you intend to use UEFI booting the drive has to have a gpt partition table so the boot loader is not located in the (extremely) limited size mbr.

What this means is that for your 3 seagate drives you posted in the output of fdisk -l you will never be able to use them for boot drives using UEFI until they are re-partitioned in the gpt format, although they will likely still work quite well using the legacy (MBR) booting.
 
Old 06-18-2021, 05:22 PM   #12
colorpurple21859
LQ Veteran
 
Registered: Jan 2008
Location: florida panhandle
Distribution: Slackware Debian, Fedora, others
Posts: 7,765

Rep: Reputation: 1677Reputation: 1677Reputation: 1677Reputation: 1677Reputation: 1677Reputation: 1677Reputation: 1677Reputation: 1677Reputation: 1677Reputation: 1677Reputation: 1677
Quote:
Model: WDC WD20 EZAZ-00GGJB0 (scsi)
Disk /dev/sdf: 2000GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags:

Number Start End Size File system Name Flags
1 1049kB 2000GB 2000GB ntfs msftdata
If this is the drive your referring to that doesn't show up as a boot option, in uefi mode a gpt disk requires a fat32 efi partition with a efi bootloader to be considered as a boot option, in legacy/csm mode there will need to be a bootloader in the protective mbr. I think some firmware/bios don't considered a gpt disk as a boot option in legacy/csm. It maybe possible that if the boot flag is set on the gpt protective mbr partition the firmware/bios may see it as a bootable drive in legacy/csm mode.

Most uefi systems will look for an EFI/Boot/bootx64.efi boot file in the efi partition if nothing is listed in nvram.

Last edited by colorpurple21859; 06-18-2021 at 05:32 PM.
 
Old 06-19-2021, 11:01 PM   #13
HannemanThrashKing
Member
 
Registered: Oct 2017
Location: Canada
Distribution: Ubuntu MATE
Posts: 35

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by colorpurple21859 View Post
If this is the drive your referring to that doesn't show up as a boot option, in uefi mode a gpt disk requires a fat32 efi partition with a efi bootloader to be considered as a boot option, in legacy/csm mode there will need to be a bootloader in the protective mbr. I think some firmware/bios don't considered a gpt disk as a boot option in legacy/csm. It maybe possible that if the boot flag is set on the gpt protective mbr partition the firmware/bios may see it as a bootable drive in legacy/csm mode.

Most uefi systems will look for an EFI/Boot/bootx64.efi boot file in the efi partition if nothing is listed in nvram.
No it's not this one, that's a drive in a usb/e-SATA III dock.Using usb 3.0 mode, I hear e-SATA III is slower plus I'd have to install the e-sata pci-e port.

It's sdd, a 1TB seagate drive. Anyways, I won't see what's what until I reboot, but I'm taking into account what computersavvy said.
 
  


Reply

Tags
bios, hard drive, motherboard, problem, ubuntu 20.04


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
Ubuntu Ultimate doesn't see DVD writer, but does see reader in VirtualBox joebpa Ubuntu 7 05-04-2012 02:56 PM
I want to copy my hard drive to a larger hard drive and boot from the new drive. lpmorgan1 Ubuntu 8 09-08-2009 12:26 AM
Ubuntu: Installed to external hard drive; boot to primary hard drive gives error 22 dcorb62 Linux - General 7 09-05-2007 12:28 AM
dual boot but can't see linux hard drive from XP battlezonehawk Linux - General 15 06-10-2007 04:01 PM
dual boot system doesn't show anymore kyttycat Linux - General 4 04-13-2004 05:37 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Hardware

All times are GMT -5. The time now is 03:34 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration