Asked 9 years, 11 months ago. Active 5 years, 5 months ago. Viewed 59k times. And why can I mount both? Any resources or color you can give would be greatly appreciated. Thank you in advance.
Improve this question. IgnacioVazquez-Abrams: I don't really have a citation. I mounted both on a Debian box, and I could write and read to both. Don't know why.
Not really a hardware or sysadmin guy, which is why I was asking for clarification. Thanks again to everyone for helping! Add a comment. Active Oldest Votes. On a modern system, a partition device will only appear if the partition actually exists. If the disk has no partition table, then it'll have no partition devices, of course. Improve this answer. Wyzard Wyzard 1, 6 6 silver badges 13 13 bronze badges.
You can have a filesystem directly on the disk itself, without a partition table. A removable device configured that way is sometimes referred to as a "superfloppy", since floppy disks typically weren't partitioned. Excellent point. Ah, partition tables and device names. Get ready to get confused with them. Have an old desktop computer with old IDE interface? The disk names in Linux are alphabetical.
So, sda means the first SCSI hard disk. The first hard drive detected by a Linux system carries the sda label. In numerical terms, it is hard drive 0 zero; counting begins from 0, not 1.
The second hard drive is sdb, the third drive, sdc, etc. In the screenshot below, there are two hard drives detected by the installer — sda and sdb. To find out the name of your attached USB drive, run sudo fdisk -l. In the output above, my external USB drive is sdb and has the partition sdb1. Linux Devices. These files are called device files and behave unlike ordinary files. If it is Linux Related and doesn't seem to fit in any other forum then this is the place. So then my Grub menu appears.
Sometimes, I get lucky and I can just press Return and my Linux installation will load straight away. Other times, there's problems with drive designations sda VS sdb VS sdc.
For instance, recently I hooked up my hard disk via USB to a computer. My Grub menu appeared and I hit Return The problem was that the computer's own internal hard disk was designated as sda , and my own hard disk was designated as sdb.
Therefore when Linux booted up, it was looking for data on the wrong hard disk because the Grub entry specified "root" as sd a 3. Even though I had to change the Grub entry for "kernel", I didn't have to change the following entry at all: Code: root hd0, I might have expected to have to change this to hd1,2.
So when Linux initially began to load, the USB hard disk was designated as sdb , and the computer's internal hard drive was sda. However, once my Linux installation had actually loaded up fully, I found that the USB hard disk was now sda , and the internal hard disk had changed to sdb??? At first I didn't think this was too big a deal.
Here's a few questions that come to mind: 1 Would it not make a hell of a lot of sense to always designate the "current hard disk" as sda by "current hard disk", I mean the one which is being booted off? Why isn't Linux like this by default? If so then I could manually select my own hard disk to be sda. View Public Profile. View Review Entries. Find More Posts by Virchanza.
View LQ Wiki Contributions. Find More Posts by GlennsPref. Find More Posts by ronlau9. Posting Rules.
0コメント